13:07:35 <ianychoi> #startmeeting OpenStack I18n Meeting
13:07:36 <openstack> Meeting started Thu Apr 13 13:07:35 2017 UTC and is due to finish in 60 minutes.  The chair is ianychoi. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:07:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:07:40 <openstack> The meeting name has been set to 'openstack_i18n_meeting'
13:07:50 <ianychoi> #topic participation
13:07:59 <jpich> Hello
13:08:11 <jftalta> jpich, hi
13:08:17 <ianychoi> Today, I have not set any topic previously on wiki but I want to talk about participation
13:08:20 <ianychoi> jpich, hi!
13:09:05 <ianychoi> It seems that participation is getting lower in I18n.. what would be the main reason? Am I doing something wrongly?
13:10:04 <jftalta> no, I don't think so. Sometimes it's high, sometimes it's low...
13:10:42 <jpich> I think it tends to get higher closer to release time, when there is a lot of work to be done perhaps?
13:11:18 <ianychoi> Personally, I am finding my new job and I am getting more busy. Recently, I have been interviewed in a company - the company looks so nice and wonderful but it does not focus on OpenStack. I may need to more focus on the new company if I finally negotiate and decide to join the company
13:11:37 <jftalta> +1. Its seems obvious
13:12:32 <jftalta> ianychoi, ok...
13:13:48 <ianychoi> #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
13:14:23 <ianychoi> So... now I want to learn and follow how Docs team prepares and organizes IRC meetings
13:15:01 <ianychoi> In Docs team, specialty teams can send "absence" reports
13:15:19 <ianychoi> I think language teams in I18n team can submit such reports
13:16:02 <ianychoi> The good thing I think is that we can discuss more input for the people and language teams who are absent
13:16:31 <jpich> That sounds great to encourage more involvement
13:16:36 <ianychoi> However, I am worried that - 1) whether they will participate or not and 2) it may encourage more absence..
13:17:55 <jpich> For 1) there is only one way to know :-)
13:18:17 <jpich> For 2) if the new format works to get more people to participate and talk about their work maybe that's ok too, as long as the conversation happens?
13:19:45 <ianychoi> jpich, +1 :)
13:23:01 <ianychoi> jftalta, are u online now ? :)
13:24:49 <ianychoi> jpich, by the way, I greatly appreciate your kind and continuous participation :) Translated Tripleo-UIs are now generally available as packages (rpms or debs)?
13:26:03 <jpich> ianychoi: It is my pleasure. I think the translated TripleO UI should be in the RDO ocata rpms by now, yes :)
13:26:09 <amotoki> what's being discussed?
13:26:18 <ianychoi> amotoki, hello!
13:26:33 <amotoki> I just clicked various channels and noticed this :)
13:26:39 <ianychoi> #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
13:26:56 <amotoki> long long agenda?
13:27:15 <amotoki> seems docs team one
13:27:19 <ianychoi> I am proposing 'absence reports' in IRC meetings from language coordinators - similar as what Docs team does with specialty teams
13:28:02 <ianychoi> Not too long :)
13:28:39 <amotoki> hmm... difficult question
13:28:57 <amotoki> IMHO the i18n team work has high and low seasons.
13:29:33 <amotoki> high season means a season where we say "Let's translate something"
13:30:06 <amotoki> low season is the first half of dev cycle. in this season we tend to get less attraction.
13:30:42 <amotoki> i think this is one reason of less attendees of the team meeting.
13:31:00 <amotoki> this is just a first impression from me
13:32:53 <ianychoi> In my opinion, nevertheless, it would be much nice if there is at least one simple communication with some specific period. What I mean that even there is low attention season, I think simple reporting (it seems that there is no translation contribution for last two weeks) from langauge teams would be fine
13:33:15 <amotoki> good point
13:33:53 <amotoki> monthly might be good?
13:34:08 <ianychoi> amotoki, yep :)
13:35:04 <amotoki> in case of Japanese team, discussion only happens before the release (though it is not so active recently) and rarely happens in other period....
13:35:34 <amotoki> I am afraid language coordinator have nothing to report every time :-(
13:36:15 <ianychoi> I will find more details with the things which would be good to be included in the report
13:37:30 <ianychoi> Currently, I think - 1) # of language team members (increased? same? decreased?)   2) Translation statistics (which projects contributed? if no, please say no)   3) If somethings are discussed in local teams, please share
13:37:54 <amotoki> sounds good items
13:38:05 <amotoki> on the other hand, we need some way to share what's happening and on-going efforts in the upstream to lang teams.
13:38:35 <jpich> Sounds like a place for i18n coordinators to step in :)
13:39:05 <ianychoi> yep good point, amotoki
13:39:36 <amotoki> go ahead everyone!
13:40:47 <ianychoi> Okay.. Then I think the final one week for each month would be the period for receiving the reports from language coordinators
13:41:12 <ianychoi> and the first IRC meeting in each month would be the period to share in the IRC meeting
13:41:43 <ianychoi> and after then, PTL would share the overall result through i18n mailing list and other mailing lists (might be docs also?)
13:43:23 <ianychoi> Anything else?
13:43:28 <ianychoi> for the topic?
13:44:09 <amotoki> ianychoi: I see you proposed a patch of POT extraction for the i18n contributor guide.
13:44:21 <amotoki> is there any progress or discussion with the docs team?
13:44:43 <ianychoi> #topic i18n contributor guide internationalization
13:45:23 <ianychoi> amotoki, yep during PTG, I discussed it with katomo and Docs team to define the structure of URLs
13:46:20 <amotoki> yeah, i was there
13:47:00 <ianychoi> (Hmm I am now a little bie confused with other topics - the structure of project install guide)
13:47:07 <ianychoi> s/bie/bit
13:47:31 <amotoki> :)
13:47:59 <amotoki> I was in and out the room randomly so it is no surprise you are confused...
13:48:16 <ianychoi> Anyway, I remember that Andreas said that i18n contributor guide would be internationalized by adding to infra scripts like training-guides
13:48:35 <ianychoi> Since training-guides is not in openstack-manuals repo and published with translated documents
13:49:02 <ianychoi> I am looking and defining what and how to be patched for i18n contributor guide
13:49:23 <amotoki> that's same as my memory
13:50:18 <ianychoi> #link https://blueprints.launchpad.net/openstack-i18n/+spec/i18n-guide-translation
13:50:36 <ianychoi> I have defined brief TO-DO lists in work items :)
13:50:57 <ianychoi> #topic IBM participation
13:52:18 <ianychoi> Recently, one IBM translator contacted me and the person said to me that she/he wants join to multiple language teams
13:52:47 <ianychoi> The person said that: "key translation contact person for IBM PowerVC.. I am part of IBM Systems, so you can say that instead. But yes, we translate in German, Spanish, French, Italian, Japanese, Korean, Portuguese (Brazil), Russian, Chinese (Taiwan), Chinese (China). The projects in our priority are keystone, neutron, cinder, glance, nova and related projects"
13:53:14 <ianychoi> Can I approve the person to join into multiple language teams as a translator?
13:54:09 <amotoki> I think it is up to language teams
13:55:11 <amotoki> generally there is no reason to reject the request, but in Japanese case, existing contirbutors are forced to clean up translation memories much last time IBM translation was imported :(
13:55:58 <ianychoi> amotoki, it caused because previous IBM translators overwrote previous translations?
13:56:05 <ianychoi> Or some merge functionality?
13:56:50 <amotoki> ianychoi: IBM contributed several projects we didn't cover. this means most new translation terms are added
13:57:36 <amotoki> when we see translation memory, IBM translation keywords looks like majority candidates and our existing glossary became minor
13:57:48 <amotoki> it confused new translators :(
13:58:04 <ianychoi> amotoki, okay. I will share your concern to the IBM person :)
13:58:35 <jpich> Were they aware of the log translations removal?
13:58:58 <amotoki> personally I don't want to repeat the same discussion and I have no plan to join the discussion. it wasted my time a lot.
13:59:37 <jpich> Ah, yes. I was just curious since they were the ones interested in it originally, and if they are now coming back
13:59:45 <jpich> but we'll see what happens
13:59:51 <ianychoi> amotoki, okay what I meant that I will defer joining in ja team and deliver your concern
13:59:55 <amotoki> they've gone so quickly.... after one cycle :(
14:00:21 <ianychoi> #topic open discussion
14:00:27 <ianychoi> But.. time is already up
14:00:29 <ianychoi> Stackalytics, python 3 support, tagging for i18n
14:00:38 <ianychoi> Those are other topics to be discussed
14:00:52 <ianychoi> #info Stackalytics, python 3 support, tagging for i18n will be discussed in next or next next IRC meeting
14:00:56 <ianychoi> Bye all :)
14:01:03 <ianychoi> #endmeeting