From: Niels de Vos <ndevos@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Fam Zheng <famz@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com,
Jeff Cody <jeff@codyprime.org>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/2] MAINTAINERS: Remove myself as block maintainer
Date: Wed, 9 Jan 2019 12:43:19 +0100 [thread overview]
Message-ID: <20190109114319.GB7869@ndevos-x270> (raw)
In-Reply-To: <20190108191216.GO11492@linux.fritz.box>
On Tue, Jan 08, 2019 at 08:12:16PM +0100, Kevin Wolf wrote:
> Am 08.01.2019 um 18:18 hat Markus Armbruster geschrieben:
> > This patch series got stuck.
> >
> > Markus Armbruster <armbru@redhat.com> writes:
> >
> > > Fam Zheng <famz@redhat.com> writes:
> > >
> > >> On Tue, 09/25 07:00, Markus Armbruster wrote:
> > >>> Jeff Cody <jcody@redhat.com> writes:
> > >>>
> > >>> > I'll not be involved in day-to-day qemu development. Remove
> > >>> > myself as maintainer from the remainder of the network block drivers
> > >>> > (and vhdx), and revert them to the general block layer maintainership.
> > >>> >
> > >>> > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > >>> > ---
> > >>> > MAINTAINERS | 14 --------------
> > >>> > 1 file changed, 14 deletions(-)
> > >>> >
> > >>> > diff --git a/MAINTAINERS b/MAINTAINERS
> > >>> > index e93f79672f..6ef6932628 100644
> > >>> > --- a/MAINTAINERS
> > >>> > +++ b/MAINTAINERS
> > >>> > @@ -1982,28 +1982,22 @@ F: block/vmdk.c
> > >>> >
> > >>> > RBD
> > >>> > M: Josh Durgin <jdurgin@redhat.com>
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > L: qemu-block@nongnu.org
> > >>> > S: Supported
> > >>> > F: block/rbd.c
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>> >
> > >>> > Sheepdog
> > >>> > M: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>
> > >>> > M: Liu Yuan <namei.unix@gmail.com>
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > L: qemu-block@nongnu.org
> > >>> > L: sheepdog@lists.wpkg.org
> > >>> > S: Supported
> > >>> > F: block/sheepdog.c
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>> >
> > >>> > VHDX
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > L: qemu-block@nongnu.org
> > >>> > S: Supported
> > >>> > F: block/vhdx*
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>>
> > >>> Does "S: Supported" make sense without an M:?
> > >>>
> > >>> >
> > >>> > VDI
> > >>> > M: Stefan Weil <sw@weilnetz.de>
> > >>> > @@ -2034,34 +2028,26 @@ F: docs/interop/nbd.txt
> > >>> > T: git git://repo.or.cz/qemu/ericb.git nbd
> > >>> >
> > >>> > NFS
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > M: Peter Lieven <pl@kamp.de>
> > >>> > L: qemu-block@nongnu.org
> > >>> > S: Maintained
> > >>> > F: block/nfs.c
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>> >
> > >>> > SSH
> > >>> > M: Richard W.M. Jones <rjones@redhat.com>
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > L: qemu-block@nongnu.org
> > >>> > S: Supported
> > >>> > F: block/ssh.c
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>> >
> > >>> > CURL
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > L: qemu-block@nongnu.org
> > >>> > S: Supported
> > >>> > F: block/curl.c
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>>
> > >>> Likewise.
> > >>>
> > >>> > GLUSTER
> > >>> > -M: Jeff Cody <jcody@redhat.com>
> > >>> > L: qemu-block@nongnu.org
> > >>> > S: Supported
> > >>> > F: block/gluster.c
> > >>> > -T: git git://github.com/codyprime/qemu-kvm-jtc.git block
> > >>>
> > >>> Likewise.
> > >>>
> > >>> > Null Block Driver
> > >>> > M: Fam Zheng <famz@redhat.com>
> > >>>
> > >>
> > >> Block drivers without an M: naturally fall under the overall maintainership of
> > >> block layer (Kevin&Max), so IMO keeping the statuses is fine. Maybe CURL can be
> > >> degraded to Maintained, though.
> > >
> > > Yes, get_maintainer.pl combines all applicable sections. Human readers
> > > are left to wonder, unless they know to look for other matches.
> > >
> > > Do we want to have a dedicated network block driver submaintainer again,
> > > if we can find one?
> > >
> > > Do we want to have a dedicated VHDX driver submaintainer again? Fam,
> > > you're maintaining VMDK, could you cover VHDX as well?
> >
> > Fam can't.
> >
> > I can see two sane options for the three sections that lose their sole
> > maintainer (VHDX, CURL, GLUSTER):
> >
> > * Downgrade to S: Orphan
> >
> > This reflects the fact that we'd like to have dedicated maintainers
> > for them. It camouflages the fact that the "Block layer core"
> > maintainers pick up the slack.
> >
> > * Delete
> >
> > The opposite.
> >
> > Kevin, Max, please pick your poison, or suggest one you find tastier.
>
> Orphan is probably by far closer to the truth than Supported. But I
> think what we really do is Odd Fixes. Not sure if that's a status that
> works in any meaningful way without having a maintainer for the specific
> thing assigned?
For Gluster we are interested in keeping it maintained in some form. At
least integration@gluster.org could be added as a list. I am not sure
there is anyone working on Gluster that would fit for a maintainer of
the driver. If you really want to put a name there, I can function as a
'maintainer' and pull in other Gluster developers in case I am otherwise
occupied.
Niels
next prev parent reply other threads:[~2019-01-09 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1537848362.git.jcody@redhat.com>
[not found] ` <0e8a512d4c95094dc12f92390200c8e753c38248.1537848362.git.jcody@redhat.com>
[not found] ` <87efdiyxv9.fsf@dusky.pond.sub.org>
[not found] ` <20180925053204.GB4558@lemon.usersys.redhat.com>
[not found] ` <87va6uvxhv.fsf@dusky.pond.sub.org>
2019-01-08 17:18 ` [Qemu-devel] [PATCH 2/2] MAINTAINERS: Remove myself as block maintainer Markus Armbruster
2019-01-08 19:12 ` Kevin Wolf
2019-01-09 10:15 ` Thomas Huth
2019-01-09 12:39 ` Markus Armbruster
2019-01-09 11:43 ` Niels de Vos [this message]
2019-01-09 12:46 ` [Qemu-devel] [Qemu-block] " Markus Armbruster
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=20190109114319.GB7869@ndevos-x270 \
--to=ndevos@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=jeff@codyprime.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).