From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:56765) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ghCMz-0003KP-SB for qemu-devel@nongnu.org; Wed, 09 Jan 2019 06:50:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ghCMx-0000SH-OD for qemu-devel@nongnu.org; Wed, 09 Jan 2019 06:50:01 -0500 Date: Wed, 9 Jan 2019 12:43:19 +0100 From: Niels de Vos Message-ID: <20190109114319.GB7869@ndevos-x270> References: <0e8a512d4c95094dc12f92390200c8e753c38248.1537848362.git.jcody@redhat.com> <87efdiyxv9.fsf@dusky.pond.sub.org> <20180925053204.GB4558@lemon.usersys.redhat.com> <87va6uvxhv.fsf@dusky.pond.sub.org> <87h8ejcbl1.fsf@dusky.pond.sub.org> <20190108191216.GO11492@linux.fritz.box> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190108191216.GO11492@linux.fritz.box> Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/2] MAINTAINERS: Remove myself as block maintainer List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Markus Armbruster , Fam Zheng , qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com, Jeff Cody 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 writes: > > > > > Fam Zheng writes: > > > > > >> On Tue, 09/25 07:00, Markus Armbruster wrote: > > >>> Jeff Cody 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 > > >>> > --- > > >>> > 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 > > >>> > -M: Jeff Cody > > >>> > 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 > > >>> > M: Liu Yuan > > >>> > -M: Jeff Cody > > >>> > 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 > > >>> > 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 > > >>> > @@ -2034,34 +2028,26 @@ F: docs/interop/nbd.txt > > >>> > T: git git://repo.or.cz/qemu/ericb.git nbd > > >>> > > > >>> > NFS > > >>> > -M: Jeff Cody > > >>> > M: Peter Lieven > > >>> > 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 > > >>> > -M: Jeff Cody > > >>> > 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 > > >>> > 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 > > >>> > 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 > > >>> > > >> > > >> 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