Am 06/29/2011 04:12 PM, schrieb Greg Stein:
On Wed, Jun 29, 2011 at 09:11, Marcus (OOo)<[email protected]> wrote:
Right. Maybe we should split this into 2 parts:
1. The very first build(s) to handle fixes for build breaker:
IMHO here it should be enough to have en-US only
For better or worse, the ASF is US-centric, so this makes sense.
I thought about en-US as it's the master language in the source, but anyway.
2. If this is done the next builds can be also used for looking into the
localizations.
We had the following set of languages for our developer milestones (DEV300
and OOO340):
- English (US) as master language
- German due to historical reasons and we had the most testers here
- French for the same reason IMHO and long strings
- Japanese due the CJK characters and to test RTL writing
- Russian due to Cyrillic charachters
- Arabic due to the characters and to test bidi writing
I doubt that we'll see the same number of people step up, that OOo saw
(say) a year ago. With the stagnation during the Sun/Oracle
acquisition, with the LibreOffice initiative, and with the recent move
to the ASF, the entire ecosystem is kind of separated. I believe it
will take some time for the system to settle down and for people to
decide where they would like to contribute.
Sure, it was just an example and why these languages were choosen. Of
course we have to look at the new contributors and then decide which
languages to build frequently for testing.
It would be great to place the above onto our wiki as "nice to have".
But I believe it will take us a while to reach it.
Done
Marcus
