On 04-09-2012 17:13, Jay Lozier wrote:
Following up on Marc's comments, how many of our non-dev contributors
are active in multiple areas. It seems like I often see the same people
in many areas.
Good point.
One of our advantages is the strong localization community.
First of all we can at least try to invoke these people in other areas
like QA and documentation.
But we should also learn from the success. LibreOffice is released in
more than one hundred languages. The localized versions are released on
the same day as the English. This fact has motivated a lot of people to
help with translation.
The localization process is kind'a self motivating:
* When translating the application we can immediately see a result as
progress in Pootle.
* We can see that our work makes sense in real life.
* We see our local language being released on the same date as the
English version.
* Localisation can be performed as a crowd task (I don't have to do
everything my self, we can work together)
Can we somehow transfer these motivating feelings to other projects?
/Leif
--
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.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.libreoffice.org/global/marketing/
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.