Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 30098 invoked from network); 30 Jun 2004 12:48:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 30 Jun 2004 12:48:28 -0000 Received: (qmail 12224 invoked by uid 500); 30 Jun 2004 12:48:18 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 12155 invoked by uid 500); 30 Jun 2004 12:48:16 -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 12058 invoked by uid 99); 30 Jun 2004 12:48:15 -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; Wed, 30 Jun 2004 05:48:14 -0700 Received: (qmail 20380 invoked by uid 2009); 30 Jun 2004 12:47:07 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Jun 2004 12:47:07 -0000 Date: Wed, 30 Jun 2004 08:47:07 -0400 (EDT) From: Dave Brondsema X-X-Sender: user0009@ferrari To: dev@forrest.apache.org Subject: Re: [VOTE] draft Forrest Project Guidelines: Roles and responsibilities In-Reply-To: <1088581401.18566.43946.camel@ighp> 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> <1088563736.18566.41555.camel@ighp> <1088581401.18566.43946.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 Wed, 30 Jun 2004, David Crossley wrote: > Nicola Ken Barozzi wrote: > > I know I'm in error in not having checked it before, > > Everybody needs to help. > > > but now that I have > > seen it I don't read in it the fact that simple committers > > cannot vote (as instead I would prefer). > > Voting is the next task to add to the document. > We had already said that we would identify the roles > and responsibilities first. Though you are right, such > things are intertwined. > I am satisfied with the roles and responsibilities, except where they are related to moving from one role to another (i.e. voting). Let's move on to discussing those areas. >From Committers, "After a successful vote,". A successful vote by whom? >From PMC, "While they are active, they are part of the PMC". I think this is a little unclear. Committers can join and disjoin from the PMC whenever they want? Mailing list membership is the indicator of PMC membership? We should also mention what the PMC does when a committer joins/disjoins it (from David's recent email: "acking you with board@ and adding you to the committee list"). Does that just mean approve his/her subscription to the mailing list? Or is the "committee list" something else? > > Also, wouldn't it be better just to refer to the main > > Apache document for this, and just clarify some points? > > That might be possible (though that main document needs > some enhancements). However most other projects seem > to also define the roles in their Guidelines. Another > issue is that we are defining an extra role that no other > project uses yet. > What extra role? I see user, developer, committer, and PMC on our page and on the ASF roles apge. A standalone document is nice, but some more lengthy issue explanations (like defining voting) can just be referenced. And then we specify in our document how voting is used for Forrest. -- Dave Brondsema : dave@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming http://csx.calvin.edu : student org