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


Hi,

Just to be 100% compliant, you need to subject your past, present and future contributions to 
MPLv2, along with LGPLv3+. Pasting the sample statement from 
https://wiki.documentfoundation.org/Development/GetInvolved: 
<https://wiki.documentfoundation.org/Development/GetInvolved:>

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

Thank you for your contribution,
Shinnok

On Nov 29, 2017, at 5:50 PM, cengiz celik <cengiz.celik@tubitak.gov.tr> wrote:

Hello LibreOffice team,

In line with our general institutional policy, code contributed to
open source projects is made available under the terms of that
project's license. All past and present contributions to LibreOffice
from TUBITAK-ULAKBIM (The Turkish Academic Network and Information
Centre) are available under LGPLv3+/MPL. Until further notice, all
future contributions to LibreOffice from TUBITAK-ULAKBIM are available
under LGPLv3+/MPL.

Pardus is a project run by TUBITAK-ULAKBIM, centered around a Debian-based GNU/Linux 
distribution. This statement covers also
contributions from the Pardus project.


Regards,


Cengiz Celik

Pardus Project Manager

_______________________________________________
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.