[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: licensing confusion

On Thu, 04 Mar 2004, Marek Habersack wrote:
> On Thu, Mar 04, 2004 at 10:08:11AM -0800, Don Armstrong scribbled:
> > You (in general) can't incorporate code which is under a license that
> > is incompatible with the GPL to create a derivative work under the GPL
> > unless you yourself are the copyright holder of both works in
> > question.
> OK, so by that token - no MPL/NPL code in Mozilla should ever use
> any GPL code, am I right in assuming that?

No, because such code is dual licensed in general.

> Note, that I assume that what's written in the mozilla (debian)
> copyright file can be understood verbatim - that _some_ files in it
> are licensed solely under MPL/NPL (while others are dual-licensed
> etc. etc.). Then those single-license files would affect the whole
> binary, that's how I understand it.

Not necesarily. The GPL only affects derived works. Presumably, these
works licensed solely under the MPL or NPL are not derived works of a
work licensed solely under the GPL.

> [T]he thing at stake is the use of OpenSSL or Cryptlib[1] in the
> Caudium[2] project. Looking at [2], I see clauses which make
> cryptlib not compatible with clauses #5 and #6 of the DFSG.

Huh? I see no such clauses[1], unless you're refering to the alternate
terms of distribution.

> The license is a BSD one, that's clear, but the terms of use and
> usage conditions seem to restrict the use to non-commercial or
> low-cost projects.

Cryptlib itself has it's own copyleft which on the face seems to be
GPL compatible. [But I've only spent 2-3 minutes glancing at the
license... closer examination is probably warranted.]

> Oh, and we cannot relicense the Caudium code, as we aren't the
> original copyright holders of the entire code. Also, I would like to
> know whether it's ok for me to issue an ITP for Cryptlib.

What you need to do is file an ITP, then bring the texts of the
licenses themselves so they can be analyzed by -legal for their DFSG

Then, once we know that the licenses themselves are DFSG Free,
indicate which code is a derivative work of what, so we can examine
the compatibility of the licenses.

Don Armstrong

NB: Your footnotes were missing from the previous message.

1: http://www.cs.auckland.ac.nz/~pgut001/cryptlib/
More than any other time in history, mankind faces a crossroads.
One path leads to despair and utter hopelessness.
The other, to total extinction.
Let us pray we have the wisdom to choose correctly.
 -- Woody Allen


Attachment: signature.asc
Description: Digital signature

Reply to: