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.
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. 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. 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. Ben Gidley www.gidley.co.uk b...@gidley.co.uk On Thu, Feb 25, 2010 at 2:24 AM, Wilson Ikeda <wilsonaik...@gmail.com>wrote: > How many on the list would think that breaking with apache and trying a > radical change (be more like a company, like SpringSource) is something > that > should be tried? After all being an Apache project does allow Donations or > Funding directly to a respective project? like Tapestry? > and i do believe that licensing concerns are bad! > > > > On Wed, Feb 24, 2010 at 2:56 PM, Thiago H. de Paula Figueiredo > > <thiag...@gmail.com> wrote: > >> > On Wed, 24 Feb 2010 19:47:07 -0300, Howard Lewis Ship < > hls...@gmail.com> > >> > wrote: > >> > > >>> >> 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!". > >> > > >> > In this case, couldn't we host these projects somewhere else and > consider > >> > them officially approved in Tapestry's website? This could even be > applied > >> > to some projects not written by the commiters, such as tapestry-jpa, > as > >> long > >> > as they meet the same quality criteria used to Tapestry itself. > > > > Quality issues are hard to gauge. > > > > Also, there's something good about having a suite of libraries that > > are released on the same schedule with the same version number. Makes > > figuring out compatibility much easier (are you listening, Hibernate?) > > > >> > > >> > -- > >> > Thiago H. de Paula Figueiredo > >> > Independent Java, Apache Tapestry 5 and Hibernate consultant, > developer, >> > and > >> > instructor > >> > Owner, software architect and developer, Ars Machina Tecnologia da > >> > Informação Ltda. > >> > http://www.arsmachina.com.br > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >> > For additional commands, e-mail: users-h...@tapestry.apache.org > >> > > >> > > > >
