All of
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <>
Cc:, xfs <>,
	Eric Sandeen <>, Eryu Guan <>
Subject: [LSF/MM/BPF TOPIC] FS Maintainers Don't Scale
Date: Thu, 30 Jan 2020 21:25:20 -0800	[thread overview]
Message-ID: <20200131052520.GC6869@magnolia> (raw)

Hi everyone,

I would like to discuss how to improve the process of shepherding code
into the kernel to make it more enjoyable for maintainers, reviewers,
and code authors.  Here is a brief summary of how we got here:

Years ago, XFS had one maintainer tending to all four key git repos
(kernel, userspace, documentation, testing).  Like most subsystems, the
maintainer did a lot of review and porting code between the kernel and
userspace, though with help from others.

It turns out that this didn't scale very well, so we split the
responsibilities into three maintainers.  Like most subsystems, the
maintainers still did a lot of review and porting work, though with help
from others.

It turns out that this system doesn't scale very well either.  Even with
three maintainers sharing access to the git trees and working together
to get reviews done, mailing list traffic has been trending upwards for
years, and we still can't keep up.  I fear that many maintainers are
burning out.  For XFS, the biggest pain point (AFAICT) is not assembly and
testing of the git trees, but keeping up with the mail and the reviews.

So what do we do about this?  I think we (the XFS project, anyway)
should increase the amount of organizing in our review process.  For
large patchsets, I would like to improve informal communication about
who the author might like to have conduct a review, who might be
interested in conducting a review, estimates of how much time a reviewer
has to spend on a patchset, and of course, feedback about how it went.
This of course is to lay the groundwork for making a case to our bosses
for growing our community, allocating time for reviews and for growing
our skills as reviewers.


I want to spend the time between right now and whenever this discussion
happens to make a list of everything that works and that could be made
better about our development process.

I want to spend five minutes at the start of the discussion to
acknowledge everyone's feelings around that list that we will have

Then I want to spend the rest of the session breaking up the problems
into small enough pieces to solve, discussing solutions to those
problems, and (ideally) pushing towards a consensus on what series of
small adjustments we can make to arrive at something that works better
for everyone.


             reply	other threads:[~2020-01-31  5:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31  5:25 Darrick J. Wong [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200131052520.GC6869@magnolia \ \ \ \ \ \ \
    --subject='Re: [LSF/MM/BPF TOPIC] FS Maintainers Don'\''t Scale' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.