Open Stack

Hi Daisy and all,

It may be off-topic already....

On Mon, Nov 4, 2013 at 2:38 AM, Ying Chun Guo <guoyingc at cn.ibm.com> wrote:
> How do you think using the same mechanism to track bugs as other projects
> (e.g. docs, infrastructure)?
> For example, bugs management in launchpad?

Perhaps your are talking about the following topic in my mail.

>> * Bug/Issue tracking
>>   * Discussion or Bug which is not specific to each translation
>> should be handled in broader scope.
>>     E.g., translation memory related, upstream bugs, ..... (I am not
>> sure these are good examples..)

In general, the same mechanism should work.
If a bug or topic is common to all languages it is very simple and the
same mechanism
should work. In many cases it is a bug of upstream projects (such as
openstack-manuals, horizon, ...).

What in my mind are for tracking topics rather than simple bugs.
It is the reason

The only difference is how to manage language-specific topics:
For example, during Japanese translations there are a glossary
discussion, wording policy
throughout a single translation and across translations.
It is better such topics are discussed in their native/local languages.
If we use a common platform for I18N, is it confortable if multiple
languages are used in a single bug system.
I believe it is not comfortable.
(For now, we Japanese team are using our own GitHub project and issue
tracking system
for this purpose.)

Regards,
Akihiro Motoki <amotoki at gmail.com>

> The question is: when finding bugs, do we fix bugs through translation UI or
> updating po files directly?
> If we choose the later one, I think launchpad can be used.
>
>
> Regards
> Ying Chun Guo (Daisy)
>
> Akihiro Motoki <amotoki at gmail.com> wrote on 2013/11/02 17:58:59:
>
>> Akihiro Motoki <amotoki at gmail.com>
>> 2013/11/02 17:58
>>
>> To
>>
>> "openstack-i18n at lists.openstack.org" <openstack-i18n at lists.openstack.org>,
>>
>> cc
>>
>> Subject
>>
>> Re: [Openstack-i18n] Collecting requirements to translation tools
>
>>
>> Hi,
>>
>> I believe the list is becoming a good share already.
>>
>> I would like to add
>>
>> * Good review interfaces and tracking status of comments.
>>   * We need a discussion for better translation. The string seems
>> wrong, I am sure what it means,.....
>>   * When the translation is updated, we need to confirm it is
>> reasonably improved.
>>   * We need to track what are addressed and what are not.
>> * Bug/Issue tracking
>>   * Discussion or Bug which is not specific to each translation
>> should be handled in broader scope.
>>     E.g., translation memory related, upstream bugs, ..... (I am not
>> sure these are good examples..)
>>
>> Thanks,
>> Akihiro
>>
>>
>
>> On Thu, Oct 17, 2013 at 6:12 PM, Ying Chun Guo <guoyingc at cn.ibm.com>
>> wrote:
>> Hi, I18n team
>>
>> One year ago, when the community was making the decision to use
>> Transifex as the translation management tool,
>> a table was made to compare several different tools:
>> https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-
>> ErDUdFgzT3VNVXQxd095bFgzODRmajJDeVE&usp=drive_web#gid=0
>>
>> Now since Transifex began to close its source code, we will do
>> another round of tool selection
>> to find the translation management tool for Openstack translation.
>>
>> We will start from requirements collection. Here I listed some.
>> (Some are copied from the old table. The last three items are newly added.
>> )
>>
>> * Cross-project translation teams
>> * Cross-project translation memory
>> * Good in-browser translation interface
>> * Good in-browser review interface
>> * Easy import/export of translation files
>> * Support for all common translation formats
>> * Git/GitHub Integration
>> * Hooks for CI infrastructure
>> * Management workflows that fit OpenStack process
>> * Self-hosted
>> * Proven success with large projects
>> * API to gather statistics about translators
>> * Easily see the translating context, i.g. the paragraph or section
>> that contains the translation string.
>> * Cross-project glossary and dictionary
>>
>> Please feel free to present your requirements to the translation
>> management tool.
>> If you know some good candidate tools, please speak out too.
>> Let's find out the most appropriate tool together, and build a
>> "wonderful" working environment for ourselves.
>>
>> Regards
>> Ying Chun Guo (Daisy)
>>
>> _______________________________________________
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
>> _______________________________________________
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n