Mozart governance procedure (continued!)

David Hopwood david.nospam.hopwood at blueyonder.co.uk
Wed Mar 9 03:23:11 CET 2005


Peter Van Roy wrote:
> Board members have exactly two weeks to vote.  After that delay their
> vote is automatically ABSTAIN [1].  The decision of the Board is
> computed from individual votes as follows:
> 
>     1. ACCEPT >= (2/3)*(ACCEPT+NEEDSWORK+REJECT)
>        The proposal is accepted.  The Board then gives the author
>        the appropriate rights to do the development, if it is a
>        standard track MEP.  The author becomes responsible for
>        developing and maintaining this part of the system.
> 
>     2. REJECT >= (1/3)*(ACCEPT+NEEDSWORK+REJECT)
>        The proposal is rejected, i.e., the author is discouraged to
>        continue work based on this MEP.  If the acceptance
>        condition holds also, the rejection is given priority, since
>        the proposal is strongly divisive.

If the REJECT criterion were REJECT > (1/3)*(ACCEPT+NEEDSWORK+REJECT)
(or similarly for ACCEPT), then it would not be possible for both
conditions to hold. That would be simpler.

-- 
David Hopwood <david.nospam.hopwood at blueyonder.co.uk>




More information about the mozart-hackers mailing list