emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: ian martins <ianxm@jhu.edu>
To: Tim Cross <theophilusx@gmail.com>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Concerns about community contributor support
Date: Thu, 22 Apr 2021 06:00:16 -0400	[thread overview]
Message-ID: <CAC=rjb4=YyCU2=pup3CbthYMuhizF2xVGzCyx9tX1HSZ78z1sQ@mail.gmail.com> (raw)
In-Reply-To: <87eef3f5qs.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]

On Wed, Apr 21, 2021 at 9:49 PM Tim Cross <theophilusx@gmail.com> wrote:

>
> ian martins <ianxm@jhu.edu> writes:
>
> > On Wed, Apr 21, 2021 at 3:45 PM Tim Cross <theophilusx@gmail.com> wrote:
> >
> >  Responding to essentially just flag you have seen the patch message
> >  really only adds noise and may even 'drown out' those responses which
> >  add real 'value' to any discussion. I also doubt that asking people to
> >  do this would actually result in any actual change of behaviour by
> >  subscribers.
> >
> > Timothy said there were 25 patches without response and the list goes
> back six months, so we're only talking about 50 emails per year.
>
> That assumes there is a single 'owner' who accepts the responsibility to
> respond to every patch submitted.
>

Why does it? If some individual notices that some patch was submitted but
hasn't gotten a response, that person can send a "thanks for submitting.
probably maintainers don't use that feature." And someone else could check
Woof every three or six months, if so inclined. It doesn't have to be
anybody's job, and it doesn't have to be limited to some predesignated
group.

Having someone respond to the author of a patch and provide some
> meaningful feedback would be great, but I don't see how that can happen
> in a project which is already stretched and with limited resources.
> There has already been multiple messages requesting additional help and
> for volunteers willing to put in the time needed to maintain parts of
> org mode. Adding to that workload isn't going to help.
>

I don't see how this adds to the workload in a significant way, but also
couldn't this be the solution to that problem? Instead of ignoring
potential future contributors we could encourage and welcome them. Maybe we
don't have to be constrained by our current limit on resources.


> To some extent, if someone submits a
> patch and hears nothing, either they have failed to clearly explain what
> the patch does (and therefore did not tweak any interest) or it is a
> patch to introduce functionality which is of low interest to community
> participants.
>

But if they hear nothing, how are they to know which was the problem? And
if it was their first contact, how should they know the problem is one of
the things you listed instead of any number of reasons one can imagine that
no one is talking to them?

[-- Attachment #2: Type: text/html, Size: 3367 bytes --]

  parent reply	other threads:[~2021-04-22 10:05 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
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                       ` ian martins [this message]
2021-04-21 19:31             ` Concerns about community contributor support 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='CAC=rjb4=YyCU2=pup3CbthYMuhizF2xVGzCyx9tX1HSZ78z1sQ@mail.gmail.com' \
    --to=ianxm@jhu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.com \
    --subject='Re: Concerns about community contributor support' \
    /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

Code repositories for project(s) associated with this 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).