opinion, for better or worse.

"Simon P. Lucy" wrote:
> For your own sake I would make it explicitly clear that the source you are
> taking is under the NPL and not the GPL to forestall attempts to say that
> you have used GPL code.  How you do this is still unclear, its feasible to
> remove the alternate licence language from each of the headers on the
> files, nothing in the licence prevents that.  Alternatively, you might
> think that a file distributed with the product that details where the
> source of the files can be found and which licence is being used is sufficient.

I recommend the latter course of action: State that you are using JS and
NSPR code under the NPL (or MPL) terms and conditions. If you modify the
original source code in any way then you would be obligated to make that
modified source available to your users yourself; you couldn't just
point users over to the mozilla.org site.

Here's some sample language that you might include in your "Credits"
file or elsewhere:

This product includes the JavaScript engine and Netscape Portable
Runtime (NSPR) libraries distributed as part of the Mozilla project;
this software is copyright 1998-2001 by Netscape Communications
Corporation and others. NSPR code is used under the terms and conditions
of the Mozilla Public License, version 1.1. JavaScript code is used
under the terms and conditions of the Netscape Public License, version
1.1. To obtain a copy of the source code for the JavaScript engine and
NSPR libraries please see
<http://www.octogroup.net/js-nspr-source.html>.

This separate file js-nspr-source.html would then contain instructions
for obtaining a copy of the JS and NSPR source code. As I mentioned
previously, you want the instructions to be detailed enough so that the
user can obtain the _exact_ JS and NSPR source code used to create the
DLLs you're shipping as part of your product. Just referring them to the
generic mozilla.org site is not sufficient.

Frank
-- 
Frank Hecker            work: http://www.collab.net/
[EMAIL PROTECTED]        home: http://www.hecker.org/

Reply via email to