On Wed, 12 Mar 2003 11:33 am, [EMAIL PROTECTED] wrote:
>
> 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.
>
I have to agree. AFAICT, accepting subprojects in the raison d'etre of the
Incubator. I was surprised by the statement that the incubator does not want
subprojects. IIRC, the board has said that all subprojects must come through
the incubator. If it's just a cork, what's the point of it?
>
> I'm worried that Tapestry hasn't been incubated, and hence is missing out
> somehow.
>
The issue is that the incubator is not incubating. It's cold and the eggs are
going off. We need to get them somewhere where they might just hatch. If
there are issues with Tapestry, will they be addressed here?
> 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'd add to the list the Pluto and Charon proposals. I haven't seen any
reaction from the incubator to these? I know there was some discussions and
issues/hurdles raised by Andy but some sort of acknowledgment would be
polite.
Conor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
