We had some IRC discussion today about how to handle the "other" projects with importing and here's a proposal based on discussions with Clark, Lyz, Steve, Daisy and Thierry. I'd like to prepare everything for this tomorrow if possible, so please speak up if you have questions or concerns, Andreas Challenge: We have translations for some projects like keystone that are not on the liberty branch. Master is already open for Mitaka. Proposal: Handle all projects that have currently translations of main files (so, not only LOG files) and liberty branches the same - like we do with horizon and nova. Details: This means, the following projects will get liberty branches: List of projects that branch with translations: openstack/ceilometer openstack/cinder openstack/designate openstack/designate-dashboard openstack/django_openstack_auth openstack/glance openstack/horizon openstack/keystone openstack/neutron openstack/nova openstack/swift openstack/zaqar List of projects branching later: openstack/openstack-manuals - to translate Install Guide The following projects will not be translated: List of projects that branch without translations in git : openstack/aodh openstack/ironic-inspector openstack/magnum openstack/magnum-ui openstack/manila openstack/sahara openstack/searchlight List of projects that branch with only LOG translations in git: openstack/barbican openstack/glance_store openstack/heat openstack/ironic openstack/trove List of projects not branching: openstack/api-site openstack/ha-guide openstack/operations-guide openstack/oslo.cache openstack/oslo.concurrency openstack/oslo.db openstack/oslo.i18n openstack/oslo.log openstack/oslo.messaging openstack/oslo.middleware openstack/oslo.policy openstack/oslo.reports openstack/oslo.service openstack/oslo.utils openstack/oslo.versionedobjects openstack/oslo.vmware openstack/python-magnumclient openstack/python-openstackclient openstack/security-doc Process 1. Before RC1 is cut, translators work with master version. 2. When stable branch is cut, branches get created in Zanata as well. Syncing will get enabled for them. 3. Translators focus on translation of stable branch. 4. Once translators are finished with translations, a copy of new translations from stable branch to master is done in Zanata . 5. Open master version to accept translations. Note: Around RC1 time, a patch to cleanup "old" translations gets proposed to both stable and master to remove any translations in git that are less than 50 % translated (we normally only delete less than 20 % to avoid to frequent deletion). What do we want to see in Liberty release: * Updated translations of files that are sufficiently translate (> 75 %) * Updated po source file that reflect state of repository * No empty/mainly untranslated language files (< 50 %) 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 09/24/2015 07:41 PM, Andreas Jaeger wrote:
We had some IRC discussion today about how to handle the "other" projects with importing and here's a proposal based on discussions with Clark, Lyz, Steve, Daisy and Thierry.
I'd like to prepare everything for this tomorrow if possible, so please speak up if you have questions or concerns,
Andreas
Challenge:
We have translations for some projects like keystone that are not on the liberty branch. Master is already open for Mitaka.
Proposal:
Handle all projects that have currently translations of main files (so, not only LOG files) and liberty branches the same - like we do with horizon and nova.
Details:
This means, the following projects will get liberty branches:
List of projects that branch with translations: openstack/ceilometer openstack/cinder openstack/designate openstack/designate-dashboard openstack/django_openstack_auth openstack/glance openstack/horizon openstack/keystone openstack/neutron openstack/nova openstack/swift openstack/zaqar
List of projects branching later: openstack/openstack-manuals - to translate Install Guide
The following projects will not be translated:
List of projects that branch without translations in git : openstack/aodh openstack/ironic-inspector openstack/magnum openstack/magnum-ui openstack/manila openstack/sahara openstack/searchlight
List of projects that branch with only LOG translations in git: openstack/barbican openstack/glance_store openstack/heat openstack/ironic openstack/trove
List of projects not branching: openstack/api-site openstack/ha-guide openstack/operations-guide openstack/oslo.cache openstack/oslo.concurrency openstack/oslo.db openstack/oslo.i18n openstack/oslo.log openstack/oslo.messaging openstack/oslo.middleware openstack/oslo.policy openstack/oslo.reports openstack/oslo.service openstack/oslo.utils openstack/oslo.versionedobjects openstack/oslo.vmware openstack/python-magnumclient openstack/python-openstackclient openstack/security-doc
Process
1. Before RC1 is cut, translators work with master version. 2. When stable branch is cut, branches get created in Zanata as well. Syncing will get enabled for them. 3. Translators focus on translation of stable branch. 4. Once translators are finished with translations, a copy of new translations from stable branch to master is done in Zanata . 5. Open master version to accept translations.
Note: Around RC1 time, a patch to cleanup "old" translations gets proposed to both stable and master to remove any translations in git that are less than 50 % translated (we normally only delete less than 20 % to avoid to frequent deletion).
66 % as last time.
What do we want to see in Liberty release: * Updated translations of files that are sufficiently translate (> 75 %) * Updated po source file that reflect state of repository * No empty/mainly untranslated language files (< 50 %)
This should be 66 % as last 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
Thank you Andreas for the detail information. I have several questions: 1. I created Nova liberty version in Zanata only. Do the liberty versions of these "other projects" be created manually or created automatically ? When shall the versions be created ? 2. There are three types in the list of projects not be translated. Do you mean not to translate them in Liberty ? What are the definition of three types ? olso.i18n is in the list of projects not branching, yet I see it has the liberty branch in git. aodh is in the list of projects that branch without translations in git, yet I see there are three language translations in its locale folder. 3. Do you plan to clean up translations of all projects? Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 2015/09/25 01:41:18:
From: Andreas Jaeger <aj@suse.com> To: "openstack-i18n@lists.openstack.org" <openstack- i18n@lists.openstack.org>, Thierry Carrez <thierry@openstack.org>, Doug Hellmann <doug@doughellmann.com> Date: 2015/09/25 01:42 Subject: [Openstack-i18n] Handling of translations for Liberty
We had some IRC discussion today about how to handle the "other" projects with importing and here's a proposal based on discussions with Clark, Lyz, Steve, Daisy and Thierry.
I'd like to prepare everything for this tomorrow if possible, so please speak up if you have questions or concerns,
Andreas
Challenge:
We have translations for some projects like keystone that are not on the liberty branch. Master is already open for Mitaka.
Proposal:
Handle all projects that have currently translations of main files (so, not only LOG files) and liberty branches the same - like we do with horizon and nova.
Details:
This means, the following projects will get liberty branches:
List of projects that branch with translations: openstack/ceilometer openstack/cinder openstack/designate openstack/designate-dashboard openstack/django_openstack_auth openstack/glance openstack/horizon openstack/keystone openstack/neutron openstack/nova openstack/swift openstack/zaqar
List of projects branching later: openstack/openstack-manuals - to translate Install Guide
The following projects will not be translated:
List of projects that branch without translations in git : openstack/aodh openstack/ironic-inspector openstack/magnum openstack/magnum-ui openstack/manila openstack/sahara openstack/searchlight
List of projects that branch with only LOG translations in git: openstack/barbican openstack/glance_store openstack/heat openstack/ironic openstack/trove
List of projects not branching: openstack/api-site openstack/ha-guide openstack/operations-guide openstack/oslo.cache openstack/oslo.concurrency openstack/oslo.db openstack/oslo.i18n openstack/oslo.log openstack/oslo.messaging openstack/oslo.middleware openstack/oslo.policy openstack/oslo.reports openstack/oslo.service openstack/oslo.utils openstack/oslo.versionedobjects openstack/oslo.vmware openstack/python-magnumclient openstack/python-openstackclient openstack/security-doc
Process
1. Before RC1 is cut, translators work with master version. 2. When stable branch is cut, branches get created in Zanata as well. Syncing will get enabled for them. 3. Translators focus on translation of stable branch. 4. Once translators are finished with translations, a copy of new translations from stable branch to master is done in Zanata . 5. Open master version to accept translations.
Note: Around RC1 time, a patch to cleanup "old" translations gets proposed to both stable and master to remove any translations in git that are less than 50 % translated (we normally only delete less than 20 % to avoid to frequent deletion).
What do we want to see in Liberty release: * Updated translations of files that are sufficiently translate (> 75 %) * Updated po source file that reflect state of repository * No empty/mainly untranslated language files (< 50 %)
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 09/25/2015 05:35 AM, Ying Chun Guo wrote:
Thank you Andreas for the detail information. I have several questions:
1. I created Nova liberty version in Zanata only. Do the liberty versions of these "other projects" be created manually or created automatically ? When shall the versions be created ?
We should be able to create the versions itself per script (one-time run) - now.
2. There are three types in the list of projects not be translated. Do you mean not to translate them in Liberty ?
Yes.
What are the definition of three types ?
See the titles I gave below.
olso.i18n is in the list of projects not branching, yet I see it has the liberty branch in git.
I wouldn't handle libraries for now, just put them in with the others.
aodh is in the list of projects that branch without translations in git, yet I see there are three language translations in its locale folder.
aodh was error on my side.
3. Do you plan to clean up translations of all projects?
Yes, for all server projects. Andreas
Best regards Ying Chun Guo (Daisy)
Andreas Jaeger <aj@suse.com> wrote on 2015/09/25 01:41:18:
From: Andreas Jaeger <aj@suse.com> To: "openstack-i18n@lists.openstack.org" <openstack- i18n@lists.openstack.org>, Thierry Carrez <thierry@openstack.org>, Doug Hellmann <doug@doughellmann.com> Date: 2015/09/25 01:42 Subject: [Openstack-i18n] Handling of translations for Liberty
We had some IRC discussion today about how to handle the "other" projects with importing and here's a proposal based on discussions with Clark, Lyz, Steve, Daisy and Thierry.
I'd like to prepare everything for this tomorrow if possible, so please speak up if you have questions or concerns,
Andreas
Challenge:
We have translations for some projects like keystone that are not on the liberty branch. Master is already open for Mitaka.
Proposal:
Handle all projects that have currently translations of main files (so, not only LOG files) and liberty branches the same - like we do with horizon and nova.
Details:
This means, the following projects will get liberty branches:
List of projects that branch with translations: openstack/ceilometer openstack/cinder openstack/designate openstack/designate-dashboard openstack/django_openstack_auth openstack/glance openstack/horizon openstack/keystone openstack/neutron openstack/nova openstack/swift openstack/zaqar
List of projects branching later: openstack/openstack-manuals - to translate Install Guide
The following projects will not be translated:
List of projects that branch without translations in git : openstack/aodh openstack/ironic-inspector openstack/magnum openstack/magnum-ui openstack/manila openstack/sahara openstack/searchlight
List of projects that branch with only LOG translations in git: openstack/barbican openstack/glance_store openstack/heat openstack/ironic openstack/trove
List of projects not branching: openstack/api-site openstack/ha-guide openstack/operations-guide openstack/oslo.cache openstack/oslo.concurrency openstack/oslo.db openstack/oslo.i18n openstack/oslo.log openstack/oslo.messaging openstack/oslo.middleware openstack/oslo.policy openstack/oslo.reports openstack/oslo.service openstack/oslo.utils openstack/oslo.versionedobjects openstack/oslo.vmware openstack/python-magnumclient openstack/python-openstackclient openstack/security-doc
Process
1. Before RC1 is cut, translators work with master version. 2. When stable branch is cut, branches get created in Zanata as well. Syncing will get enabled for them. 3. Translators focus on translation of stable branch. 4. Once translators are finished with translations, a copy of new translations from stable branch to master is done in Zanata . 5. Open master version to accept translations.
Note: Around RC1 time, a patch to cleanup "old" translations gets proposed to both stable and master to remove any translations in git that are less than 50 % translated (we normally only delete less than 20 % to avoid to frequent deletion).
What do we want to see in Liberty release: * Updated translations of files that are sufficiently translate (> 75 %) * Updated po source file that reflect state of repository * No empty/mainly untranslated language files (< 50 %)
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
-- 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 discussed further with Daisy, and we cleaned up some details. I put my email now up on the wiki as reference: https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling Daisy and myself have created stable branches for those repositories that have already branched, 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 2015-09-25 15:21, Andreas Jaeger wrote:
I discussed further with Daisy, and we cleaned up some details.
I put my email now up on the wiki as reference:
https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling
Daisy and myself have created stable branches for those repositories that have already branched,
The Japanese team has translated ironic to 80 % (message count), so I'm adding ironic to the list of translated repositories now, 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 2015-09-29 08:45, Andreas Jaeger wrote:
On 2015-09-25 15:21, Andreas Jaeger wrote:
I discussed further with Daisy, and we cleaned up some details.
I put my email now up on the wiki as reference:
https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling
Daisy and myself have created stable branches for those repositories that have already branched,
The Japanese team has translated ironic to 80 % (message count), so I'm adding ironic to the list of translated repositories now,
And the German team heat, so enabling that one now as well - in infra and on translate.openstack.org, 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
Andreas, I am not sure it is worth adding more translations for Liberty. Most of the progress in Japanese translation happens due to the accidental merge of IBM translation. I don't think Japanese team has no enough to review translations other than Horizon until Liberty release. We are reviewing most of IBM translations but it is still under way and the progress is about 50-60%. 2015-09-29 15:45 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2015-09-25 15:21, Andreas Jaeger wrote:
I discussed further with Daisy, and we cleaned up some details.
I put my email now up on the wiki as reference:
https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling
Daisy and myself have created stable branches for those repositories that have already branched,
The Japanese team has translated ironic to 80 % (message count), so I'm adding ironic to the list of translated repositories now,
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 9/29/2015 at 09:02, in message <CALhU9tnfG4BXt5DNJuLoVFfMDuHEC1erFsc=m7-_4WKdCXc=yw@mail.gmail.com>, Akihiro Motoki <amotoki@gmail.com> wrote: Andreas,
I am not sure it is worth adding more translations for Liberty.
Most of the progress in Japanese translation happens due to the accidental merge of IBM translation. I don't think Japanese team has no enough to review translations other than Horizon until Liberty release. We are reviewing most of IBM translations but it is still under way and the progress is about 50-60%.
OK, I'll remove the proposed change for ironic and update everything else again, 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 9/29/2015 at 09:02, in message <CALhU9tnfG4BXt5DNJuLoVFfMDuHEC1erFsc=m7-_4WKdCXc=yw@mail.gmail.com>, Akihiro Motoki <amotoki@gmail.com> wrote: Andreas,
I am not sure it is worth adding more translations for Liberty.
Most of the progress in Japanese translation happens due to the accidental merge of IBM translation. I don't think Japanese team has no enough to review translations other than Horizon until Liberty release. We are reviewing most of IBM translations but it is still under way and the progress is about 50-60%.
WE use message count, not word count - for ironic it's 80 %. Ok, I'll remove ironic again, 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
Hi Akihiro, Andreas,
The Japanese team has translated ironic to 80 % (message count), so I'm adding ironic to the list of translated repositories now,
Most of the progress in Japanese translation happens due to the accidental merge of IBM translation. I don't think Japanese team has no enough to review translations other than Horizon until Liberty release. We are reviewing most of IBM translations but it is still under way and the progress is about 50-60%.
Regarding ironic Japanese, I reviewed and modified IBM translation, and translated the remaining strings. It is not an accident :) # Other projects are under review in my understand.
Akihiro-san
How about import ironic Japanese? Any objection? Cloud you review ironic translation if you have time?
WE use message count, not word count
agree. Thanks, KATO Tomoyuki
Thanks for clarifying the situation, Tomo. I am fine with merging it. Apart from the progress, I was a bit surprised why Ironic was handled specially. In Japanese, we are making good progress on other projects. For example, keystone and ceilometer have good progress and the first round of keystone review has been done. What is the criteria of this decision. Thanks, Akihiro 2015年9月29日火曜日、KATO Tomoyuki<tomo@dream.daynight.jp>さんは書きました:
Hi Akihiro, Andreas,
The Japanese team has translated ironic to 80 % (message count), so I'm adding ironic to the list of translated repositories now,
Most of the progress in Japanese translation happens due to the accidental merge of IBM translation. I don't think Japanese team has no enough to review translations other than Horizon until Liberty release. We are reviewing most of IBM translations but it is still under way and the progress is about 50-60%.
Regarding ironic Japanese, I reviewed and modified IBM translation, and translated the remaining strings. It is not an accident :) # Other projects are under review in my understand.
Akihiro-san
How about import ironic Japanese? Any objection?
Cloud you review ironic translation if you have time?
WE use message count, not word count
agree.
Thanks, KATO Tomoyuki
On 2015-09-29 16:25, Akihiro Motoki wrote:
Thanks for clarifying the situation, Tomo. I am fine with merging it.
Will do now.
Apart from the progress, I was a bit surprised why Ironic was handled specially.
On what side special? When I made the list, it was made on projects that were translated already good enough. Ironic was not in the list. Please review the wiki link and check yourself the git repository for translation files. Now I moved ironic up in the list...
In Japanese, we are making good progress on other projects. For example, keystone and ceilometer have good progress and the first round of keystone review has been done. What is the criteria of this decision.
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
Hi Andreas, 2015-09-30 15:11 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2015-09-29 16:25, Akihiro Motoki wrote:
Thanks for clarifying the situation, Tomo. I am fine with merging it.
Will do now.
Apart from the progress, I was a bit surprised why Ironic was handled
specially.
On what side special? When I made the list, it was made on projects that were translated already good enough. Ironic was not in the list. Please review the wiki link and check yourself the git repository for translation files.
Now I moved ironic up in the list...
Thanks. now I got the full context. I wan't check the wiki Translations/Infrastructure#Release_handling and I thought the master branch is marked as read-only for all projects with stable/liberty branch (it is because I focused on translation reviews in my spare time in these days) but it turns out my misunderstanding. Thanks, Akihiro
In Japanese, we are making good progress on other projects.
For example, keystone and ceilometer have good progress and the first round of keystone review has been done. What is the criteria of this decision.
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
participants (4)
-
Akihiro Motoki
-
Andreas Jaeger
-
KATO Tomoyuki
-
Ying Chun Guo