On Fri, Nov 25, 2011 at 9:01 PM, Jean Weber <email@example.com> wrote:
The existing user guides are licensed the same as the OOo guides they were derived from, and the
templates include this licensing information on the Copyright page (GPL and CC-BY dual license).
NEW documents, however, could be licensed differently. I propose that new docs be dual licensed
CC-BY-SA (preferred by LibreOffice) and Apache (so our work can be reused by Apache OpenOffice
and other products).
If this group agrees, or if there are no objections, I will change the template. Any new docs
created from the template would then show the new license info.
Note 1: Changing copyright (license) info in the template will not change it in existing docs,
even when they are updated to a new template. Styles and footers change, but existing text in the
body of the docs does not.
Note 2: We can't change the license on existing docs without contacting the original contributors
and getting their agreement. However, that doesn't prevent us from licensing new docs differently.
The thought comes to me that maybe it would be a good idea to consult
the BoD about this question? I'm fairly certain they'll have input to
offer about licensing issues...
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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