07:02:48 #startmeeting OpenStack I18n meeting 07:02:48 Meeting started Thu Nov 17 07:02:48 2016 UTC and is due to finish in 60 minutes. The chair is ianychoi. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:02:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:02:51 The meeting name has been set to 'openstack_i18n_meeting' 07:03:10 Hi How are you all? 07:03:59 good! 07:04:06 Nice :) 07:04:17 lots of work, daily business 07:04:19 :) 07:04:51 Me too, and recently I am working on generating install-guide PDFs from rsts... it needs more work than I first expected.. 07:05:01 #topic Review on last meeting actions 07:05:13 #link http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/openstack_i18n_meeting.2016-11-10-13.01.html 07:05:30 There were a few actions from the last meeting: ianychoi and eumel8 07:05:42 eumel8, thanks a lot for attending the last infra team meeting! 07:06:09 #link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-11-15-19.02.html 07:06:20 Number 7 describes the conversation :) 07:06:22 yes 07:06:40 for me was attending the infra team meeting on Tuesday 07:07:20 we've got two volunteers to support the zanata server upgrade to xenial 07:07:22 I sent an e-mail to aeng the result, because Zanata team wants to know status 07:07:29 sure 07:07:34 eumel8, yep so nice :) 07:08:10 process looks good to me, but I was unsure if we want an upgrade or a complete new installation? 07:08:23 And for me, I have submitted feedback and sent a mail to Heidi copying to katomo :) 07:08:29 (mascot) 07:08:47 Also, for i18n-spec use cases, I am writting it 07:08:47 I read it. thanks 07:08:48 #link https://etherpad.openstack.org/p/i18n-specs-use-cases 07:08:58 katomo, np :) 07:09:18 #link https://review.openstack.org/#/c/397098/ 07:09:52 This is my initial commit for i18n-specs and I think we might polish a template: https://review.openstack.org/#/c/397098/1/template.rst to make more appropriate into i18n team 07:12:09 very good, ianychoi 07:12:27 eumel8, thanks :) Any recommendations on use-cases? 07:12:40 no 07:12:42 not yet 07:13:07 And please review https://review.openstack.org/#/c/397098/ eumel8 and katomo :) 07:13:14 ok 07:13:16 sure 07:13:57 I think I might need to send an e-mail for spec use-cases to current core reviewers and language coordinators.. 07:14:07 Thanks a lot! 07:14:51 #topic open discussions 07:15:39 Actually, I was busy on other work rather than i18n... but today I have fixed for i18n: https://review.openstack.org/#/c/398730/ 07:16:54 #link http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002592.html 07:17:07 good finding. sorry for breakage Mitaka translation. fix release is undergoing. 07:17:09 For this, it would be much better if more i18n members will share opinions 07:17:27 hm 07:17:41 katomo, one more worse thing was that I reviewed the previous patch... I should have found the bug.... 07:18:23 ugo 07:18:32 no worries 07:18:39 katomo, after fixing it, would you change http://docs.openstack.org/ja/ to link Newton? 07:18:49 Newton install guides for Japanese 07:18:51 yeah 07:19:01 I will take care of Korean version 07:19:36 Thanks 07:22:00 katomo, one question: for install-guides, just >75% for install-guides would be okay, or >75% for both install-guides and common would be needed? 07:22:24 systematically, no need 07:22:55 Hmm.. then the decision would be dependent to languages? 07:23:05 also, "common" for stable branch mainly contains "get started" content. 07:23:27 therefore, I myself don't think it is so important. 07:24:12 Since.. I think Chinese and French have good ratio for install-guides (>75) but more translation on common seems to be needed. If they want to publish install-guides, then I want to add translation jobs of install-guides for both two + other languages (I need to check ratio) 07:24:35 eumel8, for German, 56.54% :) 07:25:21 I see 07:25:26 I know 07:25:40 katomo, sorry for lots of question.. :) But would you update progress for blueprints? https://blueprints.launchpad.net/openstack-i18n 07:26:02 sorry, no progress. 07:26:45 katomo, that's fine. What I want to ask is that for example, https://blueprints.launchpad.net/openstack-i18n/+spec/release-notes-translation -> I think all things were done, right? 07:28:09 ah, yep 07:28:17 eumel8, you can +2 :) 07:28:35 i18n-specs has the same previlege as openstack/i18n :) 07:28:45 too shy 07:29:28 haha eumel8 is so expert on i18n with puppet :) 07:30:31 +2 07:30:34 Hmm.. I think I need to triage bugs on openstack-i18n: https://bugs.launchpad.net/openstack-i18n 07:31:15 #action ianychoi will triage bugs in openstack-i18n: https://bugs.launchpad.net/openstack-i18n 07:31:24 russian and chinese 07:32:30 Yep on Barcelona Summit, I asked adiantum for defining bug management process for local languages with project contributors. 07:33:05 After i18n-spec is ready, I think I need to ask adiantum to write a simple spec :) 07:33:38 ok 07:33:48 Currently, I like this: uploading bugs into openstack-i18n 07:34:06 Thanks to that, I now know that more local people are interested in i18n activities 07:36:46 yes, I tried always to collect more people to the team 07:37:10 Thanks a lot :) 07:37:22 By the way.. because it is just open discussion, have you seen this? 07:37:24 http://www.ubergizmo.com/2016/11/google-translate-neural-machine-translation/ 07:38:04 I have seen this article in Korean yesterday, and I thought that our activities will be easier thanks to AI :) 07:39:35 the next logical thing for machine learning 07:39:49 The world is really changing..... 07:40:27 eumel8, aha and how about translation checksite you think? 07:40:58 maybe we can use this Google API sometimes in Zanata 07:41:16 translation checksite ... I don't know 07:41:50 have you talked to cloudnull last time? 07:41:51 Hmm... current issue might be DevStack vs. ansible? 07:42:13 yes, and ansible without container 07:42:15 eumel8, I shared to you for the last talk with cloudnull about a week ago. Have you seen it? 07:42:40 yes 07:43:00 I asked cloudnull for performance and their opinion on difference between devstack and ansible 07:45:27 when sent you the message? 07:45:44 Hmm... I don't know how I help for translation checksite. But at least revising http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_check_site.html from your draft on Etherpad may attract more members 07:45:54 About one week ago.. I will check it 07:46:34 #link http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2016-11-09.log.html#t2016-11-09T16:07:20 07:47:33 Hi all 07:47:37 jftalta, hi! 07:48:07 Hi jftalta 07:48:10 eumel8, http://paste.openstack.org/show/589541/ (I have just copied) 07:48:36 I am heading to office bu train. Internet connection is pretty bad 07:48:46 thx 07:48:55 jftalta, have you arrived at your office? :) Huk train... thanks for today participation! 07:48:57 s/bu/by 07:49:24 No, not yet. 07:49:37 ianychoi: we have to think about it. It depends more on the infra team as on ansible. 07:49:55 Hi eumel8 07:50:00 At the moment I would say, without container it makes no sence 07:50:16 hi jftalta! 07:50:28 sense 07:51:49 I could test the horizon container installation from ansible on a plain ubuntu vm. 07:52:05 eumel8, what I currently want is to just open horizon translation checksite around on the 2nd to 3rd week on the next January. I need to check schedule again, but since we have not enough time, I just want to deploy horizon with translation once 07:52:18 just once. To collect feedback 07:52:20 but then you have duplicated code if you need adjustments on the origin 07:52:37 eumel8, yep I completely agree with you 07:53:06 But.. hmm.. for Ocata, I am not sure whether container based approach will be successfully landed in next January or not. 07:53:35 For DevStack, I think I can ask just once to infra team members.. if they are willing to 07:53:38 I think we have to start still with a work around 07:53:45 not nice, I know 07:53:45 I prefer container approach :) 07:54:20 But.. I also want to have one translation checksite during Ocata cycle :) 07:54:45 container aoproach : +1 07:54:59 Then.. how about just DevStack for next January and at the same time developing container-based approach? 07:55:04 how often you want a upgrade of the site? 07:55:22 I hope that container-based approach will be successfully landed on P-cycle 07:55:53 For Ocata cycle, it seems to be difficult... This is my current thinking just considering with timeline... 07:56:21 eumel8, for Ocata, I think just once around soft string freeze would be sufficient 07:56:32 Ideally, daily or weekly refresh 07:56:45 maybe the openstack-ansible team has also requirements for a test environment what we can also use in the future. 07:56:56 eumel8, oh nice :) 07:57:08 I mean NOT ideally :-)) 07:57:46 haha okay. For this refresh period maybe we need to ask to language coordinators 07:57:55 For me, just once per week is good 07:58:04 but with one new installation around soft string we can deal with the infra team 07:58:41 as far as i know, container based approach may prevent from lots of dealing with the infra team, right? 07:58:45 weekly is not possible if you need the infra team personaly 07:59:16 I want a kind of automatic refresh mechanism.. but I am not sure 07:59:28 I think it's caused for root access to the machine to enter the container 07:59:55 that was my understanding from my talk with pleia2 07:59:56 eumel8, maybe you will have root access for containers if it will be implemented 08:00:07 we will see 08:00:11 Hmm.. time is up 08:00:12 time is over :) 08:00:26 Let's move to #openstack-i18n channel if we need to discuss more 08:00:38 Thanks you all, eumel8 , katomo and jftalta ! 08:00:41 #endmeeting