Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 79463 invoked from network); 1 Oct 2006 15:41:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Oct 2006 15:41:49 -0000 Received: (qmail 95571 invoked by uid 500); 1 Oct 2006 15:41:47 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 95455 invoked by uid 500); 1 Oct 2006 15:41:47 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 95444 invoked by uid 99); 1 Oct 2006 15:41:47 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Oct 2006 08:41:47 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from [65.223.216.181] ([65.223.216.181:52692] helo=amereast-smg1.iona.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id CA/40-04602-6B1EF154 for ; Sun, 01 Oct 2006 08:41:43 -0700 Received: from amer-ems1.IONAGLOBAL.COM ([10.65.6.25]) by amereast-smg1.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k91FfZL6005596 for ; Sun, 1 Oct 2006 11:41:35 -0400 (EDT) Received: from [10.43.1.230] ([10.59.0.10]) by amer-ems1.IONAGLOBAL.COM with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Oct 2006 11:41:30 -0400 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <451FE067.90608@envoisolutions.com> References: <451A52E2.6020402@iona.com> <451A5567.3060907@odoko.co.uk> <451BFE19.3030407@envoisolutions.com> <7edfeeef0609280959x3c0345aub441a4c084f569d0@mail.gmail.com> <51C39328-A7DF-4D09-8457-5CA1B9753996@maven.org> <932C6EA3-AC64-4414-80F2-1480670B10FA@jaguNET.com> <451FE067.90608@envoisolutions.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8E05D52E-CCFC-4D06-AE4E-2D1E88B9E279@iona.com> Content-Transfer-Encoding: 7bit From: Steve Vinoski Subject: Re: PPMCs [was Re: what are required for contributing to release management] Date: Sun, 1 Oct 2006 11:41:29 -0400 To: general@incubator.apache.org X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 01 Oct 2006 15:41:30.0313 (UTC) FILETIME=[1088B390:01C6E570] X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N +1 to Dan's opinion. --steve On Oct 1, 2006, at 11:36 AM, Dan Diephouse wrote: > Hi Jim, > > Jim Jagielski wrote: > >> >> On Sep 30, 2006, at 11:51 AM, Jason van Zyl wrote: >> >>> >>> On 28 Sep 06, at 12:59 PM 28 Sep 06, Garrett Rooney wrote: >>> >>>> >>>> Well, PMCs are formed by the board when a project moves to top >>>> level >>>> status. PPMCs are formed for an incubating project, and exactly >>>> how >>>> that works tends to differ a bit between projects. Some >>>> mentors start >>>> off with just the mentors on the PPMC, and then invite project >>>> members >>>> as time goes on (or that's the impression I've gotten). Others >>>> just >>>> start with the whole group of committers plus the mentors on the >>>> PPMC >>>> (that's what we did with Abdera). >>>> >>> >>> I think starting with the mentors is the wisest choice as at >>> that point any committers can be brought aboard if deemed fit. >>> So that can support both models as all committers can be brought >>> aboard if it fits, or over time if more suitable. I was also >>> confused about this as I heard one thing from Noel and one thing >>> from Jim, but the mentors deciding seems sensible as projects >>> can be dealt with on a case by case basis. I don't believe >>> committers should automatically be made (P)PMC members as to me >>> it's a different level of understanding and commitment. >>> >> >> http://incubator.apache.org/guides/ppmc.html > > I assume you're referring to this sentence: > > "Initially, it is composed of the Podling's mentors and initial > committers." > > I have also found some threads which indicate that all committers > should be added [1][2]. I want to know here - who is wrong? The > documentation? Or the previous incubated projects who didn't add > all the initial committers? There is also the following sentence > which adds some doubt that the above is the official policy: > > "The PPMC is directly responsible for the oversight of the podling > and it also decides who to add as a PPMC member." > > While this could be referrering to post PPMC formation, it isn't > clear. I will happily make a patch for the documentation to make > things more clear if there is consensus. > > > I am pretty philosophically against making every committer PPMC > members. Apache is meritocracy based and IMO it makes much more > sense to start with the mentors on the PPMC and have committers > voted on based on their leadership. There may be many people on the > incubation proposal or who have committed code to a project in the > past, but an additional level of leadership is needed [3]. Not > everyone may have the necessary leadership skills, and to > presuppose they do because they have contributed good code, is IMO, > a mistake. > > > Cheerz, > - Dan > > 1. http://mail-archives.apache.org/mod_mbox/incubator-general/ > 200312.mbox/%3C3FD9F8C4.5090404@apache.org%3E > 2. http://mail-archives.apache.org/mod_mbox/incubator-general/ > 200603.mbox/%3c44162B45.2090701@rowe-clan.net%3e > 3. See Project Management Committee section here http:// > www.apache.org/foundation/how-it-works.html#structure > > -- > Dan Diephouse > (616) 971-2053 > Envoi Solutions LLC > http://netzooid.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org