<html><body>
<p><tt><font size="2">Clark Boylan <cboylan@sapwetik.org> wrote on 09/09/2015 08:26:51 PM:<br>
<br>
> From: Clark Boylan <cboylan@sapwetik.org></font></tt><br>
<tt><font size="2">> To: openstack-i18n@lists.openstack.org</font></tt><br>
<tt><font size="2">> Date: 09/09/2015 08:27 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [Openstack-i18n] IBM translations to contribute</font></tt><br>
<tt><font size="2">> <br>
> On Wed, Sep 9, 2015, at 02:34 PM, Douglas Fish wrote:<br>
> > <br>
> > <br>
> > Hi i18n Friends,<br>
> > <br>
> > I'm happy to share that we are proceeding with our plan to share our IBM<br>
> > translations with the OpenStack community.<br>
> > <br>
> > To review and follow up on what was shared in the 2015-08-20 i18n team<br>
> > meeting [1]:<br>
> > - We would like to contribute our IBM translations for projects<br>
> > ceilometer,<br>
> > glance, heat, nova, ironic, neutron, cinder, keystone, and swift. Note<br>
> > that<br>
> > Horizon is not in this list because the community has been focused on<br>
> > translating Horizon; I'm concerned there may be excessive terminology<br>
> > conflicts.<br>
> > - We have translations for de es fr it ja ko_KR pt_BR ru zh_CN<br>
> > zh_TW<br>
> > - These contributions are based on our Kilo translations. They have been<br>
> > reviewed and tested.<br>
> > - In order to facilitate an informal review by the translation teams<br>
> > before<br>
> > uploading I've made the translations available at<br>
> > <a href="https://github.com/doug-fish/openstack-translations">https://github.com/doug-fish/openstack-translations</a> . The repository is<br>
> > private. If you'd like access, just share your github id with me via<br>
> > email<br>
> > (drfish@us.ibm.com) or IRC (doug-fish) and I'll give you access.<br>
> > - Segments that have been updated with IBM translations have a comment<br>
> > "Contributed by IBM" added. This is to enable reviewing; I don't expect<br>
> > these comments to remain in Zanata after the upload.<br>
> > <br>
> > At a high level, our process is that we are extracting the existing PO<br>
> > files from Zanata, then using Babel based code to compare our IBM<br>
> > translations with the community ones and filling in any blanks. We've<br>
> > taken<br>
> > care not to overwrite any existing translations.<br>
> > <br>
> > These proposed files are based on what we extracted from Zanata recently<br>
> > (today). Our intent is to run this tooling again after the review period<br>
> > to<br>
> > pick up any community translations that have occurred. I'm aware that<br>
> > translations for Nova are not updated in Zanata yet, but again, I expect<br>
> > to<br>
> > handle this by re-running our tools.<br>
> > <br>
> > I'm working with Thomas Cocozzello (tjcocozz) and Lucas Palm (lapalm) who<br>
> > have coded our tools and scripts to handle this. They are requesting to<br>
> > join the language teams in Zanata so that if there are no concerns noted<br>
> > during the review they can upload translation contributions.<br>
> > <br>
> > I plan to ask Tom and Lucas to upload these files on 2015-09-14 unless<br>
> > there are concerns noted during the reviews.<br>
> > <br>
> > Please let me know if you have questions or concerns!<br>
> > <br>
> > Doug<br>
> > <br>
> > 1.<br>
> > <a href="http://eavesdrop.openstack.org/meetings/openstack_i18n/2015/">http://eavesdrop.openstack.org/meetings/openstack_i18n/2015/</a><br>
> openstack_i18n.2015-08-20-13.03.log.html<br>
> > <br>
> > <br>
> > Doug Fish<br>
> <br>
> After reading the meeting log it appears that using a git repo of some<br>
> sort to perform easy diffing was the suggested way to go through this<br>
> process. My only concern with that is these translations are being<br>
> treated in a special manner to the detriment of other contributors that<br>
> have to go through the normal translation process in Zanata (and<br>
> previously Transifex). At the very least current translators may not<br>
> realize that there is a bunch of work done because it is currently<br>
> hidden behind a private Github repo.<br>
> <br>
> My suggestion would be to push these translations into Zanata the same<br>
> way any other translator would. That communicates to other translators<br>
> where to focus both review and translation efforts. And if we need<br>
> better diffing abilities that may make for a good feature request to<br>
> Zanata? (note this is based on my understanding that translations in<br>
> Zanata have to be approved/accepted and I don't think that we should<br>
> bypass that process as all other translators have to go through it).<br>
> <br>
> If that is not feasible for practical reasons my suggestion would be to<br>
> use Gerrit instead of Github and perform the review in the open. This<br>
> way we have record of the reviews and anyone can participate using the<br>
> tools already in use for reviewing git changes by OpenStack. You should<br>
> be able to push changes to various projects updating their .po(t) files<br>
> in order to get the diffs. If you do it atop the current translation<br>
> change proposals in Gerrit you should get the correct diffs out of it.<br>
> <br>
> I know I would personally be a lot more comfortable with this if<br>
> Andreas' could weigh in on it. Maybe we can get his feedback before<br>
> making too many changes? Also, do let me know if the infrastructure team<br>
> can do anything to help IBM contribute upstream first so that we can<br>
> avoid needing to work through special cases like this in the future. If<br>
> there are deficiencies in the system/tooling it would be great to fix<br>
> them.<br>
> <br>
> Clark<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>
</font></tt><br>
<tt><font size="2">Clark, I think you and I have a lot of agreement about the translation process. I agree it would be better if contributions like this could be handled using the normal processes. I had the same expectation you did that translations had to be approved/accepted before they were included in the service's git repositories; I now understand this is not the case. While it's true that Zanata includes a review feature, this is a post-acceptance review. Unreviewed translations are included in the exported PO files. Translation reviews happen at a later time.</font></tt><br>
<br>
<tt><font size="2">As a consumer of translations, it's important that they go through a process that parallels the process of the code: translations need to have a review before they are included in the normally exported PO files, just like code needs to have a review before it gets included in the git repositories. I understand this will not be an easy change. Performing reviews will take time, and our translators are already pressed for time the last few weeks of the release. We'll need to explore solutions to this problem. We need to make sure we can get broader participation in the translation process, and perhaps translations should not be made available until the first stable fixpack in order to give translators time to complete this work.</font></tt><br>
<br>
<tt><font size="2">Please note that we are not bypassing any features of Zanata. I've added this informal review in github based on discussion that occurred in the i18n meeting. If the translation teams found that there was a terminology or other problem with the translations we intend to contribute, there is no easy way for them to reject them all in Zanata. At the end of this informal review, these translations will be uploaded into Zanata just like any translation team member could, and the usual processes will all still apply.</font></tt><br>
<br>
<tt><font size="2">Andreas, do you have any concern or further suggestion?</font></tt><br>
<br>
<tt><font size="2">Doug</font></tt></body></html>