Hi Ben,
On Wed, 2011-06-01 at 12:37 -0700, BRM wrote:
FYI - LGPL/GPL does not _require_ that code be contributed back to the
_community_. Projects work best when that happens, but that is not a
requirement.
True - on the other hand, if millions of people have the right to get
the source code (a mass market product). If a copy-left license is used
- it means the cheapest way to do that is to provide the source to
everyone. If no (C) assignment is required, then those changes can
trivially be merged, of course that is the LibreOffice structure.
But a fair point, it is conditioned to distribution :-) It is also the
case that the Apache license has no requirement to share changes with
anyone. Some argue that this lack of requirement encourages sharing, I
am very un-persuaded by that personally and historically around OO.o
this has clearly not been the case ;-)
Regards,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.