Re: Comments on bylaws

[Stefan Bodewig <bo...@apache.org>]

On Fri, 31 Jan 2003, Costin Manolache <cm...@yahoo.com> wrote:
> Stefan Bodewig wrote:

>> I appreciate that you've left out any automatic promotion from
>> committer to PMC member, even vaguely hinted ones like "typically
>> happens after six months".
> 
> I would preffer it qualified as "six months of active
> contributions".

As I said, I'm happy without saying anything about a timeframe at all.

> Contribution = code, review, docs, mailing list

+1

> AFAIK adopting a codebase is a majority decision in jakarta. 

It is, but we could do it our own way 8-)

Later in that thread I agreed to Conor's suggestion to require 2/3
majority for this.

> I personally preffer we define "consensus" as 2/3 - instead of
> unanimity.

No.  I'd rather have both, consensus and 2/3 majority decisions and
make clear which type of decision is used where.

> Removing a PMC member or breaking a veto or changing the charter
> should be done with a 2/3 vote,

Removing a PMC member should be unanimous IMHO.  Breaking a veto is a
different thing.  If the veto is valid, it cannot be broken, no matter
which majority.  If it is not valid, it is void.

> and I would add a requirement on asking for board feedback.

I hope we'll never get into this situation, and I'm sure we'll consult
the board if it will ever come to this.

Stefan

Re: Comments on bylaws

[Nicola Ken Barozzi <ni...@apache.org>]

Stefan Bodewig wrote:

>Breaking a veto is a
> different thing.  If the veto is valid, it cannot be broken, no matter
> which majority.  If it is not valid, it is void.

Correct. Valid vetos cannot be broken or overruled.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------

Re: Comments on bylaws

[Conor MacNeill <co...@cortexebusiness.com.au>]

Thanks for the feedback - I've done an update with the following changes

1. Increase inactivity period to six months
2. Form of contibution not limited to code
3. Definition of 2/3 majority approval and rationale
4. Definition of codebase adoption action with 2/3 majority approval
5. Addition of removal actions with consensus approval. Also added
    a requirement for the PMC chair to inform the board of such actions
6. Voting timeframes.

Conor