How, exactly, is Tapestry ever expected to exit the proposal stage? Despite repeated attempts, Tapestry is NOT in BugZilla. We're still forced to use SourceForge for bug tracking.
Tapestry's mailing lists are not getting archived any more (not since 2/21). Nobody seems to know ANY of the procedures for getting things done. Nothing is documented. Simple things like the correct way to distribute a release (including signing and mirroring) are just "known" by the right people ... and I don't even know who is in the know. Andrew and Dion have been helpful, both before the move and after. The only other accomplishment of the incubation process has been a code audit that resulted in a shuffling of the libraries checked into CVS and distributed with the framework. Jakarta infrastructure is non-existent. Worse, the Jakarta culture erroneously expects things to get done based on e-mails, rather than something organized, like using BugZilla to track infrastructure requests. The Incubator team has yet to provide a time table or a check list to indicate what the exit criteria are. In terms of Tapestry's commitments to the Incubator, it looks like we're more than there (based on http://incubator.apache.org/process.html). In terms of Incubator's commitments to Tapestry ... that is, to assist Tapestry in moving into Jakarta, fitting in, and accessing infrastructure; very little has been accomplished. -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/proposals/tapestry --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
