Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
MPL Upgrade: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 55: | Line 55: | ||
====What code would have its licence upgraded?==== | ====What code would have its licence upgraded?==== | ||
All code which is currently | All code in active projects which is currently under the MPL (perhaps in combination with other licenses). | ||
There are two projects within Mozilla which have historically had greater independence - Bugzilla and Rhino. Neither uses the usual tri-licensing scheme - 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. | 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. | ||
| Line 62: | Line 64: | ||
(This is the current plan; subject to confirmation with project leaders.) | (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: | 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: | ||
| Line 76: | Line 76: | ||
* chatzilla | * chatzilla | ||
* l10n-central | * l10n-central | ||
* Any | * Any active labs projects using the MPL | ||
* | * 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. | 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. | ||