On 24.02.2010 23:47 schrieb Howard Lewis Ship:
One of the challenges of running Tapestry as an Apache project is that, due to licensing concerns, a lot of the integrations are non-starters. I keep expecting someone to say "Hey, You can't integrate with Hibernate! It's LGPL!".
I thought the consensus here was that linking to LGPL'ed work from an optional module is OK with ASF policies. So I don't expect for anyone to complain about the tapestry-hibernate module. A tapestry-jpa module wouldn't have any problems, though :).
Some days I fantasize about just moving the code base up to GitHub and stripping "Apache" from the name. But that adds its own set of problems, and the "cachet" of being an Apache project perhaps outweighs the convenience of being free from (the admittedly minimal) oversight and bureaucracy of Apache. Here, too, I have Clojure envy.
A project is not just about a source repository. We'd still want to have a maven repository, CI server, bugtracker, webserver, mailing lists, ... GitHub just doesn't provide that (apart from it being inaccessible quite often). Being an Apache project provides us with all that and in addition protects us from legal actions from third parties (and of course there is the prestige :)) - at the cost of stricter license policies and some bureaucracy. This bureaucracy and those processes have put forth some high quality software products that are leaders in their respective areas so I feel they can't be that bad.
Just my thoughts. Uli --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
