Open Stack

On Fri, Sep 11, 2015, at 11:00 AM, Ying Chun Guo wrote:
> Hi, all
> 
> I have talked with Clark, Doug, and some translators today.
> As a summary, here are my understanding to the current situation.
> 
> 1. Translators welcome IBM contributions because that 
> could help to lessen the translation efforts.
> 2. IBM contributions have to go through the formal translation
> process, including: translating in Zanata (although offline and then 
> upload), 
> being reviewed by reviewers, being pulled from Zanata, being reviewed 
> in Gerrit, and passing the testing, before it gets merged finally.
> 3. Zanata doesn't support to pull reviewed and approved translations.
> All translations except rejected translations, even not reviewed 
> translations, will be pulled. 
> 4. Because IBM contributions are a batch of translations, translators 
> might not have enough time
> to review one by one. Some translation team may want to do a pre-review 
> before the po files 
> are uploaded to Zanata.
> 
> The key point is how to do the pre-review.
> 
> Based on all the feedback I collected today, there are several options.
> Option #1: Pre-review in a private github repo.
> This one is not good because it's private, not public.
> Option #2: Pre-review in Gerrit
> The good thing is that it's public and under Openstack governance.
> The bad thing is that it'll take draft translations to developers' sight.
> Developers may get confused when they see the translation patch.
> What's more, messages in IBM's po files might in a different order, which 
> makes the 
> comparing with existing po files difficult.
> Option #3: Pre-review in Zanata by taking the advantages of version.
> Create a new version in Zanata, named as ibm-translation.
> Ask IBM to upload po files there.
> Translators could review in the web UI, or review offline by downloading 
> the po files.
> Translators make comments or updates through Zanata. 
> IBM make improvement based on the comments.
> When translators are OK with IBM translations, merge these two versions.
> Option #4: No pre-review at all
> Some translation teams don't mind it much as long as it covers only the 
> missing areas 
> of existing translation.
> 
> I think, #3 is the best one.
> I have made a test in Zanata test server.
> I created a new version of Nova, see: 
> https://translate-dev.openstack.org/iteration/view/nova/ibm-translation 
> I asked IBM to upload the Italian translations of document "nova".
> You could see the percentage increase to 90%, while in master version the 
> percentage is still 37%.
If the translators are happy with doing it this way this seems like a
reasonable approach. Keeps everything in the open and allows us to avoid
adding a bunch of unreviewed translations to the po files in Gerrit
which seems to be the other key concern. So if this works for you then I
am happy with it.
> 
> As translation team becomes more and more popular,
> there would be more people (or company) who want to contribute their 
> translations in po files. I want to create a formal process for those
> who want to contribute translations in batch.
I do not think we want to encourage this behavior at all. We (OpenStack)
provide tooling to perform the translations upstream. This is where
translations should happen instead of happening at many different
downstreams who then have to figure out how to merge the translations
when they are pushed in batches. We should just be translating as we go
and working together.

If there are deficiencies in the tooling that prevent this from
happening we should work to fix them not work around around them by
suggesting different downstreams should solve these problems
individually on their own.

All that said, you can edit translations locally in po files and push
them up with the zanata cli tool right? If translators prefer that
workflow to the web UI they can do that today unless I misunderstand
something.
> So I would like to collect your feedback to option #3.
> 
> @ Team coordinators, let me know what do you want to check in pre-review, 
> and whether using Zanata version
> could support you well.
> @ Clark and Elizabeth, let me know if you are OK with it from the 
> infrastructure perspective.
> @ Carlos, maybe you could give us good suggestion as a Zanata expert.
> 
> Thank you all.
> 
> Best regards
> Ying Chun Guo (Daisy)