Public SourceMage Discussion List

[Jaka Kranjc <jakakranjc AT email.si>]

Seconded.

On Friday 05 May 2006 15:53, Jeremy Blosser (emrys) wrote:
> I move for the following amendment:
>
> diff -dupr approved/policy_voting amend1/policy_voting
> --- approved/policy_voting      Tue Apr 18 11:34:53 2006
> +++ amend1/policy_voting        Fri May  5 08:49:22 2006
> @@ -83,8 +83,9 @@ Lead Voting Process:
>    of the vote to be valid.
>  - Lead Developers MUST cast a vote.
>  - General Developers MAY cast a vote.
> -- 51% of the Lead Developers MUST cast a vote, or the vote is invalid.
> -- Votes require a simple (51%) majority to pass.
> +- More than 50% of the Lead Developers MUST cast a vote, or the vote is
> +  invalid.
> +- Votes require a simple majority (greater than 50% of all votes cast) to
> pass. - If no quorom or majority is achieved, and the vote is for a Project
> or Component lead, and the incumbent is a valid candidate, they are
> reelected. If there is no incumbent or they have not accepted a nomination,
> the position @@ -119,9 +120,10 @@ Issue Voting Process:
>  - Lead Developers MUST cast a vote.
>  - General Developers MAY cast a vote, but their votes are advisory only
> (i.e., non-binding).
> -- 51% of the Lead Developers MUST cast a vote, or the vote is invalid and
> -  fails.
> -- Votes require a simple (51%) majority (of all binding votes cast) to
> pass. +- More than 50% of the Lead Developers MUST cast a vote, or the vote
> is +  invalid and fails.
> +- Votes require a simple majority (greater than 50% of all binding votes
> cast) +  to pass.
>  - Motions which pass are considered active immediately upon the majority
> vote reaching the Mailing List.
>
> @@ -129,10 +131,12 @@ Developer Removal Voting Process:
>  - General and Lead Developer Removal Votes WILL proceed per the Issue
> Voting Process described above, with the following exceptions:
>    - The Developer in question MUST NOT vote.
> -  - Removal Votes require a super (67%) majority to pass.
> +  - Removal Votes require a super majority (greater than 2/3 of all
> binding +    votes cast) to pass.
>    - Exception to the above: Automatic Removal Votes (triggered by
> inactivity as specified in the Developer Organization document)
> automatically pass unless -    a simple (51%) majority vote against the
> removal.
> +    a simple majority (greater than 50% of all binding votes cast) vote
> against +    the removal.
>  - Successful or failed removal votes MAY be vetoed by the entire group of
>    Developers.
>  - If an Automated Removal Vote fails fails, the Developer in question WILL
> be @@ -149,7 +153,8 @@ Veto Process:
>    - For Removal Votes, the Developer in question MUST NOT vote.
>    - Lead Developers MAY vote, but are not required to.
>    - General Developers MAY cast a binding vote.
> -  - 51% of the Developers (Lead + General Developers) MUST cast a vote, or
> the -    veto is invalid and fails.
> -  - Vetos require a super (67%) majority to pass.
> +  - More than 50% of the Developers (Lead + General Developers) MUST cast
> a +    vote, or the veto is invalid and fails.
> +  - Vetos require a super majority (greater than 2/3 of all votes cast) to
> +    pass.
>  - Veto votes are final.