07:02:15 <Daisy> #startmeeting OpenStack I18n Meeting
07:02:16 <openstack> Meeting started Thu Mar  6 07:02:15 2014 UTC and is due to finish in 60 minutes.  The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:02:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:02:19 <openstack> The meeting name has been set to 'openstack_i18n_meeting'
07:02:45 <Daisy> Hello again.
07:02:57 <jpich> Hello
07:03:03 <epico> Hello
07:03:08 <Daisy> :)
07:03:12 <Daisy> Nice to have you two.
07:03:27 <Daisy> So let's start the discussion.
07:03:38 <Daisy> #topic Horizon translation
07:03:51 <Daisy> https://www.transifex.com/projects/p/horizon/
07:04:22 <Daisy> In order to support Horizion translation for Icehouse release, there are several things we need to do.
07:04:36 <Daisy> 1. Scripts
07:04:53 <chandan_kumar> hola!
07:05:08 <Daisy> We may need two scripts: We may need two: Proposal translation to Transifex, and upstream translation to Git.
07:05:21 <Daisy> Hello, chandan_kumar . We just started.
07:05:46 <Daisy> For the first one, there is a patch: https://review.openstack.org/#/c/68042/
07:05:50 <Daisy> waiting for approval.
07:06:31 <Daisy> After this patch is merged, the translation resources in Transifex could be updated automatically, synchronized with Horizon master branch now.
07:06:53 <Daisy> Each update of Horizon master branch, new version of po files will be generated and updated in Transifex.
07:07:38 <Daisy> Just a reminder, since after RC1, icehouse release will switch to "icehouse" branch, right, jpich ?
07:07:59 <jpich> Daisy: That's my understanding, yes - there will be a stable/icehouse branch
07:08:03 <jpich> and master will become juno
07:08:14 <Daisy> So we need to disable the automation synchronization at that time.
07:08:26 <Daisy> Although I don't know how to disable a Jenkins job now.
07:08:52 <jpich> Right, I'm not sure either
07:09:26 <jpich> That sounds like a question for the infra folks, I'm sure they'll be happy to help
07:09:55 <Daisy> The second script "upstream translation to Git" is not ready yet. It will propose a patch to git. Somebody needs to approve the patch before it could be merged. Still, it should relate with master before RC1 and switch to stable/icehouse after RC1.
07:10:37 <Daisy> I would like to be the owner of these two scripts.
07:10:46 <jpich> Daisy: Actually, maybe we don't need to disable the infra script - we can simply disable Transifex automatic po file sync?
07:11:14 <Daisy> jpich: I don't know if it is possible
07:11:24 <jpich> I thought we did this before
07:11:52 <Daisy> Before, the Horizon update in Transifex was implemented by a checkbox in Transifex. Now it doesn't.
07:12:19 <Daisy> The resources in Transfiex don't link to files in Git now.
07:12:35 <Daisy> So I think it's not able to disable it by uncheck the checkbox.
07:12:40 <jpich> Ok! I should take the time to understand the first script better :) Thanks for the explanation!
07:12:43 * fifieldt wanders in
07:13:02 <Daisy> welcome, fifieldt
07:13:05 <jpich> o/
07:13:28 <Daisy> jpich proposed to take "Translation impact" into consideration.
07:13:45 <Daisy> I think we could, but it's low priority that the above two scripts.
07:14:13 <Daisy> We could follow what "Doc impact" did.
07:14:17 <fifieldt> TranslationImpact would not be hard to code
07:14:28 <Daisy> Great, fifieldt !
07:14:30 <Daisy> You are master.
07:14:31 <fifieldt> the hard bit is getting people to use it :)
07:14:38 <jpich> I'm not sure the TranslationImpact tag would work very well because it's only relevant to a specific time period
07:14:41 <fifieldt> would it only be used after String fgreeze?
07:14:55 <jpich> Yes, that's my understanding
07:15:06 <Daisy> I agree.
07:15:06 <jpich> Otherwise it would be a lot of spam during the development cycle :)
07:15:09 <fifieldt> How did the string changes after string freeze work last cycle?
07:15:18 <fifieldt> it was my impression that we got emails
07:15:22 <fifieldt> with information about the changes
07:15:35 <fifieldt> since the reviewers are already instructed to do so
07:15:39 <DeeJay1> IMHO the translation impact should only be done on the proposed and stable branches, so it won't spam (and hi BTW ;)
07:15:53 <jpich> There may have been some heads-up from people monitoring the patches coming in
07:16:08 <fifieldt> having a TranslationImpact tag could have the opposite effect to what we want
07:16:13 <Daisy> Last release, Akihiro will send email to I18n ML to inform us the strings were changed.
07:16:18 <fifieldt> it could make it more easy to justify string changes
07:16:30 <fifieldt> which is not ideal :)
07:17:15 <jpich> I don't think the tag will work because it's so dependent on when the patch is merged - if a patch was submitted before FF it wouldn't have the tag but need it
07:17:26 <fifieldt> yeah, that's another good point
07:17:40 <fifieldt> I think the more important part about string freeze is preventing strings from changing, rather than communicating that they have changed
07:17:42 <jpich> and then if a patch doesn't get merged in time, authors would need to update their commit or confusing emails would be sent
07:17:49 <fifieldt> a good point
07:17:53 * DeeJay1 would like to have blocking i18n reviews on the gates
07:18:22 <Daisy> so no need to work on "TranslationImpact"?
07:18:30 <jpich> I don't think so
07:18:40 <fifieldt> perhaps we can monitor how the communiication works during this period
07:18:43 <fifieldt> and make a decision later
07:18:50 <fifieldt> if the communication is bad, maybe we need to do something
07:18:53 <fifieldt> but if it's OK
07:18:57 <fifieldt> then maybe we can be lazy
07:18:57 <fifieldt> ?
07:19:00 <Daisy> If the automation synchronization is enabled, somebody could see the completion rate is changed from 100% to 99%, or some number less than 100%.
07:19:17 <jpich> We discussed last time, especially in Horizon there's going to be a number of small changes between now and RC in the strings for sure
07:19:24 <jpich> Because bug fixes add new error messages, etc
07:20:05 <Daisy> Yes, especially some bugs with I18n tag are reported.
07:20:35 <Daisy> so decision is: we still use communication, other than automation email notification.
07:20:47 <jpich> My impression is that the communication is good and when it isn't people are willing to learn to avoid making i18n's folks' lives harder - though I may be biased :)
07:21:12 <Daisy> OK. then.
07:21:36 <Daisy> Next, we also need to complete horizon messages translation
07:22:04 <Daisy> From my point of view, it's not a big workload, for those languages released in last version.
07:22:32 <Daisy> I think, there are not a big number of new strings added.
07:22:50 <Daisy> But for the languages without a good base, it will be a big workload.
07:23:41 <Daisy> There is no specific date for RC1 release yet.
07:23:55 <Daisy> it is guess it could happen at the end of March.
07:24:26 <fifieldt> that sounds right
07:24:30 <Daisy> So the end of March may be a checkpoint for us to finish the translation.
07:24:30 <jpich> From https://wiki.openstack.org/wiki/Icehouse_Release_Schedule I think it will be around March 25th
07:24:33 <fifieldt> RC time starts on March 27
07:25:17 <Daisy> OK. So let's make the time as March 24 for our translators to finish the translation.
07:25:44 <Daisy> From my experiences in last release, some language teams may not catch this checkpoint.
07:26:06 <Daisy> Some languages team may check our deadline, that is before the last RC.
07:26:20 <Daisy> may catch our deadline, that is before the last RC.
07:27:04 <Daisy> So anyway, we push the team to finish the translation before March 24, especially for these languages with good base.
07:27:49 <Daisy> We welcome more language to be released in Icehouse
07:28:08 <Daisy> That cloud show our "improvement".
07:29:48 <Daisy> czech & German has a good base too, more than 50% have been translated.
07:30:11 <Daisy> We need to broadcast to community ML, to promote Horizon translations.
07:30:42 <Daisy> Next thing is about "I18n Test and bug report"
07:31:23 <Daisy> Last release, Akihiro provided a test website, which was proved to be a big help for translators to review and to test.
07:31:55 <Daisy> I will see if he could provide the same test website for this release.
07:32:21 <Daisy> OK. That's all things in my mind about Horizon message translation.
07:32:36 <jpich> The test site may also be something we want to work with infra to provide in the future, since it's so important
07:32:38 <DeeJay1> Daisy: please tell him that if he needs resources I got a physical machine idling which handles the docs build
07:32:50 <Daisy> great, DeeJay1 .
07:33:28 <Daisy> jpich, you are right, but I don't know if it's in the scope of openstack infra.
07:33:59 <Daisy> and, it is only used for a short period too.
07:34:00 <DeeJay1> jpich: well, just running seperate jobs for the docs hit opposition :/
07:34:18 <jpich> DeeJay1: Really? I wasn't aware :/
07:34:52 <jpich> In my mind they provide all sorts of magical support to all the OpenStack projects that need it, but I guess there are limits
07:35:19 <jpich> May still be worth having a chat just to check :) But as long as we have volunteers to maintain this, it's not a problem
07:35:39 <Daisy> :)
07:36:12 <Daisy> Are there anything I missed for Horizon translation?
07:36:56 <Daisy> if no, let's move to next topic.
07:36:59 <Daisy> #topic "installation guide" translation and publish
07:36:59 <fifieldt> it sounds good
07:37:13 <Daisy> https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/install-guide/
07:37:14 <DeeJay1> Daisy: BTW https://bugs.launchpad.net/openstack-i18n/+bug/1277873
07:37:58 <Daisy> DeeJay1: thanks for reminder. I will put it to my TODO list.
07:38:14 <Daisy> bad memory for me now.
07:38:32 <DeeJay1> Daisy: I fear we'll get many more strings to fix on transifex when that bug is fixed
07:39:13 <Daisy> there will be a new project related with it, DeeJay1. And the messages translation besides Horizon are not started, actually.
07:39:40 <Daisy> a new project in Transifex.
07:40:02 <Daisy> can we go back to installation guide translation?
07:40:36 <Daisy> From the progress, Japanese and Korean are almost finished. Chinese and German are more than half.
07:41:12 <Daisy> I promise to finish the translation in March and I hope the website for Korean and Chinese could be ready before the summit.
07:41:47 <Daisy> fifieldt: I remember you mentioned the installation guide that we are translating now is for Icehouse, and there are still changes from time to time.
07:41:55 <Daisy> When do you think it could be finalized?
07:41:56 <fifieldt> this is true
07:42:12 <fifieldt> the aim is before release
07:42:22 <fifieldt> certainly all of the major work will be done before then
07:42:38 <fifieldt> the only major work going into the install guide is in the neutron section
07:42:51 <Daisy> so my aim is to publish the Japanese, Korean and Chinese version at the same time when the English version is finallized.
07:42:55 <fifieldt> for all of the other sections, it is mainly tweaks in the sections we see as <placeholder>
07:43:03 <fifieldt> and also deleting some unnecessary steps
07:43:11 <fifieldt> it is unlikely new steps will be added outside neutron
07:43:18 <fifieldt> sounds good
07:43:53 <Daisy> great!
07:44:00 <Daisy> I had a chat with David Cramer, the developer of Maven plugin.
07:44:06 <fifieldt> I am marking cli-guide as no longer accepting translations
07:44:09 <fifieldt> it seems it has been deleted
07:44:10 <Daisy> Now the plugin can only support Japanese and Chinese font.
07:44:21 <Daisy> But he promise to make it support Korean font in this month.
07:44:27 <fifieldt> great!
07:45:13 <Daisy> fifieldt: I think version management is also necessary for documentation too. Just as what I did for Horizon, horizon has Havana version and master version.
07:45:24 <Daisy> I mean, the translation.
07:45:27 <fifieldt> for some of the books, yes
07:45:39 <Daisy> Horizon will have Icehouse version soon.
07:46:04 <Daisy> Which books don't need versions?
07:46:51 <fifieldt> the ones that are 'contiuously published;
07:47:02 <fifieldt> eg image-guide
07:47:20 <Daisy> so these books are always the latest version?
07:47:25 <fifieldt> yes
07:47:31 <fifieldt> high-availability-guide
07:47:46 <fifieldt> and some of the others
07:47:55 <fifieldt> it might be worth talking to annegentle to clarify plans
07:48:09 <Daisy> ok. After installation guide is finalized, will it move to a stable branch?
07:48:40 <fifieldt> yes
07:48:41 <Daisy> Now all the synchronization in Transifex are related with master branch.
07:49:20 <Daisy> ok. I will put it in my mind. it may cause some issue.
07:50:29 <Daisy> I think I need to merge the po files into manuals repository manually.
07:50:33 <fifieldt> Daisy, AJaeger is also available to discuss the build job failure :)
07:50:43 <AJaeger> Hi!
07:51:04 <Daisy> Hi, AJaeger
07:51:18 <AJaeger> error message is " Pushing translations for resource openstack-manuals-i18n.cli-reference: -  https://www.transifex.com/api/2/project/openstack-manuals-i18n/resource/cli-reference/stats/ NOT FOUND"
07:51:30 <AJaeger> so, my guess is that needs to be created in transifex.
07:52:00 <Daisy> Yes, it's not in the Transifex now.
07:52:28 <AJaeger> so, can we do a manual creation/import?
07:52:49 <Daisy> AJaeger, could you tell me the context where you will use this project? In my mind, if it's in manuals, it could be automatic created by some jobs.
07:53:18 <AJaeger> This is about openstack-manuals.
07:54:58 <AJaeger> We seldom create new manuals, so an automatic job might be overkill.
07:55:07 <Daisy> I think it could be automatic created by script: https://github.com/openstack-infra/config/blob/master/modules/jenkins/files/slave_scripts/upstream_translation_update_manuals.sh
07:55:21 <Daisy> Yes, understand.
07:56:35 <AJaeger> Daisy, sure, go ahead and enhance ;)
07:56:46 <Daisy> AJaeger: I found there was no locale folder in cli-reference.
07:56:51 <Daisy> I will take a look at it after meeting.
07:57:08 <Daisy> #topic: open discussion
07:57:15 <Daisy> anything to discuss here?
07:57:34 <epico> https://blueprints.launchpad.net/oslo/+spec/log-messages-id
07:57:42 <epico> Could I update the blueprint?
07:58:05 <epico> Whiteboard section.
07:58:10 <Daisy> Yes, you could, epico
07:58:21 <epico> Daisy, Okay :)
07:58:21 <Daisy> Do you have right to do it？
07:58:31 * epico dunno it...
07:58:55 <Daisy> Let me put you as the draft, not sure if I have right too.
07:58:59 <Daisy> drafter.
07:59:06 <epico> Daisy, thanks.
07:59:09 <jpich> A question for DeeJay1: you mentioned wishing for the ability to block reviews for i18n reasons. For what kind of reviews and problems? (So I can watch out for it)
08:00:09 <jpich> Daisy, epico: I think everyone can update blueprint whiteboards but the other fields are usually protected
08:00:26 <epico> jpich, thanks, I see.
08:00:29 <Daisy> thanks for the clarify.
08:01:08 <Daisy> DeeJay1: could you answer jpich's question? I'm curious too.
08:01:31 <jpich> Tip: It's good practice to put your name and the date before your changes in the whiteboard so people know who added the comment :-)
08:01:45 <epico> Sure :)
08:02:14 <Daisy> I think, DeeJay1 may be not around now. I'm going to close the meeting. We can discuss offline.
08:02:22 <Daisy> Thank you all for your time.
08:02:26 <jpich> Or writing a very long answer ;) Maybe we can discuss on list
08:02:28 <jpich> Thanks!
08:02:41 <jpich> Or in #openstack-translation
08:02:48 <epico> Thanks!
08:02:52 <Daisy> #endmeeting