Updates on I18n SIG: Translation Sync Issues and Launchpad Bug Notifications
Hi all, I’d like to share updates on two key I18n SIG topics: 1. Horizon translation sync issues The sync mechanism between Git project repositories and translation data on Zanata, based on old infrastructure, is causing some challenges for Horizon project [1]. Currently, I am handling the sync manually, as shown here [2]. While progress on the Weblate migration is slow, I hope this temporary solution helps for now. 2. Launchpad bug alarms on mailing list I apologize for the excessive Launchpad bug notifications on the mailing list. I discovered that modifying the I18n mailing list settings could prevent these alarms, and I have temporarily applied the changes. [Next Steps] Looking ahead, here are some proposed actions to improve the situation: a. Recent translation bug reports have been overly granular. Moving forward, I recommend managing translation bugs with a more project-wide approach. b. Many bug reports lack clarity regarding which projects they pertain to. I plan to mark such unclear reports as “Invalid.” c. I hope contributors will gain a better understanding of the overall translation process soon. d. I am exploring whether it’s possible to introduce bug submission templates or improve the guidelines for reporting translation bugs [3]. I will revert the mailing list settings after these improvements are in place. Thank you for your patience and understanding. Thank you all, /Ian [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [2] https://review.opendev.org/c/openstack/horizon/+/939607 [3] https://docs.openstack.org/i18n/latest/bug_report.html
Hi Ian, Long time no see. I just noticed this email when looking thru openstack emails. While I am not active in OpenStack now, there are several points I can help based on my past knowledge.
I apologize for the excessive Launchpad bug notifications on the mailing list. I discovered that modifying the I18n mailing list settings could prevent these alarms, and I have temporarily applied the changes.
The reason of notifications to this list is because “OpenStack I18n Core Team” team (on launchpad) subscribes openstack-i18n launchpad project [4] and the email address of the i18n core team (on launchpad) is configured to this mailing list [5]. I am not sure why this kind of configuration was done, but it is totally different from other project team in OpenStack. I believe “OpenStack I18n Core Team” launchpad team should unsubscribe openstack-i18n bug. Ian, you are the only active administrator of this launchpad team, so perhaps only you can unsubscribe bug notifications (at [4]). After tha you do not need the special mailing list configuration to block bug mails.
[Next Steps]
Looking ahead, here are some proposed actions to improve the situation:
a. Recent translation bug reports have been overly granular. Moving forward, I recommend managing translation bugs with a more project-wide approach. b. Many bug reports lack clarity regarding which projects they pertain to. I plan to mark such unclear reports as “Invalid.” c. I hope contributors will gain a better understanding of the overall translation process soon. d. I am exploring whether it’s possible to introduce bug submission templates or improve the guidelines for reporting translation bugs [3].
Generally sounds good. Regarding the bug report template, you can find it at "Configure Bugs" menu [6] of the bug page. The template and the guideline there have not been updated for long. We can adjust them to match the current situation. [4] https://bugs.launchpad.net/openstack-i18n/+subscriptions [5] https://launchpad.net/~openstack-i18n-core [6] https://bugs.launchpad.net/openstack-i18n/+configure-bugtracker Thanks, Akihiro Motoki (amotoki) On Sun, Jan 26, 2025 at 3:28 PM Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Hi all,
I’d like to share updates on two key I18n SIG topics:
1. Horizon translation sync issues
The sync mechanism between Git project repositories and translation data on Zanata, based on old infrastructure, is causing some challenges for Horizon project [1].
Currently, I am handling the sync manually, as shown here [2].
While progress on the Weblate migration is slow, I hope this temporary solution helps for now.
2. Launchpad bug alarms on mailing list
I apologize for the excessive Launchpad bug notifications on the mailing list. I discovered that modifying the I18n mailing list settings could prevent these alarms, and I have temporarily applied the changes.
[Next Steps]
Looking ahead, here are some proposed actions to improve the situation:
a. Recent translation bug reports have been overly granular. Moving forward, I recommend managing translation bugs with a more project-wide approach. b. Many bug reports lack clarity regarding which projects they pertain to. I plan to mark such unclear reports as “Invalid.” c. I hope contributors will gain a better understanding of the overall translation process soon. d. I am exploring whether it’s possible to introduce bug submission templates or improve the guidelines for reporting translation bugs [3].
I will revert the mailing list settings after these improvements are in place.
Thank you for your patience and understanding.
Thank you all,
/Ian
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [2] https://review.opendev.org/c/openstack/horizon/+/939607 [3] https://docs.openstack.org/i18n/latest/bug_report.html _______________________________________________ OpenStack-I18n mailing list -- openstack-i18n@lists.openstack.org To unsubscribe send an email to openstack-i18n-leave@lists.openstack.org
participants (2)
-
Akihiro Motoki
-
Ian Y. Choi