Accountapprovers, antispam, confirm, emeritus
4,925
edits
Changes
→How would it happen?
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:
* mozilla-central / mozilla-inbound
* comm-central
* tamarin-redux
* camino
* dom-inspector
* venkman
<i>If you feel this list is incorrect by omission or commission, please let us know.</i>
Repos which feed into mozilla-central (e.g. mozilla-inbound, tracemonkey) would need to merge the changes from mozilla-central, and run the script to upgrade any new files they might have created, before making any further merges into to mozilla-central.
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.
Merges from any other repositories into mozilla-central would need to have the license upgraded before the merge was permitted. In terms of mechanics, after various dry-runs which made sure the script was working correctly, we would probably declare a "relicensing day" where the trees would be closed to other changes, and we would make all of the upgrades and various back-and-forth merges, before asking people to update their local trees.
====What about the list of Contributors?====
