Ross
-------- Original Message -------- Date: Tue, 3 May 2005 16:17:07 -0700 (PDT) From: Brian Behlendorf <[EMAIL PROTECTED]> To: Ross Gardler <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: SISSL compatible with ASL?
The ASL-licensed works can be combined with SISSL-licensed works without the license on one part encumbering the license on the other. However SISSL-licensed works can not be sublicensed under the ASL, which means you can not incorporate the SISSL licensed works into a work that as a whole is licensed under the ASL. Which means the SISSL works must be kept out of CVS/SVN and treated like an external dependency. As best I can tell.
Brian
On Tue, 3 May 2005, Ross Gardler wrote:
Over at Apache Forrest we have a plugin that needs to include the API libs from OpenOffice.org (no source code). However, we are unsure if the Sun Industry Standards Source License (SISSL) is compatible with the ASL.
OOo is Tri licensed under the GPL, LGPL (obviously, not compatible) and the Sun Industry Standards Source License (SISSL), so we are considering the SISSL.
The FAQ at http://www.openoffice.org/FAQs/faq-licensing.html#1 seems to imply that it should be compatible:
"This licensing structure provides the necessary flexibility for combination of OpenOffice.org technologies with projects using other licenses (e.g. MPL, Apache, Artistic, etc.)."
However, being no legal experts we have no idea if this objective is realised. Can someone with a little more understanding of these things pass verdict?
The SISSL license can be seen at http://www.openoffice.org/license.html
Thanks, Ross
--------------------------------------------------------------------- DISCLAIMER: Discussions on this list are informational and educational only, are not privileged and do not constitute legal advice. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
