to focus on tapestry:
1. Getting all its license issues worked out - (which seems done) 2. Getting in gump (to fit in with Jakarta) 3. Getting to project status.
I am specifically not going to focus on:
4. Making the incubator viable.
My motivation is to see Tapestry do well and make its way into Jakarta. Later if there is some other project I want to
sponsor maybe I'll contribute to 4. (although the "incubator" is the wrong approach)
-Andy
Why is this concept so hard to understand? Incubator is a project. It is
not an entity. By definition, anything done by way of incubation falls
under the category of incubator. The only question is whether what is
done is marked as progress or not, and for that somebody actually has
to make note of it within the incubator module.
This is no different from any other Apache project. I can spend hundreds of hours working on the best-thing-since-sliced-bread for an HTTP server, but no progress is made until I commit those changes to an httpd module and the rest of the project agrees (or doesn't disagree) that it is okay. Collaborative development requires that extra bit of work. If nobody does that work, then a project will never pass through incubator.
....Roy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
