Ensuring Quality in Ubuntu Translations

amachu techie amachu.techie at gmail.com
Fri Nov 10 16:25:02 GMT 2006


> There has to be a barrier: you cannot start translating without any
> knowledge - thinking of e.g. word lists and guidelines. So if people
> just start to translate without even having to read a short
> introduction, they will produce bad translations under normal
> circumstances.

We face exactly the same problem. We will translate something this week and
next week when we go and see it, it will be changed. Some barrier, its not a
permanent one.. but this is something done, to make a new user get
accustomed to the environment of the existing translators.

Some checks if a user comes and tries to start a Translation without
becoming a member of a approved LoCo Team, the rosetta system should
instruct the user join the Translation Team.

Now comes the role of the Admin of the Translation Team. Whenever some one
tries to join a Translation Team, the admin should take up the responsibilty
of interacting with that user, get his details like experience in
translation... and if needed arrange for some kind of training... for the
new user... And if there is a real need.. include the new user as part of
translation team....

> I totally agree on your idea for the second team. Perhaps it shouldn't
> be called qa-team, but approved translators team.

This team can be internal and not explicitly declared in Lauchpad. May be
wiki page in wiki.ubuntu.com displaying the roles and responsibilities of
each member of a LoCo team should be suffcient. This page will display, who
all are the translators and who all are the QA persons.

Regards,

Sri Ramadoss M,
wiki.ubuntu.com/sriramadas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/rosetta-users/attachments/20061110/7ec3b3b9/attachment.htm 


More information about the rosetta-users mailing list