Return-Path: Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: (qmail 84599 invoked from network); 14 Nov 2005 05:22:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Nov 2005 05:22:27 -0000 Received: (qmail 68305 invoked by uid 500); 14 Nov 2005 05:22:21 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 68104 invoked by uid 500); 14 Nov 2005 05:22:20 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list legal-discuss@apache.org Delivered-To: moderator for legal-discuss@apache.org Received: (qmail 63120 invoked by uid 99); 14 Nov 2005 05:11:52 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of rooneg@gmail.com designates 64.233.184.194 as permitted sender) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TBp9KFmT9RaFq+bDXA0wyAj0lUlstLq2bF2F0F1g8dUDCHtGfz+R8IqY7Eu32AcDikE9Vbxy3MGyFW+xt6tZ5aCAb3ay0ChCelkJVFJe6KGYPqMsnViLwAC5tHg4UOwZO4qAMexr39QrDq8LQdNvDT2OoUTOFF4e5jPQFs/w6n4= Message-ID: <7edfeeef0511132111r6dd4838vbee6fbe5319b611a@mail.gmail.com> Date: Sun, 13 Nov 2005 21:11:30 -0800 From: Garrett Rooney Sender: rooneg@gmail.com To: ASF Legal Discuss Subject: What kind of oversight Is required for a release? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is actually a subject that came up on IRC a while back, and nobody had an especially great answer, but it was suggested that it might be a topic to discuss on this list. The initial question was, who is actually allowed to vote on a release of an Apache project? In the projects I've been involved in, either as a committer and PMC member (APR) or as a very occasional contributor (HTTPD), the project documentation indicates that three +1 votes from committers are needed, but in recent days I've heard multiple people say that only PMC members are actually allowed to vote, since that's what is required for proper oversight of the release process. When I asked where the "3 +1 votes from PMC members" rule was actually written down, nobody knew. If you trace it back, apparently it was discussed on the ASF members mailing list, but that's not an especially great place to send out these kind of directives, considering that a large number of the ASF developers are not actually members. So at the end of the discussion, there really wasn't any real consensus on what was required, or where one could go to actually find ASF wide rules on these matters. Please note that I don't have a strong opinion one way or another on who is able to vote on a release. If 3 +1 votes from PMC members is what is required for us to be able to claim we're maintaining proper oversight of member projects, that's fine with me, I just wish it could be written down someplace where a new contributor or committer or even PMC member can be expected to find it, rather than having to hear about it through the grapevine as seems to be the case these days. -garrett --------------------------------------------------------------------- DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See for official ASF policies and documents. --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org