Re: [Xen-devel] [PATCH] MAINTAINERS: add myself for kconfig

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Wed, 2016-01-06 at 14:26 +0000, Tim Deegan wrote:
> At 06:45 -0700 on 06 Jan (1452062722), Jan Beulich wrote:
> > > > > On 05.01.16 at 13:07, <ian.campbell@xxxxxxxxxx> wrote:
> > > On Wed, 2015-12-16 at 08:41 -0600, Doug Goldstein wrote:
> > > > Added myself as the maintainer of kconfig.
> > > > 
> > > > CC: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > > > CC: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> > > > CC: Jan Beulich <jbeulich@xxxxxxxx>
> > > > CC: Keir Fraser <keir@xxxxxxx>
> > > > CC: Tim Deegan <tim@xxxxxxx>
> > > > 
> > > > Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx>
> > > 
> > > Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > 
> > Which reminds me that I meant to reply before the holidays,
> > but then didn't get around to.
> > 
> > To be honest, I'm not convinced. On one hand I'm certainly
> > happy for this to not fall under THE REST, but on the other
> > hand I've checked your, Doug, history on both Xen and Linux
> > without finding (on the Linux side) any Kconfig related
> > contribution, and only few earlier ones on either side. I hope
> > you understand that I'm uncertain about a relative newcomer
> > to be immediately granted maintainership over a non-negligible
> > (both in terms of size and functionality) piece of code.
> 
> The usual failure mode for Xen contributors is that they leave the
> code and never follow up; this is a strong sign that Doug is going to
> stick around, and IMO ought to be encouraged!ÂÂAnd in any case Xen as
> a whole has a chronic lack of reviewer bandwidth which will only be
> fixed by welcoming new reviewers.

FWIW I agree with this

A MAINTAINERS entry is also a point of contact and it does seem to me to be
absolutely appropriate for Doug to get CCd on any Kconfig related issues.

We shouldn't be expecting (or encouraging) Kconfig development work in the
context of Xen either, since we do not want to fork this code. So from our
PoV maintenance of the code means liaising with upstream and importing new
versions when appropriate, a bar which I think Doug has easily reached.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel