mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Joe Perches <joe@perches.com>
Cc: Greg KH <gregkh@suse.de>,
	devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: What's the staging review and acceptance process?
Date: Thu, 22 Apr 2010 11:25:04 +0200	[thread overview]
Message-ID: <4BD015F0.5090901@s5r6.in-berlin.de> (raw)
In-Reply-To: <1271915718.1730.687.camel@Joe-Laptop.home>

On 4/22/2010 7:55 AM, Joe Perches wrote:
> On Wed, 2010-04-21 at 22:49 -0700, Greg KH wrote:
>> On Wed, Apr 21, 2010 at 09:25:57PM -0700, Joe Perches wrote:
>> > On Wed, 2010-04-21 at 20:45 -0700, Greg KH wrote:
>> > > That caused the huge backlog staring at me right now.
>> > Which likely discouraged the new contributors who
>> > submitted stuff still in that backlog.
>> do you have any evidence of this causing people to go away?
> 
> I think it's pretty established that response delays
> cause losses of one type or another.

Perhaps, perhaps not.  OTOH, the development process documentation
contains the advice not to be discouraged if feedback isn't immediate,
and if in doubt, simply resubmit sometime later.
http://lxr.linux.no/#linux-old+v2.4.0/Documentation/SubmittingPatches#L180
I.e. it is well known that delays may happen and that people should not
worry about them.

If people /do/ get discouraged nevertheless, then this is because they
do not want or cannot afford to spend the (little) time to resubmit or
just ask what the review progress is.  If this happened to a bug fix of
an existing feature, than that is sad and our loss.  But if this
happened to a patch that is meant to develop a new feature --- such as
fundamentally all patches to drivers/staging/ --- then there is not any
real loss of a potential contributor, IMO:  Mid-term or long-term
contributors need to be people who work with the reviewers and
maintainers, and that means to cope with occasional delays.

Of course, if there is a subsystem with _permanent_ huge delays or
actual patch loss or is orphaned entirely, then somebody needs to step
in and offer help with review (which is a hard task and only worthwhile
if the volunteering reviewer is credible) and perhaps with maintenance
duties (which is easier).
-- 
Stefan Richter
-=====-==-=- -=-- =-==-
http://arcgraph.de/sr/

  parent reply	other threads:[~2010-04-22  9:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 20:32 Joe Perches
2010-04-22  3:45 ` Greg KH
2010-04-22  4:25   ` Joe Perches
2010-04-22  5:49     ` Greg KH
2010-04-22  5:55       ` Joe Perches
2010-04-22  6:12         ` Greg KH
2010-04-22  6:28           ` Joe Perches
2010-04-22  6:35             ` Jaya Kumar
2010-04-22  6:42           ` Olivier Galibert
2010-04-22 19:58             ` John W. Linville
2010-04-22 20:06               ` Randy Dunlap
2010-04-22 20:17                 ` Greg KH
2010-04-22  9:25         ` Stefan Richter [this message]
2010-04-22  9:17       ` Alan Cox
2010-04-22 20:18         ` Greg KH
2010-04-22 22:46           ` Willy Tarreau

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BD015F0.5090901@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome