linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: elder@kernel.org, Mark Tinguely <tinguely@sgi.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: XFS leadership and a new co-maintainer candidate
Date: Fri, 8 Nov 2013 13:45:50 -0600	[thread overview]
Message-ID: <20131108194550.GZ1935@sgi.com> (raw)
In-Reply-To: <527D28DC.6060305@redhat.com>

Hey Ric,

On Fri, Nov 08, 2013 at 01:09:32PM -0500, Ric Wheeler wrote:
> On 11/08/2013 01:03 PM, Ben Myers wrote:
> >Hey Ric,
> >
> >On Fri, Nov 08, 2013 at 06:03:41AM -0500, Ric Wheeler wrote:
> >>In the XFS community, we have 2 clear leaders in terms of
> >>contributions of significant feaures and depth of knowledge -
> >>Christoph and Dave.
> >>
> >>If you look at the number of patches submitted by developers since
> >>3.0 who have more than 10 patches, we get the following:
> >>
> >>     319 Author: Dave Chinner <dchinner@redhat.com>
> >>     163 Author: Christoph Hellwig <hch@infradead.org>
> >>      51 Author: Christoph Hellwig <hch@lst.de>
> >>      35 Author: Linus Torvalds <torvalds@linux-foundation.org>
> >>      34 Author: Chandra Seetharaman <sekharan@us.ibm.com>
> >>      29 Author: Al Viro <viro@zeniv.linux.org.uk>
> >>      28 Author: Brian Foster <bfoster@redhat.com>
> >>      25 Author: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
> >>      24 Author: Jeff Liu <jeff.liu@oracle.com>
> >>      21 Author: Jie Liu <jeff.liu@oracle.com>
> >>      20 Author: Mark Tinguely <tinguely@sgi.com>
> >>      16 Author: Dave Chinner <david@fromorbit.com>
> >>      12 Author: Eric Sandeen <sandeen@redhat.com>
> >>      12 Author: Carlos Maiolino <cmaiolino@redhat.com>
> >>
> >>If we as a community had more capacity for patch review, Dave's
> >>numbers would have jumped up even higher :)
> >>
> >>It is certainly very welcome to bring new developers into our
> >>community, but if we are going to add a co-maintainer for XFS, we
> >>really need to have one of our two leading developers in that role.
> >Mark is replacing Alex as my backup because Alex is really busy at
> >Linaro and asked to be taken off awhile ago.  The holiday season is
> >coming up and I fully intend to go off my meds, turn in to Fonzy the
> >bear, and eat my hat.  I need someone to watch the shop while I'm off
> >exploring on Mars.  I trust Mark to do that because he is totally
> >awesome.
> >
> >-Ben
> 
> I don't mean any disrepect to you or to Mark,
       
Don't worry about it, I have plenty to spare.  ;P

> but maintainership is
> something that you earn over time by proving yourself in the
> community as a developer and a leader of the technology on a
> personal level.
>
> It is not something that gets managed by the community of developers
> and has the key role of keeping the most frequent developers engaged
> and happy.  That has not been working for us as a community lately.
> 
> Dave Chinner is the obvious person to take on the maintainer role as
> someone who has an order of magnitude more code contributed than
> either of you (even combined).
> 
> Christoph, if he has time, would also be an excellent candidate.

Eric is also a good choice.  I'd be happy to add all three.

-Ben

  reply	other threads:[~2013-11-08 19:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131107220208.GY1935@sgi.com>
     [not found] ` <527C0F64.3010906@sgi.com>
     [not found]   ` <527C4B27.6020205@redhat.com>
2013-11-08 11:03     ` XFS leadership and a new co-maintainer candidate Ric Wheeler
2013-11-08 18:03       ` Ben Myers
2013-11-08 18:09         ` Ric Wheeler
2013-11-08 19:45           ` Ben Myers [this message]
2013-11-08 19:34         ` Christoph Hellwig
2013-11-08 20:32           ` Ric Wheeler
2013-11-08 20:46           ` Ben Myers
2013-11-08 20:50             ` Ric Wheeler
2013-11-08 22:03               ` [PATCH] update xfs maintainers Ben Myers
2013-11-08 22:07                 ` Ric Wheeler
2013-11-08 22:17                   ` Ben Myers
2013-11-08 23:32                     ` Ric Wheeler
2013-11-09 23:17                       ` Ben Myers
2013-11-08 22:59                 ` Zhi Yong Wu
2013-11-08 23:44                   ` NeilBrown
2013-11-09 23:51                     ` Ben Myers
2013-11-10  0:30                       ` Ben Myers
2013-11-10  3:13                         ` Stan Hoeppner
2013-11-10 23:32                           ` Dave Chinner
2013-11-10 23:12                         ` Dave Chinner
2013-11-11  3:49                           ` Ben Myers
2013-11-14  6:22                 ` Dave Chinner
2013-11-15  0:33                   ` Ben Myers
2013-11-14 18:25                 ` Alex Elder
2013-11-12 17:32             ` XFS leadership and a new co-maintainer candidate Christoph Hellwig
2013-11-12 19:30               ` Ben Myers

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=20131108194550.GZ1935@sgi.com \
    --to=bpm@sgi.com \
    --cc=elder@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --cc=tinguely@sgi.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xfs@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).