rave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgard...@apache.org
Subject svn commit: r1096051 - /incubator/rave/site/trunk/content/rave/get-involved.mdtext
Date Fri, 22 Apr 2011 21:35:26 GMT
Author: rgardler
Date: Fri Apr 22 21:35:26 2011
New Revision: 1096051

URL: http://svn.apache.org/viewvc?rev=1096051&view=rev
Log:
Add some basic information on decision making and link to the detail docs

Modified:
    incubator/rave/site/trunk/content/rave/get-involved.mdtext

Modified: incubator/rave/site/trunk/content/rave/get-involved.mdtext
URL: http://svn.apache.org/viewvc/incubator/rave/site/trunk/content/rave/get-involved.mdtext?rev=1096051&r1=1096050&r2=1096051&view=diff
==============================================================================
--- incubator/rave/site/trunk/content/rave/get-involved.mdtext (original)
+++ incubator/rave/site/trunk/content/rave/get-involved.mdtext Fri Apr 22 21:35:26 2011
@@ -17,7 +17,7 @@ Notice:    Licensed to the Apache Softwa
            under the License.
 
 You don't need to be a software developer to contribute to 
-Apache Rave. To be succesful this project 
+Apache Rave. To be successful this project 
 requires a huge range of different skills, levels of involvement and degrees of 
 technical expertise. So, if you want to get involved in Apache Rave, there 
 is almost certainly a role for you. 
@@ -41,11 +41,52 @@ 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. 
 
+## Mailing lists
+
 Your first engagement with the project should be to subscribe to our
 mailing list by sending a mail to 
 [rave-dev-subscribe@incubator.apache.org][1]. Once you have subscribed
 you should say hello by posting to [rave-dev@incubator.apache.org][2].
 
+## 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][3] 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][4] amongst the community.
+
+Once there is a consensus people can proceed with the work under the [lazy 
+consensus][3] model.
+
+### Voting
+
+Occasionally a "feel" for consensus is not enough. Sometimes we need to 
+have a measurable consensus. For example, when [voting][5] in new committers or 
+to approve a release. 
 
   [1]: mailto://rave-dev-subscribe@incubator.apache.org
-  [2]: mailto://rave-dev@incubator.apache.org
\ No newline at end of file
+  [2]: mailto://rave-dev@incubator.apache.org
+  [3]: docs/governance/lazyConsensus.html
+  [4]: docs/governance/consensusBuilding.html
+  [4]: docs/governance/voting.html
\ No newline at end of file



Mime
View raw message