Several volunteers have approached board and MC members about one
seemingly secondary issue, which has not been dealt in any way since the
beginning of the LibreOffice project: what structure, and what name,
should we give to the former Native-langage projects that are even to
this day an essential and invaluable part of our community.
A short reminder of what native-language projects are: they're not only
localization projects. They do translation (localization) of
LibreOffice, users support in a specific language, local promotion and
marketing, documentation translation, QA of localized builds, etc.
Because of that, the name is somewhat a non-trivial decision, and it
also calls for a more formalized structure of these teams.
I thought I would start this discussion as I was the lead of the
"Native-Language Confederation" during the times of the old
OpenOffice.org project. Now I no longer work on this, but at least some
of you know me :-) .
Your ideas are welcome.
Co-Founder & Director, The Document Foundation,
Zimmerstr. 69, 10117 Berlin, Germany
Rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted
- [libreoffice-projects] What's in a name? former Native-Language projects and structure · Charles-H. Schulz
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