Dobry vecer,

projekt lokalizace Openoffice.org do cestiny je velmi blizko cile (tedy
plne integrace cestiny do originalni verze). Abychom mohli fungovat jako
opravdovy lokalizacni build je nutne, aby nase finalni verze prosla
overenim kvality, tzv. Q&A. Tento proces je pro lokalizacni buildy popsan
na strankach uvedenych v nize citovanem dopise
(http://qa.openoffice.org/localized/).

Pro tento projekt hledame cloveka, ktery by byl ochoten vest ceskou Q&A,
nastudovat, jak vse vlastne funguje, vypracovat popis úplny tohoto procesu
pro nove testery a aktivne se podilet na samotnem overovani kvality ceskych
buildu. Vedouci tohoto projektu bude mit na starosti webove stranky ceskeho
Q&A projektu na strankach http://cs.openoffice.org/ i samotne stranky, na
kterych probiha testovani kvality ceskych lokalizacnich buildů.

Pokud dosahneme toho, ze nase buildy budou overeny, mohou byt sireny
v ramci OpenOffice.org Mirror Network a obecne stoupne jejich kvalita,
nebot vyvojari a prekladatele dostanou kvalitni feedback od testeru a budou
moci zjistene chyby lepe odstranovat.

Mate-li nekdo zajem o takovou praci, nevahejte a predstavte nam na dev@cs
sve vize. Nebojte se, plnou podporu vyvojarskeho tymu mate k dispozici.

Pokud mate "pouze" zajem o to stat se testerem buildů, nevahejte a take se
prihlaste, at si můze novy vedouci projektu vybirat sve
spolupracovniky. Tato prace je vhodna i pro typicke uzivatele, kteri dnes
a denne pracuji s OpenOffice.org a nas projekt je zajima.

Diky za nabidky.

From: Louis Suarez-Potts <louis@openoffice.org>
To: <dev@l10n.openoffice.org>
Message-ID: <BAC5ECBB.33847%louis@openoffice.org>
Subject: [l10n-dev] Localized builds

Hi
As many of you know, we have created a system for testing localized builds.
The full system is explained here:
    http://qa.openoffice.org/localized/

What it describes is a process by which builds created by the community
(including Sun) can be characterized and uploaded to our extensive mirror
network (we have 60 or so servers).  Tested builds are characterised as such
and can be called "official"; untested are unofficial.  Tested builds go to
the /localized directory; untested to /contrib/localized (this may change).
An explanation of this is on the page referenced above and also here,
http://distribution.openoffice.org/files.html.  The idea is to make it easy
for our mirror network to distribute relevant directories and to maximize
the distribution of files. It's worked well, so far.

The system of testing works with the Native-Lang projects. There are now ten
or so such projects, and leads of the projects help with coordinating the
process. 

But there are some vague areas.
1. Who creates the localizations?
    *The table of responsibilities on l10n names those who are responsible
(http://l10n.openoffice.org/localization_responsibilities.html).  However,
others also make builds, causing some confusion.  Ideally, all those
creating builds work with those listed on the table.

2. Who is responsible for making sure the build is deployed to the server
network?
    *Right now, if a localization has no N-L associated, it is anyone's
guess.  (Sander and Armin and dedicated community members do many of the
locs but not all.)  I'd like to change that, and suggest a process by which
localizations can be if not all tested then efficiently placed in the server
network. 
    *I would like to suggest that all who are working on localizations and
who are part of l10n follow the process described above. That is, for builds
to be entered into QA'ing or, if that is not relevant, then uploaded to the
gateway server for later dissemination. (Right now, we have mainly 1.0.1
builds out there but there are more than that done; and the ones that are
done are being done almost independently.)

The point of this process is to make it more certain that the mirror network
and thus more people will be able to download OpenOffice.org in their
language. It is also to put in place a process for testing all possible
builds.

Thus, to process would be:
1. Build is localized by a member of this project listed on the
responsibilities page.
 2. Build is submitted to QA for testing. If not N-L project is available
and if testing is not an option, then the build is directly uploaded to the
gateway server.
  3. The QA status page maintainer updates the status page.
4. I update the download pages.

Note that updating the status page is really important here. It is what
tells us if a build is ready.
Finally, I'd like us to use releases@openoffice.org more for indicating
md5sums, further status, and so on. It is the standard list for things
having to do with releases and localized builds are of course releases. They
represent a major part of OpenOffice.org and help greatly in furthering
OpenOffice.org and StarOffice.

So, that's the process.  Please comment on this list.

Thanks

Louis Suarez-Potts
Community Manager
OpenOffice.org