Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 43369 invoked from network); 2 Dec 2003 16:45:58 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Dec 2003 16:45:58 -0000 Received: (qmail 7151 invoked by uid 500); 2 Dec 2003 16:45:51 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 7111 invoked by uid 500); 2 Dec 2003 16:45:50 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk X-No-Archive: no List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 7089 invoked from network); 2 Dec 2003 16:45:50 -0000 Received: from unknown (HELO mail.devtech.com) (66.112.202.2) by daedalus.apache.org with SMTP; 2 Dec 2003 16:45:50 -0000 Received: from localhost ([127.0.0.1]) by mail.devtech.com (JAMES SMTP Server 2.2.0-dev) with SMTP ID 990 for ; Tue, 2 Dec 2003 11:45:52 -0500 (EST) From: "Noel J. Bergman" To: Subject: RE: [RT] Incubator Reorg Date: Tue, 2 Dec 2003 11:45:41 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <3FCCB90F.4020603@apache.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Nicola Ken Barozzi wrote: > Noel J. Bergman wrote: > > >Who should be on each ppmc? > > > - all PMC members of the future PMC (committers + landing PMC members) > > > - all Incubator PMC members (or just mentors?) > > > > AIUI, yes. All of the above. > So the Mentors would be the only ones that must stay also on the other > project mailing lists, correct? The PPMC would consist of *all* PMC members from both the landing PMC and the Incubator PMC, plus the committers. Yes, I believe that we could say that the Mentors would be the ones required to participate on the -dev list. The rest would have to "catch up" to the extent that PPMC discussion requires external context. Otherwise, I don't think that it scales. > Also, IIUC committers would be on the PPMC but not on the PMC, correct? This might bear tweaking, but I don't believe that for Incubator purposes, the project Committers would be part of the Incubator PMC. If this structure were adopted by Jakarta, however, each sub-project would have a PPMC, and the Jakarta PMC would be the union of all. > > >5) Reporting the the main Incubator PMC > > Non-issue (see above). > If we make a Lenya PPMC list, it will be private IIUC. Correct. > Development and discussions will still go on the dev lists, and > only Mentors have to be there. Hence there is a status update issue. > Or maybe I just got it all wrong... Yes, but the status update issue would occur on the PPMC list, which *IS* the union of the Incubator PMC, the Cocoon PMC and the Lenya Committers. That is what the notion of reporting to the "main Incubator PMC" is a non-issue. The correct issue is reporting to the PPMC. The PPMC would be the means by which a project is governed. The PPMC list is the private list for its use. The PMC is for the Incubator, itself. As I am envisioning this working, if there is an issue to be addressed by the PPMC, and that issue is to be discussed in public, the PPMC would have to subscribe to the public list for discussion. There would be a summary posting to the PPMC list letting everyone know of the issue, with references to the archives. That appears to balance providing oversight with being overwhelmed. That's my current strawman. Work for you? --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org