<html><body>
<p><font size="2" face="sans-serif">Thank you for sharing your thoughts, Akihiro.</font><br>
<br>
<font size="2" face="sans-serif">I think, we have to finish our goals step by step.</font><br>
<br>
<font size="2" face="sans-serif">The most important thing in my mind is to create corresponding resources in Transifex </font><br>
<font size="2" face="sans-serif">for the master branch, and automate the synchronize uploading and downloading process.</font><br>
<font size="2" face="sans-serif">Because string frozen date for Icehouse will come in March. We should make everything </font><br>
<font size="2" face="sans-serif">ready before that time.</font><br>
<br>
<font size="2" face="sans-serif">If you are available, we can have a discussion in the IRC meeting tomorrow.</font><br>
<br>
<font size="2" face="sans-serif">Best regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<br>
<tt><font size="2">Akihiro Motoki <amotoki@gmail.com> wrote on 2014/01/14 12:50:07:<br>
<br>
> Akihiro Motoki <amotoki@gmail.com> </font></tt><br>
<tt><font size="2">> 2014/01/14 12:50</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo/China/IBM@IBMCN, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> Julie Pichon <jpichon@redhat.com>, "openstack-<br>
> i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-i18n] Horizon patch with translation impact (havana)</font></tt><br>
<tt><font size="2">> <br>
> Hi,<br>
> <br>
> I think we need to consider two things:<br>
> (a) maintenance policy of stable release translations<br>
> (b) how to automate the process<br>
> <br>
> Regarding (a), in my understanding, we already have a consensus to maintain<br>
> translation up-to-date though it is not well-documented so far.<br>
> Daisy renamed Transifex horizon resources to *-havana to allow this.<br>
> From this point of view, there is no reason to give -1/-2 to the<br>
> proposed patch from Julie.<br>
> <br>
> Regarding (b), we should move to the automated process as Daisy wrote and<br>
> I wrote about it several times :-)<br>
> We need a volunteer to work on it. This is just a topic of the process.<br>
> <br>
> > I think, it's no question for Horizon to use #1 to update Transifex<br>
> > resources automatically.<br>
> <br>
> Agree in general.<br>
> <br>
> Before automating the process, we need to discuss how to deal with the switch<br>
> from master to milestone-proposed just before the release.<br>
> Once RC1 is shipped, master branch is open to development of the next release<br>
> but translations teams still want to work on the release.<br>
> <br>
> > How about #2 ?<br>
> > I remember originally Horizon team disabled automatics downloading because<br>
> > messy characters in po.en would cause broken in Horizon test.<br>
> > Now this issue has been resolved.<br>
> <br>
> Yes. It was really an old topic and fixed. It was because English PO<br>
> file has Georgian characters<br>
> and the unit tests failed. Horizon no longer has English PO files<br>
> since it is the source language<br>
> and the problem never happens now.<br>
> <br>
> > So I wonder if Horizon would like to adopt #2 to enable the automatics<br>
> > translation downloading now.<br>
> <br>
> For master branch, the automated translation imports works to me.<br>
> How about stable branch and milestone-proposed?<br>
> <br>
> For stable branch, we need to import well-reviewed translations.<br>
> How can we achieve this with an automated process?<br>
> I think this is the reason that automated process of translation imports<br>
> is not enabled by default now.<br>
> <br>
> For milestone-proposed, the meaning of the branch changes depending on<br>
> the phase,<br>
> I think it is not easy to make the process automated.<br>
> <br>
> <br>
> Thanks,<br>
> Akihiro<br>
> <br>
> On Mon, Jan 13, 2014 at 11:34 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:<br>
> > Hi, Julie<br>
> ><br>
> > I think it's time to consider the automation synchronization between Horizon<br>
> > source code and Transifex resources.<br>
> ><br>
> > The general solution now in community is to use Jenkins jobs.<br>
> > Most of openstack projects use this method to synchronize their PoT files<br>
> > with Transifex resources.<br>
> ><br>
> > There are two kinds of jobs:<br>
> > #1 A job after a commit event in git to generate PoT files and update<br>
> > Transifex resources if the PoT files are changed.<br>
> > #2 A regular job to download translations and create a gerrit review request<br>
> > to merge po files.<br>
> ><br>
> > I think, it's no question for Horizon to use #1 to update Transifex<br>
> > resources automatically. How about #2 ?<br>
> > I remember originally Horizon team disabled automatics downloading because<br>
> > messy characters in po.en would cause broken in Horizon test.<br>
> > Now this issue has been resolved.<br>
> > So I wonder if Horizon would like to adopt #2 to enable the automatics<br>
> > translation downloading now.<br>
> ><br>
> > Best regards<br>
> > Ying Chun Guo (Daisy)<br>
> ><br>
> ><br>
> > Julie Pichon <jpichon@redhat.com> wrote on 2014/01/09 18:42:30:<br>
> ><br>
> >> Julie Pichon <jpichon@redhat.com><br>
> >> 2014/01/09 18:42<br>
> >><br>
> >> To<br>
> >><br>
> >> Ying Chun Guo/China/IBM@IBMCN,<br>
> >><br>
> >> cc<br>
> >><br>
> >> Subject<br>
> >><br>
> >> Re: [Openstack-i18n] Horizon patch with translation impact (havana)<br>
> >><br>
> >> Hello Daisy,<br>
> >><br>
> >> Thank you for your reply! Did you mean to send this email only to me? I<br>
> >> think<br>
> >> it would be useful to reply to the list to have the answer available in<br>
> >> the<br>
> >> archives, too - I'll be happy to resend my own answer as well.<br>
> >><br>
> >> "Ying Chun Guo" <guoyingc@cn.ibm.com> wrote:<br>
> >> > Hi, Julie<br>
> >> ><br>
> >> > The Horizon translation resources for Havana have been renamed with a<br>
> >> > prefix "Havana" in Transifex.<br>
> >> > The update is not automatic, both from source codes to Transifex and<br>
> >> > from<br>
> >> > Transifex to source codes.<br>
> >> > We could synchronize these resources with source codes. But we need to<br>
> >> > do<br>
> >> > it manually.<br>
> >><br>
> >> Understood, thank you for the information!<br>
> >><br>
> >> > Although we don't have plan to update stable/havana translations, there<br>
> >> > is<br>
> >> > no stop for translators to do it.<br>
> >> ><br>
> >> > Are there any plan to release a new version of Horizon stable?<br>
> >> > If there is, we can call for translators support to update translations.<br>
> >><br>
> >> There are 3 more Havana releases planned [0]. I imagine the string<br>
> >> changes will<br>
> >> be very minimal, more and more so.<br>
> >><br>
> >> Cheers,<br>
> >><br>
> >> Julie<br>
> >><br>
> >><br>
> >> [0] <a href="https://wiki.openstack.org/wiki/">https://wiki.openstack.org/wiki/</a><br>
> >> StableBranchRelease#Planned_stable.2Fhavana_releases<br>
> >><br>
> >> ><br>
> >> > Best regards<br>
> >> > Ying Chun Guo (Daisy)<br>
> >> ><br>
> >> ><br>
> >> > Julie Pichon <jpichon@redhat.com> wrote on 2014/01/09 01:26:27:<br>
> >> ><br>
> >> > > Julie Pichon <jpichon@redhat.com><br>
> >> > > 2014/01/09 01:26<br>
> >> > ><br>
> >> > > To<br>
> >> > ><br>
> >> > > "openstack-i18n@lists.openstack.org"<br>
> >> > <openstack-i18n@lists.openstack.org>,<br>
> >> > ><br>
> >> > > cc<br>
> >> > ><br>
> >> > > Subject<br>
> >> > ><br>
> >> > > [Openstack-i18n] Horizon patch with translation impact (havana)<br>
> ><br>
> ><br>
> >> > ><br>
> >> > > Hi,<br>
> >> > ><br>
> >> > > I submitted a backport to Havana [0] that corrects a mistake in a help<br>
> >> > > message, but I'm not quite sure if we're still planning on updating<br>
> >> > > the<br>
> >> > > stable/havana translations. If you don't feel it's appropriate in this<br>
> >> > > case, please feel free to -1/-2 the patch. Thank you!<br>
> >> > ><br>
> >> > > ...Also if the discussions on the translation update schedules for<br>
> >> > > stable and master have been summarised somewhere, please let me know.<br>
> >> > > I can't recall the decided outcome.<br>
> >> > ><br>
> >> > > Thanks,<br>
> >> > ><br>
> >> > > Julie<br>
> >> > ><br>
> >> > > [0] <a href="https://review.openstack.org/#/c/65506/">https://review.openstack.org/#/c/65506/</a><br>
> >> > ><br>
> >> > > _______________________________________________<br>
> >> > > Openstack-i18n mailing list<br>
> >> > > Openstack-i18n@lists.openstack.org<br>
> >> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> >> > ><br>
> >><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Openstack-i18n mailing list<br>
> > Openstack-i18n@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> ><br>
> <br>
</font></tt></body></html>