Public SourceMage Discussion List

["Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>]

On Apr 17, Jeremy Blosser (emrys) [jblosser-smgl AT firinn.org] wrote:
> That's the summary of this proposal, and I think it's accurate.  The full
> docs are attached.

A couple of things have come up in discussion:

- A fatal flaw, if we have eg 23 developers and 20 of them are leads and 3
  of them are not, 2 of the 3 non-leads have all the veto power.  To fix
  this, I'm amending the proposal to allow leads to vote in vetos.  The
  intent of the veto is to allow a super majority of the full project to
  overrule the leads, so I think this is appropriate.

- Removal Votes require a super majority to pass.  This is so that Leads
  can't just easily throw out a new elected Lead they don't like that the
  General Developers have elected.  However, it means that if someone comes
  up for a removal vote through inactivity, it would still take a super
  majority to confirm their removal.  To fix this I'm amending the proposal
  so that the automated removal votes *pass* unless a simple majority votes
  opposed to them.

diff attached...
diff -ur d2/policy_developers now/policy_developers
--- d2/policy_developers        Tue Apr 18 11:35:02 2006
+++ now/policy_developers       Tue Apr 18 11:35:40 2006
@@ -21,8 +21,7 @@
 - have the option to cast a binding vote in all Lead Election votes.
 - have the option to cast a non-binding vote in all other votes.
 - can be removed by a super majority vote of the Lead Developers.
-- can have a removal vote vetoed by a super majority vote of the General
-  Developers.
+- can have a removal vote vetoed by a super majority vote of all Developers.
 - are automatically nominated and seconded for a removal vote after one year 
of
   inactivity (defined as no committed changes to any part of the project's
   source code or documentation repositories).
@@ -36,8 +35,7 @@
 - serve an unlimited term as long as they are not removed by vote.
 - can be removed as Leads by a super majority vote of the other Lead
   Developers.
-- can have a removal vote vetoed by a super majority vote of the General
-  Developers.
+- can have a removal vote vetoed by a super majority vote of all Developers.
 - are automatically removed without vote or veto if they fail to cast any 
votes
   for two consecutive months or longer, provided there were at least two 
votes
   hold in that period.
@@ -56,8 +54,7 @@
 - serve a one year term, with no limit on number of terms.
 - can be removed as Project or Component Leads by a super majority vote of 
the
   other Lead Developers.
-- can have a removal vote vetoed by a super majority vote of the General
-  Developers.
+- can have a removal vote vetoed by a super majority vote of all Developers.
 - remain Lead Developers if removed.
 
 Assistants:
diff -ur d2/policy_voting now/policy_voting
--- d2/policy_voting    Tue Apr 18 11:13:05 2006
+++ now/policy_voting   Tue Apr 18 11:34:53 2006
@@ -130,20 +130,26 @@
   Process described above, with the following exceptions:
   - The Developer in question MUST NOT vote.
   - Removal Votes require a super (67%) majority to pass.
-- Successful or failed removal votes MAY be vetoed by the General Developers.
+  - 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.
+- 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
+  automatically nominated and seconded for a Removal Vote every six months 
they
+  continue to be inactive.
 
-General Developer Veto Process:
-- The General Developers MAY veto any Developer Removal Votes and any Issue
-  Votes which would modify the Project's organizational structure or Voting
-  Policy.
+Veto Process:
+- The Developers MAY veto any Developer Removal Votes and any Issue Votes 
which
+  would modify the Project's organizational structure or Voting Policy.
 - Motions to veto MUST reach the Mailing List within 72 hours of the 
scheduled
   end of the vote in question.
 - Veto votes WILL proceed per the Issue Voting Process described above, with
   the following exceptions:
   - For Removal Votes, the Developer in question MUST NOT vote.
-  - Lead Developers MUST NOT vote.
+  - Lead Developers MAY vote, but are not required to.
   - General Developers MAY cast a binding vote.
-  - 51% of the General Developers MUST cast a vote, or the veto is invalid 
and
-    fails.
+  - 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.
 - Veto votes are final.

Attachment: pgppFkD_OLS5X.pgp
Description: PGP signature