emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Derek Chen-Becker <derek@chen-becker.org>,
	 Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Re: Contributing (looking for good first issues to tackle)
Date: Sun, 15 Dec 2024 11:10:40 +0100	[thread overview]
Message-ID: <871py9cl3z.fsf@bzg.fr> (raw)
In-Reply-To: <87y10nwhc4.fsf@localhost> (Ihor Radchenko's message of "Tue, 10 Dec 2024 17:58:19 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> Woof! is the way to track issues, at least eventually.

My goal for 2025 is to rewrite Woof! to make it more useful and using
it for Org is a great opportunity for that.

See https://github.com/bzg/woof?tab=readme-ov-file#planning-a-rewrite

> Woof! is still in early development, and we have an annoying bug there
> causing some issues to remain open even after marking them closed.

Yes, this is annoying. It may happen when Woof! processes an email
that trigger an error and leave the whole application in an unstable
state (without crashing though).

>    Bastien, can we do something about it? This problem keeps confusing
>    potential contributors.

It is on top of my priorities to make Woof! more stable. 

For personal reasons, I'm not yet in a position to set a deadline for
this, but it's clearly in my mind.

> As you can see, marking things completed is just a bug in Woof that we
> should eventually solve. Woof! is written in Clojure and developed in
> https://sr.ht/~bzg/woof/. Probably it is not what you want. (Or, if you
> do, I am sure that Bastien will welcome contributions there.)

Woof! is now hosted on https://github.com/bzg/woof only - it was
confusing to host it on several places.

HTH,

-- 
 Bastien Guerry


  reply	other threads:[~2024-12-15 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10  6:41 Contributing (looking for good first issues to tackle) Derek Chen-Becker
2024-12-10 10:02 ` Dilip
2024-12-10 17:03   ` Derek Chen-Becker
2024-12-10 18:07     ` Ihor Radchenko
2024-12-10 19:14       ` Derek Chen-Becker
2024-12-13 17:30         ` Ihor Radchenko
2024-12-10 13:39 ` Russell Adams
2024-12-10 17:58 ` Ihor Radchenko
2024-12-15 10:10   ` Bastien Guerry [this message]
2024-12-15 10:33     ` Ihor Radchenko
2024-12-15 12:04       ` Bastien Guerry
2024-12-16 17:50         ` Ihor Radchenko
2024-12-16 18:41           ` Bastien Guerry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871py9cl3z.fsf@bzg.fr \
    --to=bzg@gnu.org \
    --cc=Emacs-orgmode@gnu.org \
    --cc=derek@chen-becker.org \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).