From: Timothy <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>
Subject: Contributor Steward role (was Re: Concerns about community contributor support)
Date: Sun, 25 Apr 2021 13:52:37 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Thank you for your well-thought-out reply.
With regards to the question your email ends with:
> What do you think? Would you be willing to take this role?
> If not, that's perfectly okay, I'll send a call for help.
The short answer is "yes, mostly". The long answer follows :P
I also think that regardless it would be good to put out a call asking
if anyone else is interested/willing to do this: I'm going to be busy
sometimes, a reduced workload is clearly preferable, and less should
slip through the cracks :)
Bastien <email@example.com> writes:
> Dear Timothy,
> thanks for raising this points so carefully, they are important.
> I see three distinct problems:
> A. The lack of response and/or follow-up when people contribute by
> sending bug reports or patches on the list.
This is something I'm definitely happy to help with.
> B. The lack of maintainance on documenting the contribution process
> and the correct expectations for future contributors.
I'm happy to document this, but I don't know what expectations should be
set. I think this is a matter that should be decided by consensus among
the current/active maintainers.
> C. The inherent difficulty to move the Org codebase forward.
I think there are some things that can be done to improve the structure
and system of contribution/development, but I'm waiting on external
developments and it will take a fair bit of my time to properly
implement a prototype. ETA 1-2 years.
> I won't comment on (C). For (A) and (B), I suggest appointing a
> "contributor steward" with these responsibilities:
> 1. Maintain updates.orgmode.org (i.e. make sure it is accurate.)
> 2. Maintain the documentation for contributors.
> 3. Help contributors enhancing their patches.
> 4. Try to reproduce bugs (and confirm them for updates.orgmode.org)
> 5. Make sure patch contributors are not left with no answer.
> You started (1), which is really appreciated.
I'll try to keep this up :)
> Tim and others mentioned (2), and that's certainly needed too.
See my comment on (B) above.
> (3) has historically been the role of the maintainer and of the core
> contributors, but helping with this is very welcome: knowing the doc
> at https://orgmode.org/worg/org-contribute.html by heart, educating
> contributors on the commit messages, etc. This all helps.
I can give this a go :)
> (4) is perhaps the most daunting task: I even think we could have
> someone only dedicated to this very important task. Just count the
> number of times Nicolas says "I cannot reproduce this." Each time,
> there is a real bug that is *not* fixed...
Mmmm, even if I say I'm willing to do this, I suspect this is something
I'd by nature push off enough that I'd frequently forget about this 😅.
> (5) is not about systematically welcome patch submitters with a
> message (that would be annoying) but to monitor updates.orgmode.org
> and decide what to do with a patch that didn't receive feedback:
> either say thanks and ping the list for why you think the patch
> deserves more attention, or thanks and dismiss the patch, or another
This is how I see this two. As I indicated at the start, I'm happy to do
this, but I think a second person would help ensure that nobody slips
through the cracks.
next prev parent reply other threads:[~2021-04-25 5:53 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 18:43 Concerns about community contributor support Timothy
2021-04-17 23:29 ` Thomas S. Dye
2021-04-18 1:56 ` Tim Cross
2021-04-18 19:39 ` Timothy
2021-04-18 22:45 ` Tim Cross
2021-04-19 21:43 ` David Masterson
2021-04-19 22:21 ` Gustav Wikström
2021-04-23 0:16 ` David Masterson
2021-04-19 23:46 ` Tim Cross
2021-04-20 8:21 ` Tom Gillespie
2021-04-23 0:34 ` David Masterson
2021-04-20 9:28 ` Jean Louis
2021-04-23 0:38 ` David Masterson
2021-04-18 5:04 ` Timothy
2021-04-18 18:45 ` Thomas S. Dye
2021-04-18 19:12 ` Timothy
2021-04-18 19:46 ` Thomas S. Dye
2021-04-18 19:59 ` Timothy
[not found] ` <a64adc3de7be49039372851ea31e4f7c@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-19 10:04 ` Eric S Fraga
2021-04-20 3:54 ` Timothy
2021-04-19 22:07 ` Gustav Wikström
2021-04-21 9:33 ` Jean Louis
2021-04-21 9:50 ` Tim Cross
2021-04-21 10:25 ` Heinz Tuechler
2021-04-21 12:55 ` ian martins
2021-04-21 13:07 ` Timothy
[not found] ` <1c557c0e35e04440ba2dadfe57e5b590@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-21 13:27 ` Eric S Fraga
2021-04-21 15:31 ` ian martins
2021-04-21 15:38 ` Bruce D'Arcus
2021-04-21 19:35 ` Tim Cross
2021-04-22 0:36 ` ian martins
2021-04-22 0:48 ` Tim Cross
2021-04-22 2:35 ` Timothy
2021-04-22 5:14 ` Maintaining babel packages — a list of packages that need help? Dr. Arne Babenhauserheide
2021-04-22 10:10 ` ian martins
2021-04-26 7:25 ` Bastien
2021-04-22 10:00 ` Concerns about community contributor support ian martins
2021-04-21 19:31 ` Tim Cross
2021-04-25 4:30 ` Bastien
2021-04-25 5:52 ` Timothy [this message]
2021-04-25 7:13 ` Contributor Steward role (was Re: Concerns about community contributor support) Bastien
2021-04-25 6:17 ` Concerns about community contributor support Tim Cross
2021-04-25 7:19 ` Bastien
2021-04-26 0:23 ` Tim Cross
2021-04-26 5:00 ` Bastien
2021-04-26 6:07 ` Tim Cross
2021-04-26 7:34 ` Bastien
2021-04-25 10:10 ` Help with reproducing bugs reported on this list (was: Concerns about community contributor support) Bastien
2021-04-27 6:28 ` Help with reproducing bugs reported on this list Bastien
2021-04-25 21:40 ` Concerns about community contributor support Nick Savage
2021-04-26 7:22 ` Bastien
2021-04-29 14:07 ` D
2021-04-29 14:16 ` Bastien
2021-04-29 14:44 ` D
2021-04-29 14:29 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).