All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Jackson <ian.jackson@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>,
	george.dunlap@citrix.com, Julien Grall <julien.grall@arm.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] MAINTAINERS: Add explicit check-in policy section
Date: Thu, 09 May 2019 05:36:41 -0600	[thread overview]
Message-ID: <5CD410C9020000780022D1D7@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <23764.2442.337734.122162@mariner.uk.xensource.com>

>>> On 09.05.19 at 13:05, <ian.jackson@citrix.com> wrote:
> George Dunlap writes ("Re: [Xen-devel] [PATCH] MAINTAINERS: Add explicit 
> check-in policy section"):
>> On 5/8/19 12:59 PM, Juergen Gross wrote:
>> > 2. In the case the submitter is a maintainer of a modified file it must
>> > have an Ack or Review from either a "nested" maintainer or a Designated
>> > reviewer of that file.
>> 
>> That changes the current meaning of "Designated Reviewer" somewhat.  At
>> the moment, it only means "Send this person an email"; if we did that,
>> it would mean, "This person is more trusted to do reviews than others".
>> 
>> Not sure what I think about that yet.
> 
> I think this is a bad idea.  The purpose was to provide a way for
> someone to be emailed which doesn't involve giving them authority,
> and which is therefore a status which can be granted on request and
> does not require any assessment etc.
> 
> If we chane this we will have to invent a new status to perform this
> function.

I think we will want to do this anyway: "Designated Reviewer" isn't
the same as "Cc <person> on patches" (which may be just because
someone wants to monitor what's being submitted / discussed). At
least that's my (non-native-English) understanding of "designated".

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com>
To: "Ian Jackson" <ian.jackson@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>,
	george.dunlap@citrix.com, Julien Grall <julien.grall@arm.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH] MAINTAINERS: Add explicit check-in policy section
Date: Thu, 09 May 2019 05:36:41 -0600	[thread overview]
Message-ID: <5CD410C9020000780022D1D7@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190509113641.TdKC1afEilZrQCnoGWef2alWjWxjiwXi8cBycoMgpUU@z> (raw)
In-Reply-To: <23764.2442.337734.122162@mariner.uk.xensource.com>

>>> On 09.05.19 at 13:05, <ian.jackson@citrix.com> wrote:
> George Dunlap writes ("Re: [Xen-devel] [PATCH] MAINTAINERS: Add explicit 
> check-in policy section"):
>> On 5/8/19 12:59 PM, Juergen Gross wrote:
>> > 2. In the case the submitter is a maintainer of a modified file it must
>> > have an Ack or Review from either a "nested" maintainer or a Designated
>> > reviewer of that file.
>> 
>> That changes the current meaning of "Designated Reviewer" somewhat.  At
>> the moment, it only means "Send this person an email"; if we did that,
>> it would mean, "This person is more trusted to do reviews than others".
>> 
>> Not sure what I think about that yet.
> 
> I think this is a bad idea.  The purpose was to provide a way for
> someone to be emailed which doesn't involve giving them authority,
> and which is therefore a status which can be granted on request and
> does not require any assessment etc.
> 
> If we chane this we will have to invent a new status to perform this
> function.

I think we will want to do this anyway: "Designated Reviewer" isn't
the same as "Cc <person> on patches" (which may be just because
someone wants to monitor what's being submitted / discussed). At
least that's my (non-native-English) understanding of "designated".

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-05-09 11:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 11:39 [PATCH] MAINTAINERS: Add explicit check-in policy section George Dunlap
2019-05-08 11:39 ` [Xen-devel] " George Dunlap
2019-05-08 11:59 ` Juergen Gross
2019-05-08 11:59   ` [Xen-devel] " Juergen Gross
2019-05-08 13:45   ` George Dunlap
2019-05-08 13:45     ` [Xen-devel] " George Dunlap
2019-05-09 11:05     ` Ian Jackson
2019-05-09 11:05       ` [Xen-devel] " Ian Jackson
2019-05-09 11:36       ` Jan Beulich [this message]
2019-05-09 11:36         ` Jan Beulich
2019-05-08 13:49 ` Jan Beulich
2019-05-08 13:49   ` [Xen-devel] " Jan Beulich
2019-05-08 15:32 ` Stefano Stabellini
2019-05-08 15:32   ` [Xen-devel] " Stefano Stabellini
2019-05-09 11:16 ` Ian Jackson
2019-05-09 11:16   ` [Xen-devel] " Ian Jackson
2019-05-09 11:45   ` George Dunlap
2019-05-09 11:45     ` [Xen-devel] " George Dunlap

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=5CD410C9020000780022D1D7@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@citrix.com \
    --cc=sstabellini@kernel.org \
    --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.