On Tue, 2008-09-16 at 08:02 +0200, Bernd Fondermann wrote:
... 
> > I only vaguely remember the founding, but I don't think anyone is 
> > getting around Incubation, I just don't think it is clear that it needs 
> > to go through incubation to begin with.
> > However, if the receiving PMC doesn't want to do incubation b/c it feels 
> > there will be enough a community in a decent amount of time, then why 
> > does it matter?  Isn't it the receiving PMC's responsibility?  Why 
> > should Labs care what happens to a project that has left labs for 
> > another place within the ASF?  
> 
> I don't have a problem to let Droids go, because it is already 
> outgrowing labs. But Droids deserves a proper growing up phase and maybe 
> to become a TLP. This can all be done in a non-Incubator PMC, too. I 
> just doubt it will ever work that well.
> 
> I see three potentially receiving PMCs currently, HC, Lucene and 
> Incubator. Maybe it does not need to go through incubation, but what's 
> so bad about it?
> 
> I'd like to here what Thorsten thinks is his preferred direction right 
> now. He was starting out with HC as I-champion, then Lucene showed up, 
> while he is still actively preparing incubation.

I entered with droids under the current bylaws. The current bylaws are
not differentiating between leaving a project to TLP or sub-project of
an existing TLP. Leaving labs is through incubation by default. 

Current discussion about promoting Droids revealed that there is a
difference for a lab project to go TLP or sub-project for a bunch of
people. We cannot ignore their points, we need to finish this
discussion, make a bylaws addition proposal with the outcome and vote on
it.

The fact that the receiving PMC (being incubator or any other TLP) are
able to accept a new project whenever they please implies a wide open
possibility for bypassing incubation for a labs project. The fact that
PMC's can create sub-projects that do not ever go through incubation is
bypassing incubation on a larger scale which IMO needs to be as well
reviewed under the light of the current discussion (whether we really
want that, since incubator was created for a purpose).

Having said all this I prepared the incubation process and am willing to
go through to it as any other new project there. Any other possibility
can cause a displeasure under valuable members of the ASF. I do not want
that promoting Droids can cause this/will be associated with it. Being
first project leaving labs, it should be a good and not a controversial
example to follow. 

> > I fail to see how the situation is any 
> > different from the case where Thorsten had gone directly to a PMC and 
> > said "I'd like to start a subproject named Droids" and that PMC either 
> > votes for it or not.
> 
> But he didn't. IIUC, partly this didn't happen because he felt that 
> Droids does not fit well into existing projects. It's a general purpose 
> crawling framework.
> Asking more provocantly, why should this be burried in some vaguely 
> fitting TLP?
> I think Droids should at least try for TLP by going through incubation.

Droids offer/uses components from hc (http protocol) and other
components from/to lucene (tika/solr crawler). The helloCrawler is
thought to be the replacement of the cocoon crawler meaning a component
for cocoon, forrest and lenya. I expect that pretty fast different use
case have the own community around them. That is the reason why I think
Droids will honor the spirit of labs (Gump and other project as well):
every committer of the ASF has write access to the repository. 

Droids fits in all places more or less but maybe Bernd is right and
going TLP would make the most sense. I thought about it a lot but not
sure about it. Entering as a sub-project may help to recruit committers
faster then in the incubator and if reached a critical mass to go TLP.

salu2
-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to