community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1135791 - /comdev/site/trunk/content/committers/index.mdtext
Date Tue, 14 Jun 2011 20:59:34 GMT
Author: rgardler
Date: Tue Jun 14 20:59:34 2011
New Revision: 1135791

Add a section on decision making


Modified: comdev/site/trunk/content/committers/index.mdtext
--- comdev/site/trunk/content/committers/index.mdtext (original)
+++ comdev/site/trunk/content/committers/index.mdtext Tue Jun 14 20:59:34 2011
@@ -20,20 +20,38 @@ Information that is useful to Apache com
 This page is intended to be an index of useful resources. This site is editable by 
 any Apache Committer, feel free to add anything useful here.
-## Project Independence
+## Decision making
+Decisions in Apache projects are the result of:
+  - action
+  - consensus in the community 
+We have, over the years, developed a very simple and effective approach to 
+consensus building and decision making. The vast majority of decisions are made
+using [lazy consensus][1], if the "lazy" approach to consensus building is deemed
+unsuitable for a particular decision then we seek to [build consensus][2] within
+the community. Very occasionally, usually for formal reasons relating to legal 
+responsibilities, it is necessary to call a [vote][3].
+Each of these three approaches is described more fully on various foundation 
+and project sites. However, we've provided an initial introduction to [decision
+making][4] here on the community development site.
+## Project independence
 While not all aspects of the Apache Way are practiced the same way by 
 all projects at the ASF, there are a number of rules that Apache 
 projects are required to follow – things like complying with PMC 
-[release voting][1], [legal policy][2], [brand policy][3], 
-using [mailing lists][4], etc., which are [documented in various places][5]. 
+[release voting][5], [legal policy][6], [brand policy][7], 
+using [mailing lists][8], etc., which are [documented in various places][9]. 
 One of these invariant rules is that projects are managed and used
 independently of any commercial interests. The goal is to create an 
 environment in which all participants are equal and thus have an equal
 opportunity to contribute to and benefit from our software, regardless
 of motivation or financial objectives. This is discussed in more detail
-in our document [Project Independence][6].
+in our document [Project Independence][10].
 <a name="Index-Assistingwithprojectmanagement"></a>
 ## Assisting with project management
@@ -49,9 +67,13 @@ activities, although non-committers can 
  * [Board Reports](/boardreport.html)
-  [1]:
-  [2]:
-  [3]:
-  [4]:
-  [5]:
-  [6]: /projectIndependence.html
\ No newline at end of file
+  [1]: /committers/lazyConsensus.html
+  [2]: /committers/consensusBuilding.html
+  [3]: /committes/voting.html
+  [4]: /committers/decisionMaking.html
+  [5]:
+  [6]:
+  [7]:
+  [8]:
+  [9]:
+  [10]: /projectIndependence.html
\ No newline at end of file

View raw message