Return-Path: Delivered-To: apmail-incubator-aries-dev-archive@minotaur.apache.org Received: (qmail 61836 invoked from network); 23 Oct 2009 14:15:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Oct 2009 14:15:15 -0000 Received: (qmail 14814 invoked by uid 500); 23 Oct 2009 14:11:17 -0000 Delivered-To: apmail-incubator-aries-dev-archive@incubator.apache.org Received: (qmail 14181 invoked by uid 500); 23 Oct 2009 14:10:07 -0000 Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: aries-dev@incubator.apache.org Delivered-To: mailing list aries-dev@incubator.apache.org Received: (qmail 13901 invoked by uid 99); 23 Oct 2009 14:10:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2009 14:10:01 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of alasdair.nottingham@gmail.com designates 209.85.211.191 as permitted sender) Received: from [209.85.211.191] (HELO mail-yw0-f191.google.com) (209.85.211.191) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2009 14:09:59 +0000 Received: by ywh29 with SMTP id 29so8147049ywh.32 for ; Fri, 23 Oct 2009 07:09:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=2OpH9vmiokH/npQuxAKods/964cSYzG+WmKNdlhwYqc=; b=h++HzRAPsiIetcWcGtkAF8FeOUCpny/YYO0sX2v1cppsDKgSjqOWHwXPfFdoveiXXJ eMkOVISkIiPYYL7WhtIn62mzYMTw2ihosFsKpGVUZzz0Z+4kUcGNLFd5HVazYEhcmENY fpNVK0skHa8x/po+UhIoVN587mOuHQWGKcmx0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=GsurxVwcOnb6WuHtiuwviqu4uPMqDo3qXl9jmb1KIsyJDO8FueMnY5NRcGUZ0E47+C jlSxBiYAUaDAS4hzAdXtsspqs8d1DJL2zzFdHYAaZzawQ+pK+3DC1KeLqAtRD1TelDmI NOzIHSaA7Wz/el6iKbx9dqMtRgvygBxhasQ3w= MIME-Version: 1.0 Received: by 10.150.44.6 with SMTP id r6mr5447752ybr.244.1256306978094; Fri, 23 Oct 2009 07:09:38 -0700 (PDT) In-Reply-To: <200910161107.46600.dkulp@apache.org> References: <200910161107.46600.dkulp@apache.org> Date: Fri, 23 Oct 2009 15:09:38 +0100 Message-ID: Subject: Re: People page for aries From: Alasdair Nottingham To: aries-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, Thanks for the information. I have been trying to get my head around all this. Based on the guidelines, what has been said here and an attempt to read between the lines I think the idea is that things operate like this: Voting is important both in podlings and in top level projects. When making decisions about how the podling should operate that do not have legal implications any vote by any member of the PPMC is considered binding in making decisions. This allows the PPMC to learn the process of managing the podling. While this is not explicitly covered in the guides it seems logical to me, and consistent with the goal of the PPMC learning how to run a project. When it comes to voting in a new committer I think that while the IPMC members votes are binding the guidelines say that the PPMC is responsible for recommending new committers. To gain such a recommendation a vote is held and the PPMC members votes are binding (this is not sufficient for committer access to be granted though). If the decision is to recommend and 3 IPMC members vote then it goes to the IPMC for silent consensus. If the decision is to recommend and less than 3 IPMC members vote then it goes to the IPMC for a full vote as per the process. When it comes to voting for a release I the same rules should apply as for voting in a new committer. I have tried to interpret the rules, but this is the best interpretation I have come up with. What do people think? Thanks