linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Andrey Albershteyn <aalbersh@redhat.com>,
	Chandan Babu R <chandanbabu@kernel.org>,
	Zorro Lang <zlang@redhat.com>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: Yearly maintainership rotation?
Date: Wed, 20 Aug 2025 08:25:52 -0700	[thread overview]
Message-ID: <20250820152552.GD7965@frogsfrogsfrogs> (raw)
In-Reply-To: <7svscwa3oy5oxavscjgapcvr7lbumsntu32fq7uhmrfqr6pino@7awm4hxzzqzb>

On Wed, Aug 20, 2025 at 10:07:02AM +0200, Carlos Maiolino wrote:
> On Tue, Aug 19, 2025 at 03:54:00PM -0700, Darrick J. Wong wrote:
> > Hi everyone,
> > 
> > Now that it's nearly September again, what do you all think about
> > rotating release managers?  Chandan has told me that he'd be willing to
> > step into maintaining upstream xfsprogs; what do the rest of you think
> > about that?
> > 
> > Also, does anyone want to tackle fstests? :D
> 
> Considering you were specific about xfxsprogs and fstests, I believe
> you excluded kernel on purpose, but anyway, from my side I'm pretty ok
> with how things are now, and I'd rather keep it as-is, specially because
> I'm enjoying the role :-)

I specifically mentioned xfsprogs because Chandan volunteered, and
fstests because Zorro has been maintaining that for a very long time.

It's fine if everyone wants to keep going as they are now, but positive
re-affirmation once a year feels (to a longtime maintainer like me,
anyway) like a face-saving way to give people an offramp if they decide
to take it.  IOWs, I think it best to help the maintainers avoid
burnout.

> Of course I'm talking about my side and my workload only, I don't speak
> for Andrey or Zorro.

<nod> No rush, you all have plenty of time to give things a good
thinking through. :)

--D

> Carlos
> 
> > 
> > --D
> > 
> 

  reply	other threads:[~2025-08-20 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pd4KqICHYbjm5ZYOHBmgSRgs-uKNopGdeI4ARGEXr12t8ZnKctQMdfVRNceZbMeFFKncvIv9_fKyKoMCmCiLfg==@protonmail.internalid>
2025-08-19 22:54 ` Yearly maintainership rotation? Darrick J. Wong
2025-08-20  8:07   ` Carlos Maiolino
2025-08-20 15:25     ` Darrick J. Wong [this message]
2025-08-26 11:23       ` Andrey Albershteyn

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=20250820152552.GD7965@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@redhat.com \
    --cc=cem@kernel.org \
    --cc=chandanbabu@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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).