On Fri, 2005-09-09 at 00:15 +0400, Aiet Kolkhi wrote:
I agree. Coordinated approach is much more efficient and greatly
improves the overal quality of the translation, as well as glossary
and style consistency.
On 8/29/05, Noriko Mizumoto <noriko(a)redhat.com> wrote:
> To avoid confliction committing same document file in same time by more
> than one translators (or maintainer), access right should be restricted
> to the maintainer, I think.
There is a timing concern here.
24 October is when the release notes freeze for translation. By then,
if we do not have separate CVS and automated file-locking available
(Plan A), we will have to use Plan B:
** Plan B **
1. One or more translators from every language gets CVS access
2. Language teams need to coordinate who is translating what. This is a
3. Translations are put back into /cvs/docs/release-notes/ tree at the
same level as the *-en.xml file.
4. Everything that is in CVS by 31 October is shipped with the -en
version of the FC5 test1 relnotes.
5. It is OK if the translations are technically accurate but buggy
translations, they are test translations, not the final release.
Does this sound OK?
If so, please get your CVS access soon, to avoid the rush. This page
explains what is needed for access:
We can move the files around later and other CVS magic, when we need to.
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide