From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Concerns about community contributor support
Date: Wed, 21 Apr 2021 19:50:59 +1000 [thread overview]
Message-ID: <87eef4hs9o.fsf@gmail.com> (raw)
In-Reply-To: <YH/xUJboiPY3LJDZ@protected.localdomain>
Jean Louis <bugs@gnu.support> writes:
> It should be clear that more maintainers and developers with direct
> access are needed for patches to be applied timely.
>
> I am sure that those on emacs-devel mailing list, Emacs developers,
> they could help on that, but maybe some of them do not observe this
> mailing list.
>
> Number of not applied patches does not seem to be that large.
>
> Project leader shall have his team and delegate them to other
> developers.
>
> This situation badly contradicts to Org mode purposes which is meant
> to manage patches.
>
> Maybe there shall be a published list of developers and project
> managers, so that this type of communication may be addressd
> properly. As now original poster explained the problem, but I did not
> see response from none of pushers, I mean those who have repository
> access.
>
> So how many people are there who have repository access?
>
> Who is not busy but willing to apply at least 1-5 patches pending?
>
I'm not sure I agree with this analysis. As Timothy mentioned a few
times, the issue is NOT about the time taken to apply patches. It is
about a lack of feedback regarding the state of the patches.
Increasing the number of people with the ability to apply
patches/changes to the repository is unlikely to be helpful. It could in
fact have the reverse result, leading to increased inconsistency and
reduced stability.
I find bug fixes are applied very quickly. Enhancements and extensions
are introduced more conservatively, but I think that is a positive
rather than negative aspect of org development. For many users, org is
already very feature rich/complete.
--
Tim Cross
next prev parent reply other threads:[~2021-04-21 10:00 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 [this message]
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
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=87eef4hs9o.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.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).