Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 22036 invoked from network); 22 Sep 2003 07:25:05 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Sep 2003 07:25:05 -0000 Received: (qmail 90059 invoked by uid 500); 22 Sep 2003 07:24:39 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 89856 invoked by uid 500); 22 Sep 2003 07:24:38 -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 89842 invoked from network); 22 Sep 2003 07:24:37 -0000 Received: from unknown (HELO mta11.mail.mel.aone.net.au) (203.2.192.99) by daedalus.apache.org with SMTP; 22 Sep 2003 07:24:37 -0000 Received: from [127.0.0.1] by mta11.mail.mel.aone.net.au with SMTP id <20030922072449.KVSA24583.mta11.mail.mel.aone.net.au@[127.0.0.1]> for ; Mon, 22 Sep 2003 17:24:49 +1000 From: Berin Lautenbach To: general@incubator.apache.org Subject: Re: Re: [PROPOSAL] PMC Vote to incubate Directory Project Date: Mon, 22 Sep 2003 17:24:49 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20030922072449.KVSA24583.mta11.mail.mel.aone.net.au@[127.0.0.1]> 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 > From: Nicola Ken Barozzi > > I don't understand: what is this incubator doing anyway if all the > > projects are incubated somewhere else? > > 1 - votes the projects into Apache after check that all the nitty-gritty > stuff has been taken care of Or does it recommend to another body that incubation processes have completed sucessfully and that that body can take on subject to their own vote. For example, I don't think the Incubator can approve a new TLP without the board voting, but it might recommend to the board that all necessary activities have been comleted. Again - I am not convinced that the Incubator should be the arbiter of what is accepted, but it definitely should be the guardian of correct process. > 2 - serves as a central place to store incubation history and > information +1. Would be good to formalise. > 3 - serves as a place where to discuss incubation per se, where > shepherds, sponsors and project members can confront +1. > 4 - serves as a place where to incubate TLP > Serves as a place to incubate anything surely? > >> People complain about lack of rules, not because there are too many. > > > > Really? who did? > > Everyone. For example Berin Lautenbach and Ted Leung, but you can put > basically anyone that asked us for something. > Just to clarify - my issue is not too many or to few rules, but that I'd like to see the rules clearly documented so that I can ensure that anything I am involved in incubating is doing what it needs to do. I've also worked a long time in large organisations, so I have a paranoia around being blind-sided by requirements I didn't know existed because they weren't documented. That might be playing in a little here :>. Cheers, Berin This message was sent through MyMail http://www.mymail.com.au --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org