db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: [doc] format of docs submitted to derby
Date Wed, 04 May 2005 17:59:14 GMT
scott hutinger wrote:
> Also, an important license issue; is OpenOffice compatible with 
> Apache?   Can we stick content created by OOo into svn?  This was a 
> current Forrest thread. 
> ... 

Ross' original question (see the post below) was if the Open Office API 
libs could be used under the Sun Industry Standards Source License 
(SISSL). And the answer was "no", they cannot be checked into SVN, so 
that plugin will have to be hosted outside Apache.

However, I assume that a document produced by Open Office *can* be 
checked into SVN (ie. as part of a web site).  After all, results of a 
gcc compile can be checked in and gcc is under the GPL license.

Does anybody see a problem with my assumption?


-------- Original Message --------
Subject: [Fwd: Re: SISSL compatible with ASL?]
Date: Wed, 04 May 2005 10:10:02 +0100
From: Ross Gardler <rgardler@apache.org>
Reply-To: dev@forrest.apache.org
To: Forrest Developers List <dev@forrest.apache.org>

The legal-discuss list came up with the attached, summary is that the
MSOffice plugin will have to be hosted elsewhere. I'll put it in the
Burrokeet CVS. Any Forest committer requiring CVS access  over there
need only ask for it.


-------- Original Message --------
Date: Tue, 3 May 2005 16:17:07 -0700 (PDT)
From: Brian Behlendorf <brian@collab.net>
To: Ross Gardler <rgardler@apache.org>
cc: legal-discuss@apache.org
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.


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: legal-discuss-unsubscribe@apache.org
 > For additional commands, e-mail: legal-discuss-help@apache.org

View raw message