From: Matthew Wilcox <willy@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Allison Collins <allison.henderson@oracle.com>,
Dave Chinner <david@fromorbit.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: Thu, 13 Feb 2020 07:46:32 -0800 [thread overview]
Message-ID: <20200213154632.GN7778@bombadil.infradead.org> (raw)
In-Reply-To: <20200213151100.GC6548@bfoster>
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/ )
It seems like the XFS development community might benefit from a
group maintainer model.
next prev parent reply other threads:[~2020-02-13 15:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 5:25 [LSF/MM/BPF TOPIC] FS Maintainers Don't Scale 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 [this message]
2020-02-16 21:55 ` Dave Chinner
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=20200213154632.GN7778@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=allison.henderson@oracle.com \
--cc=amir73il@gmail.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.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 \
/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).