From: "Gustav Wikström" <email@example.com>
To: TEC <firstname.lastname@example.org>,
Subject: Re: Concerns about community contributor support
Date: Mon, 19 Apr 2021 22:07:05 +0000 [thread overview]
Message-ID: <HE1PR02MB317762342564799F4D3CFF60DA499@HE1PR02MB3177.eurprd02.prod.outlook.com> (raw)
Another data point from me. I agree with your concerns, although they are difficult to solve! Since we're talking about voluntary work and non-paid work. And maintenance can take a lot of time and effort.
This is not the first time this topic comes up on the list. Both you and me took part of the discussion after the 9.4.2 release, that hinted at similar topics . And since Bastien has been in the process of handing over the maintenance role to someone else for quite some time now, it's not strange that the issue will continue to resurface until that process is done.
What I take away from this thread is mainly one thing: Another hand raised, eager to take on community work! Since you mentioned that you're interested. The more the merrier! Open source is tough though. It's very much a meritocracy. But by doing stuff that is considered to be good, and good stuff will come back to you.
Org mode isn't "finished". And I for one hope the community can continue to surprise with new, nice functionality. Even though some are perfectly happy where it is right now. In my world this is dual property of stability and extensibility is enabled by refactoring into a stable, small(er), less entangled and functional core while also encouraging extension packages/modes. Like org-roam and the likes.
A suggestion from me, fwiw, and if you're serious about getting more involved in the community, is to see if Bastien has some time to discuss this maintenance transition, and to see if there is anywhere where you can fit into that picture. But start small. ;)
I'm very interested in hearing more on how the thoughts are going in that department - and if there are others who have similar thoughts as you in terms of maybe putting more time into the project. But maybe don't see how help out, and with what.
Personally I'm also still hoping for "Org mode maintainer/advocate/whatever" to be something that someone out there can be occupied full time with. The value of the ideas and the software surely is there to warrant it. The question is only how to make it interesting enough for people to help out with funding!
From: Emacs-orgmode <email@example.com> on behalf of Timothy <firstname.lastname@example.org>
Sent: Friday, April 16, 2021 20:43
Subject: Concerns about community contributor support
Over the last few months I have felt an increasing level of concern over
the lack of response to patches. This email is rather long, but please,
bear with me. The goal is to start a discussion on the problems this
creates, and consider short and long-term solutions.
When both community and maintainer response to new patches is lacking,
many first-time contributors are actively dissuaded from contributing
again. Furthermore, each patch represents a considerable time investment
--- particularly if it's from an individual who is new to the mailing
list / patch workflow. Org-mode is not "done" and still requires the
support of long-term contributors to keep improving, anything that
discourages them from contributing back to the community needs to be
carefully understood and resolved if we want to continue harmoniously.
Take for example Jay Bosamiya's patch from September last year . It
appears to be his first submission to this mailing list, and yet there
has been absolutely no response to it. There are currently 24 other
patches listed on the updates.orgmode.org which have seen no response
from this community, some of which are from first-time contributors.
There are 36 other patches with at least two replies, but yet to be
resolved. Bastien's updates.orgmode.org is fantastic in helping prevent
contributions slip through the cracks, but it is also highlighting the
lack of community response to a significant number of patches.
This mailing list was my first experience with an email+patch based
contribution workflow. Thankfully, I received prompt and friendly
feedback and was guided through the adjustments needed so it could be
merged in a timely manner. Should my patch have been similarly ignored,
I would have been quite disheartened; it is not an overstatement to say
I would likely have written off this mailing list and not tried again.
Simply put, this is not good enough. This does a disservice to those
that have dedicated time and effort to try and better this project only
to be ignored. Not rejected, not even acknowledged, nothing.
It is imperative that this community improves our response to
contributions for the long-term health of this project. Do not take me
to be a doomsayer; I have faith that Org is going to keep on improving
regardless. However, failing to welcome and encourage contributors has a
deleterious effect on the health of the project.
I do not blame the maintainers in the slightest. As Bastien brought up
in a recent worg discussion, as time goes on we find ourselves taking on
more and more life responsibilities. Therefore it's in our best interest
to delegate some of the maintainer responsibilities to consistently
active, and supportive community members to "pass down the torch" so the
community and platform can continue to expand with grace and care.
What can the community do?
I don't know of any silver bullet, but I believe there are some steps
which could help, namely:
+ The development and publication of "reasonable expectations" which
contributors should have when submitting a patch, and that the
maintainers should strive to uphold (e.g. "expect a response within
+ A community effort/sprint to respond to those patches that have been
+ Onboarding of new maintainers, when reasonable and suitable candidates
exist (I'd very willingly throw my hat in the ring for consideration).
If it's too much work, spread it out as much as possible.
If any other ideas come to mind, please share them so we can discuss
Finally, it's not all bad.
While this discussion has called for some criticism, I don't want to
give the false impression that I think nothing is working and nobody is
supporting contributors. This is not the case at all, there are some
standout individuals one the mailing list who have been fantastic. Kudos
to you all.
My best to everyone,
next prev parent reply other threads:[~2021-04-19 22:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 18:43 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 [this message]
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 ` Contributor Steward role (was Re: Concerns about community contributor support) Timothy
2021-04-25 7:13 ` 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).