Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4DF7CE7C.8000506@apache.org>
Date: Tue, 14 Jun 2011 22:11:24 +0100
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Decision making at the ASF
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

How do we make decisions in ASF projects?

The short answer is copied below, if you want to learn more about the 
specific processes mentioned here then you'll find links to more info at 
[1] (note there are also some useful links for new committers at the 
bottom of that page):

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, if the "lazy" approach to 
consensus building is deemed unsuitable for a particular decision then 
we seek to build consensus within the community. Very occasionally, 
usually for formal reasons relating to legal responsibilities, it is 
necessary to call a vote.

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 here on the community development site.


[1] http://community.apache.org/committers/