Steven Noels wrote:
Steven,
I was trying not to post the obvious, but yes: this seems largely premature. No code, a restricted community, too much committers coming from one company, I've seen better proposals being fought over lately. Also, possible future integration 'ideas' with some related projects would be comforting (Jetspeed, Tomcat, Struts/Tiles, and the Cocoon portal framework for a starter).
I think these are exactly the sort of questions incubator is designed to answer. Tapestry was about seeing how an existing project can come into Apache. Perhaps Pluto is an opportunity to understand how a new project can be created and encouraged at Apache. They are both interesting challenges for the incubator.
As for your issues, "No code" is true (for now) but that is the sort of project Pluto represents. If at the end, the incubator PMC decides that the project still has the problems you identify (if they are in fact problems), then the project should remain in incubation until the community is self supporting, or be discontinued, whatever. That is a decision for further down the track, I think.It would seem to me that if JetSpeed is in scope for Jakarta,
IMHO, a reference implementation at Apache of a Portal standard would be appropriate, especially considering JetSpeed is already at Jakarta. I'm not into portals myself so I can't really comment on the project's merits beyond that.
Conor
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
