Re: [vote] MRFC 0026: On-Site Toolbar Management for MidCOM 2.6+

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+1 for more Apache-compatible process. Who shall revise the mRFC  
process mRFC?


On Mar 6, 2006, at 11:09, Johan Bernhardsson wrote:

> +1 :)
>
> /Johan
>
> On Mon, 2006-03-06 at 11:03 +0200, Jukka Zitting wrote:
>> Hi,
>>
>> On 3/6/06, Torben Nehmer <[email protected]> wrote:
>>>> A situation calling for an update to the mRFC process. How about
>>>> adopting the Apache lazy consensus rules?
>>>
>>> In short: What it is about?
>>
>> The Apache voting rules for code modifications (essentially what  
>> mRFCs
>> are for) normally require three +1 votes and no -1 votes (all
>> committers have a veto right). Lazy consensus is a relaxed form of
>> these rules where at least a single +1 and no -1 votes will be enough
>> to pass a vote.
>>
>> See http://www.apache.org/foundation/voting.html for more details.
>>
>> BR,
>>
>> Jukka Zitting
>>
>> --
>> Yukatan - http://yukatan.fi/ - [email protected]
>> Software craftsmanship, JCR consulting, and Java development
> -- 
> Johan Bernhardsson
>
> Linux/CMS/Network Consultant
>
> Phone:  +46-13-73244
> Mobile: +46-705-111751
> Fax:    +46-13-73190
> Email/Jabber/Sip:  [email protected]
> Web:    www.anykey.se

Henri Bergius
Consultant Partner, Nemein
henri.bergius-ZpG/[email protected]

Midgard CMS
www.midgard-project.org



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEDABwNkT8k497k9IRAuR5AKDUNbpnJsvkwJKdhlZZHX87seNJkACbBYNh
wrZrCXsR8mKkmZfQrnjLHp8=
=LTLP
-----END PGP SIGNATURE-----