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


Hi,

doesn't CC0 also apply to code as well? In any case I don't claim any
copyright on my code. Anyway here goes:

All of my past & future contributions to LibreOffice may be licensed under
the MPLv2/LGPLv3+ dual license.

Best wishes,
Christoph

jan iversen <jani@documentfoundation.org> schrieb am Mi., 10. Feb. 2016
08:15:

Hi

Just to be sure, with this license statement you can contribute
documentation but not code, see the step-by-step guide if you want to
contribute code.

rgds
jan i.


Sent from my iPad, please excuse any misspellings

On 10 Feb 2016, at 07:56, jan iversen <jani@documentfoundation.org>
wrote:

WELCOME
Thanks for your license statement.

If you want help to get started or have any questions, then please
contact me. I am here to help you (and others) in getting their first patch
submitted.

LibreOffice is a very big program and getting it built, setting up
gerrit, and getting the first patch right can be a bit challenging,
therefore do not hesitate to email me if you want help.

We have made a step by step guide to help you get started:

https://wiki.documentfoundation.org/Development/GetInvolved/DeveloperStepByStep

rgds
Jan Iversen.

Sent from my iPad, please excuse any misspellings

_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


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.