From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
elder@kernel.org, Mark Tinguely <tinguely@sgi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, Ric Wheeler <rwheeler@redhat.com>
Subject: Re: XFS leadership and a new co-maintainer candidate
Date: Tue, 12 Nov 2013 13:30:01 -0600 [thread overview]
Message-ID: <20131112193001.GB10553@sgi.com> (raw)
In-Reply-To: <20131112173253.GA15089@infradead.org>
Hey,
On Tue, Nov 12, 2013 at 09:32:53AM -0800, Christoph Hellwig wrote:
> On Fri, Nov 08, 2013 at 02:46:06PM -0600, Ben Myers wrote:
> > That really didn't happen Christoph. It's not in my tree or in a pull request.
>
> I'll take my back room complain back then, but I still think that this
> is not a useful way to discuss something like this.
Thanks. Tact, Ben, Tact. ;)
> > Linus, let me know what you want to do. I do think we're doing a fair job
> > over here, and (geez) I'm just trying to add Mark as my backup since Alex
> > is too busy. I know the RH people want more control, and that's
> > understandable, but they really don't need to replace me to get their code
> > in. Ouch.
>
> I'd really like to see more diversity in XFS maintainers. The SGI focus has
> defintively been an issue again and again because it seems when one SGI
> person is too busy the others usually are as well. As mentioned before
> there's also been historically a way too high turnover, with the associated
> transition pains.
I think diversity in XFS maintainers is a great idea. How wide of a net are
you suggesting we cast? I guess it sort of depends upon what you feel is the
purpose of the file.
> By making sure we have a broader base for the maintainers, and a more open
> infrastructure we'll all win.
Agreed.
> Note that we already had that sort
> of instructure on kernel.org, but gave up on it because many people
> perceived the effort to re-gain the kernel.org accounts to high.
It is a little difficult to find your way into the web of trust. Not everyone
is in a position to make way to a conference, or to meet people in person. And
even then it can be intimidating to ask for a signature.
> I would also really like to get a clarification on "I know the RH people want
> more control, and that's understandable, but they really don't need to
> replace me to get their code in". What specific people are you worried about
> an what code? What makes "the RH people" less worthy to their code in than
> "the SGI" people.
I'm convinced we're having this discussion for the right reasons, so let's let
that line of discussion die where it is.
Regards,
Ben
prev parent reply other threads:[~2013-11-12 19:30 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 ` 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-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 [this message]
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=20131112193001.GB10553@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
all inboxes | Powered by JetHome®