*** aeng has quit IRC | 00:27 | |
*** crazymozart1 has joined #openstack-i18n | 00:27 | |
*** crazymozart has quit IRC | 00:30 | |
openstackgerrit | KATO Tomoyuki proposed openstack/i18n master: Make description for ATC accurate https://review.openstack.org/437188 | 00:34 |
---|---|---|
*** aeng has joined #openstack-i18n | 00:44 | |
ianychoi | amotoki, now in around :) | 00:55 |
amotoki | ianychoi: hi | 00:56 |
ianychoi | good morning! | 00:56 |
amotoki | ianychoi: I just would like to ask your opinion on https://review.openstack.org/#/c/448639/ . | 00:56 |
ianychoi | amotoki, okay looking | 00:57 |
amotoki | ianychoi: I wonder what approach is good. | 00:57 |
ianychoi | amotoki, interesting, I did not know that the contribution as a coordinator is counted as "contributor" role | 00:59 |
amotoki | ianychoi: it is a bit different. | 01:00 |
*** aeng has quit IRC | 01:00 | |
amotoki | ianychoi: even if a coordinator also has 'translator' or 'reviewer' role, 'translator' or 'reviewer' role is not displayed in the lang team page. | 01:00 |
amotoki | ianychoi: so zanata_users.py cannot recognize them as translator or reviewer. | 01:01 |
amotoki | ianychoi: stackalytics and other i18n zanata tools now use only 'translators' field in translator_teams.yaml, | 01:02 |
amotoki | so if coordinators are not listed in 'translators' I am afraid nothing will be count. | 01:02 |
ianychoi | amotoki, when I see now https://translate.openstack.org/language/view/ja , to222 has all three roles with "checked" status in html source file | 01:03 |
ianychoi | amotoki, it may imply that coordinators should have all three roles I think | 01:04 |
amotoki | I think you are admin, so you can see checkboxes for three roles. | 01:05 |
amotoki | but in usual case we cannot see the checkboxes and just see 'coordinator'. | 01:05 |
ianychoi | amotoki, oh really | 01:05 |
amotoki | ianychoi: you can check by logging out zanata :) | 01:06 |
ianychoi | amotoki, thanks a lot you're right. I sometimes do not notice with guest access or general user access to Zanata | 01:06 |
amotoki | there are several approaches I think. | 01:07 |
amotoki | (a) my current approach, (b) use some privileged API to get more detail user info (if possible) | 01:07 |
amotoki | (c) update stackalytics or other tools to honor other fields (reviewers and coordinators) | 01:08 |
ianychoi | amotoki, in admin, add three roles are checked for coordinators. So IMO regarding coordinators to have all roles would be the way - I think it is your approach (a) | 01:08 |
amotoki | that's true for most lang teams. If you look at https://review.openstack.org/#/c/448620/3/tools/zanata/translation_team.yaml, some lang team is an exception | 01:10 |
amotoki | but I think it is accidental and we can assume coordinators are translators/reviewers as well. | 01:10 |
ianychoi | (b) is also a good idea. Currently, infra team has a previleged API key, but I am not sure whether adding more privileged users or sharing the API key would be the good way or not. | 01:12 |
ianychoi | Let's go for (a) :) | 01:13 |
*** aeng has joined #openstack-i18n | 01:13 | |
amotoki | thanks. In addition, it may be a good idea to make zanata_users.py a periodic job | 01:15 |
ianychoi | amotoki, yep for this, I think it might be better to create i18n-tools repository. It would be similar with openstack-doc-tools with release | 01:17 |
ianychoi | (release meant versioned management by pip) | 01:18 |
ianychoi | Then shell scripts will be able to stay in openstack-infra/project-config by adding i18n-tools in requirement.txt | 01:18 |
amotoki | personally I don't think we need more repository now as we release nothing from the main i18n repo. | 01:18 |
ianychoi | If just openstack/i18n repo deals with such things, that would be fine - What I am worried in different perspective is that some translators are not developers and I want to find better ways how to suggest more participation | 01:20 |
ianychoi | For current tools, relatively few people in i18n team would be able to review but IMO at least language coordinators can review for other things such as glossary and contributor guide updates | 01:21 |
amotoki | yes, I agree on that point. on the other hand, i18n repo is small, so can't we distinguish them easily? | 01:23 |
ianychoi | Without such separation of repos, it is difficult to increase the number of core reviews in i18n-core. -> That is my another point of view but it is just the draft of my idea. I realize that there are no reviews for i18n-specs repository unfortunately | 01:23 |
amotoki | I am okay with either way. | 01:24 |
-amotoki- is just aware of i18n-specs repo NOW! | 01:24 | |
ianychoi | But I agree that in genereal having more repositories for a few number of people would not be a good idea | 01:24 |
ianychoi | Haha yep I want I18n team to go for more official status | 01:25 |
amotoki | if we have multiple repos, it is not easy to track reviews on multiple repos without some gerrit dashboard. | 01:26 |
ianychoi | Hmm, that's another good point | 01:26 |
ianychoi | amotoki, yep another possible idea would be related to how to define i18n-core criteria I think. | 01:28 |
ianychoi | I usually thought that for example > 10 reviews in one cycle would be a kind of criteria for i18n-core | 01:29 |
amotoki | ianychoi: that's an important point to keep the i18n team healthy. | 01:29 |
ianychoi | But one worry is that some reviewers from translators would have difficulty to review tools written in Python | 01:30 |
amotoki | ianychoi: what kind of activities usually happens? I think it is a start-line to think these kind of things | 01:30 |
amotoki | In my view, i18n-specs might be too much for us. blueprints on openstack-i18n launchpad sounds enough to me | 01:31 |
ianychoi | 1) i18n contributor guide documentation 2) glossary update from language teams 3) development things in tools/ directory 4) minor fix from others (e.g., typo, requirement update from proposal bot) | 01:32 |
ianychoi | 5) maintenance things (e.g., adding tox.ini job) | 01:32 |
amotoki | oh,,, it's past 10:30. I need to go to a meeting... will check later | 01:33 |
ianychoi | amotoki, hmm yep blueprint would be enough.. assuming that tracking in blueprint goes well | 01:33 |
ianychoi | amotoki, yep I see have a good meeting :) | 01:33 |
*** guoshan has joined #openstack-i18n | 01:46 | |
*** ianychoi has quit IRC | 01:48 | |
*** ianychoi has joined #openstack-i18n | 01:54 | |
openstackgerrit | Merged openstack/i18n master: Drop unnecessary comments from zanata_users https://review.openstack.org/448618 | 02:20 |
*** epico has joined #openstack-i18n | 03:17 | |
*** amotoki has quit IRC | 03:37 | |
*** amotoki has joined #openstack-i18n | 03:50 | |
*** amotoki has quit IRC | 03:55 | |
*** amotoki has joined #openstack-i18n | 03:59 | |
*** guoshan has quit IRC | 04:01 | |
*** amotoki has quit IRC | 04:19 | |
*** amotoki has joined #openstack-i18n | 04:28 | |
*** guoshan has joined #openstack-i18n | 05:02 | |
*** guoshan has quit IRC | 05:07 | |
*** guoshan has joined #openstack-i18n | 06:03 | |
*** tonyb_ has joined #openstack-i18n | 06:06 | |
*** guoshan has quit IRC | 06:07 | |
*** ykatabam has left #openstack-i18n | 06:09 | |
*** tonyb has quit IRC | 06:13 | |
*** guoshan has joined #openstack-i18n | 06:20 | |
*** eumel8 has joined #openstack-i18n | 06:24 | |
eumel8 | hiho! | 06:35 |
eumel8 | just updated https://review.openstack.org/#/c/440825/ - please review | 06:35 |
*** pahuang has quit IRC | 06:36 | |
eumel8 | I'm a bit unsure regarding https://review.openstack.org/#/c/440825/1/specs/translation_check_site.rst@45 - maybe someone can take a look. thx | 06:36 |
ianychoi | eumel8, hi :) | 06:47 |
eumel8 | morning ianychoi :) | 06:48 |
*** amotoki_ has joined #openstack-i18n | 06:52 | |
*** amotoki has quit IRC | 06:55 | |
*** amoralej|off is now known as amoralej | 07:43 | |
*** tesseract has joined #openstack-i18n | 07:44 | |
*** eumel8 has quit IRC | 08:00 | |
*** pcaruana has joined #openstack-i18n | 08:06 | |
*** ykatabam has joined #openstack-i18n | 08:07 | |
*** Administrator_ has quit IRC | 08:20 | |
*** Administrator_ has joined #openstack-i18n | 08:21 | |
*** guoshan has quit IRC | 08:21 | |
*** guoshan has joined #openstack-i18n | 08:23 | |
*** makowals_ has quit IRC | 09:00 | |
*** makowals has joined #openstack-i18n | 09:01 | |
*** openstackgerrit has quit IRC | 09:03 | |
*** epico has quit IRC | 09:27 | |
*** epico has joined #openstack-i18n | 09:38 | |
*** rinfintelodc has joined #openstack-i18n | 09:40 | |
*** amotoki_ has quit IRC | 09:40 | |
*** ykatabam has left #openstack-i18n | 09:41 | |
rinfintelodc | Hello! Can you tell me or help me to identify a use case in a real world OpenStack service which uses oslo i18n library heavily? | 09:42 |
ianychoi | rinfintelodc, hello use case? | 09:42 |
rinfintelodc | sorry? | 09:45 |
ianychoi | rinfintelodc, what means use case? | 09:46 |
rinfintelodc | I meant an example from the real world where i18n is heavily used | 09:47 |
ianychoi | rinfintelodc, so many projects already make use of oslo i18n library such as nova, neutron, and so on | 09:48 |
ianychoi | I could not figure out what heavy use is: lots of translation? | 09:49 |
ianychoi | Or the heavy requirement of using oslo.i18n? | 09:49 |
rinfintelodc | by heavy use I meant "lots of calls to i18n methods" | 09:50 |
rinfintelodc | which is the same with "lots of translation". Thank you | 09:58 |
*** amotoki has joined #openstack-i18n | 09:59 | |
ianychoi | rinfintelodc, https://review.openstack.org/#/c/427805/ is one example I have last seen | 10:06 |
ianychoi | rinfintelodc, you can find similar source implementations on nova, neutron, cinder, keystone, and so on. | 10:06 |
ianychoi | Hope that it addresses your question | 10:06 |
ianychoi | rinfintelodc, or http://tarballs.openstack.org/translation-source/keystone/master/keystone/locale/ would another example of call results from oslo.i18n | 10:09 |
*** makowals has quit IRC | 10:38 | |
*** makowals has joined #openstack-i18n | 10:43 | |
*** amotoki has quit IRC | 10:46 | |
*** amotoki has joined #openstack-i18n | 10:49 | |
*** epico has quit IRC | 10:54 | |
*** guoshan has quit IRC | 11:02 | |
*** rinfintelodc has quit IRC | 11:25 | |
*** amotoki has quit IRC | 11:45 | |
*** vi01et03_ has joined #openstack-i18n | 11:50 | |
*** vi01et03_ has quit IRC | 11:53 | |
*** steveg_afk has joined #openstack-i18n | 12:18 | |
*** guoshan has joined #openstack-i18n | 12:29 | |
*** steveg_afk has quit IRC | 12:30 | |
*** tono has joined #openstack-i18n | 12:31 | |
*** tono has quit IRC | 12:37 | |
*** guoshan has quit IRC | 12:49 | |
*** tono has joined #openstack-i18n | 13:02 | |
*** tono has quit IRC | 13:06 | |
*** amoralej is now known as amoralej|lunch | 13:07 | |
*** guoshan has joined #openstack-i18n | 13:08 | |
*** amotoki has joined #openstack-i18n | 13:13 | |
*** steveg_afk has joined #openstack-i18n | 13:34 | |
*** guoshan has quit IRC | 13:36 | |
*** guoshan has joined #openstack-i18n | 13:37 | |
*** aesantosd has joined #openstack-i18n | 13:44 | |
*** amoralej|lunch is now known as amoralej | 14:22 | |
*** guoshan has quit IRC | 14:26 | |
*** aesantosd has quit IRC | 15:16 | |
*** aesantosd has joined #openstack-i18n | 15:43 | |
*** amoralej is now known as amoralej|brb | 15:54 | |
*** amoralej|brb is now known as amoralej | 16:41 | |
amotoki | infra script which imports release note translations has been merged. | 16:59 |
amotoki | let's check it works as expected tomorrow and this weekend | 17:00 |
*** amotoki has quit IRC | 17:14 | |
*** pcaruana has quit IRC | 17:14 | |
*** steveg_afk has quit IRC | 19:22 | |
*** tesseract has quit IRC | 19:28 | |
*** amoralej is now known as amoralej|off | 19:46 | |
*** steveg_afk has joined #openstack-i18n | 20:37 | |
*** aesantosd has quit IRC | 21:33 | |
*** ykatabam has joined #openstack-i18n | 22:03 | |
*** aeng has quit IRC | 22:46 | |
*** aeng has joined #openstack-i18n | 22:47 | |
*** pahuang has joined #openstack-i18n | 23:21 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!