Hi all,
BRM wrote (03-11-10 14:41)
So let's get back to the real issue - the _only_ reason for copyright
assignment is to help the organizers of LibreOffice (TDF) with keeping the
license
current - e.g. moving from LGPLv3 to LGPLv4, etc.
If the TDF SC and LibreOffice developers are not concerned about that issue
(and from what I have seen in this thread the guidance is already to license as
LGPLv3+ for new contributions and there is nothing we, TDF/etc, can do about
Sun/Oracle owned code), then there is no reason for copyright assignment,
pure and simple.
Any kind of other fear mongering to get copyright assignment put in place is
unjustified.
However, all that doesn't mean it might not be good for TDF to offer developers
the choice of copyright assignment without requiring it; something that would
also be good to offer the estates of deceased developers when those situations
arrive. But that is all - an option should the developer with to exercise it.
Having read all fine explanations, (strong) opinions, I think this is
simply the best we can do.
So +1 from my side,
Cor
--
- giving openoffice.org its foundation :: The Document Foundation -
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
Context
- Re: [tdf-discuss] Copyright Assignments & the Document Foundation (continued)
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.