From: "Darrick J. Wong" <djwong@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
corbet@lwn.net, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, david@fromorbit.com,
cem@kernel.org, sandeen@sandeen.net, chandan.babu@oracle.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: [PATCH 1/3] docs: add maintainer entry profile for XFS
Date: Fri, 11 Aug 2023 17:04:56 -0700 [thread overview]
Message-ID: <20230812000456.GA2375177@frogsfrogsfrogs> (raw)
In-Reply-To: <ZNaMhgqbLJGdateQ@bombadil.infradead.org>
On Fri, Aug 11, 2023 at 12:31:18PM -0700, Luis Chamberlain wrote:
> On Tue, Aug 01, 2023 at 12:58:21PM -0700, Darrick J. Wong wrote:
> > +Roles
> > +-----
> > +There are seven key roles in the XFS project.
> > +- **Testing Lead**: This person is responsible for setting the test
> > + coverage goals of the project, negotiating with developers to decide
> > + on new tests for new features, and making sure that developers and
> > + release managers execute on the testing.
> > +
> > + The testing lead should identify themselves with an ``M:`` entry in
> > + the XFS section of the fstests MAINTAINERS file.
>
> I think breaking responsibility down is very sensible, and should hopefully
> allow you to not burn out. Given I realize how difficult it is to do all
> the tasks, and since I'm already doing quite a bit of testing of XFS
> on linux-next I can volunteer to help with this task of testing lead
> if folks also think it may be useful to the community.
>
> The only thing is I'd like to also ask if Amir would join me on the
> role to avoid conflicts of interest when and if it comes down to testing
> features I'm involved in somehow.
Good question. Amir?
(/me also notes that he's listed as R: in fstests MAINTAINERS so he can
pinch hit if there are conflicts of interest, at least for xfs/iomap
stuff.)
--D
> Luis
next prev parent reply other threads:[~2023-08-12 0:05 UTC|newest]
Thread overview: 21+ 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 [this message]
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 ` [PATCHSET 0/3] xfs: maintainer transition for 6.6 Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 16:24 [PATCHSET v2 " Darrick J. Wong
2023-08-04 16:25 ` [PATCH 1/3] docs: add maintainer entry profile for XFS Darrick J. Wong
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=20230812000456.GA2375177@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=mcgrof@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).