incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Incubator DOA (Re: [STATUS] Tapestry [LACK-OF] Progress)
Date Wed, 12 Mar 2003 00:33:24 GMT
Nicola Ken Barozzi <> wrote on 12/03/2003 09:18:34 AM:

> I think that probably in case of subprojects it's quite obvious that 
> PMCs should take the incubation into account themselves. One from us 
> could simple monitor that project for some time and help needed, but 
> only as an extra helper.

The Incubator project needs to take a proactive role in ensuring that new 
projects are brought to Apache the right way, not just be an extra helper. 
This means documentation, processes to be followed etc.

> > IMHO, scrap this failed experiment and let Tapestry migrate to Jakarta
> > without being further jerked around.
> I'd agree.

I'm worried that Tapestry hasn't been incubated, and hence is missing out 

> Anyway, Tapestry has *not* been incubated, at least not by the 
> Incubator. It has been followed by Dion and Andy (whom I thank BTW), 
> that are not Incubator PMCers. I don't see how something that we have 
> not done goes to our demerit.

I'll agree to disagree on that point.

> If there is one thing that I have learned from this, is that we cannot 
> delegate to others that are not from this PMC.
> Another is that we need more PMCers, especially from the Java land.

I'm hoping that the incubator project didn't delegate the incubation of 
Tapestry to myself and Andy without somehow informing us. There have been 
various requests along the way for more information and documentation 
along the way, and many unanswered emails {1-4} etc.

> I'll make a more articulated summary on this soon. I hope I've been able 

> to capture the failings that have brought to this rant and address them, 

> at least tentatively, in a reasonable manner.

Having been involved in helping Tapestry, I feel a complete absence of any 
incubation presence working with the project. I can't speak about any 
other effort.

dIon Gillard, Multitask Consulting

View raw message