13:13:33 #startmeeting OpenStack I18n Meeting 13:13:34 Meeting started Thu May 25 13:13:33 2017 UTC and is due to finish in 60 minutes. The chair is ianychoi. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:13:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:13:37 The meeting name has been set to 'openstack_i18n_meeting' 13:13:44 jpich, jftalta: sorry for late 13:14:24 No problems :) 13:14:33 How are you going? :) 13:15:03 All good here! Yourself? 13:15:20 ianychoi: Hi ! does not matter, don't worry ;) 13:15:29 o/ 13:15:59 asettle, wow hello! 13:16:00 asettle : hi 13:16:11 Yellow yellow! 13:16:36 #topic Glossary management 13:17:12 jftalta: How do you think about http://lists.openstack.org/pipermail/openstack-i18n/2017-May/002924.html ? 13:17:28 Currently, there is no response from Turkish language coordinator 13:17:35 inaychoi: give me a sec... 13:17:43 And one Turkish translator wants to upload such glossary\ 13:18:05 I originally thought that publizing the announcement would be good 13:18:29 +1 13:18:51 +1 13:20:40 I don't know how to deal with the review 13:20:49 Just +2 & Workflow? 13:22:19 It's only been a couple of days, it might be ok to give a bit more time for feedback? 13:22:35 jpich, +1 :) 13:22:47 jpich: I agree 13:22:59 jpich, jftalta: thanks a lot for the opinion 13:23:42 :) 13:24:13 #topic Horizon: translation percentage criteria for translate checksite 13:24:53 o/ 13:25:08 robcresswell, hi! 13:25:33 robcresswell: hi 13:25:46 o/ 13:25:52 robcresswell, I am finding the bug link we discussed previously... 13:26:48 \link https://bugs.launchpad.net/openstack-i18n/+bug/1690233 13:26:49 Launchpad bug 1690233 in openstack i18n "A couple of django-js.po files are missing from Horizon tree" [High,Confirmed] 13:27:00 robcresswell, thanks :) 13:27:02 #link https://bugs.launchpad.net/openstack-i18n/+bug/1690233 13:27:22 Sorry ,I meant to do #, but Macbooks are stupid and change my keyboard all the time. 13:27:27 robcresswell, I don't object to it but the problem is now I don't have enought time to revise the infra script... 13:27:39 robcresswell, fine :) (Me also uses macbook... stupid) 13:27:44 All we need to do is delete one line from it 13:28:10 or more. Maybe a few lines to delete :) 13:28:20 IMO :) 13:28:56 robcresswell, can I ask which line? 13:29:34 what's the current topic ?... 13:29:53 jftalta: Look at the bug above ^^ 13:30:24 Basically, there is some issues with the infra scripts not pulling down files with certain % of translation 13:30:51 But it has a bug, and so I'm in favour of just removing all detection and just using whatever translations are available 13:31:04 and leave it up to the operator to decide what languages to use or not 13:31:49 robcresswell, I am okay for such direction :) But... might it need to revise infra-scripts? Or not? 13:32:33 Ah, thx, ok. Sorry, I did not understand the topic title :( 13:32:43 As in, remove all checks - so even if only one sentence is translated for the language, the translation file would get pulled in? 13:33:10 jpich: Effectively, yes 13:33:23 Either that, or we make the infra scripts smarter 13:33:53 The thing is, right now, its got some pretty big bug that means in some situations a large number of translated strings dont get pulled down. 13:35:40 I remember issues where we'd pull po files for languages that had only one unreviewed translation for a less common language, which looked more like someone playing with/learning about Zanata than something worthwhile for users. I guess the "veto"/check can be done when writing up the language list application side 13:35:54 robcresswell, for me one concern is: in Horizon there is also releasenotes.po and there might be Horizon developer documentation po files in future. One idea might be to exclude po files: releasenotes.po and the other idea might be to specify Horizon po file names: e.g., django.po, djangojs.po, and so on 13:36:07 (...unless the language list is generated automatically I guess) 13:36:30 jpich: Its automatic now, so that may be problematic. You can filter it by specifying langs in settings though. 13:36:39 Maybe we need to make the infra script smarter 13:37:58 It doesn't seem super fair to push onto the operator the responsibility of figuring translation status for each language yeah... 13:38:07 robcresswell, I agree with you. Let's discuss later :) 13:38:24 I understand the infra script stuff is complicated though!! /me still has a couple of related unresolved bugs 13:38:32 #topic Impact on Docs team governance and recent changes 13:38:56 Sorry I need to be away for a while.. 10 minutes. asettle: would you explain briefly some background of this topic? 13:39:10 Uhh 13:39:26 You mean the email threads? 13:39:28 ianychoi: ^ 13:39:40 asettle, yep :) 13:39:50 Okay 13:39:58 So, some of you might have seen my emails to the ML or not 13:40:02 asettle, they were not shared to openstack-i18n mailing list so plz explain :) 13:40:29 But docs is looking at changing the direction of things, and pushing the responsibility of writing documentation back out to the project repos 13:40:47 I will forward the email I sent to the docs ML to the I18N ML now 13:41:08 :) 13:41:10 You can see the email I sent out to the dev ML here 13:41:12 #link http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html 13:41:20 ok, thx 13:41:30 We're discussing *how* we're going to do this 13:41:37 Here is the why 13:41:39 #link http://lists.openstack.org/pipermail/openstack-dev/2017-May/117053.html 13:41:44 Whihc i will fowward to the ML now 13:42:24 Okay, just did that 13:42:36 There's going to be some changes, but the way I understand it this hsouldn't change the way things are translated 13:42:49 However, there are some guides we will consider EOLing in the future if there is no movement or contributions to them 13:42:54 Such as the Architecture or HA guide 13:43:36 I'm not too sure what else to add there, we're just sort of waiting for the decisions to be made by the community to move on 13:43:46 We'll work on the planning in Pike, for execution in Queens 13:43:53 I will not be the PTL, so this will be up to the community 13:43:57 Anyway, questions? :) 13:44:21 need a couple of minutes to read these emails... 13:44:25 No worries, it's a lot at once 13:44:33 Sorry about that jftalta 13:46:19 "As we all know, we are rapidly losing key contributors and core reviewers" :-( 13:46:24 Yeah, sadly :( 13:46:30 But it also isn't really a shock 13:52:18 asettle, thanks a lot for the explanation! 13:52:25 \o/ 13:54:04 asettle, actually translation support on install tutorials is what we discussed on the last ptg. Now i want to modify this goal - i wanna defer it to Queens 13:54:41 Makes sense :) 13:55:43 asettle, I think install guides part might be distributed to multiple repos by some further directions - it is still in discussion afaik. So supporting distributed docs sources should be considered in I18n team. 13:56:21 It's a lot of work for you guys, but it's no different to us :( might be worth discussing with infra how we can potentially managed impact on I18N 13:56:54 asettle, +1 :) 13:57:28 jftalta, jpich: question - https://docs.openstack.org/project-install-guide/ocata/ landing page also needs to be translated? 13:58:53 ianychoi, yes it does, imo 13:59:19 I'm not familiar with the project but if the content is translated, it'd probably be good to get the landing page too 13:59:22 asettle, if i18n team wants to translate https://docs.openstack.org/project-install-guide/ocata/ page then it needs to be managed by git 13:59:47 asettle, that's another one I want to discuss with u 14:00:12 ianychoi: sure - send me an email :) i'm happy to go through things with you 14:00:13 asettle, robcresswell, jftalta, jpich : thanks a lot for today coming! 14:00:18 Thanks :D 14:00:25 asettle, yep! 14:00:32 :-) 14:00:35 Thanks! :) 14:00:39 #endmeeting