- OpenStack-I18n - lists.openstack.org

[i18n][i18n-ar][horizon] Errors with Arabic translations
by François Magimel 06 Dec '18

06 Dec '18

Hello ! Yesterday and this morning, the "propose-translation-update" job for Horizon failed due to some errors in Arabic translations : - [0] was due to an extra "\n" - [1] was due to missing translations [2] (msgstr 3 to 5 are mandatory if there are at least one non empty msgstr). After being added to the Arabic team, I removed the extra "\n" and marked translation [2] as fuzzy. I'm waiting for the friday build but it should be ok :). I hope it will help to fix similar failures in the future. Cheers, François [0] http://logs.openstack.org/periodic/git.openstack.org/openstack/horizon/mast… [1] http://logs.openstack.org/periodic/git.openstack.org/openstack/horizon/mast… [2] https://translate.openstack.org/webtrans/translate?project=horizon&iteratio…

2 1

[Bug 1794401] Re: Suspend Instance and Shelve instance have same name in French
by Akihiro Motoki 28 Nov '18

28 Nov '18

translation should be fixed in the translation platform (translate.openstack.org).[1] Horizon is not related. Removing horizon from the affected project. [1] https://docs.openstack.org/i18n/latest/ ** No longer affects: horizon -- 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: New 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

[Bug 1794401] Re: Suspend Instance and Shelve instance have same name in French
by Akihiro Motoki 28 Nov '18

28 Nov '18

This looks like a translation bug. Forwarding to openstack-i18n. ** Also 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/1794401 Title: Suspend Instance and Shelve instance have same name in French Status in openstack i18n: New 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

[docs][i18n] Team meeting proposal
by Frank Kloeker 19 Nov '18

19 Nov '18

Hello, in the last weeks we had some informal discussions about combined team meeting for documentation and translation team. There should be overlapping topics and other project teams or operator would have the same contact persons on the same place. We also save resources on meeting chairs. Here are my proposal: 1) Meeting room #openstack-meeting 2) Switch back from (informal) Office Hour to (formal) Team Meeting. Topics for upcoming meetings will be collected on a Wiki page. If there are no topic we would skip the meeting. So often we recorded empty sessions in the past. 3) Meeting time is Thursday 07:00 UTC (odd week), 16:00 UTC (even week) 4) First part (30 min) I18n topics, second part documentation topics, meetingbot will recorded two sessions, so it's easier to read specific topics later. 5) Rotating meeting chairs between the two teams. This should renew a little bit the conversation and we are more flexible and visible on the move. kind regards Frank (PTL I18n)

4 3

[docs][i18n] Team dinner Berlin Summit
by Frank Kloeker 16 Nov '18

16 Nov '18

