Is LGPL-3.0 compatible with MPL-2.0?
It depends — here's on what:
Usually fine since each only governs its own files/library, but check the specific pair (EPL has GPL-style frictions). See overrides. Result license is the more restrictive of the inputs. You must satisfy every input license's notice and source-offer terms. Verify pairwise compatibility first.
Resulting work's license: LGPL-3.0-only
General guidance, not legal advice.
Obligations when redistributing as open source
- LGPL-3.0: retain the copyright notice and license text.
- LGPL-3.0: state significant changes made to the code.
- LGPL-3.0: publish the source of any modifications to the library itself.
- LGPL-3.0: modifications to the library must remain under LGPL-3.0.
- MPL-2.0: retain the copyright notice and license text.
- MPL-2.0: state significant changes made to the code.
- MPL-2.0: disclose the source of modified MPL-2.0 files.
- MPL-2.0: modified MPL-2.0 files must remain under MPL-2.0.
Other distribution models
The verdict is the same under every distribution model; the obligations differ. Check this pair in the tool to switch models.