[Top] [All Lists]

Re: XFS leadership and a new co-maintainer candidate

To: xfs@xxxxxxxxxxx
Subject: Re: XFS leadership and a new co-maintainer candidate
From: Phil White <cerise-xfs@xxxxxxxxxxxx>
Date: Fri, 8 Nov 2013 13:29:09 -0800
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <mailman.2046.1383942763.4413.xfs@xxxxxxxxxxx>
References: <mailman.2046.1383942763.4413.xfs@xxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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@xxxxxxxxxx>
>     163 Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
>      51 Author: Christoph Hellwig <hch@xxxxxx>
>      35 Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
>      34 Author: Chandra Seetharaman <sekharan@xxxxxxxxxx>
>      29 Author: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
>      28 Author: Brian Foster <bfoster@xxxxxxxxxx>
>      25 Author: Zhi Yong Wu <wuzhy@xxxxxxxxxxxxxxxxxx>
>      24 Author: Jeff Liu <jeff.liu@xxxxxxxxxx>
>      21 Author: Jie Liu <jeff.liu@xxxxxxxxxx>
>      20 Author: Mark Tinguely <tinguely@xxxxxxx>
>      16 Author: Dave Chinner <david@xxxxxxxxxxxxx>
>      12 Author: Eric Sandeen <sandeen@xxxxxxxxxx>
>      12 Author: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
> 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.


<Prev in Thread] Current Thread [Next in Thread>