Jump to: navigation, search

Difference between revisions of "I18n Extra-AC collection"

(How to deal with Extra-ATC data: added info on perms and config file)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=== How to deal with Extra-ATC data ===
+
=== How to deal with Extra-AC data ===
  
# At the beginning of the release goto https://releases.openstack.org and look for Extra-ATC deadline and mark the date in your diary
+
# At the beginning of the release go to https://releases.openstack.org and look for Extra-AC deadline and mark the date in your diary
 
# Few days before checkout governance and i18n repo
 
# Few days before checkout governance and i18n repo
 
# goto the tools/zanata directory in i18n repo
 
# goto the tools/zanata directory in i18n repo
# run zanata_users.py to refresh the user list and submit a patch
+
# run zanata_users.py to refresh the user list and submit a patch, or simply run with zanata-users-sync tox environment - for example,
# run zanata_userinfo.py to get detailed user info from Zanata;
+
  $ tox -ezanata-users-sync
  This step requires ''~/.config/zanata.ini'' file, get it's contents from [https://translate.openstack.org/dashboard/settings/client?dswid=-3129# Zanata User settings -> Client].
+
# run zanata_userinfo.py to get detailed user info from Zanata. This step requires ''~/.config/zanata.ini'' file, get it's contents from [https://translate.openstack.org/dashboard/settings/client?dswid=-3129# Zanata User settings -> Client]. You have to be Zanata server admin to be able to pull extended users information. For example,
  You have to be Zanata server admin to pull extended users information.
+
  $ tox -e venv -- python tools/zanata/zanata_userinfo.py tools/zanata/translation_team.yaml
 
# goto https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics to see when the last statistic run was done
 
# goto https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics to see when the last statistic run was done
 
# clean up old versions in Zanata to improve runtime
 
# clean up old versions in Zanata to improve runtime
# run zanata_stats.py with the right timeframe, i.e. ./zanata_stats.py -s 2018-02-26 -e 2018-07-09 translation_team.yaml (be carefull, this step takes at least one day)
+
# run zanata_stats.py with the right timeframe - for example (be careful, this step takes at least one day),
 +
  $ tox -evenv -- tools/zanata/zanata_stats.py -s 2023-10-15 -e 2024-04-03 tools/zanata/translation_team.yaml -o zanata_stats_output.csv
 
# goto playbooks directory in i18n repo
 
# goto playbooks directory in i18n repo
# copy projects.yaml from governance repo here
+
# copy sigs-repos.yaml from governance repo here
# copy zanata_stats_output.csv and zanata_userinfo_output.csv here
+
# copy zanata_stats_output.csv and zanata_userinfo_output.csv to vars directory
# run ansible-playbook generate_atc.yml
+
# run ansible-playbook generate_ac.yml
# review output /tmp/atc.wiki and edit the wiki page with the new data (https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics)
+
  $ tox -e ansible -- ansible-playbook generate_ac.yml
# review output /tmp/atc.stats and prepare a patch for projects.yaml in governance repo (delete old I18n Extra-ATC and copy the new in)
+
# review output /tmp/ac.wiki and edit the wiki page with the new data (https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics)
# copy zanata_stats_output.csv to doc/source/data/<cycle>.csv in i18n repom edit doc/source/atc-stats.rst, and propose a patch  
+
# review output /tmp/ac.stats and prepare a patch for sigs-repos.yaml in governance repo (delete old I18n Extra-AC and copy the new in)
 +
# copy zanata_stats_output.csv to doc/source/data/<cycle>.csv in i18n repo, edit doc/source/atc-stats.rst, and propose a patch  
 
# announce the results
 
# announce the results

Latest revision as of 14:24, 17 February 2024

How to deal with Extra-AC data

  1. At the beginning of the release go to https://releases.openstack.org and look for Extra-AC deadline and mark the date in your diary
  2. Few days before checkout governance and i18n repo
  3. goto the tools/zanata directory in i18n repo
  4. run zanata_users.py to refresh the user list and submit a patch, or simply run with zanata-users-sync tox environment - for example,
  $ tox -ezanata-users-sync
  1. run zanata_userinfo.py to get detailed user info from Zanata. This step requires ~/.config/zanata.ini file, get it's contents from Zanata User settings -> Client. You have to be Zanata server admin to be able to pull extended users information. For example,
  $ tox -e venv -- python tools/zanata/zanata_userinfo.py tools/zanata/translation_team.yaml
  1. goto https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics to see when the last statistic run was done
  2. clean up old versions in Zanata to improve runtime
  3. run zanata_stats.py with the right timeframe - for example (be careful, this step takes at least one day),
  $ tox -evenv -- tools/zanata/zanata_stats.py -s 2023-10-15 -e 2024-04-03 tools/zanata/translation_team.yaml -o zanata_stats_output.csv
  1. goto playbooks directory in i18n repo
  2. copy sigs-repos.yaml from governance repo here
  3. copy zanata_stats_output.csv and zanata_userinfo_output.csv to vars directory
  4. run ansible-playbook generate_ac.yml
  $ tox -e ansible -- ansible-playbook generate_ac.yml
  1. review output /tmp/ac.wiki and edit the wiki page with the new data (https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics)
  2. review output /tmp/ac.stats and prepare a patch for sigs-repos.yaml in governance repo (delete old I18n Extra-AC and copy the new in)
  3. copy zanata_stats_output.csv to doc/source/data/<cycle>.csv in i18n repo, edit doc/source/atc-stats.rst, and propose a patch
  4. announce the results