Search results
The release of MPL 2.0 was the result of a two year process that revised MPL 1.1. A Revision FAQ. documents this process, and explains the most significant changes made. Historical Documents. Various historical documents relating to the Mozilla and Netscape Public Licenses are available, including deprecated versions of the license such as MPL ...
- Version 2.0
Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the...
- 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
These files are made available for historical and reference...
- Version 2.0
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
People also ask
What is the Mozilla Public License (MPL)?
Does Mozilla use the MPL?
How do I use the Mozilla Public License?
What does multiple-licensed mean?
- 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.
Nothing. The Mozilla-provided binary packages already meet the requirements of sections 3.1 to 3.5, and include the notices required by section 3.6. You may distribute them under the terms of the MPL. If you are offering a warranty, you must make clear that it is offered by you alone . Mozilla offers no warranties on our binaries.
The Mozilla Public License 1.1 (MPL 1.1) In January, 1998, Netscape Communications decided to release the binary code of its Communicator web-brower for free. Less than 24 hours later, it … - Selection from Understanding Open Source and Free Software Licensing [Book]
