Return-Path: X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F61B928A for ; Thu, 9 Feb 2012 01:43:22 +0000 (UTC) Received: (qmail 39748 invoked by uid 500); 9 Feb 2012 01:43:22 -0000 Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org Received: (qmail 39677 invoked by uid 500); 9 Feb 2012 01:43:22 -0000 Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-commits@incubator.apache.org Received: (qmail 39670 invoked by uid 99); 9 Feb 2012 01:43:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2012 01:43:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2012 01:43:21 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 4345723889F7 for ; Thu, 9 Feb 2012 01:43:01 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r804304 - /websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html Date: Thu, 09 Feb 2012 01:43:01 -0000 To: ooo-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120209014301.4345723889F7@eris.apache.org> Author: buildbot Date: Thu Feb 9 01:43:00 2012 New Revision: 804304 Log: Staging update by buildbot for openofficeorg Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html ============================================================================== --- websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html (original) +++ websites/staging/openofficeorg/trunk/content/openofficeorg/community-faqs.html Thu Feb 9 01:43:00 2012 @@ -88,18 +88,18 @@ set of simple processes to ensure things

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 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 amongst the community.

Once there is a consensus people can proceed with the work under the lazy consensus model.

What about voting?

Occasionally a "feel" for consensus is not enough. Sometimes we need to have a measurable consensus. For example, when voting in new committers or to approve a release.