Accountapprovers, antispam, confirm, emeritus
4,925
edits
Changes
no edit summary
====What code would have its licence upgraded?====
All code in active projects which is currently tri-licensedunder the MPL (perhaps in combination with other licenses). There are a few two projects within Mozilla which have a different historically had greater independence - Bugzilla and Rhino. Neither uses the usual tri-licensing scheme (e.g. - Bugzilla is MPL; 1.1 only, and Rhino is MPL/GPL). For those projects, whether to shift or not is a discussion to be had with their leadership.
Should an upgrade be agreed, any project which is MPL-only (such as Bugzilla) would need to add the Exhibit-B GPL-incompatibility language to their licence header.
(This is the current plan; subject to confirmation with project leaders.)
More specifically, we would write (or repurpose) a script to replace existing tri-licence blocks with the MPL 2 boilerplate (which is only 3 lines long). We would run it against the following repositories:
* chatzilla
* l10n-central
* Any tri-licensed active labs projectsusing the MPL* XXXAny more?NSS trunk (which is still in CVS) <i>If you feel this list is incorrect by omission or commission, please let us know.</i>
Some repositories such as release repositories are effectively forks of some of the above code from earlier points in time. We would not plan to upgrade the licence on those repositories, but just let them fall out of use naturally.
