Search results
No
- No. The license requires that Modifications (as defined in Section 1.10 of the license) must be licensed under the MPL and made available to anyone to whom you distribute the Source Code.
People also ask
Who can use software under the MPL?
Should I use MPL 2.0?
What is an MPL license?
What is MPL & how does it work?
Jan 30, 2024 · Q18: Should MPL be used for non-software works? MPL was written with software in mind, and should generally only be used for software. However, for consistency and simplicity, it may be appropriate to use the MPL for non-software works (such as documentation, images, and sound files) that are written primarily for use in MPL-licensed software.
In principle, this is incompatible with the MPL license, but the MPL-2.0 license has a special exception for allowing the code to be distributed under the terms of the GPL licenses. However, an author can also choose to explicitly disable that exception.
Full Text. MPL is a copyleft license that is easy to comply with. You must make the source code for any of your changes available under MPL, but you can combine the MPL software with proprietary code, as long as you keep the MPL code in separate files. Version 2.0 is, by default, compatible with LGPL and GPL version 2 or greater.
MPL source code files can be directly copied into a (possibly) proprietary software project ( static linking ), while LGPL licensed code must be dynamically linked (loosely linked to the possibly proprietary software project, so that end-users can switch out the licensed software library for another version of the licensed software library).
- I believe you've stated the differences between the Mozilla Public License and the GNU Lesser General Public License accurately, and either may sui...
- The answer of DougM and AER makes a fair point. MPLv2 and LGPLv3 with static exception are the same regarding the events that would trigger the cop...
- Dynamic linking and thus LGPL imposes extra obstacles for packaging the proprietary software product, without promoting more contributions to the o...
Apr 27, 2013 · Multiple licensing works because the person USING the library (that's you) gets to pick which of the available licenses to use it under. So, for a commercial app, you can still use the code by using it under the LGPL (read the LGPL itself for details).
The MPL is an open-source license designed to protect its own code. If you modify MPL code, you need to publish those modifications under the MPL. That's the focus of the license. There's no "viral" requirement to affect the licensing provisions of the rest of your code.
Apr 29, 2024 · Can I use the GPL for something other than software? Why don't you use the GPL for manuals? Are there translations of the GPL into other languages? Why are some GNU libraries released under the ordinary GPL rather than the Lesser GPL? Who has the power to enforce the GPL?
