Added Leadership Voting rules in line with comments section

Signed-off-by: Lars Kurth <lars.kurth@citrix.com>

diff --git a/.DS_Store b/.DS_Store
new file mode 100644 (file)
index 0000000..a3c5e35
Binary files /dev/null and b/.DS_Store differ

diff --git a/governance.html b/governance.html
index a69f3fe3ba91496560c430913fe3766d36f1137a..2d4987e37bc9165c6a1c912c8a83c904dbfd3b77 100644 (file)
--- a/governance.html
+++ b/governance.html
@@ -454,18 +454,15 @@ This section attempts to
 <pre>
 -------------------------------------------------------------------------------------
 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.
 -------------------------------------------------------------------------------------
 </pre>
-<p>Decisions (also called Resolutions) require a <b>2/3rd</b> 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.</p>
+<p>Decisions (also called Resolutions) require a <b>2/3rd</b> 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 <a href="#exceptional-circumstances">
+  leadership team to function</a>.</p>
 <p>Leadership team decisions normally have to be made actively: in other
   words each team member has to cast a vote <b>explicitly</b> 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.</p>
 <p><u>Passed/Failed Resolutions:</u></p>
+<p>Voting is conducted in line with the following rules:</p>
 <ul>
-  <li>TODO</li>
+  <li>Project leadership team members vote for (<b>+1</b>) or against 
+    (<b>-1</b>) a resolution. There is no differentiation between <b>+1</b>/
+    <b>+2</b> and <b>-1</b>/<b>-2</b>: in other words a <b>+2</b> is counted
+    as a vote for, a <b>-2</b> as a vote against the resolution. The number of
+    votes for and against a resolution is called <b>active vote</b>. <b>0</b> 
+    votes <b>are not counted</b> as an active vote.
+  </li>
+  <li>A <b>quorum of more than 50% of active votes</b> 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.</li>
+  <li>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:
+    <table>
+      <tr>
+        <th width="175px" align="left">Active Votes</th>
+        <td width="25px">10</td>
+        <td width="25px">9</td>
+        <td width="25px">8</td>
+        <td width="25px">7</td>
+        <td width="25px">6</td>
+        <td width="25px">5</td>
+        <td width="25px">4</td>
+        <td width="25px">3</td>
+        <td width="25px">2</td>
+      </tr>
+      <tr>
+        <th align="left">+1 votes needed to pass</th>
+        <td>7</td>
+        <td>6</td>
+        <td>6</td>
+        <td>5</td>
+        <td>4</td>
+        <td>4</td>
+        <td>3</td>
+        <td>2</td>
+        <td>2</td>
+      </tr>
+    </table>
+   </li>
 </ul>
 <pre>
 -------------------------------------------------------------------------------------
-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:
   <li>A codeline</li>
   <li>A sub-project or team portal on Xenproject.org (in an area separate
     from mature projects)</li>
-  <li>A wiki page on <a href="http://wiki.xenproject.org">wiki.xenproject.org</a>    (this is expected to be maintained by the project lead)</li>
+  <li>A wiki page on <a href="http://wiki.xenproject.org">wiki.xenproject.org</a>
+    (this is expected to be maintained by the project lead)</li>
 </ul>
 <h3>Incubating a Project</h3>
 <p>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</li>
   <li>The project's wiki pages will be tagged as <strong>archived</strong>.
     A project may be completed (i.e. it has achieved its goals and/or
-    fulfilled its charter) in which case it is tagged as <strong>completed</strong>    and <strong>archived</strong>.</li>
+    fulfilled its charter) in which case it is tagged as <strong>completed</strong>
+    and <strong>archived</strong>.</li>
   <li>The project or team portal on Xenproject.org will be moved into an
-    <strong>Archive</strong> section. We may have a <strong>Completed</strong>    section within the <strong>Archive</strong> section.</li>
+    <strong>Archive</strong> section. We may have a <strong>Completed</strong>
+    section within the <strong>Archive</strong> section.</li>
 </ul>
 <p>In cases where the project has delivered code into other sub-projects
   hosted on Xenproject.org, the code will be</p>
@@ -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)</li>
 </ul>
+<p>
+  <a id="exceptional-circumstances"> </a>
+</p>
 <h3>Exceptional Circumstances</h3>
 <h4>Incubation Projects without Project Lead</h4>
 <p>Projects which lose their project lead during the incubation phase, and
@@ -976,7 +1018,8 @@ ISSUES TO BE ADDRESSED LATER:
       </ul>
     </li>
     <li><strong>v2.1 May 2016:</strong> Clarify Committer Elections
-      as per this <a href="http://lists.xenproject.org/archives/html/xen-devel/2016-05/msg00801.html">discussion</a>      and <a href="http://lists.xenproject.org/archives/html/xen-devel/2016-05/msg01614.html">vote</a></li>
+      as per this <a href="http://lists.xenproject.org/archives/html/xen-devel/2016-05/msg00801.html">discussion</a>
+      and <a href="http://lists.xenproject.org/archives/html/xen-devel/2016-05/msg01614.html">vote</a></li>
     <li><strong>v2.0 May 2012:</strong> Changes to reflect transition from
       xen.org to xenproject.org
       <ul>
@@ -993,7 +1036,8 @@ ISSUES TO BE ADDRESSED LATER:
         <li>Refer to sub-projects and teams instead of projects where appropriate</li>
       </ul>
     </li>
-    <li><strong><a href="index.php?option=com_content&amp;view=archive&amp;year=2013&amp;month=3">v1.2</a> May 2012:</strong>      Minor changes
+    <li><strong><a href="index.php?option=com_content&amp;view=archive&amp;year=2013&amp;month=3">v1.2</a> May 2012:</strong>
+      Minor changes
       <ul>
         <li>Fixed typo and ambiguity in the role of Project Lead.</li>
         <li>Added section on Conflict Resolution.</li>