qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] MAINTAINERS: clarify some of the tags
Date: Thu, 15 Nov 2018 10:46:21 -0600	[thread overview]
Message-ID: <1c020087-acd7-302a-d5be-dcdbf7b7084d@redhat.com> (raw)
In-Reply-To: <20181115172032.53945f5e.cohuck@redhat.com>

On 11/15/18 10:20 AM, Cornelia Huck wrote:
> On Fri, 26 Oct 2018 12:57:11 +0200
> Cornelia Huck <cohuck@redhat.com> wrote:
> 
>> The MAINTAINERS file is a bit sparse on information about what
>> the different designators are. Let's add some more information
>> to give contributors a better idea about what the different
>> roles are.
>>
>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>> ---
>>
>> This came out of a discussion about what being a 'reviewer' listed in
>> this file actually means. A reviewer probably should already have a
>> track record of doing helpful reviews before being listed in here.
>>
>> While at it, I also tried to add some more hints for the other entries.
>> This patch is supposed to be a starting point for further discussion.
> 
> Ping. Further discussion would be good :)

Recent threads have mentioned the possibility of potentially adding a 
new category P: for the person that submits pull requests, although I'm 
not quite sure how that is different from M: as a maintainer

>> +++ b/MAINTAINERS
>> @@ -12,9 +12,14 @@ consult qemu-devel and not any specific individual privately.
>>   Descriptions of section entries:
>>   
>>   	M: Mail patches to: FullName <address@domain>
>> +	   Maintainers are looking after a certain area and must be CCed on
>> +	   patches. They are considered the main contact point.

Maybe add something along the lines of "However, a maintainer may accept 
code that has been reviewed by others without explicitly reviewing it 
themselves"?

>>   	R: Designated reviewer: FullName <address@domain>
>>   	   These reviewers should be CCed on patches.
>> +	   Reviewers are familiar with the subject matter and provide feedback
>> +	   even though they are not maintainers.
>>   	L: Mailing list that is relevant to this area
>> +	   These lists should be CCed on patches.
>>   	W: Web-page with status/info
>>   	Q: Patchwork web based patch tracking system site
>>   	T: SCM tree type and location.  Type is one of: git, hg, quilt, stgit.
> 

At any rate, I like the idea of adding the additional descriptions for 
the categories, even if we still bike-shed on the wording or even the 
set of categories to use.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-11-15 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 10:57 [Qemu-devel] [PATCH RFC] MAINTAINERS: clarify some of the tags Cornelia Huck
2018-11-15 16:20 ` Cornelia Huck
2018-11-15 16:46   ` Eric Blake [this message]
2018-11-16 15:14     ` Cornelia Huck
2018-11-16 15:23       ` Eric Blake
2018-11-16 15:33         ` Cornelia Huck
2018-11-19 11:20           ` Peter Maydell
2018-11-15 18:32 ` 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=1c020087-acd7-302a-d5be-dcdbf7b7084d@redhat.com \
    --to=eblake@redhat.com \
    --cc=cohuck@redhat.com \
    --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).