13:00:22 <eumel8> #startmeeting OpenStack I18n Meeting
13:00:22 <openstack> Meeting started Thu Oct 26 13:00:22 2017 UTC and is due to finish in 60 minutes.  The chair is eumel8. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:25 <openstack> The meeting name has been set to 'openstack_i18n_meeting'
13:00:42 <genek> hi eumel8
13:01:39 <eumel8> hi genek
13:02:12 <eumel8> welcome to the I18n team meeting
13:02:37 <genek> Missed a lot of meetings after school started ;-(
13:03:04 <jftalta> Hi
13:03:22 <genek> hi jftalta
13:03:23 <eumel8> hi jftalta
13:03:50 <eumel8> rare guests ;-)
13:05:00 <eumel8> I have only some status reports today
13:05:25 <jftalta> ok
13:05:26 <eumel8> #topic Sydney Summit - Onbarding Session Forum
13:05:55 <eumel8> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20550/docsi18n-project-onboarding
13:06:07 <eumel8> Sydney Summit is on the horizon
13:06:31 <eumel8> a docs/i18n onboarding session is now scheduled
13:07:04 <eumel8> pkovar will be there from docs team and maybe amotoki for i18n together with Zanata guys
13:07:07 <genek> I'll put it on my agenda
13:07:28 <eumel8> ++
13:07:34 <jftalta> I'll be there to
13:07:54 <eumel8> lucky guys :)
13:08:51 <eumel8> I'm not, because the talks from our company were not voted
13:09:06 <eumel8> and it's too far away ;)
13:09:20 <genek> eumel8: I see
13:10:01 <eumel8> but if you're there and you have time to support, you're welcome :)
13:10:59 <genek> I'll be there
13:11:14 <eumel8> great
13:11:35 <eumel8> next topic
13:11:45 <eumel8> #topic Status Translation checksite
13:11:56 <eumel8> #link https://review.openstack.org/#/c/487936/
13:12:13 <eumel8> there is still no progress on the translation checksite
13:12:44 <eumel8> We're ready to go but we need the infra-team which is occupied with the zuul v3 migration
13:13:43 <eumel8> Hopefully it becomes calmer and we can move on till the cycle translation phase
13:14:50 <eumel8> that's the status of the translation checksite
13:14:56 <eumel8> next topic
13:15:11 <eumel8> #topic Status Zanata upgrade
13:15:19 <jftalta> the target is to get the translation site up and running for the Rocky release cycle ?
13:16:01 <eumel8> jftalta: yes, but latest at the end of the year
13:16:10 <jftalta> ok
13:16:49 <eumel8> we are nearly at the target but I told this very often in the past and then it takes more time then expected
13:17:26 <eumel8> For Zanata upgrade it's similar: #link https://review.openstack.org/#/c/506795/
13:18:12 <eumel8> there are only 3 core-reviewers in puppet-infra and then it takes time to merge things
13:19:01 <eumel8> maybe during the summit the Zanata guys can push the upgrade forward
13:19:41 <eumel8> my expectation would be also an upgrade in this year
13:21:15 <eumel8> if there are no questions I would skip the next topic because ianychoi isn't here
13:21:38 <amotoki> hi
13:21:50 <eumel8> He is working on generic pdf build process #link https://review.openstack.org/#/c/509297/
13:22:19 <eumel8> and I could imagine we can support him if he has no time to work on that
13:22:28 <eumel8> hi amotoki!
13:22:33 <genek> hi amotoki
13:23:11 <eumel8> #topic Open Discussion
13:24:29 <eumel8> amotoki: I mentioned the Docs/I18n onboarding session in Sydney where you could participate: https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20550/docsi18n-project-onboarding
13:24:49 <eumel8> maybe pkovar contacted you yesterday
13:25:15 <jftalta> hi amotoki
13:25:32 <amotoki> eumel8: is there anything needed to prepare?
13:26:04 <amotoki> eumel8: perhaps I can join the session unless I get up too late
13:26:28 <eumel8> amotoki: for the onbarding session not
13:26:45 <amotoki> eumel8: yeah, the onboarding session
13:26:53 <eumel8> people come and will ask questions about documentation and translation
13:27:01 <amotoki> eumel8: ah nice
13:27:56 <jftalta> it's a kind of speed hiring ;)
13:28:51 <eumel8> In Boston we had not so much audience because it's english speaking area, but I could imagine that will change in the asia/pacific region
13:29:23 <amotoki> Sydney is in English speaking area too :p
13:29:36 <genek> Yeah
13:29:41 <eumel8> amotoki: I mean AROUND :-))
13:29:43 <genek> Probably next time in Germany
13:29:54 <genek> eumel8: I see
13:30:15 <amotoki> no at YVR?
13:30:31 <eumel8> we had much more interests in Tokyo for example
13:31:27 <eumel8> amotoki: what is YVR?
13:31:27 <ianychoi> hi
13:31:42 <ianychoi> i can chat after 10 mins sorry
13:31:50 <eumel8> hi ianychoi!
13:31:51 <eumel8> ok
13:31:55 <amotoki> btw, is anyone working on translation support of documentation again after doc-migration?
13:32:04 <jftalta> ianychoi: hi !
13:32:09 <eumel8> ianychoi: don't worry
13:32:24 <amotoki> ianychoi: hi
13:32:30 <eumel8> amotoki: yes, I think
13:32:51 <jftalta> eumel8: YVR is Vancouver
13:33:05 <amotoki> I have been busy after PTG and could do nothing since then
13:33:12 <eumel8> jftalta: thx :)
13:33:14 <amotoki> so I wonder if there is any progress
13:33:29 <amotoki> sorry for using such abbrev
13:33:38 <amotoki> YVR is the airport code of Vancouver
13:33:48 <eumel8> got it
13:34:02 <eumel8> but I wasn't never there ;)
13:34:10 <amotoki> and we used YVR as etherpad prefix at the last summit at Vancouver...
13:36:03 <eumel8> amotoki: AJaeger is helping us a lot, so we are able to work on translation after doc-migration and zuul v 3 migration.
13:36:38 <amotoki> eumel8: so, do we already support transaltion for docs in project repos?
13:36:50 <amotoki> like install guide or something
13:37:48 <eumel8> amotoki: what I understand are the new zuul jobs now so generic and easy to adapt to other projects
13:38:12 <amotoki> eumel8: yeah, that's true
13:39:20 <amotoki> as I said in PTG, we need to split POT files into meaningful pieces and vice versa in translation jobs
13:39:27 <eumel8> amotoki: you have one project in mind? I asked openstack-ansible but there are not so much interests in translating the doc in other languages
13:40:13 <amotoki> eumel8: no, my target is a specific area like the install guide
13:40:36 <amotoki> we previously had good transaltion coverage but after doc-migratoin all are gone
13:41:13 <amotoki> the install guide was split out into most projects (nova, glance, keystone, cinder, neutron, horizon ......)
13:41:52 <amotoki> personally I stopped translation works in docs and am just supporting transaltion (i.e., i18n infra)
13:42:13 <amotoki> so if there is no interest on translations of such guides I am okay to stop translation support.
13:42:49 <ianychoi> Hi eumel8 jftalta amotoki :)
13:42:51 <eumel8> yes, thats true. I can send a poll if the projects are interested.
13:43:01 <eumel8> ianychoi: hello again
13:43:05 <ianychoi> :)
13:43:13 <genek> hi ianychoi
13:43:16 <amotoki> eumel8: I am not sure it is a question we should ask to individual project teams
13:43:16 <jftalta> eumel8 : sounds good
13:43:36 <ianychoi> genek, oh hi!
13:43:36 <eumel8> ianychoi: we talking about translation of project documentation
13:43:42 <amotoki> they are not translators. they maintain english versions
13:44:00 <ianychoi> genek, I met your friend in Korea yesterday - ONOS contributor
13:44:11 <genek> ianychoi: yeah, he told me
13:44:29 <eumel8> amotoki: on the other hand it would be a bit strange if one project is translated and another not
13:44:30 <ianychoi> eumel8, okay. Would there be some problems to support translation for project specific documentations?
13:44:53 <amotoki> eumel8: yes, it needs to be project-wide
13:44:58 <ianychoi> genek, great :) And I assigned you on Launchpad item. Please see it later
13:45:07 <amotoki> I think translation support itself is really simple
13:45:17 <ianychoi> amotoki, I agree with u
13:45:20 <genek> ianychoi: I think I replied it right after, did you get the notification?
13:45:31 <genek> +1 with amotoki
13:45:38 <amotoki> so I think the key point is there are interest of translations from language teams.
13:45:57 <ianychoi> One difficult would be that there may be more translation errors from infra side, but we may need to make some priorities. Just supporting would be simple I think.
13:46:07 <eumel8> ianychoi: just wondering if there are no interests from the project teams
13:46:22 <ianychoi> genek, not yet because of too much e-mails nowadays..
13:47:14 <ianychoi> eumel8, IMO project specific docs which are linked from install-tutorials should be interested in translators
13:47:36 <ianychoi> genek, oh i have just seen https://bugs.launchpad.net/openstack-i18n/+bug/1672927 - thanks a lot!
13:47:46 <openstack> ianychoi: Error: Could not gather data from Launchpad for bug #1672927 (https://launchpad.net/bugs/1672927). The error has been logged
13:48:15 <amotoki> IMO (as my hat of neutron/horizon core) it is completely up to translation teams. we are just maintaining English version. If there is a need for translation we can support it if enough instruction is provided.
13:50:28 <eumel8> amotoki: I'm not sure if we are able to support this. That are a lot's of projects.
13:51:19 <amotoki> eumel8: on that point, we can set priorities and add necessary settings (for example, sphinx conf) to prioritized projects first
13:51:37 <ianychoi> I agree with amotoki :)
13:51:56 <eumel8> mhm, okay, then I would start with horizon and then we see how it will work.
13:51:56 <amotoki> if there is no translation we never both individual teams (with translation import patches)
13:52:32 <eumel8> for the others I send a poll and after the feedback we can priorisize
13:52:44 <amotoki> horizon and neutron are easy for testing as I can approve changes :)
13:52:51 <eumel8> :)
13:53:16 <eumel8> ianychoi: you want to talk the last 5 min about the pdf build thing?
13:53:40 <ianychoi> eumel8, sure but PDF building is related to Docs a lot and also less on I18n
13:53:48 <eumel8> #topic Status PDF build spec
13:53:58 <eumel8> #link https://review.openstack.org/#/c/509297/
13:54:33 <eumel8> ianychoi: there were some email communication in the past. Are there anything what we can do?
13:54:48 <ianychoi> Now my question is that the review is related with docs team and not I18n team - would it be a good topic for I18n team?
13:55:43 <eumel8> I don't know. You think the doc team has to work on it?
13:56:01 <ianychoi> eumel8, the agenda is for Docs team, not I18n team but now we are in I18n team meeting
13:56:20 <ianychoi> eumel8, you think that PDF build is also useful for I18n team?
13:56:51 <eumel8> double-check: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Next_meeting_:_Oct_26_2017.2C_13:00_UTC
13:57:27 <eumel8> ianychoi: only for clarification. I'm fine with that to set this on the agenda for the docs team meeting :)
13:57:44 <amotoki> it totally depends on how much docs are translated :) and :(
13:58:15 <amotoki> I think it is potentially useful for well translated documentations
13:58:29 <eumel8> we will see :)
13:58:54 <ianychoi> eumel8, I am happy to tell to update the status for PDF builds - I originally wanted to ask some Korean colleagues to contribute on this but their progress is so slow. One concern for me is that it is now very hard to share the status in Docs team meeting.
13:59:07 <ianychoi> It would be because of my busy life mainly...
13:59:19 <eumel8> time is over. thx for participating and discussion
13:59:24 <amotoki> In my understanding, PDF discussion is mainly for archival usage though
13:59:30 <eumel8> we can switch to i18n channel
13:59:42 <ianychoi> Yep
13:59:48 <amotoki> ianychoi: the meeting time of docs meeting seems to be revisit again :)
13:59:49 <genek> thanks all :)
13:59:57 <ianychoi> Thanks a lot eumel8 amotoki genek and jftalta today!
14:00:01 <eumel8> #endmeeting