diff --git a/doc/source/glossary.rst b/doc/source/glossary.rst index 83bd1a5..0061700 100644 --- a/doc/source/glossary.rst +++ b/doc/source/glossary.rst @@ -18,9 +18,9 @@ propose a change to the Gerrit review system. Once your change is merged, the updated glossary will be uploaded to Zanata. Note that the upload to Zanata is a **manual** process now. -Only the Zanata administrator (usually the I18n PTL and some limited folks) -can upload a glossary. If your glossary is not uploaded, contact the I18n team -or the PTL via the i18n mailing list. +Only the Zanata administrator (usually the I18n SIG Chair and some limited +folks like core reviewers) can upload a glossary. If your glossary is not +uploaded, contact the I18n team or the SIG Chair via the i18n mailing list. .. note:: diff --git a/doc/source/i18n_team_meeting.rst b/doc/source/i18n_team_meeting.rst index 4850d89..96c2bf1 100644 --- a/doc/source/i18n_team_meeting.rst +++ b/doc/source/i18n_team_meeting.rst @@ -2,7 +2,19 @@ I18n team meeting ================= -The I18n team holds weekly Team Meetings on Thursdays at alternating +.. note:: + + While I18n team is not holding meetings with regular cadence, it is highly + encouraged to propose discussion topics and share opinions in open + source manner. If you have any agenda which looks relevant for I18n team, + feel free to propose by :ref:`getting in touch `. + +.. note:: + + I18n team is looking for meeting chairs - please reach SIG Chair if + interested. + +The I18n team previously held weekly Team Meetings on Thursdays at alternating times in #openstack-meeting IRC channel. To download ICS file, please visit `eavesdrop `_ page. @@ -14,16 +26,15 @@ To download ICS file, please visit Odd and even values are calculated based on `ISO week numbers `_. -The meeting is interconnected with the `Documentation Team Meeting `_. -The first 30 minutes are reserved for I18n topics and the second part -is for Documentation Team topics. +The meeting was interconnected with the `Documentation Team Meeting `_. +The first 30 minutes were reserved for I18n topics and the second part +was for Documentation Team topics. Meeting agenda -------------- Everybody can propose agenda topics on `I18nTeamMeeting Wiki Page `_. -If there are no topics proposed, the meeting might be canceled for that -week. +If there are no topics proposed, the meeting might be canceled for that week. Usual topics @@ -35,7 +46,7 @@ Usual topics Handy links (always sort of on the agenda) * `Translation plan `_ -* `Translation statistics `_ +* `Translation statistics `_ * `Bug lists `_ * `Open reviews in openstack/i18n `_ * `Broken Translation Jobs on Zuul `_ @@ -44,7 +55,7 @@ Previous meetings ----------------- You can refer to `previous meeting logs with their notes -`_. +`_. IRC web client -------------- @@ -60,7 +71,7 @@ This is a useful commands for the IRC meeting. .. code-block:: none - #startmeeting openstack_i18n_team_meeting + #startmeeting openstack_i18n_meeting #topic open discussions #info useful information #link http://contents diff --git a/doc/source/index.rst b/doc/source/index.rst index cda59dd..18a4fe8 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -27,7 +27,7 @@ Contents handling_bugs official_translator lang_team - ptl + sig_chair check_translation translation_tips glossary @@ -62,7 +62,6 @@ OpenStack I18n team * Mailing List: `openstack-i18n@lists.openstack.org `_ * IRC channel: ``#openstack-i18n`` on OFTC -* :doc:`IRC meeting ` .. only:: html diff --git a/doc/source/official_translator.rst b/doc/source/official_translator.rst index 58d275b..5a6c6f3 100644 --- a/doc/source/official_translator.rst +++ b/doc/source/official_translator.rst @@ -84,22 +84,28 @@ for OpenStack TC (Technical Committee). For more detail on AC and TC, see `OpenStack Technical Committee Charter `_. +.. note:: + AC is a renamed term from "ATC" (Active Technical Contributor) which are + the same. You can see more details on `2021-06-02 'OpenStack ATC' + definition `_. + This page also uses ATC term to mention old calculation and statistics. + As of now, AC of official translators are treated as extra ACs as we have no way to collect statistics automatically now. -The list of extra ACs is maintained by the PTL or SIG Chair and usually updated +The list of extra ACs is maintained by the SIG Chair and is usually updated short before the deadline of extra ACs nomination in each release cycle. The deadline of extra ACs nomination can be checked in the release schedule page at http://releases.openstack.org/ (for example, http://releases.openstack.org/bobcat/schedule.html). -Translators who translate and review at least 300 words combinedly +Translators who translate and review 300 and more words combinedly in the last six months until the deadline of extra ACs nomination are nominated as ACs, and the AC status of translators is valid for one year. Translation count and review count can be added up. -The detail period is determined by the PTL or SIG Chair in each cycle. -For Antelope cycle, the six month period was from 2022-10-05 to 2023-03-22, -and this AC status will expire on March 2024 if there will be no -additional translation contributions. +The detail period is determined by the SIG Chair in each cycle. +For Newton cycle, the six month period was from 2016-02-01 to 2016-07-31, +and the ATC status expired on July 2017 for the translators and reviewers with +no additional contributions. .. note:: @@ -117,8 +123,8 @@ projects and/or SIGs. AC members of I18n project -------------------------- -A current list of all ACs is available at -https://github.com/openstack/governance/blob/master/reference/sigs-repos.yaml. +A current list all ACs is available at ``i18n`` part in +https://opendev.org/openstack/governance/src/branch/master/reference/sigs-repos.yaml. The statistics are calculated using `a Python script `__ @@ -145,31 +151,3 @@ OpenStack projects and the ATC list was maintained by proposing a patch to :maxdepth: 2 atc-stats - -.. _i18n-auc: - -AUC status in I18n project --------------------------- - -.. note:: - - As User Committee no longer operated from August 1, 2020, I18n team now - does not look up AUC status. See `OpenStack User Committee - Charter `_ - for more information. - -As OpenStack evolved, Active User Contributor (AUC) recognition process was -introduced by the `OpenStack User Committee (UC) `_. -AUCs are acknowledged to operators and users who contributed aligned with UC -governance. - -In Zanata, some project translations such as -`OpenStack User Survey `_ -and `OpenStack whitepapers `_ -are not in `official projects `_ -but strongly encouraged to translate for better OpenStack world, -and translators who translated those projects are recognized as AUCs. - -As of now, similar as ATCs, there is no way to collect statistics automatically. -The list of AUCs was calculated by the PTL and is usually updated -by communication with UC. diff --git a/doc/source/release_management.rst b/doc/source/release_management.rst index 3e3eb86..c09fc8e 100644 --- a/doc/source/release_management.rst +++ b/doc/source/release_management.rst @@ -39,10 +39,10 @@ Note that StringFreezes are applied to I18n team target projects and with * Translate **master** version on Zanata. -#. [I18n PTL] Call for translation +#. [I18n SIG Chair] Call for translation -#. [I18n PTL] Coordinate release and translation import schedule of individual - projects with PTL or I18n liaison. +#. [I18n SIG Chair] Coordinate release and translation import schedule of + individual projects with SIG Chair or I18n liaison. #. [Project] Release RC1 and create a stable branch. ``Hard StringFreeze`` is in effect. diff --git a/doc/source/ptl.rst b/doc/source/sig_chair.rst similarity index 65% rename from doc/source/ptl.rst rename to doc/source/sig_chair.rst index b24bdb4..61294b7 100644 --- a/doc/source/ptl.rst +++ b/doc/source/sig_chair.rst @@ -1,35 +1,29 @@ -============== -I18n PTL Guide -============== +==================== +I18n SIG Chair 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. +This chapter describes tasks for I18n SIG Chair and gives some useful hints. +If you want to be I18n SIG Chair or you new in this role, please read +carefully. For all other is this chapter informal. -Election --------- +.. note:: + + Since I18n team previously followed as a form of official projects, some + of the below description may assume detail tasks as PTL responsibility. + See `Project Team Guide `_ + which is a reference for PTLs for more information, and I18n team now + follows as a form of working group defined as SIGs (Special Interest + Groups). -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 +I18n team participates in various cross project liaisons like Release +Management, Documentation and Infrastructure tasks. 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. +do not have to be I18n SIG Chair. Active I18n cores are highly encouraged. Project Goals And Translation Plan ---------------------------------- @@ -49,9 +43,9 @@ 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 +The SIG Chair is supported in the work by the `I18n core team `__. +The person designates such kind of project team members and reviews the list +from time to time. The usual 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. @@ -66,17 +60,17 @@ bug and triaging bug priorities. You can find the member list on Release Management ------------------ -The work for PTL and Zanata administrator is described in chapter +The work for SIG Chair and Zanata administrator is described in chapter :doc:`release_management`. This covers also questions about string freezes and work with stable branches. -Extra-ATCs Deadline +Extra-ACs Deadline ------------------- -Each cycle has a date set for Extra-ATCs, e.g. `Queens Cycle +Each cycle has a date set for Extra-ACs, e.g. `Queens Cycle `__. Maintenance on I18n site is described in chapter :ref:`project-maintenance`. -All the OpenStack members can propose extra ATCs, but I18n PTL is highly +All the OpenStack members can propose extra ACs, but I18n SIG Chair is highly encouraged to report the list in each cycle. Here are some useful proposals as example: @@ -123,16 +117,6 @@ I18n blueprints are listed also on `Launchpad `__. - I18n Mailing List Management ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/source/tools.rst b/doc/source/tools.rst index 94d857d..ed2316a 100644 --- a/doc/source/tools.rst +++ b/doc/source/tools.rst @@ -346,7 +346,7 @@ To run the script: Extract Zanata user information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -At the moment, the I18n PTL needs to maintain the ATC list of the I18n +At the moment, the I18n SIG Chair needs to maintain the AC list of the I18n project manually around the end of each release cycle. This requires name and e-mail address of individual translators.