I am trying to manage a large community of translators. Unfortunately the way roles work at this time doesn’t completely fit my needs.
What I would like to do is for each language assign one person to be the language coordinator. That person gets to make the final call on everything for that language. I need that person to be able to lock translations for a certain string.
What I don’t need is for reviewed strings to get locked from being edited by non-reviewers. I can see how that is useful on some projects, but on ours we want new translators to be able to improve existing strings as well, and locked strings seem to cause new translators to sign off because they can’t really do what they came to do.
I would like to configure roles for our projects to work like this:
Reviewers can still mark texts as reviewed or proofread to give an indication that something has been checked, but reviewed and proofread strings are not locked for anyone. When they get edited, they simply get un-proofread and un-reviewed automatically.
The language coordinator can mark a string as “Agreed on” and by doing so lock the string.
The job of the language coordinator is to find the consensus between the other translators and reviewers.
Setting permissions this way creates a much clearer leadership structure. It prevents endless discussion while still allowing for some discussion, and it prevents new translators from signing off.
For a project maintainer it means each language now has one spokesperson: the language coordinator.
This would be good for quality and consistency across translations: one person decides on the style, and because he is the only one signing off on everything he will notice most inconsistencies.
It should also be possible to not have a language coordinator assigned, in case we haven’t found someone we trust to be that person yet.