You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by ro...@apache.org on 2012/02/09 02:38:15 UTC
svn commit: r1242201 -
/incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext
Author: robweir
Date: Thu Feb 9 01:38:14 2012
New Revision: 1242201
URL: http://svn.apache.org/viewvc?rev=1242201&view=rev
Log:
Move decision making content here from the "how to participate" page
Modified:
incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext
Modified: incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext?rev=1242201&r1=1242200&r2=1242201&view=diff
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/community-faqs.mdtext Thu Feb 9 01:38:14 2012
@@ -16,5 +16,48 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
+## How are decisions made in the project?
+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.
+
+
+### What is "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.
+
+### What about 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.
+
+
+
+ [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]: https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted
\ No newline at end of file