[apparmor] proposal - Commit Policy update

[John Johansen]

On 08/10/2010 11:15 AM, Jamie Strandboge wrote:
> On Tue, 2010-08-10 at 04:59 -0400, John Johansen wrote:
>> I would like to update the commit policy to include a rule pertaining
>> to NAKs.  Basically I don't want AppArmor to have a situation where one
>> core dev has veto power, so that a single NAK can kill a proposed change.
>>
>> What I propose is this (or something like it),
>>
>> A NAK from a core dev should be taken with due consideration but
>> ACKs from two other core devs can override it if necessary.
>>
> 
> I am going to abstain from voting but will say I feel that the commit
> policy should be stronger still. If a core developer has a strong enough
> objection to NAK, then perhaps at least 3 core developers should be
> required to ACK it. If this stifles innovation and/or getting the job
> done, we can reevaluate.
> 
I'm fine with that, basically I didn't want to set the bar too high
as there are currently a limited number of core devs, but I think
3 is a good number, too.