- OpenStack-I18n - lists.openstack.org

[Bug 2092541] [NEW] Mistype in RU - RBAC Policies
by Ivan Anfimov 26 Dec '24

26 Dec '24

Public bug reported: OpenStack 2024.2 Dalmatian En: RBAC Policies Ru: Политики RABC Correct to: Политики RBAC ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/2092541 Title: Mistype in RU - RBAC Policies Status in openstack i18n: New Bug description: OpenStack 2024.2 Dalmatian En: RBAC Policies Ru: Политики RABC Correct to: Политики RBAC To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/2092541/+subscriptions

1 0

[i18n][ptg] I18n SIG vPTG summary
by Ian Y. Choi 30 Oct '24

30 Oct '24

Hi all, I would like to share with you a summary of the recent discussions held during the 2025.1 Epoxy PTG regarding the Internationalization (I18n) Special Interest Group (SIG). During the period, the I18n SIG explored approaches to improve multilingual support, discussing Weblate migration, AI-based translation implementation, sustainable documentation translation strategies, and addressing current translation tool issues. Special thank you to TC and Nova team for elaborate discussions. Please refer to the below brief summary from Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-i18n . 1. Overall Translation Status discussion - Clarifying that StringFreezes applies to Horizon and dashboard plugin projects [1] - Confusion exists about the current state of translations. Horizon translations were added months ago but not proposed by the tooling. : No translation proposals on the master branch after April 19, 2024. [2] : Horizon removed Python 3.8 support [3], while translation jobs depend on Ubuntu Bionic. 2. Towards sustainable Documentation Translation - Discussion on utilizing AI machine translation: : Proposal to use Weblate's machine translation feature. : Consideration of open-source tools like LibreTranslate [4]. : Concerns raised about legal issues. - Emphasis on the necessity of human reviewers: : Suggestion to create a 'language-moderator' group in Gerrit? : Need to add voting labels for translation patches. 3. Weblate Migration - Ongoing migration of translated project files from Zanata to Weblate. - Integration with Zuul is the second-phase goal. - Difficulties encountered due to API usage issues. 4. Weblate Issues - There was an authentication issue with Weblate and openinfraid (note: but it appears to be resolved now. Thank you @rosmaita!) 5. AI Translation Approach - Step-by-step ways a. Model selection b. Community review of the model c. Model utilization d. Model + RAG (Reviewed/Translated OpenStack documents, glossary) utilization - Plan to conduct PoC with Nova RST documents. 6. Action items - To start a 3-month PoC to test AI translation with Nova RST files (ianychoi) - Zuul investigation for Weblate migration (seongsoocho) - Horizon Zuul job issue check (discussion with other teams) Thank you all, /Ian [1] https://review.opendev.org/c/openstack/releases/+/930929 [2] https://review.opendev.org/q/owner:proposal-bot+project:openstack/horizon+b… [3] https://docs.openstack.org/releasenotes/horizon/2024.2.html#upgrade-notes [4] https://github.com/LibreTranslate/LibreTranslate

1 0

[i18n] i18n SIG PTG Schedule & Key Topics for Discussion
by Seongsoo Cho 25 Oct '24

25 Oct '24

Hi i18n SIG Team I’m pleased to announce the i18n SIG schedule for the upcoming PTG. Here are the details: Dates: • October 23rd: 13:00 - 15:00 UTC • October 24th: 13:00 - 15:00 UTC We encourage you to check the meeting minutes and contribute to the discussion by accessing the following Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-i18n Key Discussion Topics: 1. Weblate Migration: We will discuss the progress and steps needed for migrating to Weblate. 2. Enhancing Translation Engagement: We’ll focus on strategies to improve the engagement and translation rates for OpenStack projects. Potential ideas, such as incorporating LLM (Large Language Models), will also be explored. We look forward to your participation and contributions to these discussions. Best Regards Seongsoo -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

2 2

[Bug 1536226] Re: Not all .po files compiled
by Cyril Roelandt 09 Oct '24

09 Oct '24

