From 79d472a471e82b8b0fd3a3d1cc1c98de8380c09a Mon Sep 17 00:00:00 2001 From: Lars Kurth Date: Wed, 10 Aug 2016 17:50:18 +0100 Subject: [PATCH] Added Leadership Voting rules in line with comments section Signed-off-by: Lars Kurth --- .DS_Store | Bin 0 -> 6148 bytes governance.html | 78 +++++++++++++++++++++++++++++++++++++----------- 2 files changed, 61 insertions(+), 17 deletions(-) create mode 100644 .DS_Store diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000000000000000000000000000000000000..a3c5e35ceb061fca8f7d6221b2d6c96e753d66af GIT binary patch literal 6148 zcmeHK%}T>S5dOASsrF!x9s^#AV4+W7C{^&>2hcYCg`_Dq5xnK8diDY+ z$g``XgBcdcO3%+6U+u<{wBH}+SpfmjP1_(1Dg&LI#jC+Cit2#$0hl_b#HO9*9O!_s)*zj4!0#7*sYkkvK3!Yt ------------------------------------------------------------------------------------- The exact majority needed is up for discussion: 2/3rd majority is just a stake -in the ground. Also, I think the differentiation between active and inactive -leadership team members is a little clumsy and may not be necessary (see discussion -below). +in the ground. However, the examples below show that this seems to be a sensible +approach to decision making. ------------------------------------------------------------------------------------- -

Decisions (also called Resolutions) require a 2/3rd majority amongst - active leadership team members. If a leadership team member has been - inactive for more than two months (i.e. the member has not engaged - with the community or leadership team for two months or more), the - team member is not considered to be part of the leadership team. - This avoids paralysis within the leadership team, if leadership team - members dissappear.

+

Decisions (also called Resolutions) require a 2/3rd majority + amongst active leadership team members in favour of a proposal. The + tallying of votes follows the rules outlined below. Note that a minimum of + 3 leadership team members is needed for a + leadership team to function.

Leadership team decisions normally have to be made actively: in other words each team member has to cast a vote explicitly expressing their opinion. The only exception are face-2-face or on-line meetings @@ -474,12 +471,51 @@ below). for decision on a resolution and asks for objections. This allows to conduct meetings more quickly.

Passed/Failed Resolutions:

+

Voting is conducted in line with the following rules:

    -
  • TODO
    • +
  • Project leadership team members vote for (+1) or against + (-1) a resolution. There is no differentiation between +1/ + +2 and -1/-2: in other words a +2 is counted + as a vote for, a -2 as a vote against the resolution. The number of + votes for and against a resolution is called active vote. 0 + votes are not counted as an active vote. +
    • +
  • A quorum of more than 50% of active votes is required for a + resolution to pass. In other words, if the leadership team has 7 members, at + least 4 active votes are required for a resolution to pass.
    • +
  • The resolution passes, if a 2/3 majority of active votes is in favour of + it. The table below maps active votes against votes needed to pass: + + + + + + + + + + + + + + + + + + + + + + + + + +
    Active Votes1098765432
    +1 votes needed to pass766544322
    + 
 -------------------------------------------------------------------------------------
-We should discuss the exact mechanism by which we tally the votes 
+This comment section contains some examples that have influenced the section above. 
 
 Let me express this as an algorithm.
 
@@ -840,7 +876,8 @@ ISSUES TO BE ADDRESSED LATER:
   
  • A codeline
    • 
   
  • A sub-project or team portal on Xenproject.org (in an area separate
     from mature projects)
    • 
-  
  • A wiki page on wiki.xenproject.org    (this is expected to be maintained by the project lead)
    • 
+  
  • A wiki page on wiki.xenproject.org
+    (this is expected to be maintained by the project lead)
    • 
 
 
    Incubating a Project
    
 
    The purpose of the incubation phase is for a project to show that it
@@ -925,9 +962,11 @@ ISSUES TO BE ADDRESSED LATER:
     from an archived projects section on Xenproject.org
   
  • The project's wiki pages will be tagged as archived.
     A project may be completed (i.e. it has achieved its goals and/or
-    fulfilled its charter) in which case it is tagged as completed    and archived.
    • 
+    fulfilled its charter) in which case it is tagged as completed
+    and archived.
   
  • The project or team portal on Xenproject.org will be moved into an
-    Archive section. We may have a Completed    section within the Archive section.
    • 
+    Archive section. We may have a Completed
+    section within the Archive section.
 
 
    In cases where the project has delivered code into other sub-projects
   hosted on Xenproject.org, the code will be
    
@@ -937,6 +976,9 @@ ISSUES TO BE ADDRESSED LATER:
     have to) remove the code in a subsequent release (it should however
     give users sufficient time to adapt)
 
+
    
+   
+
    
 
    Exceptional Circumstances
    
 
    Incubation Projects without Project Lead
    
 
    Projects which lose their project lead during the incubation phase, and
@@ -976,7 +1018,8 @@ ISSUES TO BE ADDRESSED LATER:
       
     
     
  • v2.1 May 2016: Clarify Committer Elections
-      as per this discussion      and vote
    • 
+      as per this discussion
+      and vote
     
  • v2.0 May 2012: Changes to reflect transition from
       xen.org to xenproject.org
       
      
@@ -993,7 +1036,8 @@ ISSUES TO BE ADDRESSED LATER:
         
    • Refer to sub-projects and teams instead of projects where appropriate
      • 
       
    
     
    • 
-    
  • v1.2 May 2012:      Minor changes
+    
  • v1.2 May 2012:
+      Minor changes
       
      
         
    • Fixed typo and ambiguity in the role of Project Lead.
      • 
         
    • Added section on Conflict Resolution.
      • 
-- 
2.39.5