Updated Licence Policy

For quite a while now I’ve been working on an updated mozilla.org License Policy. This document has two parts:

  • A prescriptive part which says what licences are and aren’t permitted for what parts of our code. There have been no changes here so this shouldn’t be a surprise to anyone, but it is now hopefully explained in a clearer way.
  • A descriptive part which says what licences currently apply to what parts of our code. This information has never been gathered in one place before, and should hopefully be helpful to people wanting to use our code in other contexts.

Please review the draft document, particularly if you are the owner of a mozilla.org project like Bugzilla, Rhino, Tinderbox etc. and make sure that you understand the prescriptive parts, and that the descriptive parts are correct :-) If either of them seems wrong, let me know and I will investigate.

8 thoughts on “Updated Licence Policy

  1. Bonsai and Registry are NPL? Is that something we’re allowed to change? AOL gave the Foundation all the rights to that stuff, right? :)

  2. That’s very useful Gerv. From the point of people using the Moz code in other projects is there something you can link to that gives a little more background on using the Tri-licenced code. Or is it really as straight forward as just picking one of them?

  3. Dave: They weren’t part of the codebase that we originally requested license change permission for. So we don’t have the permission of any external contributors. That’s at least one reason. Also, effectively the NPL is now the same as the MPL, as any Netscape-specific clauses are pretty much unusable.

    SteveLee: There are FAQs of various sorts linked from http://www.mozilla.org/MPL/. Ideally, people pick one to follow, but retain the headers of all three and so their changes can be picked up by us.

  4. xpidl is mpl-tri, you’re confused with libidl. i had a nice comment for this months ago, but your comment system ate it.