Hello, thanks to all participants of the OpenStack Summit in Berlin. Hopefully you have an event with enough success and fun so far. I really appreciate that you are here in Berlin. To round up I would like to have the Docs- and I18n team for a team dinner on Thursday, after the Onboarding Session. I reserved a table for 18:30 on Restaurant Scheune (https://www.google.com/maps/reserve/v/dine/m/DH2FjXOtEXw) We can start on the CityCube possibly on foot. I want to skip the I18n Office Hour on Thursday. kind regards Frank menu: http://www.scheune-restaurant.de/

2 4

Sharing upstream contribution mentoring result with Korea user group
by Ian Y. Choi 30 Oct '18

30 Oct '18

Hello, I got involved organizing & mentoring Korean people for OpenStack upstream contribution for about last two months, and would like to share with community members. Total nine mentees had started to learn OpenStack, contributed, and finally survived as volunteers for 1) developing OpenStack mobile app for better mobile user interfaces and experiences (inspired from https://github.com/stackerz/app which worked on Juno release), and 2) translating OpenStack official project artifacts including documents, and Container Whitepaper ( https://www.openstack.org/containers/leveraging-containers-and-openstack/ ). Korea user group organizers (Seongsoo Cho, Taehee Jang, Hocheol Shin, Sungjin Kang, and Andrew Yongjoon Kong) all helped to organize total 8 offline meetups + one mini-hackathon and mentored to attendees. The followings are brief summary: - "OpenStack Controller" Android app is available on Play Store : https://play.google.com/store/apps/details?id=openstack.contributhon.com.op… (GitHub: https://github.com/kosslab-kr/openstack-controller ) - Most high-priority projects (although it is not during string freeze period) and documents are 100% translated into Korean: Horizon, OpenStack-Helm, I18n Guide, and Container Whitepaper. - Total 18,695 words were translated into Korean by four contributors (confirmed through Zanata API: https://translate.openstack.org/rest/stats/user/[Zanata ID]/2018-08-16..2018-10-25 ): +------------+---------------+-----------------+ | Zanata ID | Name | Number of words | +------------+---------------+-----------------+ | ardentpark | Soonyeul Park | 12517 | +------------+---------------+-----------------+ | bnitech | Dongbim Im | 693 | +------------+---------------+-----------------+ | csucom | Sungwook Choi | 4397 | +------------+---------------+-----------------+ | jaeho93 | Jaeho Cho | 1088 | +------------+---------------+-----------------+ - The list of projects translated into Korean are described as: +-------------------------------------+-----------------+ | Project | Number of words | +-------------------------------------+-----------------+ | api-site | 20 | +-------------------------------------+-----------------+ | cinder | 405 | +-------------------------------------+-----------------+ | designate-dashboard | 4 | +-------------------------------------+-----------------+ | horizon | 3226 | +-------------------------------------+-----------------+ | i18n | 434 | +-------------------------------------+-----------------+ | ironic | 4 | +-------------------------------------+-----------------+ | Leveraging Containers and OpenStack | 5480 | +-------------------------------------+-----------------+ | neutron-lbaas-dashboard | 5 | +-------------------------------------+-----------------+ | openstack-helm | 8835 | +-------------------------------------+-----------------+ | trove-dashboard | 89 | +-------------------------------------+-----------------+ | zun-ui | 193 | +-------------------------------------+-----------------+ I would like to really appreciate all co-mentors and participants on such a big event for promoting OpenStack contribution. The venue and food were supported by Korea Open Source Software Development Center ( https://kosslab.kr/ ). With many thanks, /Ian

3 2

[Proposal] I18n Contributor Guide doc folder to follow documentation structure
by Ian Y. Choi 30 Oct '18

30 Oct '18

Hello team, I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is based on rst files in http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but the folder structure is different from other project documents after project document migration [1]. How about moving rst files except index.rst into "contributor" folder like [2] to follow project document structure? With many thanks, /Ian [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migra… [2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/

3 4

[I18n] No Office Hour this week
by Frank Kloeker 02 Oct '18

02 Oct '18

Hello, due the national holiday in Germany tomorrow and the long weekend after that, there will be no I18n Office Hour this week. Next session will be held on 2018/10/11 13:00 UTC [1]. kind regards Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

1 0

Re: [OpenStack-I18n] [openstack-dev] [docs][i18n][ptg] Stein PTG Summary
by Ian Y. Choi 24 Sep '18

24 Sep '18

Thanks a lot for nice summary on Docs part especially! I would like to add an additional summary with more context from I18n perspective. Note: I mainly participated in Docs/I18n discussion only on Monday & Tuesday (not available during Wed - Fri due to conflicts with other work in my country), and my summary would be different from current I18n PTL if he have parcipated in Stein PTG, but I would like to summarize as I18n ex-PTL (Ocata, Pike) and as one of active partcipants in Docs/I18n discussion. Documentation & I18n teams started to have collaborative discussions from Pike PTG. Following with Queens & Rocky cycle, I am so happy that Documentation & I18n teams had tight collaboration again at Stein PTG for horizontal discussion with sharing issues and tight collaboration. More details for I18n issues are available at the bottom part ("i18n Topics") in: https://etherpad.openstack.org/p/docs-i18n-ptg-stein PROJECT DOCUMENTATION TRANSLATION SUPPORT This year, I18n team actively started to support project documentation translation [1] and there had progress on defining documentation translation targets, generatepot infra jobs, and translation sync on from project repositories to Zanata for translation sources & from Zanata to project repositories for translated strings. [2] and [3] are parts of work I18n team did on previous cycle, and the final part would be how to support translated documentation publication aligned with Documentation team, since PDF support implementation is also related with how to publish PDF files for project repositories. Although there were so nice discussion during last Vancouver Summit [4], more generic idea on infra side how to better support translated documentation & PDF builds and translation would be needed after some changes on Project Testing Interface which is used for project documentation builds [5]. [6] is a nice summary from Doug (really appreciated!) for the direction and plans on PDF and translation builds by making use of openstack-tox-docs job [7], and I18n team would like to continue to work with Documentation and Infrastructure teams on actual implementation suring Stein cycle. USER SURVEY, TRANSLATING WHITEPAPERS, AND RECOGNITION ON TRANSLATORS With nice collaboration between Foundation and I18n team, I18n team started to translate OpenStack user survey [8] after initial discussion on Pike PTG and, edge computing whitepaper [9], and container whitepaer [10] into multiple languages with many language coordinators and translators. Those translation effort might be different from Active Technical Contributor (ATC) recognition which translators also got for OpenStack project translation and techical documentation translation [11]. Some translators shared that they would be interested in translating technical documents but not interested in OpenStack user survey and other non-technical documents. I thought that it might be due to different governance (Foundation-led & official projects with technical committee might be different), and Active User Contributor (AUC) [12] recognition might be a good idea. Although I could not discuss in details with User Committee members during PTG, Foundation agreed that AUC recognition for such translators would be a good idea and Melvin, one of user committee agreed with the idea during a very short conversation. In my opinion, it would take some time for more discussion and agreement on detail criteria (e.g., which number of words might be good aligning with current AUC recognition criteria), User Committee, and Foundation), but let's try to move forward on this :) Also, documentation on detail steps and activities with user survey on further years and more on whitepapers would be important, so I18n team will more document how I18n team members do action with steps like [13]. And some translators shared concerns what there is no I18n in OpenStack project navigator and map. It would be also related with recognition on what translators contributed. Foundation explained that it might be the intention of the purpose of each artifact (e.g., OpenStack were designed to show OpenStack components and how those components interact each other with technical perspective), and Foundation shared that Foundation would do best to aggregate scattered definitions (e.g., [14], [15], and somewhere more) for consistency, and find a nice place for Docs, i18n, Congress, etc... on the Software/Project Navigator. TRANSLATING CONTRIBUTOR GUIDE WITH FIRST CONTACT SIG The detail summary is in [16]. To summarize, - I shared I18n process to First Contact SIG members. Participants acknowledged that setting *translation period* would be needed but starting from initial translation process would be a good idea since it is not translated yet - Participants think that user groups would be interested in translating contributor guide. - Me will setup translation sync and publication on contributor guide and Kendall Nelson would kindly help explain the background of adding contributor guide for translator target. I18N-ING STORYBOARD [17] Although I18n team now uses Launchpad [18] for task management, I think there are mix on multiple language issues on "bugs" section, which prevents from maintance by language coordinators. After discussion on I18n mailing list [19], I thought that it would be very grat if Storyboard is internationalized so that I18n team can migrate from Launchpad to Storyboard and more global contributors access to Storyboard with their native language. One issue regarding I18n-ing Storyboard was that story description for most projects needs to be written in English, but I18n-ing Storyboard might mislead contributors to write description in non-English. Participants thought that adding a warning message on posting pages (e.g., posting a Story) would solve this issue. Participants shared current implementation technologies used in Storyboard and other dashboard projects such as Horizon and TripleO UI. Brainstorming and making use of I18n-ing libraries on Storyboard is an action item at current point. PROCESS ON OPENSTACK-HELM DOC FROM NON-ENGLISH TO ENGLISH* * I participated in a brief discussion with OpenStack-Helm team for documentation contribution from Korean to English. Current documentation and I18n process starts from English to multiple languages, but some active contributors in OpenStack-Helm team would like to contribute to Korean documentation first and translate from Korean into English. My suggestion is to keep current documentation and I18n process but add more additional steps before English rst-based documentation. For example, if OpenStack-Helm team cores agree to have *doc-ko_KR/source* folder, contributing Korean documentation is limited to the folder, Zanata helps to translate from Korean to English on the folder, translated po can make English rsts, and translated rst files are added to *doc/source* folder, there might be no affect on existing documentation & I18n process and Korean documentation contrubution and translation from Korean to English would be encouraged. OpenStack-Helm team agreed with this step, and I think this would be a good step for more Internationalization as a pilot project first but this can be extended to more projects in future. This is my summary on I18n issues discussed during Stein PTG. Thanks a lot for all members who involve and help Documentation and I18n. Although there were no discussion on setting translation plans and priorities, let's do that through [21] with Frank :) And finally, more pictures are available through [22] :) With many thanks, /Ian [1] https://blueprints.launchpad.net/openstack-i18n/+spec/project-doc-translati… [2] https://review.openstack.org/#/c/545377/ [3] https://review.openstack.org/#/c/581000/ [4] https://etherpad.openstack.org/p/YVR-docs-support-pdf-and-translation [5] https://review.openstack.org/#/c/580495/ [6] http://lists.openstack.org/pipermail/openstack-dev/2018-September/134609.ht… [7] https://docs.openstack.org/infra/openstack-zuul-jobs/jobs.html#job-openstac… [8] https://www.openstack.org/user-survey [9] https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-da… [10] https://www.openstack.org/containers/leveraging-containers-and-openstack/ [11] https://docs.openstack.org/i18n/latest/official_translator.html#atc-status-… [12] https://governance.openstack.org/uc/reference/charter.html#active-user-cont… [13] https://docs.openstack.org/i18n/latest/release_management.html [14] https://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project… [15] https://github.com/ttx/openstack-map/blob/master/openstack_components.yaml [16] https://etherpad.openstack.org/p/FC_SIG_ptg_stein [17] https://etherpad.openstack.org/p/sb-stein-ptg-planning [18] https://launchpad.net/openstack-i18n [19] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003307.h… [20] http://lists.openstack.org/pipermail/openstack/2018-September/046937.html [21] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003314.h… [22] https://www.dropbox.com/sh/2pmvfkstudih2wf/AAAG2c6C_OXorMRFH66AvboYa/Docs%2… Petr Kovar wrote on 9/20/2018 8:37 AM: > Hi all, > > Just wanted to share a summary of docs- and i18n-related meetings > and discussions we had in Denver last week during the Stein Project > Teams Gathering. > > The overall schedule for all our sessions with additional comments and > meeting minutes can be found here: > > https://etherpad.openstack.org/p/docs-i18n-ptg-stein > > Our obligatory team picture (with quite a few members missing) can be > found here (courtesy of Foundation folks): > > https://pmkovar.fedorapeople.org/DSC_4422.JPG > > To summarize what I found most important: > > OPS DOCS > > We met with the Ops community to discuss the future of Ops docs. The plan > is for the Ops group to take ownership of the operations-guide (done), > ha-guide (in progress), and the arch-design guide (to do). > > These three documents are being moved from openstack-manuals to their own > repos, owned by the newly formed Operations Documentation SIG. > > See also > https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018-operations-guide > for more notes. > > DOCS SITE & DESIGN > > We discussed improving the site navigation, guide summaries (particularly > install-guide), adding a new index page for project team contrib guides, and > more. We met with the Foundation staff to discuss the possibility of getting > assistance with site design work. > > We are also looking into accepting contributions from the Strategic Focus > Areas folks to make parts of the docs toolchain like openstackdocstheme more > easily reusable outside of the official OpenStack infrastructure. > > We got feedback on front page template for project team docs, with Ironic > being the pilot for us. > > We got input on restructuring and reworking specs site to make it easier > for users to understand that specs are not feature descriptions nor project > docs, and to make it more consistent in how the project teams publish their > specs. This will need to be further discussed with the folks owning the > specs site infra. > > Support status badges showing at the top of docs.o.o pages may not work well > for projects following the cycle-with-intermediary release model, such as > Swift. We need to rethink how we configure and present the badges. > > There are also some UX bugs present for the badges > (https://bugs.launchpad.net/openstack-doc-tools/+bug/1788389) > > TRANSLATIONS > > We met with the infra team to discuss progress on translating project team > docs and, related to that, PDF builds. > > With the Foundation staff, we discussed translating Edge and Container > whitepapers and related material. > > REFERENCE, REST API DOCS AND RELEASE NOTES > > With the QA team, we discussed the scope and purpose of the > /doc/source/reference documentation area in project docs. Because the > scope of /reference might be unclear and used inconsistently by project > teams, the suggestion is to continue with the original migration plan and > migrate REST API and possibly Release Notes under /doc/source, as described > in https://docs.openstack.org/doc-contrib-guide/project-guides.html. > > CONTRIBUTOR GUIDE > > The OpenStack Contributor Guide was discussed in a separate session, see > https://etherpad.openstack.org/p/FC_SIG_ptg_stein for notes. > > THAT'S IT? > > Please add to the list if I missed anything important, particularly for > i18n. > > Thank you to everybody who attended the sessions, and a special thanks goes > to all the PTG organizers! > > Cheers, > pk > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

2 2

[Bug 1792867] [NEW] 安装和配置计算节点 in Installation Guide
by wangjianqiang 17 Sep '18

17 Sep '18

Public bug reported: vim /etc/nova/nova.conf [DEFAULT] ... rpc_backend = rabbit [oslo_messaging_rabbit] ... rabbit_host = controller rabbit_userid = openstack rabbit_password = RABBIT_PASS tail -f /var/log/nova/nova-compute.log 2018-09-17 13:02:17.467 2320 INFO oslo.messaging._drivers.impl_rabbit [-] Delaying reconnect for 1.0 seconds... 2018-09-17 13:02:18.475 2320 ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 9 seconds. [DEFAULT] ... rpc_backend = rabbit #[oslo_messaging_rabbit] ... rabbit_host = controller rabbit_userid = openstack rabbit_password = RABBIT_PASS liberty版本安装nova计算节点时报错，直接将消息队列配置全部放入默认区域，重启服务恢复正常 ----------------------------------- Release: 0.1 on 2016-11-24 07:54 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/liberty/zh_CN/install-guide-ubuntu/nova-compute-… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1792867 Title: 安装和配置计算节点 in Installation Guide Status in openstack i18n: New Bug description: vim /etc/nova/nova.conf [DEFAULT] ... rpc_backend = rabbit [oslo_messaging_rabbit] ... rabbit_host = controller rabbit_userid = openstack rabbit_password = RABBIT_PASS tail -f /var/log/nova/nova-compute.log 2018-09-17 13:02:17.467 2320 INFO oslo.messaging._drivers.impl_rabbit [-] Delaying reconnect for 1.0 seconds... 2018-09-17 13:02:18.475 2320 ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 9 seconds. [DEFAULT] ... rpc_backend = rabbit #[oslo_messaging_rabbit] ... rabbit_host = controller rabbit_userid = openstack rabbit_password = RABBIT_PASS liberty版本安装nova计算节点时报错，直接将消息队列配置全部放入默认区域，重启服务恢复正常 ----------------------------------- Release: 0.1 on 2016-11-24 07:54 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/liberty/zh_CN/install-guide-ubuntu/nova-compute-… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1792867/+subscriptions

1 0