Open Stack

Hi Daisy and the team,

2015-12-17 19:35 GMT+09:00 Ying Chun Guo <guoyingc at cn.ibm.com>:
> Hi, Akihiro
>
> Please let me know your comments to https://review.openstack.org/258924

I commented your above review.

I proposed a counter proposal https://review.openstack.org/261767.
This is just an idea. I am open to the input.

Comments inline below.

> Answers to your question:
>
> 1. Context
>
> The current solution in my patch could not satisfy this requirement about
> context.
> If we want to put context to glossary, we need to develop our own extension
> of sphinx-build.
> How do you think the priority to support context ?

IMHO supporting contexts is important to make discussion on glossary productive.
As you can see in Japanese glossary on OpenStack wiki [1], I believe
that discussion contexts
are important for further discussions and it also helps new
contributors understand the background.

In my proposal https://review.openstack.org/261767,
we maintain all contexts in YAML glossary files.

> 2. Process
>
> If people want to change the glossary, e.g. add, update, change the
> comments, add coments
> following process is designed.
>
> a> the requestor submits a patch to i18n repo
> b> core team approve the patch
> c> the auto uploading process is triggered. terminology.pot is uploaded to
> Zanata for translation
> d> translators finish translation
> e> Zanata admin manually patch terminology.pot and its translation po files,
> and upload to Zanata

IMO the glossary needs to be reviewed more carefully compared to
regular translations.
In regular translations, all translated strings are imported, but for
glossary it is better that
only reviewed strings are imported. Another choice is to use gerrit
for the glossary review.
My proposal https://review.openstack.org/261767 implements the latter option.

Thought?

Thanks,
Akihiro

>
> Best regards
> Ying Chun Guo (Daisy)
>
>
> Akihiro Motoki <amotoki at gmail.com> wrote on 2015/12/02 02:29:44:
>
>> From: Akihiro Motoki <amotoki at gmail.com>
>> To: "openstack-i18n at lists.openstack.org"
>> <Openstack-i18n at lists.openstack.org>
>> Date: 2015/12/02 02:32
>> Subject: [Openstack-i18n] How do we manage glossary?
>
>>
>> Hi team,
>>
>> Recently we added the glossary to the i18n repo [1].
>> I wonder how we can manage the glossary and am sending this mail.
>> The glossary can be referred to in Zanata, so it would be useful.
>>
>> Mainly I have two questions.
>>
>> The first point is what is the expected process to manage the glossary.
>> How can we update the glossary?
>> When is it uploaded to Zanata for translations?
>>
>> The second point is how we can have the context.
>> I think the second point is also important.
>> Each entry in our glossary has some background, for example
>> why we reach the current consensus.
>> This kind of context is important to discuss for further improvements.
>>
>> I updated the glossary for Japanese translation last week
>> and I added various description about backgrounds of the glossary.
>> I feel it is important to keep the context.
>> How can we manage the context?
>>
>> I don't have a good idea now.
>> I would like to raise these questions for broader discussion.
>>
>> Thanks,
>> Akihiro
>>
>> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n
>>
>> _______________________________________________
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>>
>