With the Apache license it is OK to make a closed-source product based on the project's source code.
With the LGPL(/GPL) it is not OK to make a closed-source product based on the project's source code.
With the MPL the core of the project's code is like LGPL(/GPL) license and non-core code can be like Apache license.
The question is rather, what companies would be interested to contribute to LibreOffice, and would rather see an MPL-licensed codebased, compared to the current LGPL.
Posted May 28, 2012 20:43 UTC (Mon) by akumria (subscriber, #7773)
[Link]
Then, presumably, a company wanting to make a commercial product based upon LibreOffice will want to assist in making the portions they need into a robust library they (and others) can re-use.
Then that component can just call into the library, no?
Relicensing and rebasing LibreOffice
Posted May 29, 2012 5:41 UTC (Tue) by jamesh (guest, #1159)
[Link]
Well, that might not help if the target platform doesn't allow the user to replace the library in their copy of your application (e.g. iOS).
Also, if the code you're interested in is common to both LibreOffice and Apache OpenOffice, then why bother creating a library when you could just use the Apache code under the ASL?
Relicensing and rebasing LibreOffice
Posted May 29, 2012 7:52 UTC (Tue) by spaetz (subscriber, #32870)
[Link]
> The question is rather, what companies would be interested to contribute to LibreOffice, and would rather see an MPL-licensed codebased, compared to the current LGPL.
AFAIK, LibO still hasn't given up hope that IBM might want to join in on the fun, and give them the opportunity to still ship their sekr3t-sauce plugins with symphony. AFAIK, that was (one of the) main motivations to go with the MPL in the first place.