-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Francesco,
Thank you for your response.
It's interesting to note that this Wikipedia article states that the SPL
"has been approved by the [FSF]" but completely fails to mention the
incompatibility with the GPL.
http://en.wikipedia.org/wiki/
Le dimanche 09 août 2009 23:53:41, Matthew Johnson a écrit :
> On Sun Aug 09 23:02, Damien Raude-Morvan wrote:
> > > I've reviewed the package and it looks clean, but I have one question.
> > > Which bit is licenced under the apache-derived licence? I can only find
> > > BSD-licenced files.
> >
> >
Matthew Johnson writes:
> I don't like:
>
> * 5. Products derived from this software may not be called
> * "OpenSymphony"
> *or "OGNL", nor may "OpenSymphony" or "OGNL" appear in their
> *name, without prior written permission of the OpenSymphony
> *Group.
>
> since we are, arguably,
On Sun Aug 09 23:02, Damien Raude-Morvan wrote:
> > I've reviewed the package and it looks clean, but I have one question.
> > Which bit is licenced under the apache-derived licence? I can only find
> > BSD-licenced files.
>
> OpenSymfony Licence (Apache derived one) is promoted by upstream as off
On Sun, 09 Aug 2009 10:27:27 -0700 Tony Mancill wrote:
[...]
> We are trying to determine the licensing status of a new package,
> libjxp-java, for which most of the source is licensed under the LGPL,
> but includes 2 (modified) files for which the original license is the
> Sun Public License 1.0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Debian Legal experts:
We are trying to determine the licensing status of a new package,
libjxp-java, for which most of the source is licensed under the LGPL,
but includes 2 (modified) files for which the original license is the
Sun Public License
6 matches
Mail list logo
