- OpenStack-I18n - lists.openstack.org

Re: [OpenStack-I18n] [i18n][tc] The future of I18n
by Ian Y. Choi 06 Sep '19

06 Sep '19

Hello, First of all, thanks a lot for raising into this thread. Please see inline: Jonathan Proulx wrote on 9/6/2019 10:37 PM: > I'd be lead by how the people working in the space want to organize, but... > > Seems like SIG would be a good fit as I18N is extremely cross project, > presumably everything has text output even if it's just logging and > not enduser focused. > > my 2¢ > -Jon > > On Fri, Sep 06, 2019 at 11:36:38AM +0200, Thierry Carrez wrote: > :Hi! > : > :The I18n project team had no PTL candidates for Ussuri, so the TC needs to > :decide what to do with it. It just happens that Ian kindly volunteered to be > :an election official, and therefore could not technically run for I18n PTL. > :So if Ian is still up for taking it, we could just go and appoint him. I love I18n, and I could not imagine OpenStack world without I18n - I would like to take I18n PTL role for Ussuari cycle if there is no objection. > : > :That said, I18n evolved a lot, to the point where it might fit the SIG > :profile better than the project team profile. > : > :As a reminder, project teams are responsible for producing > :OpenStack-the-software, and since they are all integral in the production of > :the software that we want to release on a time-based schedule, they come with > :a number of mandatory tasks (like designating a PTL every 6 months). > : > :SIGs (special interest groups) are OpenStack teams that work on a mission > :that is not directly producing a piece of the OpenStack release. SIG members > :are bound by their mission, rather than by a specific OpenStack release > :deliverable. There is no mandatory task, as it is OK if the group goes > :dormant for a while. > : > :The I18n team regroups translators, with an interest of making OpenStack (in > :general, not just the software) more accessible to non-English speakers. They > :currently try to translate the OpenStack user survey, the Horizon dashboard > :messages, and key documentation. > : > :It could still continue as a project team (since it still produces Horizon > :translations), but I'd argue that at this point it is not what defines them. > :The fact that they are translators is what defines them, which IMHO makes > :them fit the SIG profile better than the project team profile. They can > :totally continue proposing translation files for Horizon as a I18n SIG, so > :there would be no technical difference. Just less mandatory tasks for the > :team. > : > :Thoughts ? First of all, I would like to more clarify the scope of which artifacts I18n team deals with. Regarding translation contributions to upstream official projects, I18n team started with 1) user-facing strings (e.g., dashboards), 2) non-user-facing strings (e.g., log messages) and 3) openstack-manuals documentation. The second one is not active after no real support for maintaining to translate log messages, and the third one is now expanded to some of project documents which there are the demand of translation like openstack-helm, openstack-ansible, and horizon ([2] includes the list of Docs team repos, project documents for operators and part of SIG). Based on the background, I can say that I18n team currently involves in total 19 dashboard projects [3], and 6 official project document repositories. Although the number of translated words is not larger than previous cycles [4], the amount of parts related with upstream official projects seems not to be small. IMHO, since it seems that I18n team's release activities [5] are rather stable, from the perspective, I think staying I18n team as SIG makes sense, but please kindly consider the followings: - Translators who have contributed translations to official OpenStack projects are currendly regarded as ATC and APC of the I18n project. It would be great if OpenStack TC and official project teams regard those translation contribution as ATC and APC of corresponding official projects, if I18n team stays as SIG. - Zanata (translation platform, instance: translate.openstack.org) open source is not maintained anymore. I18n team wanted to change translation platform to something other than Zanata [6] but current I18n team members don't have enough technical bandwidth to do that (FYI: Fedora team just started to migrate from Zanata to Weblate [7] - not easy stuff and non-small budget were agreed to use by Council). Regardless of I18n team's status as an official team or SIG, such migration to a new translation platform indeed needs the support from the current governance (TC, UC, Foundation, Board of Directors, ...). - Another my brief understanding on the difference between as an official team and as SIG from the perspective of Four Opens is that SIGs and working groups seems that they have some flexibility using non-opensource tools for communication. For example, me, as PTL currently encourage all the translators to come to the tools official teams use such as IRC, mailing lists, and Launchpad (note: I18n team has not migrated from Launchpad to Storyboard) - I like to use them and I strongly believe that using such tools can assure that the team is following Four Opens well. But sometimes I encounter some reality - local language teams prefer to use their preferred communication protocols. I might need to think more how I18n team as SIG communicates well with members, but I think the team members might want to more find out how to better communicate with language teams (e.g., using Hangout, Slack, and so on from the feedback) , and try to use better communication tools which might be comfortable to translators who have little background on development. Note that I have not discussed the details with team members - I am still open with my thoughts, would like to more listen to opinions from the team members, and originally wanted to expand the discussion with such perspective during upcoming PTG in Shanghai with more Chinese translators. And dear OpenStackers including I18n team members & translators: please kindly share your sincere thoughts. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-dev/2017-March/114191.html [2] https://translate.openstack.org/version-group/view/doc-resources/projects [3] https://translate.openstack.org/version-group/view/Train-dashboard-translat… [4] http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007989.html [5] https://docs.openstack.org/i18n/latest/release_management.html [6] https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-pla… [7] https://fedoraproject.org/wiki/L10N_Move_to_Weblate > : > :-- > :Thierry Carrez (ttx) > :

