Hello Christophe,
Le Wed, 16 Feb 2011 15:28:43 +0100,
Christophe Strobbe <christophe.strobbe@esat.kuleuven.be> a écrit :
Hi,
I have a question about licences and copyright. As many of you know,
contributing code to the core of OpenOffice.org requires that one
signs the Oracle Contributor Agreement [1] (which is identical to the
Sun Contributor Agreement). Extensions are exempt from this [2].
So, IANAL, I'm not Oracle, this is not a TDF official statement, don't
put your cat in the microwave, etc, etc....
1. Now imagine that I contribute code to LibreOffice and the
contribution is accepted. Is it then still acceptable (from a
copyright point of view) to sign the Oracle Contributor Agreement and
submit the same code to OpenOffice.org?
Yes.
2. Conversely, if I sign the Oracle Contributor Agreement and submit
code (and it gets accepted, otherwise the copyright reverts to me),
can I then still submit the same code to LibreOffice or would that
cause problems for LibreOffice (because Oracle now shares copyright
of the code I submitted)?
Yes. Actually that's what we do when we "pull" the OOo codebase over to
us.
2.b. Can I contribute the code to LibreOffice while the acceptance of
my patch to OpenOffice.org is still pending?
Yes.
Best,
Charles.
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***
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.