Mozilla Public License 2.0, explained

Weak copyleft MPL-2.0

MPL-2.0 is a file-level copyleft: you can combine MPL code with closed-source code, but changes to the MPL files themselves must be shared under the MPL.

Not legal advice. Read the licence text for the exact terms.

What it allows

  • Use the code in commercial and closed-source products
  • Combine it with code under other licences in a larger work
  • Rely on a patent licence from contributors

What it requires

  • Make the source of MPL-covered files (with your changes) available to the people you distribute to
  • Keep the licence notices
  • Tell recipients where to get that source

When it matters

Shipping an appAllowed. If you changed MPL files, publish those files' source; your own files stay yours.
A hosted service (SaaS)No obligation while you do not distribute the code.
Internal useNo obligation.

Its family: weak copyleft

You can use the library in a closed-source product, but changes to the library's own files (MPL, EPL) or to the library itself (LGPL) must be shared under the same licence. LGPL also expects users to be able to replace the library, which is simple with dynamic linking and harder with static linking or bundling.

Questions

Is MPL-2.0 compatible with GPL?

Yes, by default MPL-2.0 allows its files to be distributed under GPL-2.0 or later, LGPL or AGPL as part of a larger work, unless the author marked them "Incompatible With Secondary Licenses".

Other licences

Published ; awaiting review.