Search results
Jan 30, 2024 · This is the Mozilla Public License (MPL) version 2.0 FAQ. It aims to answer the most common questions people have about using and distributing code under the MPL. Please note that, while this FAQ is intended to be accurate and helpful, it is not the license, and may not cover important issues that affect you and your specific situation.
If you do not delete the provisions above, a recipient may use your version of this file under either the MPL or the _____ License." [NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code.
MPL is a copyleft license that is easy to comply with. You must make the source code for any of your changes available under MPL, but you can combine the MPL software with proprietary code, as long as you keep the MPL code in separate files.
However, an author can also choose to explicitly disable that exception. From a legal standpoint, this means that any license is permissible, but the GPL license can be problematic if your project contains/depends on code under the MPL-1.3 license or the MPL-2.0 license that is marked as "Incompatible with Secondary Licenses".
If you do not delete the provisions above, a recipient may use your version of this file under either the MPL or the [___] License." NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code.
People also ask
What is an MPL license?
What is full text MPL?
Do modifications need to be licensed under the MPL?
What's changed in MPL 2.0?
So the LGPL can potentially extend its copyleft to new files. Edge-case: Using MPL enables users not to share their improvements. MPL is a file-level copyleft license. It means that if somebody embed it in a larger project (statically or dynamically) and make a change to your file, he only has to release the change made to this particular file.
May 9, 2016 · Yes, you can combine code that is licensed under MPL 2.0 into a project that contains source code from one or more other licenses, including the MIT License. However, the individual source files licensed under the MPL will need to remain licensed under the MPL, including any modifications that you make to the MPL-licensed files.