1 0

[I18n] PTL Non-Candidacy
by Ian Y. Choi 02 Sep '19

02 Sep '19

Hello I18n team, As announced by [1], now is U-cycle (Ussuri) PTL nomination period, and only less than 2 days are left from now. I will not run for I18n PTL for U-cycle because I am now serving as an PTL/TC election official and the role conflicts with running for PTL [2]. I ran for election official to better understand OpenStack ecosystem and more interact with community members, not to leave from I18n team. I will still stay around I18n team, but it would be so great if someone runs for I18n PTL on upcoming cycle. Also, I shared the current status of I18n team on last July [3]. If you have not read this, please read for more information. Note that I will be at Shanghai Summit + PTG for more I18n sessions as an official team succeeding from my current PTL activities - please prioritize to participate in upcoming Summit + PTG with any kind of ways - both online and offline participation should be definitely fine. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008679.h… [2] https://wiki.openstack.org/wiki/Election_Officiating_Guidelines [3] http://lists.openstack.org/pipermail/openstack-i18n/2019-July/003439.html

1 0

[I18n] project team status update regarding internationalization/translation as July 2019
by Ian Y. Choi 30 Jul '19

30 Jul '19

Hello all, I would like to share current project team status for better visibility into I18n team members, copying to openstack-discuss and user-committee thread: 1. Translation and team effort status There are still lots of translation contribution as you see through Stackalytics: https://www.stackalytics.com/?metric=translations&release=train . The number of translated words is not larger than the previous cycle, but I estimate that it will be similar or a little bit less than the previous cycle since I18n usually contributes translations a lot especially during Soft & Hard StringFreeze periods. Note that I18n team currently sets higher priority on OpenStack user survey translation and project document translations. Such priorities information can be found on Zanata dashboard: https://translate.openstack.org/ . Other progress such as migrating Zanata into other translation platform seems slow - me and Frank are planning to have a virtual sprint. 2. Shanghai Summit & PTG preparation : Frank submitted his presentation including me and Hoarce (China team). Let's wait for final approval on presentation submission. : There should be PTG at Shanghai - please add your name and detail thinking to Etherpad mentioned in http://lists.openstack.org/pipermail/openstack-i18n/2019-July/003436.html . I strongly think to more encourage participation since I expect more participation especially from Chinese translators & contributors. 3. Updating ATC & AUC : Frank previously submitted extra-ATC for Stein through https://review.opendev.org/#/c/633398/ , and this time I would like to submit the stat calculation from 2019-01-26 to 2019-07-25. : All contributors who had commits on openstack/i18n repository will be automatically regarded as Active Technical Contributors [1], and I18n team would like to nominate all translators who contributed translations on OpenStack official repositories (https://governance.openstack.org/tc/reference/projects/ ) >= 300 words as extra-ATCs assuming that their Zanata e-mail IDs are registered as Foundation members. : All translators who contributed >=300 word tranlations to the following projects will be nominated as Active User Contributors [2] assuming that their Zanata e-mail IDs are registered as Foundation members: "contributor-guide, edge-computing, leveraging-containers-openstack, openstack-user-survey, operations-guide". This is new nomination after the decision during Stein PTG with User Committee: Please see [3] and [4] if you would like to follow-up with more information. I will do this nomination for ATC & AUC as PTL just after July 25, although the due of extra ATC is Aug 26-30 [5] since I synced with Foundation that the price of Summit ticket will increase around Aug 7 : processing within the due will be fine, also I set period exactly for six months. 4. Team status : Although I regularly be online during I18n (+Docs) IRC team meetings, I couldn't find enough quorum, and I couldn't proceed more deep conversation with language teams (usually no reply from my e-mails unfortunately). : Current I18n team core members seem busy but when I communicate with them, all they are still very supportive to I18n team projects. I really appreciate their kind help. : Also, I find that some translators are very active comparing to some inactive language coordinators. In this case, would it be a good idea to nominate them as language coordinators? Please share your thoughts. : However, if such lack of team member conversations keep going, then I18n team might decide during upcoming PTG to make translation from an official team status into Special Interest Group [6]. This would mean that there will be no official PTL election and there will be no extra-ATC nomination, although I need to more figure out in details in future. With many thanks, /Ian [1] https://docs.openstack.org/i18n/latest/official_translator.html#atc-status-… [2]https://governance.openstack.org/uc/reference/charter.html#active-user-co… [3] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003316.h… [4] http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-10-01-18.02.html [5] https://releases.openstack.org/train/schedule.html [6] https://governance.openstack.org/sigs/

2 2

operations guide import fails for id language due to invalid character
by Andreas Jaeger 24 Jul '19

24 Jul '19