The Glance patch was abandoned 5 years ago as it was deemed unnecessary. Similar code merged in other projects has also been removed since. I'm going to close this bug, feel free to reopen if needed. ** Changed in: glance Status: In Progress => Invalid -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: Invalid Status in OpenStack Heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: Won't Fix Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

Canceling today i18n meeting
by Ian Y. Choi 05 Jun '24

05 Jun '24

Hello all, Due to unavailability of both chairs, today i18n meeting is canceled. Note that previous meeting details and logs (2024) are on [1] and [2]. Thank you all, /Ian [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting [2] https://meetings.opendev.org/meetings/openstack_i18n_meeting/2024/

1 0

[I18n][PTG] 2024.2 Dalmatian PTG - I18n SIG summary
by Ian Y. Choi 25 Apr '24

25 Apr '24

Hi all, As I18n SIG lead, I would like to share with you a summary of the recent discussions held during the 2024.2 Dalmatian PTG regarding the Internationalization (I18n) Special Interest Group (SIG). Firstly, I would like to express my sincere appreciation to the entire community for their commitment to make OpenStack more internationalized. The efforts put forth in translating and making OpenStack accessible globally are truly commendable, thanks to the contributions of numerous individuals, although we are under unprecedented situations and even Zanata will sunset soon [1]. During the PTG, I18n SIG covered several important topics with active and invaluable contributors including Seongsoo (a special thanks for his leadership both I18n team and within the Korea User group): 1. Progress on open reviews for I18n: We discussed pending items in the OpenStack/I18n repository and the status of various reviews. 2. Discussion on the OpenStack/I18n repository structure: This included plans to embrace the use of Weblate - wlc library and add tox environment and corresponding requirements.txt. 3. Pilot work progress on governance translation support: A demonstration was provided on setting up a new project with API and CLI. 4. Feasibility discussion on migrating from translate.openstack.org earlier than [1]. Deliberation on target languages and next steps for user survey translation. 5. User survey translation discussion: Target languages and next steps were deliberated upon. In sum, I18n will continue our effort to finalize the migration from Zanata to Weblate to emphasize the importance of I18n as a fundamental component for global OpenStack accessibility. Thank you for your continuation of the I18n SIG. If you have any questions or would like further information on any of the discussed topics, please don't hesitate to reach out. Best regards, /Ian [1] https://lists.osci.io/hyperkitty/list/zanata-sunset@lists.osci.io/thread/6F… [2] I18n PTG Etherpad: https://etherpad.opendev.org/p/apr2024-ptg-i18n [3] I18n PTG Team Photo 1: https://1drv.ms/i/s!AgSCQctkWshsgb8ZvM-l7Ol1UOxNjA?e=5tdLpb [3] I18n PTG Team Photo 2: https://cdn.discordapp.com/attachments/1192271703057911888/1228373792162840…

1 0

[i18n][PTG] I18n SIG 2024.2 (Dalmatian) PTG Planning
by Ian Y. Choi 11 Apr '24

11 Apr '24

Hi, PTG is happening this week. @seongsoo and I have blocked time slots (Thu 21-22 UTC & Fri 14-16 UTC). Anyone can check via https://ptg.opendev.org/ptg.html and please let me know if more discussion is needed during PTG. Those are topics what I am thinking currently but it is open - feel free to suggest any topic to be discussed: - Moving forward on open reviews for i18n: at least, there are several pending items on openstack/i18n repo - openstack/i18n repository structure discussion to embrace the use of weblate - wlc library on tools/weblate and others including the addition of tox environment and corresponding requirements.txt - Pilot work progress discussion on governance translation support on weblate platform - Overall feasible migration plan discussion to sunset translate.openstack.org earlier than zanata.translate.org Discussions will be shared via Etherpad: https://etherpad.opendev.org/p/apr2024-ptg-i18n . Lastly, please don't forget to register if you have forgotten: https://ptg2024.openinfra.dev/ :) Looking forward to a productive PTG with I18n. Thank you, /Ian

2 1

Survey to schedule i18n SIG 2024.04 PTG
by Seongsoo Cho 18 Mar '24

18 Mar '24

Hi i18n SIG I create a survey to schedule i18n SIG 2024.04 PTG. Please let me know, what time and day works best for you. survey: https://framadate.org/tY49ETqtFD9R4LPt Best Regards Seongsoo -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[I18n] IRC Meeting date change on the next week: March 14th, 13:30 UTC
by Ian Y. Choi 07 Mar '24

07 Mar '24

Hello all, Due to schedule changes from active participants, the next I18n meeting will happen on March 14th, 13:30 UTC on #openstack-i18n IRC channel. Note that previous meeting details and logs (2024) are on [1] and [2].. Thank you all, /Ian [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting [2] https://meetings.opendev.org/meetings/openstack_i18n_meeting/2024/

1 0

[StringFreeze] Soft period was over - Plz contribute translation for the release!
by Ian Y. Choi 07 Mar '24

07 Mar '24

Dear language coordinators & translators! Only a few weeks left before the official 2024.1 Caracal release [1] and I would like to share that the last week was the Soft StringFreeze period. Language teams need to focus on Horizon and Horizon-related projects before all translated strings will be packaged for upcoming release. For more details on how the I18n team is doing with releases (especially Horizon & plugin projects), please see [2]. If you have questions, feel free to ask through openstack-i18n at lists.openstack.org mailing list or ask I18n members on IRC #openstack-i18n channel. Thank you all for your contribution! /Ian [1] https://releases.openstack.org/caracal/schedule.html [2] https://docs.openstack.org/i18n/latest/release_management.html On Fri, Mar 1, 2024 at 11:27 PM Herve Beraud <hberaud(a)redhat.com> wrote: > > Development Focus > ----------------- > > We just passed feature freeze! Until release branches are cut, you > should stop accepting featureful changes to deliverables following the > cycle-with-rc release model, or to libraries. Exceptions should be > discussed on separate threads on the mailing-list, and feature freeze > exceptions approved by the team's PTL. > > Focus should be on finding and fixing release-critical bugs, so that > release candidates and final versions of the 2024.1/Caracal deliverables can be > proposed, well ahead of the final 2024.1/Caracal release date. > > General Information > ------------------- > > We are still finishing up processing a few release requests, but the > 2024.1/Caracal release requirements are now frozen. If new library releases are > needed to fix release-critical bugs in 2024.1/Caracal, you must request a > Requirements Freeze Exception (RFE) from the requirements team before we > can do a new release to avoid having something released in 2024.1/Caracal that > is not actually usable. This is done by posting to the openstack-discuss > mailing list with a subject line similar to: > > [$PROJECT][requirements] RFE requested for $PROJECT_LIB > > Include justification/reasoning for why a RFE is needed for this lib. > If/when the requirements team OKs the post-freeze update, we can then > process a new release. > > A soft String freeze is now in effect, in order to let the I18N team do the > translation work in good conditions. In Horizon and the various dashboard > plugins, you should stop accepting changes that modify user-visible > strings. Exceptions should be discussed on the mailing-list. By > March 25, 2024 this will become a hard string freeze, with no changes > in user-visible strings allowed. > > Actions > ------- > > stable/2024.1 branches should be created soon for all not-already-branched > libraries. You should expect 2-3 changes to be proposed for each: a > .gitreview update, a reno update (skipped for projects not using reno), > and a tox.ini constraints URL update. Please review those in priority > so that the branch can be functional ASAP. > > The Prelude section of reno release notes is rendered as the top level > overview for the release. Any important overall messaging for 2024.1/Caracal > changes should be added there to make sure the consumers of your release > notes see them. > > Upcoming Deadlines & Dates > -------------------------- > > Cycle Highlights Due: March 7th, 2024 (R-4 week) > RC1 deadline: week of March 11, 2024 (R-3 week) > Final RC deadline: week of March 25, 2024 (R-1 week) > Final 2024.1/Caracal release: April 3, 2024 > Dalmatian PTG: April 8-12, 2024 > > -- > Hervé Beraud > Senior Software Engineer at Red Hat > irc: hberaud > https://github.com/4383/ >

1 0