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
→What code would have its licence upgraded?
| Line 54: | Line 54: | ||
All code in active projects which is currently under the MPL (perhaps in combination with other licenses). | 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. | 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 ([https://bugzilla.mozilla.org/show_bug.cgi?id=680131 Bugzilla discussion]). | ||
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. | ||