On 25.02.2010 09:41 schrieb Ben Gidley:
I think being an Apache project is really useful for 'selling' tapestry into a corporate client. They have heard of Apache and that helps a lot.
Not only that. It also provides us with a very good infrastructure and protects us from legal actions against the developers. In addition, the bureaucracy and processes imposed on us from the ASF have put forth some very succesful projects so I guess they can't be that bad.
People have managed to build commercial communities around Apache projects - good examples are Active MQ, Maven (via Sonatype) and Geronimo. It may help to have a group of people actively pushing Tapestry (like Spring Source) and supporting it - but it isn't quite the same as 'infrastructure' type components like a MQ, J2EE container or even Spring which is now billing itself as a complete platform.
Indeed. And it has failed before for Tapestry. Remember the Tapestry Support Network?
A tapestry-hub may work - you could spin up a site with something like Gitorious (though it would be better to have one in tapestry!!). It would need a good wiki and then it could become the home of tapestry.
I'd rather leave the home of Tapestry at Apache.
If people are interested I may be able to help and may even be able to get some hosting sponsored (no guarentees) which would let us run things.
I still don't see what the purpose of such a site should be. I personally don't want Tapestry to be developed somewhere else then at Apache - for various reasons. And before there is no plan on what to do on an additional site, I'm against it. Tapestry really can't use another stale site without a real purpose. I'd rather people invest their energy in helping write documenatation, fix bugs, add features and most important evangelize Tapestry.
Uli --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
