incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <br...@apache.org>
Subject Re: [VOTE] Change the project bylaws to modify the PMC Chair voting process and add a term length
Date Mon, 04 Mar 2013 16:36:13 GMT
+1 (to the text, and overall - thanks!)

On 05/03/2013, at 2:33 AM, Chip Childers <chip.childers@sungard.com> wrote:

> On Fri, Mar 01, 2013 at 11:16:36AM -0500, Chip Childers wrote:
>> Hi all,
>> 
>> As previously discussed [1], we'd like to make a change to our bylaws
>> [2] to modify the method of selecting a PMC chair.  We also want to add 
>> a term for the chair.
>> 
>> [1] http://markmail.org/message/ifwwce657u36yuwz
>> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Apache+CloudStack+Project+Bylaws
>> 
>> 
>> 
>> Below are the specific changes I'd like you to vote on:
>> 
>> (1) A change to bylaw section 2.4.5 as follows:
>> 
>> CURRENT:
>> 
>>  2.4.5. If the current chair of the PMC resigns, the PMC votes to
>>  recommend a new chair using Single Transferable Vote (STV) voting.
>>  See http://wiki.apache.org/general/BoardVoting for specifics. The
>>  decision must be ratified by the Apache board.
>> 
>> PROPOSED:
>> 
>>  2.4.5. If the current chair of the PMC resigns, or the term of the 
>>  current chair expires, the PMC votes to
>>  recommend a new chair through consensus via a lazy 2/3 majority 
>>  voting method.  In the case that consensus is not achieved, the PMC
>>  will vote for a chair using Single Transferable Vote (STV) voting.
>>  Due to the fact that the discussions are about specific individuals, 
>>  this vote would be held on the cloudstack-private mail list.
>>  The decision must be ratified by the Apache board.
>> 
>> (2) The addition of a new bylaw section: 2.4.6:
>> 
>> PROPOSED:
>> 
>>  2.4.6. The role of PMC chair will have a one year term.  The intention
>>  of this term is to allow for a rotation of the role amongst the PMC
>>  members.  This intention does not prohibit the PMC from selecting the
>>  same chair to serve consecutive terms.
>> 
>> 
>> 
>> Per our bylaws (section 3.4.9), this change requires a lazy majority of
>> PMC members to pass.
>> 
>> The whole community is encouraged to vote on this issue!
>> 
>> This vote will be open for at least 72 hours.
>> 
>> Please respond with one of the following:
>> 
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> Thanks!
>> 
>> -chip
> 
> In response to Brett's question on the related DISCUSS thread, I'd like
> to clarify the proposed 2.4.5. text as follows:
> 
>   2.4.5. If the current chair of the PMC resigns, or the term of the 
>   current chair expires, the PMC will attempt to reach consensus on a new
>   chair through discussion, confirming that consensus via a vote to
>   recommend a new chair using a lazy 2/3 majority voting method.  
>   In the case that consensus is not achieved, the PMC
>   will vote for a chair using Single Transferable Vote (STV) voting.
>   Due to the fact that the discussions are about specific individuals, 
>   this vote would be held on the cloudstack-private mail list.
>   The decision must be ratified by the Apache board.
> 
> The relevant change above is to explain that the PMC will attempt to reach
> consensus on a name for the chair position via discussion, and then confirm 
> that via a 2/3 majority vote.  STV will only be used in the case of discussion
> not leading to a consensus.
> 
> I believe that the spirit of the text remains the same, but is a bit more clear 
> now.  Unless there are any objections, I'll assume we can keep this vote thread 
> going as a vote on the clarified text above.
> 
> I'll keep this vote open for another day, and close it out tomorrow.
> 
> -chip

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






Mime
View raw message