Hi all,
As a lot of you know, we as translators have access to the documentation cvs.
Now, a lot of translators are member of cvsdocs. But you maybe not need that: if you're not working on the original docs, you don't need that. Having cvsl10n group membership is enough: you get all access to /po directories and files.
So should we revoke everyone just translating from cvsdocs and add them to cvsl10n (if you're not in there yet).
Thoughts, suggestions?
Bart
Hi,
Now, a lot of translators are member of cvsdocs. But you maybe not need that: if you're not working on the original docs, you don't need that. Having cvsl10n group membership is enough: you get all access to /po directories and files.
indeed having access to cvsdocs is needed, because in order to build documentation you need to create a "Draft" image and commit it, and you need cvsdocs access for this. This step is only needed the first time you translate documentation, and for the remaining documentation, having cvsl10n is enough because you only have to translate po files.
So should we revoke everyone just translating from cvsdocs and add them to cvsl10n (if you're not in there yet).
IMHO, nope. Instead, we should be sure that cvsl10n membership is enough for translators to work on documentation, and that cvsdocs is not needed (i.e. allow cvsl10n to commit the "draft" images).
Regards.
On Mon, 2007-11-26 at 10:05 +0100, Xavier Conde Rueda wrote:
Now, a lot of translators are member of cvsdocs. But you maybe not need that: if you're not working on the original docs, you don't need that. Having cvsl10n group membership is enough: you get all access to /po directories and files.
indeed having access to cvsdocs is needed, because in order to build documentation you need to create a "Draft" image and commit it, and you need cvsdocs access for this. This step is only needed the first time you translate documentation, and for the remaining documentation, having cvsl10n is enough because you only have to translate po files.
So should we revoke everyone just translating from cvsdocs and add them to cvsl10n (if you're not in there yet).
IMHO, nope. Instead, we should be sure that cvsl10n membership is enough for translators to work on documentation, and that cvsdocs is not needed (i.e. allow cvsl10n to commit the "draft" images).
Oh, that's a great point. I wonder to what extent we can make this work by making "po/" directories for these materials in Docs CVS.