All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: Lars Kurth <lars.kurth@citrix.com>, Keir Fraser <keir@xen.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] MAINTAINERS: Clarify the meaning of nested maintainership
Date: Thu, 28 Apr 2016 17:18:28 +0100	[thread overview]
Message-ID: <572237D4.9040804@citrix.com> (raw)
In-Reply-To: <20160428154921.GH12379@char.us.oracle.com>

On 28/04/16 16:49, Konrad Rzeszutek Wilk wrote:
> On Thu, Apr 28, 2016 at 11:28:20AM +0100, Wei Liu wrote:
>> On Wed, Apr 27, 2016 at 05:06:27PM +0100, George Dunlap wrote:
>>> Clarify the meaning of nested maintainership.
>>>
>>> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
>>> ---
>>> We had a discussion about the meaning of nested maintainership at the
>>> recent Xen Hackathon.  The notes of that meeting can be found on this
>>> list [1].  No decision is official until discussed on this list, so
>>> consider this patch the official proposal for this change, and object
>>> or ask for clarification accordingly.
>>>
>>> Compared to v1, there is one change that is worth pointing out: The
>>> claim that THE REST consists of all committers.  This is the case at
>>> the moment, but this change would codify that this is an invariant we
>>> intend to keep going forward.
>>>
>>> The advantage of this is that the dispute resolution mentioned in this
>>> patch for maintainers who can't agree lines up directly with the
>>> fall-back for broader community issues upon which we can't reach
>>> consensus.
>>>
>>> [1] marc.info/?i=<EDB48431-C3EF-4461-B2D2-3AB95EA6C392@gmail.com>
>>>
>>> Changes in v2:
>>> - fixed spelling of "maintainer"
>>> - fixed path of multi.c
>>> - clarified that the resolution by REST would be by *majority* vote
>>> - Asserted that The REST consists of all committers
>>>
>>> CC: Ian Jackson <ian.jackson@eu.citrix.com>
>>> CC: Jan Beulich <jbeulich@suse.com>
>>> CC: Keir Fraser <keir@xen.org>
>>> CC: Tim Deegan <tim@xen.org>
>>> CC: Wei Liu <wei.liu2@citrix.com>
>>> CC: Konrad Wilk <konrad.wilk@oracle.com>
>>> CC: Andrew Cooper <andrew.cooper3@citrix.com>
>>> CC: Lars Kurth <lars.kurth@citrix.com>
>>
>>
>> Acked-by: Wei Liu <wei.liu2@citrix.com>
> 
> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

Thanks Konrad.

I'll check this in tomorrow morning with whatever Acks it has at that
point unless someone objects before then.

 -George


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

      reply	other threads:[~2016-04-28 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 16:06 [PATCH v2] MAINTAINERS: Clarify the meaning of nested maintainership George Dunlap
2016-04-28 10:13 ` Jan Beulich
2016-04-28 10:28 ` Wei Liu
2016-04-28 15:49   ` Konrad Rzeszutek Wilk
2016-04-28 16:18     ` George Dunlap [this message]

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=572237D4.9040804@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.