From: Bastien <bzg@gnu.org>
To: Mario Frasca <mario@anche.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: issue tracker?
Date: Sun, 07 Jun 2020 11:38:31 +0200 [thread overview]
Message-ID: <87v9k3nrl4.fsf@gnu.org> (raw)
In-Reply-To: <e95156d7-8e14-a4fd-ab01-738ae421d665@anche.no> (Mario Frasca's message of "Sat, 6 Jun 2020 11:15:28 -0500")
Hi Mario,
Mario Frasca <mario@anche.no> writes:
> very interesting approach.
Thanks for looking more closely into it.
> sounds like you don't want to manage the status changes a bit
> tighter. I know, I can check the code, but it's more practical if we
> mention it here explicitly. anybody can send status change emails?
Yes, anybody can confirm a bug and anybody can mark it as fixed.
> I mean, this is an open list, anybody who just knows how to put a
> header to an email can confirm a bug?
Yes. The pattern I've seen in the last 15 ten years is that someone
sends a bug report and 50% of the time it is not really possible to
reproduce the bug. And people who reproduce bugs are not always code
contributors, they can be "power users", so I think it's safe to allow
anyone to confirm a bug -- that's something that really helps.
> on the other hand, I never tried to add extra headers using
> thunderbird.
Yes, you can:
https://www.lifewire.com/arbitrary-custom-heading-email-thunderbird-1173089
> apart from the technical aspect, I would suggest: anybody can
> 'vote-for' a bug, and you keep a counter on voted-for.
It would require people to register on updates.orgmode.org.
I'm not sure the expected benefit is really worth it for now.
> but only a maintainer can 'confirm' (that fixing that bug is
> desirable).
I think it is important that anyone can confirm a bug.
> then
> we new contributors can choose which confirmed bug is easy enough for
> us to make an attempt. or which fits our interests and skills. or
> which has accumulated most votes, hasn't been rejected, so we can
> remind the maintainer.
>
> … if the "main focus" is recruiting, I would also suggest a category
> "good first issue".
I have seen "good first issues" in many repositories and I don't think
it is sufficient as a way to attract new contributors: those tags are
useful when you also actively organize the contribution and the
onboarding of new contributors.
Also, "good first issues" are often those we can fix very easily and
there is no good reason not to fix them.
That said, I would love to organize a hackathon for Org-mode where
people would gather online for one day, exchange ideas, break and fix
things, propose new features, etc. That is, IMHO, the way to recruit
new contributors, on top of simply formally asking "who would like to
be in charge of X, Y and Z?"
> I understand, not a bug "tracking" tool, but it sounds like it's able
> to shed some light in the dark.
Yes, I hope so!
--
Bastien
next prev parent reply other threads:[~2020-06-07 9:39 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 21:24 issue tracker? Anthony Carrico
2020-05-18 22:21 ` Nick Dokos
2020-05-18 23:13 ` James R Miller
2020-05-19 7:33 ` tomas
2020-05-19 14:02 ` James R Miller
2020-05-19 14:05 ` James R Miller
2020-05-19 14:53 ` tomas
2020-05-19 14:58 ` Bruce D'Arcus
2020-05-19 16:45 ` Timothy
2020-05-19 16:57 ` Russell Adams
2020-05-19 17:03 ` Timothy
2020-05-19 17:29 ` Russell Adams
2020-05-19 18:50 ` James R Miller
2020-05-19 19:42 ` Eric Abrahamsen
2020-05-19 20:17 ` Roland Everaert
2020-05-19 20:47 ` Diego Zamboni
2020-05-19 21:28 ` Eric Abrahamsen
2020-05-19 19:48 ` Russell Adams
2020-05-19 20:14 ` Trey Ethan Harris
2020-05-19 20:57 ` gyro funch
2020-05-19 23:22 ` James R Miller
2020-05-20 9:22 ` Eric S Fraga
2020-05-20 9:40 ` Detlef Steuer
2020-05-20 11:12 ` Stefan Nobis
2020-05-20 16:41 ` Jud Taylor
2020-05-20 18:55 ` gennady.uraltsev
2020-05-20 22:05 ` Bob Newell
2020-05-21 8:10 ` Nicolas Goaziou
2020-05-21 11:21 ` Bruce D'Arcus
2020-05-21 14:46 ` Kévin Le Gouguec
2020-05-21 16:31 ` Eric Abrahamsen
2020-05-22 8:17 ` Roland Everaert
2020-05-22 14:53 ` Anthony Carrico
2020-05-23 12:57 ` Roland Everaert
2020-05-23 13:14 ` Russell Adams
2020-05-25 11:20 ` Roland Everaert
2020-05-26 12:34 ` Robert Pluim
2020-06-01 14:40 ` Bastien
2020-06-01 14:36 ` Bastien
2020-05-26 19:17 ` Matthew Lundin
2020-06-01 14:43 ` Bastien
2020-05-27 17:59 ` Mario Frasca
2020-05-27 18:12 ` Russell Adams
2020-05-27 18:48 ` Eric Abrahamsen
2020-05-31 8:49 ` Russell Adams
2020-06-01 14:45 ` Bastien
2020-06-01 15:46 ` Mario Frasca
2020-06-01 15:53 ` Bastien
2020-06-01 16:28 ` Mario Frasca
2020-06-01 16:54 ` Russell Adams
2020-06-02 11:57 ` Bastien
2020-06-05 22:44 ` Mario Frasca
2020-06-06 7:57 ` Bastien
2020-06-06 16:15 ` Mario Frasca
2020-06-07 9:38 ` Bastien [this message]
2020-06-07 13:50 ` Mario Frasca
2020-06-08 9:11 ` Bastien
2020-05-21 2:35 ` Anthony Carrico
2020-05-21 3:12 ` James R Miller
2020-05-21 5:33 ` Russell Adams
2020-05-21 7:31 ` Kévin Le Gouguec
2020-05-21 14:18 ` Anthony Carrico
2020-05-21 14:38 ` tomas
2020-05-21 14:38 ` Anthony Carrico
2020-05-21 15:05 ` Kévin Le Gouguec
2020-05-22 16:56 ` Ken Mankoff
2020-05-26 19:36 ` Matthew Lundin
2020-06-01 14:59 ` Bastien
2020-09-14 5:23 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2020-06-02 11:38 Vladimir Nikishkin
2020-06-02 11:55 ` Bastien
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=87v9k3nrl4.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mario@anche.no \
/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).