From: Lars Kurth <larskurth@MacBook-Pro-3.local>
Date: Thu, 21 Jul 2016 15:19:55 +0000 (+0100)
Subject: Added comment sections to highight problem areas
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=75a64266c5ab9e02b76ecfa39b63519085dba52d;p=people%2Flarsk%2Fsecurity-process.git

Added comment sections to highight problem areas

These are marked by
<pre>
-------------------------------------------------------------------------
...
-------------------------------------------------------------------------
</pre>

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

diff --git a/governance.html b/governance.html
index 003a6b2..b84ee2f 100644
--- a/governance.html
+++ b/governance.html
@@ -51,11 +51,27 @@
 <p>The Xen Project is a meritocracy. The more you contribute the more responsibility
   you will earn. Leadership roles in Xen are also merit-based and earned
   by peer acclaim.</p>
+<pre>
+-------------------------------------------------------------------------------------
+I moved the "Roles" section up and split it into two sections with unmodified content
+- Xen Project Wide Roles
+- Project Team Roles
+-------------------------------------------------------------------------------------
+</pre>
 <p>
   <a id="roles"></a>
   <a id="roles-global"></a>
 </p>
 <h2>Xen Project Wide Roles</h2>
+<pre>
+-------------------------------------------------------------------------------------
+MINOR ISSUES TO BE ADDRESSED LATER: 
+- Sub-projects and Teams would benefit from some forward references to highlight the 
+  difference between incubation mature projects.
+- Also we should clarify what assets a sub-project owns. 
+- Add the role of Community Manager as it used throughout the document
+-------------------------------------------------------------------------------------
+</pre>
 <h3>Sub-projects and Teams</h3>
 <p>The Xen Project organizes itself into a number of sub-projects, which
   follow the <a href="#project-governance">Project Governance</a> (or
@@ -95,6 +111,16 @@
   <a id="roles-local"></a>
 </p>
 <h2>Project Team Roles</h2>
+<pre>
+-------------------------------------------------------------------------------------
+ISSUES TO BE ADDRESSED LATER: 
+- Fix minor Inaccuracies and Improvements
+- Allow for customization of roles by sub-projects (but this definition is the default)
+- Allow for Security Response Team
+- Allow for sub-projects to be lead by a Project Leadership Team (which may include a 
+  Project Lead)
+-------------------------------------------------------------------------------------
+</pre>
 <h3>Maintainers</h3>
 <p>Maintainers own one or several components in the Xen tree. A maintainer
   reviews and approves changes that affect their components. It is a
@@ -118,6 +144,11 @@
   project leads can also act as referees should disagreements amongst
   committers of the project arise. The project lead typically also has
   write access to resources, such as the web page of a specific project.</p>
+<pre>
+-------------------------------------------------------------------------------------
+Moved this section 
+-------------------------------------------------------------------------------------
+</pre>
 <p>
   <a id="contributions"></a>
 </p>
@@ -135,16 +166,49 @@
 <ul>
   <li><a href="/help/contribution-guidelines.html">Contribution Guidelines</a></li>
 </ul>
+<pre>
+-------------------------------------------------------------------------------------
+Consolidated all Decision Making Related topics into one section 
+- I changed the order of the sections from ...
+  "Consensus Decision Making, Conflict Resolution, Elections and Formal Votes" to 
+  "Consensus Decision Making, Formal Votes, Conflict Resolution, Elections"
+- I changed header titles and fixed the headline  
+
+Otherwise the relevant sections remain identical, with the exception of comment 
+sections that I added, which highlight issues that are to be addressed.
+-------------------------------------------------------------------------------------
+</pre>
 <p>
   <a id="decisions"></a>
 </p>
 <h2>Decision Making, Conflict Resolution, Role Nominations and Elections</h2>
+<pre>
+-------------------------------------------------------------------------------------
+ISSUES TO BE ADDRESSED LATER:
+- Add a pre-amble explaining the different decision making mechanisms and when they 
+  apply
+- Add a section about review and commit, which is the primary means of making 
+  code related decisions
+-------------------------------------------------------------------------------------
+</pre>
 <h3>Consensus Decision Making</h3>
+<pre>
+-------------------------------------------------------------------------------------
+ISSUES TO BE ADDRESSED LATER:
+- The "Consensus Decision Making" section is totally wrong. It does not describe 
+  "Lazy Consensus"
+-------------------------------------------------------------------------------------
+</pre>
 <p>Sub-projects or teams hosted on Xenproject.org are normally auto-governing
   and driven by the people who volunteer for the job. This functions
   well for most cases. When more formal decision making and coordination
   is required, decisions are taken with a lazy consensus approach: a
   few positive votes with no negative vote are enough to get going.</p>
+<pre>
+-------------------------------------------------------------------------------------
+- Introduce -2 to +2 voting under a new section
+-------------------------------------------------------------------------------------
+</pre>
 <p>Voting is done with numbers:</p>
 <ul>
   <li>+1 : a positive vote</li>
@@ -160,6 +224,14 @@
   <a id="conflict"> </a>
 </p>
 <h3>Conflict Resolution</h3>
+<pre>
+-------------------------------------------------------------------------------------
+ISSUES TO BE ADDRESSED LATER: 
+- Generalise refereeing in terms of Project Leadership instead of specific roles
+- Also some examples for sPecific situations that have happened in the past may be 
+  useful
+-------------------------------------------------------------------------------------
+</pre>
 <h4>Refereeing</h4>
 <p>Sub-projects and teams hosted on Xenproject.org are not democracies but
   meritocracies. In situations where there is disagreement on issues
@@ -180,6 +252,12 @@
   of mature projects will hold a private majority vote. If the vote is
   tied, the <a href="/join.html">Xen Project Advisory Board</a>  will break
   the tie through a casting vote.</p>
+<pre>
+-------------------------------------------------------------------------------------
+Changed headline structure: h2 to h3
+Removed Formal Votes from headline as it has been moved into a separate section
+-------------------------------------------------------------------------------------
+</pre>
 <h3>Elections</h3>
 <h4>Maintainer Elections</h4>
 <p>Developers who have earned the trust of maintainers (including the project
@@ -228,6 +306,18 @@
   <a id="formal-votes"></a>
 </p>
 <h2>Formal Votes</h2>
+<pre>
+-------------------------------------------------------------------------------------
+ISSUES TO BE ADDRESSED LATER: 
+- Local votes should be handled elsewhere: this section should only cover global
+  decision making
+- Better specify scope : when are Formal Votes applicable
+- In fact we do not have any clear rules for tallying votes (do votes have to be 
+  unanimous or not)
+- Note that the voting eligibility is maintainers? Do we want to retain this? 
+  I assume NO, as in practive we never did this.
+-------------------------------------------------------------------------------------
+</pre>
 <p>Sometimes it is necessary to conduct formal voting within the community
   (outside of elections). Formal votes are necessary when processes and
   procedures are introduced or changed, or as part of the
@@ -274,6 +364,12 @@
 <p>
   <a id="project-governance"></a>
 </p>
+<pre>
+-------------------------------------------------------------------------------------
+ISSUES TO BE ADDRESSED LATER: 
+- Verify terminology in light of changes above
+-------------------------------------------------------------------------------------
+</pre>
 <h2>Project Governance</h2>
 <h3>Basic Project Life Cycle</h3>
 <p>The proposal is to follow a simple basic flow:</p>