Search results
Jan 30, 2024 · Q10: I want to distribute (outside my organization) an executable program based on MPL-licensed source code that I have modified. What do I have to do? You must make available the MPL-licensed portions of the source code as described in the previous question, and inform the recipients how they can obtain such source code (Section 3.2).
The MPL license is a copyleft license, which means that in principle people are not allowed to distribute code that is under the MPL-2.0 license under different terms. The GPL licenses (including LGPL and AGPL) require that the entire application is distributed under the terms of the GPL license.
People also ask
Can I combine source code licensed under the MPL?
Can I distribute MPL-licensed source code?
What is an MPL license?
Can I modify the code from MPL?
May 9, 2016 · Yes, you can combine code that is licensed under MPL 2.0 into a project that contains source code from one or more other licenses, including the MIT License. However, the individual source files licensed under the MPL will need to remain licensed under the MPL, including any modifications that you make to the MPL-licensed files.
That doesn't mean you can't also sell it (like they sell Linux CD's) but you must also release the source code for free. That might work for you, but probably not. LGPL: If you use it in your application then you can still have a closed source proprietary licensed application.
- It is perfectly all right to sell an "aggregrate" of closed-source and open-source software according to the GPL FAQ. If the company compiled a Lin...
- IANAL, but this is what I've learned. I would be very interested to know if any of it is incorrect: LGPL: If you statically link it it in your app...
- There are clear cases and then some muddy one for which you'll get more opinion that lawyers you present the case. Your rules match my understandi...
- Git is covered by GPLv2. Generally, if you have any questions on FSF's licensing, the way to go is. the license itself (it's not some doorstopper...
- GPL is NOT compatible with closed source. If they used GPL-licensed packeges/modules and closed the source, in the general case they would be in vi...
4. 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. The idea of the attribution requirement is to make people aware of the ...
Aug 20, 2021 · 3. The Mozilla Public License 2.0 is a license that specifically allows you to include source code licensed under it, in any program without restrictions, provided users are given a copy of the MPL-licensed code, and the license is reproduced. This is in a way a step between the LGPL, which requires you to give users a method by which to modify ...
Nov 28, 2016 · You must make available the MPL-licensed portions of the source code as described in the previous question, and inform the recipients how they can obtain such source code (Section 3.2). And finally, yes providing a notice with a link to the source code is sufficient. Whether it is the original source code or the source code of your modified ...
