- OpenStack-I18n - lists.openstack.org

[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

[Bug 1794401] Re: Suspend Instance and Shelve instance have same name in French
by Ian Y. Choi 22 Feb '24

22 Feb '24

** Changed in: openstack-i18n Importance: Undecided => High ** Changed in: openstack-i18n Status: Fix Committed => Fix Released -- 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/1794401 Title: Suspend Instance and Shelve instance have same name in French Status in openstack i18n: Fix Released Bug description: In the french version for Horizon, "Suspend Instance" and "Shelve instance" are both called "Suspendre l'instance" To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1794401/+subscriptions

1 0

[I18n] SIG Team meeting starting Jan 17 13:30 UTC #openstack-i18n
by Ian Y. Choi 17 Jan '24

17 Jan '24

I would like to share that below is the I18n SIG meeting cadence and the first meeting will start at Jan 17 13:30 UTC in #openstack-i18n IRC channel. You can download the ICS file through [1]. Note that previous meeting information is described on [2]. Before updating wiki and corresponding pages, please let me or another meeting chair (IRC: seongsoocho) share any agenda if you want to discuss I18n things. - time: '1330' duration: 45 day: Wednesday irc: openstack-i18n frequency: biweekly-odd - time: '2315' duration: 45 day: Wednesday irc: openstack-i18n frequency: biweekly-even Thank you, /Ian [1] https://meetings.opendev.org/#I18N_Team_Meeting [2] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

1 0

Re: [i18n][infra] Future of translate.openstack.org
by Seongsoo Cho 21 Dec '23

21 Dec '23

Hi Tony i18n SIG still uses translate.openstack.org as a translation platform for the OpenInfra Project. We are working in progress to migrate to weblate translation platform. Please keep it there until the migration is complete. Best regards Seongsoo Cho On Fri, Dec 8, 2023 at 1:02 AM Tony Breeds <tony(a)bakeyournoodle.com> wrote: > > Hello all, > The infra team is in the process of replacing older bionic servers > with jammy based ones. We're nearing the end of that process and one > of the remaining servers is translate.openstack.org. This server is > primarily running zanata, which if I understand correctly, is no > longer in use by the i18n team. > > I understand that there is a new platform that requies some tooling, > if a dedicated server is needed for that we can spin up a newer jammy > based server. > > So can we just retire this translate.openstack.org? > > Yours Tony. -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

3 2

[i18n] New users activation
by Dmitriy Rabotyagov 21 Dec '23

21 Dec '23

Hey, We recently got a couple of inquiries in openstack-ansible IRC that folks would love to contribute to translations of Horizon to languages like Arabic, but they can get pass account activation. So I was wondering if account activation still happens and what is the process for that to get new translators onboarded? Thanks in advance.

2 1

Discuss i18n IRC Meeting date
by Seongsoo Cho 15 Nov '23

15 Nov '23

Hi i18n Team. It's time to update our regular meeting date. This is the current meeting date in the doc, but actually, there are no meeting. [1] Every odd week: 16:00 UTC, Thursday Every even week: 07:00 UTC, Thursday So I want to set a new meeting date. For now, I'd like to have a monthly IRC meeting. Please let me know what days and times work best for you. Survey form: https://forms.gle/SZUFmwJS6QTs4akNA Best Regards Seongsoo [1] https://docs.openstack.org/i18n/latest/i18n_team_meeting.html -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[Bug 2034921] [NEW] Migrating Userinfo & ZanataUtils to Weblate Version
by Nayeon Kim 25 Oct '23

25 Oct '23

Public bug reported: Creating bug to keep track of Zanata to Weblate migration. In specific, zanata_userinfo.py(https://opendev.org/openstack/i18n/src/branch/master/too… ZanataUtils.py(https://opendev.org/openstack/i18n/src/branch/master/tools/z… 's class is being used in userinfo.py file, so migrating ZanataUtils.py is also a must. However, it is used not only in i18n repo, but also in zuul jobs, so must focus on migrating the specific parts for the userinfo.py first. These changes are made as part of followed blueprint. https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation- platform ** Affects: openstack-i18n Importance: Undecided Status: New ** Description changed: Creating bug to keep track of Zanata to Weblate migration. In specific, zanata_userinfo.py(https://opendev.org/openstack/i18n/src/branch/master/too… - ZanataUtils.p(https://opendev.org/openstack/i18n/src/branch/master/tools/za…'s - class is being used in userinfo.py file, so migrating ZanataUtils.py is - also a must. However, it is used not only in i18n repo, but also in zuul - jobs, so must focus on migrating the specific parts for the userinfo.py - first. + ZanataUtils.py(https://opendev.org/openstack/i18n/src/branch/master/tools/z… + 's class is being used in userinfo.py file, so migrating ZanataUtils.py + is also a must. However, it is used not only in i18n repo, but also in + zuul jobs, so must focus on migrating the specific parts for the + userinfo.py first. These changes are made as part of followed blueprint. https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation- platform -- 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/2034921 Title: Migrating Userinfo & ZanataUtils to Weblate Version Status in openstack i18n: New Bug description: Creating bug to keep track of Zanata to Weblate migration. In specific, zanata_userinfo.py(https://opendev.org/openstack/i18n/src/branch/master/too… ZanataUtils.py(https://opendev.org/openstack/i18n/src/branch/master/tools/z… 's class is being used in userinfo.py file, so migrating ZanataUtils.py is also a must. However, it is used not only in i18n repo, but also in zuul jobs, so must focus on migrating the specific parts for the userinfo.py first. These changes are made as part of followed blueprint. https://blueprints.launchpad.net/openstack-i18n/+spec/renew- translation-platform To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/2034921/+subscriptions

2 1