Return-Path: Delivered-To: apmail-hc-commits-archive@www.apache.org Received: (qmail 2676 invoked from network); 8 Feb 2008 18:55:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Feb 2008 18:55:03 -0000 Received: (qmail 8182 invoked by uid 500); 8 Feb 2008 18:54:56 -0000 Delivered-To: apmail-hc-commits-archive@hc.apache.org Received: (qmail 8154 invoked by uid 500); 8 Feb 2008 18:54:56 -0000 Mailing-List: contact commits-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list commits@hc.apache.org Received: (qmail 8144 invoked by uid 99); 8 Feb 2008 18:54:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2008 10:54:56 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2008 18:54:35 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id E17061A9832; Fri, 8 Feb 2008 10:54:42 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r619977 - /httpcomponents/project/src/site/apt/bylaws.apt Date: Fri, 08 Feb 2008 18:54:42 -0000 To: commits@hc.apache.org From: rolandw@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20080208185442.E17061A9832@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: rolandw Date: Fri Feb 8 10:54:32 2008 New Revision: 619977 URL: http://svn.apache.org/viewvc?rev=619977&view=rev Log: moved mailing list example to PMC section Modified: httpcomponents/project/src/site/apt/bylaws.apt Modified: httpcomponents/project/src/site/apt/bylaws.apt URL: http://svn.apache.org/viewvc/httpcomponents/project/src/site/apt/bylaws.apt?rev=619977&r1=619976&r2=619977&view=diff ============================================================================== --- httpcomponents/project/src/site/apt/bylaws.apt (original) +++ httpcomponents/project/src/site/apt/bylaws.apt Fri Feb 8 10:54:32 2008 @@ -116,6 +116,8 @@ * establishing new subprojects + * requesting Apache resources (mailing lists, issue tracking,...) + * ... Binary Voting allows only for the votes +1 (approval) and -1 (objection). @@ -152,9 +154,8 @@ additional input from community members, polls can be run on the same or other mailing lists. Voting on community decisions should be restricted to cases where it is - necessary or desirable to formally record the consensus. Examples are - the creation of new mailing lists (Infra will ask for the vote thread), - or the approval of a long-term project plan. + necessary or desirable to formally record the consensus, for example when + a long-term project plan is approved. Discussions and voting must take place on the public project mailing lists. Community Voting is non-binary, typical vote values are: @@ -186,7 +187,7 @@ As a rule of thumb, "If" questions are consensus decisions while "How" and "When" questions are majority decisions. For example, - it is a consensus decision a new mailing list should be created. + it is a consensus decision a new feature should be implemented. It is a majority decision an issue in the code should be solved, or the next release of a deliverable will be cut. If it is not clear and cannot be established by discussion whether a