openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1242202 - /incubator/ooo/site/trunk/content/openofficeorg/get-involved.mdtext
Date Thu, 09 Feb 2012 01:41:33 GMT
Author: robweir
Date: Thu Feb  9 01:41:33 2012
New Revision: 1242202

Move decision making content here to the Community FAQ's


Modified: incubator/ooo/site/trunk/content/openofficeorg/get-involved.mdtext
--- incubator/ooo/site/trunk/content/openofficeorg/get-involved.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/get-involved.mdtext Thu Feb  9 01:41:33
@@ -41,49 +41,12 @@ the community. The project team and the 
 therefore welcome and encourage participation, and attempt to make it 
 as easy as possible for people to get involved. 
-We maintain a list of specific areas where we need volunteers on our [Help Wanted] [15] page
of the wiki.
+We maintain a list of specific areas where we need volunteers on our [Help Wanted] [10] page
of the wiki.
 ## Mailing lists
 Your first engagement with the project should be to subscribe to our
-[mailing lists][14].
-## Decision Making
-The most important thing about engaging with any Apache project is that everyone
-is equal. All people with an opinion are entitled to express that opinion and, where 
-appropriate, have it considered by the community.
-To some the idea of having to establish consensus in a large and distributed team 
-sounds inefficient and frustrating. Don't despair though, The Apache Way has a
-set of simple processes to ensure things proceed at a good pace.
-In ASF projects we don't like to vote. We reserve that for the few things that need 
-official approval for legal or process reasons (e.g. a release or a new committer). 
-Most of the time we work with the consensus building techniques documented below.
-### Lazy Consensus
-[Lazy consensus][10] is the first, and possibly the most important, consensus building 
-tool we have. Essentially lazy consensus means that you don't need to get explicit
-approval to proceed, but you need to be prepared to listen if someone objects.
-### Consensus Building
-Sometimes lazy consensus is not appropriate. In such cases it is necessary to
-make a proposal to the mailing list and discuss options. There are mechanisms
-for quickly showing your support or otherwise for a proposal and 
-[building consensus][11] amongst the community.
-Once there is a consensus people can proceed with the work under the [lazy 
-consensus][12] model.
-### Voting
-Occasionally a "feel" for consensus is not enough. Sometimes we need to 
-have a measurable consensus. For example, when [voting][13] in new committers or 
-to approve a release. 
+[mailing lists][11].
   [1]: mailto://
@@ -95,9 +58,5 @@ to approve a release. 
-  [10]: /openofficeorg/docs/governance/lazyConsensus.html
-  [11]: /openofficeorg/docs/governance/consensusBuilding.html
-  [12]: /openofficeorg/docs/governance/lazyConsensus.html
-  [13]: /openofficeorg/docs/governance/voting.html
-  [14]:/openofficeorg/mailing-lists.html
-  [15]:
\ No newline at end of file
+  [10]:
+  [11]:/openofficeorg/mailing-lists.html
\ No newline at end of file

View raw message