There's an error because a character 08 is in the translated text, see: http://logs.openstack.org/periodic/opendev.org/openstack/operations-guide/m… Could anybody look into this and delete the offending string, please? Andreas -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

[I18n][ptg] Shanghai PTG/Forum Attendance
by Ian Y. Choi 11 Jul '19

11 Jul '19

Hello, Like other official teams, I18n team has been also asked to get an idea of how many people are planning to attend the PTG and/or Forum. I have created an Etherpad to start collecting topics as well as a list of people who are planning to attend [1], and if you think you may be in Shanghai or are in a timezone that can participate remotely, please update the Etherpad. Note that this upcoming PTG/Forum is very Asia-timezone friendly - I highly encourage people in Asia countries (including China, surely) to participate offline or remotely. Thanks! With many thanks, /Ian [1] https://etherpad.openstack.org/p/i18n-shanghai-ptg-planning

1 0

Stackalytics for Translations broken
by Robert Simai 28 Jun '19

28 Jun '19

Hi, I was just checking Stackalytics and found there are no results when I change the Metric to "Translations" while that used to work reliably in the past. Opened a bug https://bugs.launchpad.net/stackalytics/+bug/1834434 in case anyone has an idea. -- Thanks, Robert

3 3

OpenStack User Survey translation in 2019 - Fwd: It’s OpenStack User Survey Time!
by Ian Y. Choi 12 Jun '19

12 Jun '19

Hello I18n team members, OpenStack user survey translation is available through [1], like previous two years. Translation is synced into [2] regularly (once everyday) but please don't hesitate to share through here if there are some translation or sync issues. With many thanks, /Ian [1] https://translate.openstack.org/iteration/view/openstack-user-survey/openst… [2] https://www.openstack.org/user-survey/survey-2019 -------- Original Message -------- Subject: It’s OpenStack User Survey Time! Date: Fri, 17 May 2019 14:29:36 -0500 From: Matt Van Winkle <mvanwinkle(a)salesforce.com> To: openstack-discuss(a)lists.openstack.org Hi everyone, If you operate OpenStack, it’s time to participate in the annual OpenStack User Survey <https://www.openstack.org/user-survey>. This is your opportunity to provide direct feedback to the OpenStack community, so we can better understand your environment and needs. We send all anonymous feedback directly to the project teams who work to improve the software and documentation. The survey will take less than 20 minutes. All participants who complete the OpenStack deployment survey will receive AUC status and discounted registration to the Shanghai Summit. Please let me or any members of the User Committee know if you have any questions. Cheers, VW -- Matt Van Winkle Senior Manager, Software Engineering | Salesforce

2 1

Stopping Queens stable version translation
by Ian Y. Choi 04 Jun '19

04 Jun '19

Hello team, Just I would like to share with team members that I18n team will stop translation for Queens stable version due to no translation activities, low demand, and low bandwidth on such a stable branch. I wanna more share that: - If some translators find bugs on latest two releases (Stein, Rocky), please share via this mailing list or Launchpad. - Such decision will start after [1] is merged. - Still other bug fixes would be fine for extended maintence purpose [2]. If someone finds significant translation bugs on such old versions, please share via this mailing list so that we can discuss how to deal with. With many thanks, /Ian [1] https://review.opendev.org/#/c/656047/ [2] https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.…

2 3

[dev][horizon][docs][i18n]Horizon Taiwanese locale issue
by Vadym Markov 29 May '19

29 May '19

Hi, There is an issue with Taiwanese locale at least in Horizon. It would be good to get a feedback from i18n team according to OpenStack docs too. Speaking about Horizon, Chinese locales were renamed in Django 1.7 [1]. Zh-cn became zh-Hans, and zh-tw became zh-Hant. Old names were marked as deprecated and finally removed in Django 1.11. Current supported Django versions are 1.11 and 2.0 [2] It is not an issue for Chinese because django locale middleware does silent fallback from zh-cn to zh-Hans. But for Taiwanese it treats zh-tw as some unknown variant of zh-* and also does fallback to default zh-cn, which is wrong. Reported bug: https://bugs.launchpad.net/horizon/+bug/1830886 Proposed solution is to migrate to new locale names everywhere in Horizon. Here are proposed steps to fix this issue: 1. Zanata jobs reconfiguration 2. Django-related backend stuff. Biggest, but easiest part because it is well documented 3. AngularJS. Quite old version is used, so we can hit some well forgotten issues. Also, testing is complicated. 4. Horizon.js components. It is the smallest part Other question will be thorougful testing of the bugfix. [1] https://docs.djangoproject.com/en/dev/releases/1.7/#language-codes-zh-cn-zh… [2] https://docs.openstack.org/horizon/latest/install/system-requirements.html

3 2

ID translation broken for openstack-ansible
by Andreas Jaeger 27 May '19

27 May '19

See https://review.opendev.org/#/c/658731/ It's now the third day with fixing one issue, import, next issue shows up - could somebody else take over and fix everything, please? Failing line: http://logs.openstack.org/31/658731/7/check/openstack-tox-docs/d442a7a/job-… Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 10