Search results
No
- No. The license requires that Modifications (as defined in Section 1.10 of the license) must be licensed under the MPL and made available to anyone to whom you distribute the Source Code.
People also ask
Can I distribute MPL-licensed source code?
Can I combine source code licensed under the MPL?
What is an MPL license?
Can I modify the code from MPL?
Jan 30, 2024 · However, new files containing no MPL-licensed code are not Modifications, and therefore do not need to be distributed under the terms of the MPL, even if you create a Larger Work (as defined in Section 1.7) by using, compiling, or distributing the non-MPL files together with MPL-licensed files.
The MPL license is a copyleft license, which means that in principle people are not allowed to distribute code that is under the MPL-2.0 license under different terms. The GPL licenses (including LGPL and AGPL) require that the entire application is distributed under the terms of the GPL license.
MPL’d code can be included in software that’s sold commercially. Change the code. Authors can alter or modify the licensed code. Distribute the code. An individual or company can make their reworked version (s) of the code available to others. Use patent claims. Contributors to the licensed code provide an explicit grant of patent rights to users.
Nov 28, 2016 · new files containing no MPL-licensed code are not Modifications, and therefore do not need to be distributed under the terms of the MPL. If you have modified MPL-licensed files, then you must share the modifications. Quoting from the MPL FAQ: Q9: I want to distribute (outside my organization) MPL-licensed source code that I have modified.
May 9, 2016 · You can mix MPL and MIT licensed code in the same project. What you can't do (without the permission of it's copyright holders) is remove the MPL license from the code. This means that if you or anyone else wants to distribute the combined source tree or binaries built from both the MIT and MPL parts of it it they must comply with both licenses ...
Feb 1, 2023 · If you distribute your proprietary software either in binary or source form to other parties ("recipients"), you must make the MPL2-licensed source code (with or without modifications) available to those other parties ("recipients"), in order to fulfill the weak copyleft requirements of MPL2.
