From dev-return-10983-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Thu Jul 01 14:34:24 2004 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 48367 invoked from network); 1 Jul 2004 14:34:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Jul 2004 14:34:23 -0000 Received: (qmail 44779 invoked by uid 500); 1 Jul 2004 14:34:25 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 44718 invoked by uid 500); 1 Jul 2004 14:34:23 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 44680 invoked by uid 99); 1 Jul 2004 14:34:22 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [65.42.175.122] (HELO ferrari.solidusdesign.com) (65.42.175.122) by apache.org (qpsmtpd/0.27.1) with SMTP; Thu, 01 Jul 2004 07:34:19 -0700 Received: (qmail 12896 invoked by uid 2009); 1 Jul 2004 14:33:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Jul 2004 14:33:08 -0000 Date: Thu, 1 Jul 2004 10:33:08 -0400 (EDT) From: Dave Brondsema X-X-Sender: user0009@ferrari To: dev@forrest.apache.org Subject: Re: [DRAFT] Forrest Project Guidelines In-Reply-To: Message-ID: References: <1086761689.31520.41527.camel@ighp> <1086772558.31520.42264.camel@ighp> <1086787587.31519.43797.camel@ighp> <1087619052.1555.68.camel@ighp> <1088303182.18566.10185.camel@ighp> <1088598159.18566.46238.camel@ighp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Thu, 1 Jul 2004, Nicola Ken Barozzi wrote: > Dave Brondsema wrote: > ... > > Moreover, if we did have non-voting committers to work on a certain > > feature, we need to define another process for "graduation" to voting > > committership. I don't like having so many levels of stratification, it > > makes the community feel less open. > > I understand. > > Let me try to explain again what I'm trying to solve instead of > discussing on the solution :-) > > Let's say that all committers can VOTE. This sets a high bar on > committership, as one needs to demonstrate that he can work well > together. Some project set this as high as 6 months of continuous and > good patches. The fact is that a voter can veto changes (even if they > have to be explained), and this can have a big impact on the community. > > In this way, the distinction between PMC members and committers is moot, > as all committers become PMC members. If they can vote, then they are > steering the project, so they are de facto part of the PMC and must take > responsibility. > > Because of this, we cannot have people helping out on a certain feature > for a limited set of time or for a particular part of the code. For > example, let's say that we put a XYZ skin in Forrest and that a certian > person wants to maintain it. Shall we make him part of the PMC? I say > no. Shall we have him send in patches continually, just to have that > skin up to date? Would not partial commit access be a solution? > > Note that partial commit access is not a step to PMC membership. It's an > alternative for some cases. > > Another use case is that we wouldn't have Lenya or Cocoon committers > with access to the CVS, as they would have to be PMC members, which has > to be voted based on merit. How would we treat this? > That explanation helped. What about this: committers cannot vote, unless they are a PMC member. After the committer demonstrates he/she can work well with us, we can propose they join the PMC. The only people who stay "just committers" would be most Lenya & Cocoon committers and task-oriented committers who don't want to be more involved. This keeps the committing roles to 2 instead of 3. -- Dave Brondsema : dave@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming http://csx.calvin.edu : student org