The Mozilla Public License
You'll learn how the Mozilla Public License (MPL) offers file-level copyleft—a middle ground between strict GPL copyleft and permissive MIT-style licenses.
What is the MPL?
The Mozilla Public License (currently version 2.0) applies copyleft at the file level rather than the entire codebase. If you modify an MPL-licensed file, you must share those changes under the MPL. However, you can combine MPL code with proprietary code in the same project, as long as they're in separate files.
Think of it like a mixed neighborhood: some houses follow strict HOA rules (MPL files), while others next door can do whatever they want (your proprietary files). The rules don't spread to neighbors—only to modifications of specific houses.
Why File-Level Copyleft Matters
Unlike the GPL (which spreads copyleft to linked code) or the LGPL (which allows dynamic linking exceptions), the MPL draws boundaries at file granularity:
- Modified MPL files → must remain MPL and open source
- New files you create → can be proprietary, even in the same binary
- Integration allowed → you can build commercial products using MPL libraries
This makes MPL popular for libraries and tools where creators want improvements shared back, but don't want to discourage commercial adoption. Firefox, Thunderbird, and LibreOffice components use MPL for exactly this reason.
Practical Implications
The MPL requires you to document which files are MPL-licensed and make source available for those files only. You can distribute binaries commercially without releasing your entire codebase—just the MPL portions and any changes you made to them.
Key Takeaway: The Mozilla Public License provides file-level copyleft, ensuring modifications to MPL code remain open while permitting proprietary code in separate files—balancing community contribution with commercial flexibility.