Open Stack

On 12/02/13 04:49, Ying Chun Guo wrote:
> Hi, team
> 
> Here are my thoughts to the access control of translations. We can
> discuss in our meeting. Thanks.
> 
> 
> ------------------------------
> Current situation:
> 
> 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. Everyday, there is a patch submitted to
> Git review, including updates to several languages.
> 
> The current solution has some disadvantages:
> 
> 1. Git reviewers might not understand non-English languages.
> 2. Even we can invite some non-English speakers to review the patch, a
> patch with 3 languages translation will need 3 translators' review.
> Without the review to a specific language, the patch can not be merged.
> It will take some time to get all the reviews.
> 3. The feedback of reviewers are not easily gotten by translators.
> 4. The "Free to all" allows any registered user to upload a PO file with
> his translations to Transifex, which might cause regressions. The Git
> reviewers can denied the patch. But somebody must upload the correct
> version of PO file manually to Transifex in order to recover from the
> regressions.
> 
> My proposal:
> 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. 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. We can send a mail to
> community and call for coordinators.
> 
> The reviewers can do the review and give suggestions through the web UI
> of Transifex. The Git review can also be used. The coordinators can be
> the required reviewers of each patch. The update frequency can be cut
> down to weekly.
> 
> TODO items:
> 1. Change the access control of OpenStack to be "Limited Access".
> 2. Change the frequency of patch generation to be weekly.
> 3. Write script to add coordinators to the reviewer list after the patch
> is pushed to Git review.
> 4. Write mail to community and call for coordinator.
> 
> Regards
> Ying Chun Guo (Daisy)

+1