Hi Daisy, Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable. Just a example,I do not check all projects. * ironic * ceilometer Regards, KATO Tomoyuki
On 11/01/2015 06:01 AM, KATO Tomoyuki wrote:
Hi Daisy,
Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable.
Just a example,I do not check all projects.
* ironic * ceilometer
Other projects should be in the same position. Did you decide in Tokyo on the "New proposal" https://wiki.openstack.org/wiki/Translations/Infrastructure#New_proposal ? That one basically says that we keep both branches open for half a year as you noticed. We can refine the proposal... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 11/01/2015 06:01 AM, KATO Tomoyuki wrote:
Hi Daisy,
Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable.
Just a example,I do not check all projects.
* ironic * ceilometer
Other projects should be in the same position.
Did you decide in Tokyo on the "New proposal" https://wiki.openstack.org/wiki/Translations/Infrastructure#New_proposal ? That one basically says that we keep both branches open for half a year as you noticed.
We can refine the proposal...
I might misunderstand something on the sessions at Tokyo Summit... Waiting Daisy's response. By the way, I will propose that we keep stable branches open for openstack-manuals to translate and publish install guides and configuration guide. Basically, we need translate install guides at stable branches after cutting stable branch. As you know, install guide at master branch is used for next release. This needs remove the unnecessary pot files so that translators do not translate the unused resources such as user guides. So I will create a blueprint to openstack-manuals. There may be other solutions. Thanks, KATO Tomoyuki
On 11/01/2015 08:21 AM, KATO Tomoyuki wrote:
On 11/01/2015 06:01 AM, KATO Tomoyuki wrote:
Hi Daisy,
Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable.
Just a example,I do not check all projects.
* ironic * ceilometer
Other projects should be in the same position.
Did you decide in Tokyo on the "New proposal" https://wiki.openstack.org/wiki/Translations/Infrastructure#New_proposal ? That one basically says that we keep both branches open for half a year as you noticed.
We can refine the proposal...
I might misunderstand something on the sessions at Tokyo Summit... Waiting Daisy's response.
Sure - please let's write up what we do in such a way that we're all on the same page.
By the way, I will propose that we keep stable branches open for openstack-manuals to translate and publish install guides and configuration guide. Basically, we need translate install guides at stable branches after cutting stable branch.
Yes, as agreed.
As you know, install guide at master branch is used for next release. This needs remove the unnecessary pot files so that translators do not translate the unused resources such as user guides. So I will create a blueprint to openstack-manuals. There may be other solutions.
Just adding "skip" to doc-tools-check-languages.conf should do the trick - please test this. Yes, we should document here as well was we do and a blueprint is a good idea. thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
2015-11-01 17:35 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 11/01/2015 08:21 AM, KATO Tomoyuki wrote:
On 11/01/2015 06:01 AM, KATO Tomoyuki wrote:
Hi Daisy,
Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable.
Just a example,I do not check all projects.
* ironic * ceilometer
Other projects should be in the same position.
Did you decide in Tokyo on the "New proposal" https://wiki.openstack.org/wiki/Translations/Infrastructure#New_proposal ? That one basically says that we keep both branches open for half a year as you noticed.
We can refine the proposal...
I might misunderstand something on the sessions at Tokyo Summit... Waiting Daisy's response.
Sure - please let's write up what we do in such a way that we're all on the same page.
+1
By the way, I will propose that we keep stable branches open for openstack-manuals to translate and publish install guides and configuration guide. Basically, we need translate install guides at stable branches after cutting stable branch.
Yes, as agreed.
openstack-manuals and other projects have a bit different situations and it is better to discuss them separately. openstack-manuals has a lot of documentations (i.e. translation resources) and only some of them need stable branches. One idea is to allow to mark read-only per resource in Zanata, As discussed in Tokyo, it is a possible feature enhancement in Zanata side, but it is not supported at the moment.
As you know, install guide at master branch is used for next release. This needs remove the unnecessary pot files so that translators do not translate the unused resources such as user guides. So I will create a blueprint to openstack-manuals. There may be other solutions.
Just adding "skip" to doc-tools-check-languages.conf should do the trick - please test this.
Yes, we should document here as well was we do and a blueprint is a good idea.
Honestly I am not sure which approach works for us. We need to test.
thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 11/01/2015 12:05 PM, Akihiro Motoki wrote:
[...] Honestly I am not sure which approach works for us. We need to test.
I agree - that's one reason for me to write it up so that everybody understands what we do and therefore knows what exactly to change. We can iterate and fine-tune - or throw away and do something completely different next time ;) Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
I think the current situation you see is same as expected and what we discussed in our Monday meetup in Tokyo. In my understanding, the master version is marked as read-only during final translations for a release. After the release the master version is open for translation again. By doing so, while translators can work on the master version, they can still maintain the stable release. What is a problem you think? Akihiro 2015-11-01 14:01 GMT+09:00 KATO Tomoyuki <tomo@dream.daynight.jp>:
Hi Daisy,
Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable.
Just a example,I do not check all projects.
* ironic * ceilometer
Regards, KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (3)
-
Akihiro Motoki
-
Andreas Jaeger
-
KATO Tomoyuki