Search results
About the License. Mozilla is the custodian of the Mozilla Public License ("MPL"), an open source / free software license. The current version of the license is MPL 2.0 ( html | plain text ). If you want to use or distribute code licensed under the MPL 2.0 and have questions about it, you may want to read the FAQ.
- Version 2.0
1.12. “Secondary License” means either the GNU General...
- MPL 1.1
the licenses granted in this Section 2.1 and are effective...
- Mozilla Licensing Policies
Mozilla Monitor. See if your email has appeared in a...
- Appropriate Header Text
Mozilla License Headers This page gives copy-and-pasteable...
- Historical Documents
Mozilla Public License, version 1.1 This is the Mozilla...
- Version 2.0
- Q16: Is "minified" Javascript Source Code?
- Q17: What Does "Distribute" Mean?
- Q18: Should MPL Be Used For Non-Software Works?
- Does The MPL 2.0 Give Me Permission to Make My Own License by Changing The MPL?
- What Does "Used" Mean in The Definition of Contributor Version (Sec. 1.2)?
No. MinifiedJavaScript, while not an "executable" in the software engineering sense of the word, is difficult for humans to read, edit, and modify. As such, it is not "the preferred form for modification" and so it is not Source Code as defined by the license. Therefore, minified JavaScript is the Executable form, and the responsibilities set out i...
The MPL uses "distribute" in the sense of delivery of a copy of the software to another person or entity. We do not use distribute to mean "make available" in the sense of "making functionality available over the web without delivery of a copy of the software." So e.g. in a web-based application, the code which runs on the server is not 'distribute...
MPL was written with software in mind, and should generally only be used for software. However, for consistency and simplicity, it may be appropriate to use the MPL for non-software works (such as documentation, images, and sound files) that are written primarily for use in MPL-licensed software.
Yes but, as with MPL 1.1, we strongly discourage you from doing so. It will almost certainly make your software much less popular and less widely used. Software developers and companies are already aware of and understand popular licenses like the MPL. If you create your own, they will have to perform a legal assessment of your changes - and may co...
“Used” in Section 1.2 means an action taken in the process of creating a Contribution or Modification.
Mozilla Public License 2.0 Requirements. Open source software licenses fall into two categories: permissive and copyleft. Copyleft licenses, in turn, come in two flavors: strong and weak. The Mozilla Public License 2.0 is in the latter group. The difference between the two forms of copyleft licenses lies in the scope of source code to be shared.
People also ask
When did the Mozilla Public License come out?
What is the difference between MPL & Mozilla Public License?
What is the difference between GPL v2 and V3 copyleft licenses?
Can a software be incompatible with a secondary license?
The Mozilla Public License (MPL) is a free and open-source weak copyleft license for most Mozilla Foundation software such as Firefox and Thunderbird. The MPL license is developed and maintained by Mozilla, which seeks to balance the concerns of both open-source and proprietary developers; it is distinguished from others as a middle ground between the permissive software BSD-style licenses and ...
- January 3, 2012
- Mozilla Foundation
Jan 5, 2012 · The Mozilla Foundation recognizes how important this compatibility is to free software projects, and to date they've made their own projects compatible by tri-licensing them under the MPL 1.1, GPL version 2 or later, and LGPL version 2.1 or later. Now they've taken the next step by including compatibility provisions in MPL 2.0.
Jan 4, 2012 · Jan 3, 2012 11:30 pm PST. Mozilla announced Tuesday the release of version 2.0 of the Mozilla Public License (MPL), which provides compatibility with the Apache and GPL licenses, opening up a ...
