Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Christophe,

        This question prolly belongs best on the dev list.

On Wed, 2011-02-16 at 15:28 +0100, Christophe Strobbe wrote:
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

        Yes - on the other hand, this creates more work for LibreOffice, and
(of course) lots of work for you submitting code to OO.o - signing and
faxing a form, CWS creation, etc. etc. That's fine of course by me, but
when it comes to merging (the inevitably different) changes from OO.o it
just makes even more work when we merge that stuff in. So this practise
is essentially not recommended.

2.b. Can I contribute the code to LibreOffice while the acceptance of 
my patch to is still pending?

        So - if it is licensed under LGPLv3+/MPL we are happy to accept it -
please post it to the dev list, we're eager to see it :-) if Oracle owns
the copyright[1], but you can license it to us under LGPLv3+/MPL, I (for
one) don't much mind who owns it :-)

        But again, you consume LibreOffice engineering resource doing merging
changes, and our life is easier if you don't do that in most cases :-)



[1] - and their assignment-cum-license is a pretty thorough way of
giving away your rights.
--  <><, Pseudo Engineer, itinerant idiot

Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


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.