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

[tdf-discuss] Licenses for extensions


I guys,

I have a simple doubt about the licensing scheme to be used for building
extensions.

I known that to be published on the extensions web site they have to have
an Open Source Licence (GPL, BSD,etc...)

But if you just want to make an extension for any purpose, and you don't
need it to be published, can any license be used? Even a closed source one?

Is there any connection between libreoffice's license and the extensions
license? Does it also apply to OpenOfffice.org?

Thanks for any replies

Cheers


-- 
*Flávio Moringa*
Project Leader

Caixa Mágica Software
Energia Open Source
Rua Soeiro Pereira Gomes, Lote 1 - 4.º B,
Edifício Espanha, 1600-196 Lisboa - Portugal
Tel.: +351 217 921 260 Fax: +351 217 921 261
http://www.caixamagica.pt
https://twitter.com/flaviomoringa
https://www.facebook.com/flaviomoringa<https://www.facebook.com/flavio.moringa>
http://pt.linkedin.com/in/flaviomoringa
http://people.caixamagica.pt/flaviomoringa

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

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.