Return-Path: Delivered-To: apmail-hc-dev-archive@www.apache.org Received: (qmail 75883 invoked from network); 4 Feb 2008 12:07:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2008 12:07:17 -0000 Received: (qmail 88527 invoked by uid 500); 4 Feb 2008 12:07:07 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 88501 invoked by uid 500); 4 Feb 2008 12:07:07 -0000 Mailing-List: contact dev-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 dev@hc.apache.org Received: (qmail 88476 invoked by uid 99); 4 Feb 2008 12:07:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 04:07:07 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of erik@codefaktor.de designates 62.75.252.62 as permitted sender) Received: from [62.75.252.62] (HELO mail.eatc.de) (62.75.252.62) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 12:06:51 +0000 Received: from [10.0.1.3] (p4FD2F0C0.dip.t-dialin.net [79.210.240.192]) by mail.eatc.de (Postfix) with ESMTP id 22B37B60F59 for ; Mon, 4 Feb 2008 13:06:35 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <47811D3E.3010606@dubioso.net> References: <47811D3E.3010606@dubioso.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <592F657B-0259-4A1F-8FC2-BBD758CC33B1@codefaktor.de> Content-Transfer-Encoding: 7bit From: Erik Abele Subject: Re: [discuss] project charter, bylaws, whatever Date: Mon, 4 Feb 2008 13:06:29 +0100 To: "HttpComponents Project" X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org On 06.01.2008, at 19:26, Roland Weber wrote: > ... > Regarding the mode of operations, I can write something up > based on the Jakarta Bylaws (which are accessible through > the "Charter" link (!) in the right-hand navigation bar): > http://jakarta.apache.org/site/management.html :-) > The two questions I expect this kind of document to answer > are: > 1. Who has a binding vote on what decisions? > 2. Which decisions require a 3/4 majority of eligible voters > and which a simple majority of votes cast? > > My current draft answers are: > a) PMC level decisions are votes on releases, on changing > the charter/bylaws, establishing new subprojects, and > accepting new committers or PMC members. Only PMC members > have a binding vote, decisions require three binding +1, > vetos can be overruled by a 3/4 majority of PMC members. > Votes are strictly binary: +/-1. +1. > b) other decisions (project plans, including a feature, new > mailing list,...) require a simple majority of cast votes, > with three binding +1. PMC members and committers have a > binding vote. Votes can be non-binary: +/-0 +/-1. +1 though only technical discussions so the new mailing list example kind of falls out there; it should be a PMC task but that's a minor nit... > Of course, the distinction between PMC members and committers > is currently hypothetical. But I like the idea of giving new > committers a binding vote on some decisions from the start. Yep, they definitely should have a say in technical discussions. > Comments, thoughts, or other feedback? Late but... Cheers, Erik --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org