Release votes are expected to be a decision of the list of people
empowered by the foundation to make that decision.  How that list
of people is populated for podlings is up to the PMC.  Right now,
the only list we have is the IPMC itself, as appointed by the board.

If the Incubator wants to create separate subcommittees to mimic the
operations of podling PMCs, with the subcommittee delegated the
right to mint incubating releases and the subcommittee membership
recorded in an appropriate place for Incubator committee records,
that would meet my approval.

The purpose of this requirement is to protect the folks who make
release decisions (i.e., to provide a corporate record of their right
to do an ASF release, since most of them have no other employment,
contract, or officer role to back them up).

....Roy

On Nov 10, 2013, at 7:34 AM, Joseph Schaefer wrote:

> Unlikely to get at least Roy’s approval because release
> votes are expected to be a decision of the full committee,
> not any one member of it.
> 
> On Nov 10, 2013, at 10:29 AM, Alan D. Cabrera <l...@toolazydogs.com> wrote:
> 
>> 
>> On Nov 10, 2013, at 1:04 AM, ant elder <ant.el...@gmail.com> wrote:
>> 
>>> How about simply changing the rules for Incubator releases so that
>>> they don't require at least three binding votes, but instead make it
>>> at least three votes only one of which must be binding. That would
>>> mean there would still be the element of oversight that a mentor vote
>>> gives but avoids all the problems with not having three mentors. I'm
>>> sure the board would grant the Incubator authority to implement that
>>> change.
>> 
>> The board has charged us to vet the podlings and their releases.  What 
>> process is used is up to us.
>> 
>> I would prefer a variant of your proposal.  The first release needs three 
>> mentor/IPMC votes.  Subsequent releases only require one mentor/IPMC vote.
>> 
>> 
>> Regards,
>> Alan
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to