Thursday, 2017-03-23

*** aeng has quit IRC00:27
*** crazymozart1 has joined #openstack-i18n00:27
*** crazymozart has quit IRC00:30
openstackgerritKATO Tomoyuki proposed openstack/i18n master: Make description for ATC accurate  https://review.openstack.org/43718800:34
*** aeng has joined #openstack-i18n00:44
ianychoiamotoki, now in around :)00:55
amotokiianychoi: hi00:56
ianychoigood morning!00:56
amotokiianychoi: I just would like to ask your opinion on https://review.openstack.org/#/c/448639/ .00:56
ianychoiamotoki, okay looking00:57
amotokiianychoi: I wonder what approach is good.00:57
ianychoiamotoki, interesting, I did not know that the contribution as a coordinator is counted as "contributor" role00:59
amotokiianychoi: it is a bit different.01:00
*** aeng has quit IRC01:00
amotokiianychoi: even if a coordinator also has 'translator' or 'reviewer' role, 'translator' or 'reviewer' role is not displayed in the lang team page.01:00
amotokiianychoi: so zanata_users.py cannot recognize them as translator or reviewer.01:01
amotokiianychoi: stackalytics and other i18n zanata tools now use only 'translators' field in translator_teams.yaml,01:02
amotokiso if coordinators are not listed in 'translators' I am afraid nothing will be count.01:02
ianychoiamotoki, when I see now https://translate.openstack.org/language/view/ja , to222 has all three roles with "checked" status in html source file01:03
ianychoiamotoki, it may imply that coordinators should have all three roles I think01:04
amotokiI think you are admin, so you can see checkboxes for three roles.01:05
amotokibut in usual case we cannot see the checkboxes and just see 'coordinator'.01:05
ianychoiamotoki, oh really01:05
amotokiianychoi: you can check by logging out zanata :)01:06
ianychoiamotoki, thanks a lot you're right. I sometimes do not notice with guest access or general user access to Zanata01:06
amotokithere 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
ianychoiamotoki, 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
amotokithat'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 exception01:10
amotokibut 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
ianychoiLet's go for (a) :)01:13
*** aeng has joined #openstack-i18n01:13
amotokithanks. In addition, it may be a good idea to make zanata_users.py a periodic job01:15
ianychoiamotoki, yep for this, I think it might be better to create i18n-tools repository. It would be similar with openstack-doc-tools with release01:17
ianychoi(release meant versioned management by pip)01:18
ianychoiThen shell scripts will be able to stay in openstack-infra/project-config by adding i18n-tools in requirement.txt01:18
amotokipersonally I don't think we need more repository now as we release nothing from the main i18n repo.01:18
ianychoiIf 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 participation01:20
ianychoiFor 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 updates01:21
amotokiyes, I agree on that point. on the other hand, i18n repo is small, so can't we distinguish them easily?01:23
ianychoiWithout 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 unfortunately01:23
amotokiI am okay with either way.01:24
-amotoki- is just aware of i18n-specs repo NOW!01:24
ianychoiBut I agree that in genereal having more repositories for a few number of people would not be a good idea01:24
ianychoiHaha yep I want I18n team to go for more official status01:25
amotokiif we have multiple repos, it is not easy to track reviews on multiple repos without some gerrit dashboard.01:26
ianychoiHmm, that's another good point01:26
ianychoiamotoki, yep another possible idea would be related to how to define i18n-core criteria I think.01:28
ianychoiI usually thought that for example > 10 reviews in one cycle would be a kind of criteria for i18n-core01:29
amotokiianychoi: that's an important point to keep the i18n team healthy.01:29
ianychoiBut one worry is that some reviewers from translators would have difficulty to review tools written in Python01:30
amotokiianychoi: what kind of activities usually happens? I think it is a start-line to think these kind of things01:30
amotokiIn my view, i18n-specs might be too much for us. blueprints on openstack-i18n launchpad sounds enough to me01:31
ianychoi1) 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
ianychoi5) maintenance things (e.g., adding tox.ini job)01:32
amotokioh,,, it's past 10:30. I need to go to a meeting... will check later01:33
ianychoiamotoki, hmm yep blueprint would be enough.. assuming that tracking in blueprint goes well01:33
ianychoiamotoki, yep I see have a good meeting :)01:33
*** guoshan has joined #openstack-i18n01:46
*** ianychoi has quit IRC01:48
*** ianychoi has joined #openstack-i18n01:54
openstackgerritMerged openstack/i18n master: Drop unnecessary comments from zanata_users  https://review.openstack.org/44861802:20
*** epico has joined #openstack-i18n03:17
*** amotoki has quit IRC03:37
*** amotoki has joined #openstack-i18n03:50
*** amotoki has quit IRC03:55
*** amotoki has joined #openstack-i18n03:59
*** guoshan has quit IRC04:01
*** amotoki has quit IRC04:19
*** amotoki has joined #openstack-i18n04:28
*** guoshan has joined #openstack-i18n05:02
*** guoshan has quit IRC05:07
*** guoshan has joined #openstack-i18n06:03
*** tonyb_ has joined #openstack-i18n06:06
*** guoshan has quit IRC06:07
*** ykatabam has left #openstack-i18n06:09
*** tonyb has quit IRC06:13
*** guoshan has joined #openstack-i18n06:20
*** eumel8 has joined #openstack-i18n06:24
eumel8hiho!06:35
eumel8just updated https://review.openstack.org/#/c/440825/ - please review06:35
*** pahuang has quit IRC06:36
eumel8I'm a bit unsure regarding https://review.openstack.org/#/c/440825/1/specs/translation_check_site.rst@45 - maybe someone can take a look. thx06:36
ianychoieumel8, hi :)06:47
eumel8morning ianychoi :)06:48
*** amotoki_ has joined #openstack-i18n06:52
*** amotoki has quit IRC06:55
*** amoralej|off is now known as amoralej07:43
*** tesseract has joined #openstack-i18n07:44
*** eumel8 has quit IRC08:00
*** pcaruana has joined #openstack-i18n08:06
*** ykatabam has joined #openstack-i18n08:07
*** Administrator_ has quit IRC08:20
*** Administrator_ has joined #openstack-i18n08:21
*** guoshan has quit IRC08:21
*** guoshan has joined #openstack-i18n08:23
*** makowals_ has quit IRC09:00
*** makowals has joined #openstack-i18n09:01
*** openstackgerrit has quit IRC09:03
*** epico has quit IRC09:27
*** epico has joined #openstack-i18n09:38
*** rinfintelodc has joined #openstack-i18n09:40
*** amotoki_ has quit IRC09:40
*** ykatabam has left #openstack-i18n09:41
rinfintelodcHello! 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
ianychoirinfintelodc, hello use case?09:42
rinfintelodcsorry?09:45
ianychoirinfintelodc, what means use case?09:46
rinfintelodcI meant an example from the real world where i18n is heavily used09:47
ianychoirinfintelodc, so many projects already make use of oslo i18n library such as nova, neutron, and so on09:48
ianychoiI could not figure out what heavy use is: lots of translation?09:49
ianychoiOr the heavy requirement of using oslo.i18n?09:49
rinfintelodcby heavy use I meant "lots of calls to i18n methods"09:50
rinfintelodcwhich is the same with "lots of translation". Thank you09:58
*** amotoki has joined #openstack-i18n09:59
ianychoirinfintelodc, https://review.openstack.org/#/c/427805/ is one example I have last seen10:06
ianychoirinfintelodc, you can find similar source implementations on nova, neutron, cinder, keystone, and so on.10:06
ianychoiHope that it addresses your question10:06
ianychoirinfintelodc, or http://tarballs.openstack.org/translation-source/keystone/master/keystone/locale/ would another example of call results from oslo.i18n10:09
*** makowals has quit IRC10:38
*** makowals has joined #openstack-i18n10:43
*** amotoki has quit IRC10:46
*** amotoki has joined #openstack-i18n10:49
*** epico has quit IRC10:54
*** guoshan has quit IRC11:02
*** rinfintelodc has quit IRC11:25
*** amotoki has quit IRC11:45
*** vi01et03_ has joined #openstack-i18n11:50
*** vi01et03_ has quit IRC11:53
*** steveg_afk has joined #openstack-i18n12:18
*** guoshan has joined #openstack-i18n12:29
*** steveg_afk has quit IRC12:30
*** tono has joined #openstack-i18n12:31
*** tono has quit IRC12:37
*** guoshan has quit IRC12:49
*** tono has joined #openstack-i18n13:02
*** tono has quit IRC13:06
*** amoralej is now known as amoralej|lunch13:07
*** guoshan has joined #openstack-i18n13:08
*** amotoki has joined #openstack-i18n13:13
*** steveg_afk has joined #openstack-i18n13:34
*** guoshan has quit IRC13:36
*** guoshan has joined #openstack-i18n13:37
*** aesantosd has joined #openstack-i18n13:44
*** amoralej|lunch is now known as amoralej14:22
*** guoshan has quit IRC14:26
*** aesantosd has quit IRC15:16
*** aesantosd has joined #openstack-i18n15:43
*** amoralej is now known as amoralej|brb15:54
*** amoralej|brb is now known as amoralej16:41
amotokiinfra script which imports release note translations has been merged.16:59
amotokilet's check it works as expected tomorrow and this weekend17:00
*** amotoki has quit IRC17:14
*** pcaruana has quit IRC17:14
*** steveg_afk has quit IRC19:22
*** tesseract has quit IRC19:28
*** amoralej is now known as amoralej|off19:46
*** steveg_afk has joined #openstack-i18n20:37
*** aesantosd has quit IRC21:33
*** ykatabam has joined #openstack-i18n22:03
*** aeng has quit IRC22:46
*** aeng has joined #openstack-i18n22:47
*** pahuang has joined #openstack-i18n23:21

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!