From: Ihor Radchenko <yantar92@posteo.net>
To: Derek Chen-Becker <derek@chen-becker.org>
Cc: Emacs-orgmode <Emacs-orgmode@gnu.org>, bzg@gnu.org
Subject: Re: Contributing (looking for good first issues to tackle)
Date: Tue, 10 Dec 2024 17:58:19 +0000 [thread overview]
Message-ID: <87y10nwhc4.fsf@localhost> (raw)
In-Reply-To: <CAMbmz5mLirm80zfrz_pqy_R3FhAVVxbhKKbYjvpqE7T=1NL1Zw@mail.gmail.com>
Derek Chen-Becker <derek@chen-becker.org> writes:
> ... I took a look at https://orgmode.org/worg/org-contribute.html and
> https://tracker.orgmode.org/bugs but it's not clear to me if this is the
> actual way we track issues or if this is just fancy indexing of the
> mailing list (both?).
Thanks for your interest!
Woof! is the way to track issues, at least eventually.
It works by indexing the mailing list, so using Woof! simply saves you
from the noise of non-bug messages we get here.
You may also follow the whole mailing list if that's ok for you.
> ... Some of the bugs reported in the list already have a
> message stating that the issue is fixed, so I'm also a little confused
> about the consistency of the Woof index vs reality.
Woof! is still in early development, and we have an annoying bug there
causing some issues to remain open even after marking them closed.
Bastien, can we do something about it? This problem keeps confusing
potential contributors.
AFAIK, the new bug reports will consistently appear in the list. So, you
can take a look at the latest reports. They are likely to be unfixed.
You can also subscribe to see new bug reports via RSS:
https://tracker.orgmode.org/bugs.rss
> ... As a first task, maybe
> is there a way I could help triage things and mark completed
> requests/bugfixes in Woof? Or do we have a different way of tracking things?
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.)
For triaging the bugs, you can look at the bugs without any response and
the bugs without _my_ response. These are the bugs I did not triage yet.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-12-10 18:40 UTC|newest]
Thread overview: 7+ 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-10 13:39 ` Russell Adams
2024-12-10 17:58 ` Ihor Radchenko [this message]
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=87y10nwhc4.fsf@localhost \
--to=yantar92@posteo.net \
--cc=Emacs-orgmode@gnu.org \
--cc=bzg@gnu.org \
--cc=derek@chen-becker.org \
/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).