linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: corbet@lwn.net, Chandan Babu R <chandan.babu@oracle.com>,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	david@fromorbit.com, cem@kernel.org, sandeen@sandeen.net,
	amir73il@gmail.com, leah.rumancik@gmail.com, zlang@kernel.org,
	fstests@vger.kernel.org, willy@infradead.org,
	shirley.ma@oracle.com, konrad.wilk@oracle.com
Subject: Re: [PATCHSET 0/3] xfs: maintainer transition for 6.6
Date: Wed, 2 Aug 2023 12:31:50 -0700	[thread overview]
Message-ID: <20230802193150.GD11352@frogsfrogsfrogs> (raw)
In-Reply-To: <169091989589.112530.11294854598557805230.stgit@frogsfrogsfrogs>

On Tue, Aug 01, 2023 at 12:58:15PM -0700, Darrick J. Wong wrote:
> Hi all,
> 
> I do not choose to continue as maintainer.

It seems I have to clarify my previous message.  I'm stepping down as XFS
maintainer.  I'm /continuing/ as a senior developer and reviewer for XFS.

I've really enjoyed my work developing XFS and bringing new online
capabilities to the filesystem.  I've struggled with the role of
maintainer for many years though, as it's impossible for one person to
do all the things that are expected of a maintainer.

I recognize that some of the stress I've put on myself, by trying to
ensure that every patch has a Reviewed-By, and I'm usually the one who
has to do that review.  It hasn't been fair.

I'm excited to continue development on XFS, and am leaving the
maintainership in capable hands.  I'm /very/ excited about online
repair, as part 2 is almost complete and ready to be sent out!

Thanks Chandan!

--D

> 
> My final act as maintainer is to write down every thing that I've been
> doing as maintainer for the past six years.  There are too many demands
> placed on the maintainer, and the only way to fix this is to delegate
> the responsibilities.  I also wrote down my impressions of the unwritten
> rules about how to contribute to XFS.
> 
> The patchset concludes with my nomination for a new release manager to
> keep things running in the interim.  Testing and triage; community
> management; and LTS maintenance are all open positions.
> 
> This is an extraordinary way to destroy everything.  Enjoy!
> Comments and questions are, as always, welcome.
> 
> --D
> ---
>  Documentation/filesystems/index.rst                |    1 
>  .../filesystems/xfs-maintainer-entry-profile.rst   |  192 ++++++++++++++++++++
>  .../maintainer/maintainer-entry-profile.rst        |    1 
>  MAINTAINERS                                        |    4 
>  4 files changed, 197 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/filesystems/xfs-maintainer-entry-profile.rst
> 

      parent reply	other threads:[~2023-08-02 19:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 19:58 [PATCHSET 0/3] xfs: maintainer transition for 6.6 Darrick J. Wong
2023-08-01 19:58 ` [PATCH 1/3] docs: add maintainer entry profile for XFS Darrick J. Wong
2023-08-04  5:09   ` Darrick J. Wong
2023-08-04  6:08     ` Chandan Babu R
2023-08-11 19:31   ` Luis Chamberlain
2023-08-12  0:04     ` Darrick J. Wong
2023-08-12  9:05       ` Amir Goldstein
2023-08-15 23:54         ` Luis Chamberlain
2023-08-16  0:11           ` Darrick J. Wong
2023-08-16  1:22             ` Luis Chamberlain
2023-08-16  6:04             ` Zorro Lang
2023-08-17  0:33               ` Darrick J. Wong
2023-08-17  1:15                 ` Luis Chamberlain
2023-08-19  2:07                   ` Darrick J. Wong
2023-08-19 19:07                     ` Luis Chamberlain
2023-08-19  3:52                 ` Zorro Lang
2023-08-01 19:58 ` [PATCH 2/3] MAINTAINERS: drop me as XFS maintainer Darrick J. Wong
2023-08-01 19:58 ` [PATCH 3/3] MAINTAINERS: add Chandan Babu as XFS release manager Darrick J. Wong
2023-08-03 13:07   ` Chandan Babu R
2023-08-02 19:31 ` Darrick J. Wong [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=20230802193150.GD11352@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=cem@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=corbet@lwn.net \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=konrad.wilk@oracle.com \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=shirley.ma@oracle.com \
    --cc=willy@infradead.org \
    --cc=zlang@kernel.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
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).