I think it might be nice to have in development, and perhaps even more
useful to know what contributed modules do not have license contributions.
 I'm usually concerned about licensing when I first consider using a module,
and don't think about it too much after that initial decision - which can be
an issue if the my project has similar functionality requirements but
different license requirements, or if there is a license change between
versions.

The maven dependency report is one of those things I should use, but really
don't, whereas a license page is easy to just "visit".


On Thu, Mar 31, 2011 at 4:54 PM, Howard Lewis Ship <[email protected]> wrote:

> I'm starting to think this would be a very unpopular idea, about on
> par with having the apps phone home on startup.
>
> On Thu, Mar 31, 2011 at 1:47 PM, Thiago H. de Paula Figueiredo
> <[email protected]> wrote:
> > On Thu, 31 Mar 2011 15:08:46 -0300, Howard Lewis Ship <[email protected]>
> > wrote:
> >
> >> I was just thinking about how to properly distribute licences (for
> >> some third party dependencies, such as YUICompressor) ... what if
> >> there was a core/AboutTapestry page, and a matching service.
> >> Contributions to the service could describe the modules (such as
> >> tapx-core) with a version number and any licence(s).  Hitting
> >> AboutTapestry would automatically display (perhaps with an accordion
> >> interface) all the details of the application in one place.
> >
> > I'm OK with that if it needs to be explicitly enabled.
> >
> > --
> > Thiago H. de Paula Figueiredo
> > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and
> > instructor
> > Owner, Ars Machina Tecnologia da Informação Ltda.
> > http://www.arsmachina.com.br
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Jonathan Barker
ITStrategic

Reply via email to