From: Phil White <cerise-xfs@l.armory.com>
To: xfs@oss.sgi.com
Subject: Re: XFS leadership and a new co-maintainer candidate
Date: Fri, 8 Nov 2013 13:29:09 -0800 [thread overview]
Message-ID: <20131108212909.GT30145@boogeyman> (raw)
In-Reply-To: <mailman.2046.1383942763.4413.xfs@oss.sgi.com>
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.
I don't have a dog in this fight, so I'm going to give my opinion on the
matter. You guys can fight it out.
I'm not really sure why amount of code contributed implies good
maintainership. Over our professional lives, I'm sure that we've worked
with a lot of people who couldn't write code worth beans who maintained
the source competently.
I'm not sure why the title is being bandied about as an honorific. It's
not the America's Cup and having a title passed around because of a particular
metric seems counterproductive.
Ben has obvious -- and good -- reasons for choosing Mark. Not only does
he have an office right nearby, but Mark has done excellent work and he's been
pretty enthusiastic while doing it.
To my mind, easy access to co-maintainers implies that it's a lot easier to
share knowledge and coordinate -- isn't that where the "co-" part of
"co-maintainer" comes from?
It's expected that some people are going to be in different time zones in an
open source project. But as I'm sure we can all attest, it's a bear to
coordinate with people who are a great many hours off from your time zone.
If I remember correctly, Dave's in Australia and Christoph's in Germany. If
we're going to have a small number of maintainers, I can see the logic in
having them be on the same continent and within a few time zones.
-Phil
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2013-11-08 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2046.1383942763.4413.xfs@oss.sgi.com>
2013-11-08 21:29 ` Phil White [this message]
2013-11-11 11:34 ` XFS leadership and a new co-maintainer candidate Carlos Maiolino
2013-11-07 22:02 xfs: update maintainers file Ben Myers
2013-11-07 22:08 ` Mark Tinguely
2013-11-08 2:23 ` Ric Wheeler
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
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-12 17:32 ` 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=20131108212909.GT30145@boogeyman \
--to=cerise-xfs@l.armory.com \
--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