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
Can I distribute MPL-licensed source code?
What is an MPL license?
Who can use software under the MPL?
Do modifications need to be licensed under the MPL?
Jan 30, 2024 · However, new files containing no MPL-licensed code are not Modifications, and therefore do not need to be distributed under the terms of the MPL, even if you create a Larger Work (as defined in Section 1.7) by using, compiling, or distributing the non-MPL files together with MPL-licensed files.
Yes. However, if you distribute/sell binaries, then you may not charge extra for the source code. And, as the MPL license is a weak copyleft license, you are giving the users of your library also the right to distribute it further, which means that selling copies of the software is not sensible from an economics viewpoint.
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...
Choose the Right License. When selling your code, the license you choose is crucial. It determines how buyers can use the code after purchase. Here are a few common types of licenses: Proprietary License: Allows the buyer to use the code but not to resell or distribute it. This is typical for software that you want to keep exclusive.
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.
The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include how they can obtain a copy of this License with every copy of the Source Code You distribute.
6. I am distributing code written by someone else under the terms of MPL 1.1. Can I distribute that code under the terms of MPL 2.0 instead of MPL 1.1? If so, how? Yes, you can, because MPL 1.1 allows anyone who received code under the terms of MPL 1.1 to distribute under the terms of a later version of the MPL.
