1

I forked a Mozilla Public License Version 2.0 licensed app and made some changes.

I want to publish the app, but I want anybody who uses my code to have to adhere to GPL v3.

Since GPL v3 is more restrictive than MPL, can I just change the License file to GPL v3? If not, what other changes would I have to make?

1
4

No, you cannot "just" change the license to GPLv3.

The MPL2.0 is a per-file strong copyleft license, with an opt-out provision to incorporate MPL-licensed files into a larger project that is under the GPL license. This means that if you only made changes to files containing MPL-licensed code, then you cannot change the license.

Also, if the author of the MPL code oped out of the GPL compatibility (by adding the phrase "Incompatible With Secondary Licenses." to the license notice), then you cannot change the license or use it in a GPL-licensed project.

To be able to publish your app under the GPLv3 license, your app must contain at least one file that does not contain any MPL-licensed code and that is already or can be licensed by you under the GPLv3 license. That triggers the compatibility clause in the MPL license and causes the MPL-licensed code to become dual-licensed under both the MPL and the GPL.

2
  • So to be clear - If I add any file myself, I can choose to make all the files in the project both GPL and MPL? That would be perfect – Dr-Bracket Apr 22 at 15:18
  • Yes, that is correct. – Bart van Ingen Schenau Apr 22 at 15:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.