Mozilla Public License

Mozilla Public License

The Mozilla Public License is a weak copyleft free and open-source software license created by the Netscape Communications Corporation legal team and stewarded by the Mozilla Foundation and the Mozilla Corporation. It was designed to bridge models used by the GNU General Public License, the Apache License, and permissive licenses such as the MIT License and the BSD license while facilitating commercial distribution by entities like Red Hat, IBM, Microsoft, and Google. The license has been applied in projects led by the Mozilla Corporation and adopted by diverse organizations including Adobe Systems, Cisco Systems, Oracle Corporation, Facebook, and Dropbox.

History

The MPL originated within the late-1990s software landscape shaped by the Netscape Navigator era and legal frameworks influenced by the Berkeley Software Distribution lineage, the GNU Project, and litigation such as AOL vs. Microsoft-era antitrust scrutiny. Key contributors included in-house counsel at Netscape Communications Corporation and external advisors connected to legal practices at DLA Piper and firms representing open-source stakeholders. The MPL 1.0 and subsequent MPL 1.1 revisions responded to compatibility issues raised by projects linked to Apache Software Foundation, Free Software Foundation, and corporate adopters like Sun Microsystems. The formalization of MPL 2.0 involved public consultation with participants from Canonical, Red Hat, IBM, Open Source Initiative, and representatives from governments such as the United States and European Commission who had procurement and standards interests. Adoption milestones include integration into flagship projects connected to Mozilla Firefox, Thunderbird, and modules used by LibreOffice contributors and companies collaborating with Eclipse Foundation and Linux Foundation initiatives.

Key Terms and Conditions

The license requires source disclosure for modifications to files under its scope and provides a file-level copyleft that contrasts with the project-wide copyleft of the GNU General Public License and with the fully permissive terms of the MIT License and the BSD license. It allows distribution of combined works under different licenses, enabling coexistence with components under the Apache License 2.0, Creative Commons-licensed documentation, and proprietary modules developed by firms like Apple and Samsung. The MPL grants patent licenses similar to provisions found in the Eclipse Public License and includes termination and warranty disclaimers influenced by precedents in litigation involving Oracle Corporation and patent assertions by entities such as Microsoft and Qualcomm. Contributors, whether individuals from projects like GNOME or corporations such as Intel Corporation, retain copyright while granting broad rights to recipients, and the license accommodates contributor agreements like those used at Apache Software Foundation and Mozilla Foundation.

Versions and Compatibility

MPL 1.0 and MPL 1.1 saw use in the late 1990s and early 2000s, but compatibility tensions with the GNU General Public License and the Apache License prompted the drafting of MPL 2.0. The MPL 2.0 revision improved compatibility with GPLv3 and clarified patent and network use terms discussed in forums attended by representatives from Free Software Foundation, Open Source Initiative, Red Hat, Canonical, and corporate counsel from Google and Microsoft. MPL 2.0 introduced clearer patent covenants and enhanced internationalization to address concerns raised by contributors from the European Union, Japan, India, and Brazil. Compatibility debates have invoked case law and policy discussions connected to European Court of Justice precedents, standards bodies like W3C, and licensing harmonization efforts involving the Software Freedom Law Center and national standardization agencies.

Adoption and Notable Uses

Prominent projects using the license include flagship products developed by organizations such as the Mozilla Corporation—notably the Mozilla Firefox web browser and Thunderbird email client—and components incorporated into infrastructure maintained by Adobe Systems, IBM, Samsung, and Dropbox. Other adopters span the Eclipse Foundation ecosystem, collaborative initiatives with the Linux Foundation, and specific modules created by contributors from Google and Facebook. Educational and research institutions including Massachusetts Institute of Technology, Stanford University, and University of California, Berkeley have used MPL-licensed code in academic projects, while governments like those of France and the United Kingdom have evaluated MPL-licensed software for public procurement. Commercial vendors in sectors represented by Siemens, Philips, and GE have also integrated MPL components into products where mixed licensing was necessary for interoperability with standards from bodies like IETF and IEEE.

Legal and Community Impact

The MPL shaped licensing strategy debates among the Free Software Foundation, the Open Source Initiative, and corporate stakeholders including Microsoft Research, IBM Research, and legal scholars from institutions such as Harvard Law School and Stanford Law School. Its file-level copyleft influenced derivative licensing choices in projects affiliated with the Apache Software Foundation, Eclipse Foundation, and various consortia negotiating intellectual property frameworks with companies like Oracle Corporation and SAP. MPL 2.0’s patent and compatibility clarifications reduced transaction costs for contributors from multinational corporations and spurred adoption in cross-jurisdictional projects involving the European Commission’s open-source policy units and national digital transformation programs. The license continues to be a pragmatic option cited in debates at Open Source Initiative panels, academic symposia at MIT Media Lab, and legal analyses by the Software Freedom Law Center and independent commentators in outlets associated with The New York Times and The Guardian.

Category:Software licenses