public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: paulmck@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	dvhart@linux.intel.com, oleg@redhat.com, sbw@mit.edu
Subject: Re: [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU
Date: Wed, 9 Jul 2014 19:42:33 +0200	[thread overview]
Message-ID: <20140709174231.GC23881@localhost.localdomain> (raw)
In-Reply-To: <1404878965.932.87.camel@joe-AO725>

On Tue, Jul 08, 2014 at 09:09:25PM -0700, Joe Perches wrote:
> On Tue, 2014-07-08 at 15:25 -0700, Paul E. McKenney wrote:
> > On Tue, Jul 08, 2014 at 03:05:16PM -0700, Joe Perches wrote:
> []
> > > I still think the concept is pretty useless and it's
> > > just a duplication of "M:", which isn't anything other
> > > than a list of who should be sent patches.
> []
> > It will be interesting to see how things go.
> 
> Yes, it might work out fine and maybe might cause some
> other beneficial changes.
> 
> > There did seem to be
> > some people who were comfortable being listed as RCU reviewers, but
> > not as RCU maintainers.  Perhaps the same thing happens elsewhere.
> 
> Maybe so.
> 
> I wrote a script to find which maintainer addresses that
> haven't signed or authored a commit in the last 2 years.
> 
> I got ~250 entries.  That's about 1/4 of all maintainer
> email addresses.
> 
> Maybe a dozen of these are false positives though because
> some maintainers prefer to receive email at one address
> but ack from another.
> 
> These are all lowercase for better matching.

Aren't we all falling in the typical pessimism trap, evil of the century!
Why do we always want to consider the lack of activity from a maintainer as a bad symptom?

What if it were actually a positive sign resulting of a finished, completed, and perfect
clean bug-free subsystem?

Once we accept that, all we need is support from the MAINTAINERS file:

diff --git a/MAINTAINERS b/MAINTAINERS
index 970c4a0..5da75dd 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -76,6 +76,9 @@ Descriptions of section entries:
 	T: SCM tree type and location.
 	   Type is one of: git, hg, quilt, stgit, topgit
 	S: Status, one of the following:
+          Finished:	The code is finished. The maintainer has fixed all
+			the bugs and adressed all missing features. No further
+			patch is needed.
 	   Supported:	Someone is actually paid to look after this.
 	   Maintained:	Someone actually looks after it.
 	   Odd Fixes:	It has a maintainer but they don't have time to do

  parent reply	other threads:[~2014-07-09 17:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 22:41 [PATCH tip/core/rcu 0/3] Maintainership changes for 3.17 Paul E. McKenney
2014-07-07 22:42 ` [PATCH tip/core/rcu 1/3] MAINTAINERS: Add "R:" designated-reviewers tag Paul E. McKenney
2014-07-07 22:42   ` [PATCH tip/core/rcu 2/3] rcu: Add designated reviewers for RCU Paul E. McKenney
2014-07-08  8:09     ` Peter Zijlstra
2014-07-08 18:06       ` Joe Perches
2014-07-08 20:41         ` Paul E. McKenney
2014-07-08 21:01           ` Joe Perches
2014-07-08 21:52             ` Paul E. McKenney
2014-07-08 22:05               ` Joe Perches
2014-07-08 22:25                 ` Paul E. McKenney
2014-07-09  4:09                   ` Joe Perches
2014-07-09 11:14                     ` Paul E. McKenney
2014-07-09 13:23                       ` Joe Perches
2014-07-10  9:39                         ` Peter Zijlstra
2014-07-10 10:00                           ` Joe Perches
2014-07-10 23:16                             ` josh
2014-07-11  8:32                               ` Peter Zijlstra
2014-07-09 17:00                     ` josh
2014-07-09 17:13                       ` Joe Perches
2014-07-09 17:42                     ` Frederic Weisbecker [this message]
2014-07-09 18:10                       ` Joe Perches
2014-07-07 22:42   ` [PATCH tip/core/rcu 3/3] rcu: Update RCU maintainership Paul E. McKenney
2014-07-08 17:58     ` Josh Triplett
2014-07-08 20:47       ` Paul E. McKenney
2014-07-07 22:55 ` [PATCH tip/core/rcu 0/3] Maintainership changes for 3.17 Joe Perches

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=20140709174231.GC23881@localhost.localdomain \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=joe@perches.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=niv@us.ibm.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sbw@mit.edu \
    --cc=tglx@linutronix.de \
    /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