MPL 2.0
Generated by GPT-5-miniExpansion Funnel Raw 65 → Dedup 0 → NER 0 → Enqueued 0
| MPL 2.0 | |
|---|---|
| Name | Mozilla Public License 2.0 |
| Author | Mozilla Foundation |
| Introduced | 2012 |
| License | Free and open-source software license |
| GPL compatibility | Yes (with caveats) |
| Copyleft | Weak copyleft |
MPL 2.0 is a free and open-source software license published by the Mozilla Foundation that revised earlier terms to improve compatibility and clarity for developers, corporations, and projects. The text harmonizes obligations for source distribution with pragmatic allowances for larger codebases and proprietary components, balancing interests familiar to stakeholders such as Red Hat, Microsoft Corporation, Google LLC, IBM, and Apple Inc.. MPL 2.0 influenced licensing choices across projects maintained by entities including the Mozilla Corporation, Eclipse Foundation, Apache Software Foundation, and Linux Foundation.
Overview
MPL 2.0 is a file-level weak copyleft license that imposes obligations on modified source files while permitting aggregation with files under different terms; this model contrasts with the strong copyleft approach used by GNU Project's GPL family and the permissive approach used by MIT License and BSD licenses. The license was crafted in the context of debates involving stakeholders such as Eric S. Raymond, Richard Stallman, Brendan Eich, Mitchell Baker, and legal teams from firms like Perkins Coie and DLA Piper. MPL 2.0 addressed interoperability issues that had affected projects like Firefox, Thunderbird, LibreOffice, and components originating from Netscape Communications Corporation history.
Key Provisions and License Text
MPL 2.0 requires recipients to make available source code for any files that are "Covered Software" when distributed in executable form, and it defines "Modifications", "Larger Work", and "Recipient" in ways shaped by precedents such as cases involving Oracle Corporation and Sun Microsystems. The license permits distribution of a Larger Work under different terms so long as MPL-covered files remain under MPL terms, a provision aligned with practices at organizations such as Canonical Ltd., Samsung Electronics, Intel Corporation, and Qualcomm. Contributors must include a notice file and may offer warranty disclaimers consistent with standards used by projects like OpenJDK, KDE, and GNOME Project. The MPL 2.0 license text clarified patent license grants and patent retaliation provisions influenced by discussions involving Microsoft Corporation, Google LLC, Facebook, Inc. (now Meta Platforms, Inc.), and patent strategies seen at IBM.
Compatibility and Permissive Interactions
A major design goal of MPL 2.0 was compatibility with permissive and copyleft licenses: the final draft included compatibility mechanisms to allow re-licensing of MPL-covered code under GPLv2-or-later and GPLv3 in combined works, addressing compatibility disputes that had involved Debian Project, FSF, and corporate contributors from Amazon.com, Inc. and Oracle Corporation. The license facilitates inclusion of MPL code in projects governed by the Apache Software Foundation and interoperates with permissive terms employed by Eclipse Foundation projects, enabling collaborations among contributors from Red Hat, Microsoft Corporation, Cisco Systems, and VMware, Inc.. MPL's text was also structured to coexist with contributor license agreements used in contexts like Linux Foundation initiatives and independent projects such as Mozilla Firefox extensions and Rust (programming language) ecosystems.
Adoption and Notable Use Cases
MPL 2.0 saw adoption by prominent projects and organizations, including the Mozilla Corporation for major components of Firefox, the LibreOffice project for selected modules, and the OpenJDK ecosystem for certain ancillary components. Corporations such as Amazon.com, Inc., Google LLC, Microsoft Corporation, Intel Corporation, and Samsung Electronics have used MPL-licensed components within larger product stacks, including cloud services and embedded systems. Notable repositories and initiatives using MPL-style licensing decisions include efforts at Mozilla Developer Network, Eclipse Foundation incubations, and collaborations between Mozilla and academic centers like MIT and Stanford University.
Legal Interpretation and Case Law
While MPL 2.0 has not generated as many high-profile litigations as GPL disputes involving SCO Group or Oracle America, Inc. v. Google, Inc., its provisions have been the subject of legal analysis in briefs and opinions by counsel from Perkins Coie, Morrison & Foerster, and firms representing entities such as Netflix, Inc. and Dropbox, Inc.. Courts and tribunals in jurisdictions influenced by precedent from United States Court of Appeals for the Ninth Circuit and contract law analyses in places like United Kingdom and Germany have considered issues like scope of "distribution", patent termination clauses, and file-level obligations similar to those adjudicated in disputes concerning GPL and Apache License cases. Academic commentary from scholars at Harvard University, Yale University, and Stanford Law School has compared MPL 2.0's enforceability and policy effects with licensing regimes advocated by FSF, OSI, and institutional repositories at Cornell University.
Version History and Development
MPL 2.0 was promulgated in 2012 as a successor to the original MPL 1.1, following multi-stakeholder drafting that involved the Mozilla Foundation, corporate legal teams from Microsoft Corporation, Red Hat, Google LLC, and community representatives from Debian Project and Free Software Foundation. The process included public consultations, legal reviews by firms like Perkins Coie and DLA Piper, and coordination with standards groups including the Open Source Initiative which later approved MPL 2.0. Subsequent discussions about patent and compatibility updates have involved ongoing contributions from entities such as Mozilla Foundation, Eclipse Foundation, Linux Foundation, and corporate stewards at IBM and Intel Corporation.