xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Cc: sstabellini@kernel.org, Wei Liu <wei.liu2@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <jbeulich@suse.com>, Ian Campbell <ijc@xen.org>
Subject: Re: [RFC] Minor change to governance document at http://www.xenproject.org/developers/governance.html
Date: Wed, 27 Apr 2016 11:57:57 +0100	[thread overview]
Message-ID: <57209B35.8010102@citrix.com> (raw)
In-Reply-To: <9F9D95F3-2842-4BEC-A092-62665A5B190E@gmail.com>

On 26/04/16 12:48, Lars Kurth wrote:
> Hi all,
> 
> following the recent process to elect new maintainers and committers, 
> I would like to suggest the following minor change to our governance 
> document. I believe the process we ran recently worked well, so we 
> should change the governance accordingly. I don't think we need to 
> change the governance to remind the community at least annually of 
> the process, but we should use the appointments@ alias, such that 
> community members can nominate new committers in private.
> 
> Here is the relevant snippet from 
> http://www.xenproject.org/developers/governance.html
> ---
> Committer Elections
> 
> Developers who have earned the trust of committers in their project 
> (including the project lead) can through election be promoted to 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> can 
> [the (including the project lead) makes no sense]
> 
> Committer. A two stage mechanism is used
> 
> * Nomination: A committers should nominate a community member publicly 
>               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>               Community members should nominate candidates by posting 
>               a proposal to appointments at xenproject dot org                                             
> 
> explaining the candidate's contributions to the project and thus why 
> they should be elected 
> 
> as a maintainer on the project's public mailing list. 
> 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> to become a Committer of the project.
> [Typo: this should have been Committer in the first place]
> 
> The nomination should include a project, cite evidence such as patches  
>                ^^^^^^^^^^^^^^^^^^^^^^^^^
>                should
> [the "include a project" makes no sense]
>  
> and other contributions where the case is not obvious. 
>                                                        ^^^^ 
>                                                        Existing 
> Committers will review all proposals, check whether the nominee 
> would be willing to accept the nomination and publish suitable 
> nominations on the project's public mailing list for wider 
> community input.
>                                                                             
> ---
> 
> In the nomination e-mail, we can then use what we used in 
> https://www.mail-archive.com/xen-devel@lists.xen.org/msg63365.html
> ---
> == Providing Feedback ==
> We are inviting community members to provide comments regarding the 
> nomination of <PERSON>. As feedback may be personal and may make 
> nominees uncomfortable, we are asking you to provide feedback by 
> sending a private mail to appointments at xenproject dot org *before* 
> <DATE> (please do *not* CC xen-devel@). 
> 
> If you want to congratulate the nominee, it is of course OK to do 
> this in public. Please use your judgement and common sense.
> ---
> 
> This is in line with what we have done earlier this month, and seems
> to be a better approach than requiring discussions about nominations
> to be public from the beginning. Public discussions about a 
> candidates track record may necessarily become personal and thus may 
> prevent good candidates from being nominated.
> 
> Any views?

This all seems reasonable:

Acked-by: George Dunlap <george.dunlap@citrix.com>


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

  reply	other threads:[~2016-04-27 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 11:48 [RFC] Minor change to governance document at http://www.xenproject.org/developers/governance.html Lars Kurth
2016-04-27 10:57 ` George Dunlap [this message]
2016-04-27 15:45 ` Wei Liu
2016-04-28 18:26 ` Konrad Rzeszutek Wilk
2016-05-04 10:14   ` Lars Kurth

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=57209B35.8010102@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ijc@xen.org \
    --cc=jbeulich@suse.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=sstabellini@kernel.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 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).