I18n PTL Guide¶
As an official project, the responsibility of the I18n PTL is generally subject to the Project Team Guide. This chapter describes tasks for I18n PTL and gives some useful hints. If you want to be I18n PTL or you new in this role, please read carefully. For all other is this chapter informal.
PTLs are elected by ATCs for each cycle. Please read Governance Election Page. Time and rules are announced there and on OpenStack Discuss Mailing List. Your candidacy is highly encouraged to share via there and on OpenStack I18n Mailing List . The proposal must be submitted to election repository (e.g. https://review.opendev.org/#/c/425775/). For this reason it is a good idea to subscribe to these mailing lists before :-)
Cross Project Liaisons¶
I18n team participates in cross project liaisons in Oslo, Release Management, Documentation and Infrastructure. Many other teams are liaisons in I18n. Visit the Cross Project Liaisons Wiki Page and designate a person for the I18n team. Note that such liaison roles do not have to be I18n PTL. Active I18n cores are highly encouraged.
In the beginning of each cycle it is a good idea to think about goals for the project in the next months and establish a translation plan. Goals are maybe still left from the last cycle and are to be reviewed. New goals are to be defined on PTG or an equivalent event. Orient the team to the OpenStack-wide goals.
The translation plan is announced on Zanata and contains the projects with the highest priority in translation. Usually these are all user-visible projects, like Horizon.
I18n Core Team¶
The PTL is supported in the work by the I18n core team. He designates such kind of project team members and reviews the list from time to time. The work of the core team is described in the Project Team Guide. Of course, core team member be can also proposed by the project team.
Launchpad I18n Core Team¶
As with I18n Core Team, the same things apply here. Launchpad I18n Core Team focuses on determining the importance of a translation and/or I18n bug and triaging bug priorities. You can find the member list on Launchpad I18n Core Member list.
The work for PTL and Zanata administrator is described in chapter リリース前後のチームの活動. This covers also questions about string freezes and work with stable branches.
Each cycle has a date set for Extra-ATCs, e.g. Queens Cycle. Maintenance on I18n site is described in chapter プロジェクトメンテナンス. All the OpenStack members can propose extra ATCs, but I18n PTL is highly encouraged to report the list in each cycle. Here are some useful proposals as example:
This Script in I18n repo collects all users and their activities.
Translation Job Control¶
Translated strings are automatically synced between translation server and Openstack infrastructure. The procedure is robust, but sometimes something can go wrong. For this reason there is a section 翻訳関連のジョブの状況監視 in the infrastructure chapter.
You can check on Gerrit, if the translated strings are imported by the project teams. Core reviewers in each repository are strong encouraged to approve translation sync patches but do not be sad if the translations are not accepted. Zanata Sync jobs are repeated every day until they are merged.
Open reviews I18n repository¶
Check from time to time open reviews on I18n repo. In addition to the PTL, the core reviewers are responsible.
Launchpad bugs & blueprints¶
Translation bugs are tracked on Launchpad. Often only the language teams are able to handle translation bugs, e.g. wrong translation words or senses. PTL fits thereon or designates bug triage liaison.
I18n blueprints are listed also on Launchpad. In normal case a blueprint has an assignee and describes a larger course of a process.
I18n IRC Team Meeting¶
Schedules and rules for the team meeting are described in chapter I18n チームミーティング PTL is chairing the meeting or determines someone to takeover. He (the PTL) also has to check if the meeting time suits most people. Configuration of chair and time is done by irc-meeting repo.
I18n Mailing List Management¶
In addition to IRC, I18n team communication takes place via a mailing list. The Mailing List Administrator is watching new subscribers, not allowed posts, and all the other things that come with the operation of such a list.