Linux-Fsdevel Archive on lore.kernel.org
 help / color / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Allison Collins <allison.henderson@oracle.com>,
	Amir Goldstein <amir73il@gmail.com>,
	lsf-pc@lists.linux-foundation.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	xfs <linux-xfs@vger.kernel.org>, Eryu Guan <guaneryu@gmail.com>,
	Eric Sandeen <sandeen@redhat.com>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] FS Maintainers Don't Scale
Date: Mon, 17 Feb 2020 08:55:56 +1100
Message-ID: <20200216215556.GZ10776@dread.disaster.area> (raw)
In-Reply-To: <20200213154632.GN7778@bombadil.infradead.org>

On Thu, Feb 13, 2020 at 07:46:32AM -0800, Matthew Wilcox wrote:
> On Thu, Feb 13, 2020 at 10:11:00AM -0500, Brian Foster wrote:
> > With regard to the burnout thing, ISTM the core functionality of the
> > maintainer is to maintain the integrity of the subtree. That involves
> > things like enforcing development process (i.e., requiring r-b tags on
> > all patches to merge), but not necessarily being obligated to resolve
> > conflicts or to review every patch that comes through in detail, or
> > guarantee that everything sent to the list makes it into the next
> > release, etc. If certain things aren't being reviewed in time or making
> > progress and that somehow results in additional pressure on the
> > maintainer, ISTM that something is wrong there..?
> > 
> > On a more logistical note, didn't we (XFS) discuss the idea of a
> > rotating maintainership at one point? I know Dave had dealt with burnout
> > after doing this job for quite some time, Darrick stepped in and it
> > sounds like he is now feeling it as well (and maybe Eric, having to hold
> > down the xfsprogs fort). I'm not maintainer nor do I really want to be,
> > but I'd be willing to contribute to maintainer like duties on a limited
> > basis if there's a need. For example, if we had a per-release rotation
> > of 3+ people willing to contribute, perhaps that could spread the pain
> > around sufficiently..? Just a thought, and of course not being a
> > maintainer I have no idea how realistic something like that might be..
> 
> Not being an XFS person, I don't want to impose anything, but have
> you read/seen Dan Vetter's talk on this subject?
> https://blog.ffwll.ch/2017/01/maintainers-dont-scale.html (plenty of
> links to follow, including particularly https://lwn.net/Articles/705228/ )

Yes, and I've talked to Dan in great detail about it over several
past LCAs... :)

> It seems like the XFS development community might benefit from a
> group maintainer model.

Yes, it may well do. The problem is the pool of XFS developers is
*much smaller* than the graphics subsystem and so a "group
maintainership" if kinda what we do already. I mean, I do have
commit rights to the XFS trees kernel.org, even though I'm not a
maintainer. I'm essentially the backup at this point - if someone
needs to take time off, I'll take over.

I think the biggest barrier to maintaining the XFS tree is the
amount of integration testing that the maintainer does on the merged
tree.  That's non-trivial, especially with how long it takes to run
fstests these days. If you're not set up to run QA 24x7 across a
bunch of different configs, then you need to get that into place
before being able to do the job of maintaining the XFS kernel
tree...

If everyone had that capability and resources at their disposal, then
rotating the tree maintenance responsibilities would be much
easier...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply index

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31  5:25 Darrick J. Wong
2020-01-31  7:30 ` [Lsf-pc] " Amir Goldstein
2020-02-01  3:20   ` Allison Collins
2020-02-02 21:46     ` Dave Chinner
2020-02-09 17:12       ` Allison Collins
2020-02-12  0:21         ` NeilBrown
2020-02-12  6:58           ` Darrick J. Wong
2020-02-12 22:06         ` Darrick J. Wong
2020-02-12 22:19           ` Dan Williams
2020-02-12 22:36             ` Darrick J. Wong
2020-02-13 15:11           ` Brian Foster
2020-02-13 15:46             ` Matthew Wilcox
2020-02-16 21:55               ` Dave Chinner [this message]
2020-02-19  0:29                 ` Darrick J. Wong
2020-02-19  1:17                   ` Theodore Y. Ts'o
2020-02-12 23:39         ` Dave Chinner
2020-02-13 15:19           ` Brian Foster
2020-02-17  0:11             ` Dave Chinner
2020-02-17 15:01               ` Brian Foster
2020-02-12 21:36       ` Darrick J. Wong
2020-02-12 22:42   ` Darrick J. Wong
2020-02-13 10:21     ` Amir Goldstein
2020-02-07 22:03 ` Matthew Wilcox
2020-02-12  3:51   ` Theodore Y. Ts'o
2020-02-12 22:29     ` Darrick J. Wong
2020-02-12 22:21   ` Darrick J. Wong
2020-02-13  1:23     ` Dave Chinner

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=20200216215556.GZ10776@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=allison.henderson@oracle.com \
    --cc=amir73il@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=guaneryu@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=sandeen@redhat.com \
    --cc=willy@infradead.org \
    /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

Linux-Fsdevel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \
		linux-fsdevel@vger.kernel.org
	public-inbox-index linux-fsdevel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git