The access to OpenStack in Transifex is set as "Free for all". Any logged-in (registered) user can submit translations to it. Git review is used to review the translation. The current solution has some disadvantages: Git reviewers might not understand non-English languages; Even we can invite some non-English speakers to review the patch, the feedback of reviewers are not easily gotten by translators. The "Free to all" allows any registered user to upload a PO file with his translations to Transifex, which might cause regressions.
Setting limited access to OpenStack project in Transifex may be better. After changing to limited access, there will be a team for each language. There are three different roles in the translation management: translators, reviewers and coordinators.
We need to discuss: - The requirements of a coordinator. The coordinators are the lead of a translation team. They are responsible for the translation team set up and the control of quality and progress. - How to gather groups around with permissions the way translators want?`
2. how to leverage professional translations?
Since some companies start the productization of OpenStack, they may generate professional translation assets, both for messages and documents. If the companies want to contribute these translations, how to handle the relationship between community translation and professional translation?
Possible ways: - Use the professional translation as translation memories - Use the professional translation instead of community translation - Anything else?
