<html><body>
<p><font size="2" face="sans-serif">Versions have been created for IBM to import their translations in the production server.</font><br>
<font size="2" face="sans-serif">These resources could be browsed through a "group" view. </font><br>
<a href="https://translate.openstack.org/version-group/view/ibm-translations-group"><font size="2" face="sans-serif">https://translate.openstack.org/version-group/view/ibm-translations-group</font></a><br>
<br>
<font size="2" face="sans-serif">@ Doug, I think you could start uploading now. </font><br>
<br>
<font size="2" face="sans-serif">Best regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<br>
<tt><font size="2">Ying Chun Guo/China/IBM@IBMCN wrote on 2015/09/18 22:40:39:<br>
<br>
> From: Ying Chun Guo/China/IBM@IBMCN</font></tt><br>
<tt><font size="2">> To: openstack-i18n@lists.openstack.org</font></tt><br>
<tt><font size="2">> Date: 2015/09/18 22:42</font></tt><br>
<tt><font size="2">> Subject: Re: [Openstack-i18n] IBM translations to contribute: update</font></tt><br>
<tt><font size="2">> <br>
> Hi, team <br>
> <br>
> I have made enough tests on the test server with the help from Doug <br>
> and his colleagues. <br>
> <br>
> In the test server, I created versions for nova, glance, cinder, <br>
> swift, ceilometer, <br>
> heat, keystone, and ironic. Doug and his colleagues uploaded their <br>
> po files for <br>
> languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I <br>
> tested merging <br>
> two versions. Things are running well. The test server is still in <br>
> good condition. <br>
> So there is no technical issues block me to do the same in the <br>
> production server. <br>
> I even tried "Group" in the test server. The "Group" feature looks wonderful.<br>
> <br>
> So if there is no objections, I will go to production server, doing <br>
> the same as <br>
> what I did in the test server. <br>
> <br>
> Best regards<br>
> Ying Chun Guo (Daisy)<br>
> <br>
> <br>
> Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM:<br>
> <br>
> > From: Douglas Fish/Rochester/IBM@IBMUS <br>
> > To: guoyingc@cn.ibm.com <br>
> > Cc: openstack-i18n@lists.openstack.org <br>
> > Date: 09/18/2015 05:14 AM <br>
> > Subject: Re: [Openstack-i18n] IBM translations to contribute: update <br>
> > <br>
> > Hi Daisy, <br>
> > <br>
> > We have translations to contribute for ceilometer, cinder, glance, <br>
> > heat, ironic, keystone, nova and swift for languages de, es, fr, it,<br>
> > ja ko-KR, pr-BR, ru, zh-CN, and zh-TW <br>
> > <br>
> > We are working to upload those to the Zanata test server to make <br>
> > sure there are no technical issues. <br>
> > <br>
> > Doug <br>
> > <br>
> > ----- Original message -----<br>
> > From: Ying Chun Guo <guoyingc@cn.ibm.com><br>
> > To: Douglas Fish/Rochester/IBM@IBMUS<br>
> > Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org><br>
> > Subject: Re: [Openstack-i18n] IBM translations to contribute: update<br>
> > Date: Thu, Sep 17, 2015 11:04 AM<br>
> > <br>
> > Hi Doug, Hi team,<br>
> > <br>
> > In today's IRC meeting, we talked about the process to get IBM translations.<br>
> > I'm going to normalize the process to contribute translations by <br>
> > uploading po files.<br>
> > <br>
> > Here are some key points during the meeting:<br>
> > <br>
> > 1. It is strongly discouraged to use the offline editor other thanweb tool. <br>
> > Because the offline editor could not take the advantages of <br>
> > translation memory and glossary, <br>
> > which might affect the translation quality.<br>
> > 2. Simply uploading po files are not allowed because it has a risk <br>
> > that the po files might contain bad translations.<br>
> > 3. In some special cases, if people who want to contribute <br>
> > translations by uploading po files, following below steps<br>
> > 3.1 Send email to I18n mailing list, describing the source <br>
> > documents and languages he/she is going to upload.<br>
> > 3.2 Zanata admin will create a branch. Then contributors could <br>
> > upload po files to the proposed branch.<br>
> > 3.3 When the uploading is done, language coordinators could <br>
> > review the translations.<br>
> > The coordinators could have two kinds of review results: <br>
> > agree to merge or deny to merge.<br>
> > If the coordinators deny to merge, coordinators should <br>
> > give some comments, either to delete this branch, or to suggestions <br>
> > to improve.<br>
> > 3.4 If the coordinators agree to merge to the master branch, <br>
> > Zanata admin will make the merge. <br>
> > A option could set during the branches merging to make sure not <br>
> > overwrite translated/approved translations in the source branch.<br>
> > After merging, the proposed branch will be deleted.<br>
> > <br>
> > I have been testing branches in the Zanata test server for several days.<br>
> > When I make sure it works fine, I will go to the production server.<br>
> > <br>
> > @Doug, please let us know which resources and which languages you <br>
> > are going to propose ? <br>
> > <br>
> > Best regards<br>
> > Ying Chun Guo (Daisy)<br>
> > <br>
> > <br>
> > "Douglas Fish" <drfish@us.ibm.com> wrote on 09/16/2015 08:05:52 PM:<br>
> > <br>
> > > From: "Douglas Fish" <drfish@us.ibm.com><br>
> > > To: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org><br>
> > > Date: 09/16/2015 08:06 PM<br>
> > > Subject: [Openstack-i18n] IBM translations to contribute: update<br>
> > ><br>
> > > Here's the revised approach we are taking to contributing our IBM<br>
> > > translations to the community, based on feedback on suggestions:<br>
> > > <br>
> > > We are planning to make the proposed translations available for a<br>
> > > pre-review as a separate branch in Zanata, but they are not there<br>
> > > yet. While testing out this upload on the development server we<br>
> > > discovered that uploading PO files caused the server to become<br>
> > > unresponsive for a while. Thanks to pleia2 and the infra team for<br>
> > > sorting that out and addressing the issue. We'll try the upload on<br>
> > > dev again tomorrow and if it goes well we will make the translations<br>
> > > available for pre-review in a separate Zanata branch.<br>
> > > <br>
> > > I had originally proposed ending the pre-review on Monday. Obviously<br>
> > > that's not going to happen! I understand that different language<br>
> > > teams have differing levels of readiness to accept these<br>
> > > contributions. I understand some groups are ready at this time,<br>
> > > while others would like to have more time, possibly even into Mitaka<br>
> > > to review. We aren't going to upload PO files for any language were<br>
> > > the team does not want them.<br>
> > > <br>
> > > Language coordinators, please let me know how you'd like to proceed<br>
> > > with these contributions for your language. Do you want<br>
> > > 1) us to upload them to Zanata's current master translations for<br>
> > > normal review and editing as soon as we can,<br>
> > > 2) us to upload them to Zanata as a separate branch for further <br>
> > pre-review, or<br>
> > > 3) hold off any submission or preview at this time.<br>
> > > <br>
> > > Please note that it important to us that we upload these<br>
> > > translations. The translations are a valued IBM asset, it's<br>
> > > important to us that they are recognized as contributed by IBM.<br>
> > ><br>
> > > I'll be at the Thursday i18n team meeting, and am available by IRC<br>
> > > (doug-fish) or email if you have questions or further concerns.<br>
> > ><br>
> > > Thanks!<br>
> > ><br>
> > > Doug_______________________________________________<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>
> 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>
</font></tt></body></html>