- OpenStack-I18n - lists.openstack.org

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

31 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

[I18n] Stein translation plans and prio
by Frank Kloeker 16 Sep '18

16 Sep '18

Hello, the PTG is just over and now we are at the beginning of the work for Stein cycle. First of all let me thank all supporters for the I18n team and all individuals who help to present OpenStack in different languages. We have made so much progress since the formation of the team. What are the workflows now for the Stein cycle: 1. Project documentation translation We have now the right Zuul jobs in the flow to pull and push documentation from project repos to Zanata and back. At the moment there are 3 early-bird projects on the list: Horizon, OpenStack Ansible, and OpenStack Helm. Expanding this list will be the main work in the cycle. 2. Whitepaper translation Early this year we started with translation of Edge Computing Whitepaper. After solving issues with publishing translated content we have here now also a flow from the origin document through translation platform and back. Container whitepaper is the second project in this space. 3. Stein Dashboard translation All translation strings from stable/rocky branch are merged back to master and we work ahead on the master branch. There are 22 projects on that list. All plans and prios are linked on the frontpage of translation platform https://translate.openstack.org Keep the stones rolling on the Stein cycle. kind regards Frank (PTL I18n)

1 0

Farewell from Zanata
by Alex Eng 13 Sep '18

13 Sep '18

Hi, Due to the company changes, I am no longer able to contribute to the Zanata Platform project. I would like to give thanks for all of you who supported the project and me over the years. I have met and get to work with some of the most wonderful and great people because of this project. There are a lot of fond memories and a great bond built which I will cherish forever. I hope that we will cross our path again in the future. Personal contact: Email: loones1595(a)gmail.com Linkedin: https://www.linkedin.com/in/alex-eng-sin-loon -- ALEX ENG

4 3

[storyboard] [I18n] Can Storyboard web pages be translatable to multiple languages?
by Ian Y. Choi 07 Sep '18

07 Sep '18

Hello, I wanna ask whether https://storyboard.openstack.org/ web pages can be translatable to multiple languages (e.g., Chinese, Japanese, Korean, German, French, Spanish, ...) or not. I have thought such idea on my mind from some time period ago, and I think now would be a good timing for raising this question since it seems that more project repositories are migrating to Storyboard, and internationalization of Storyboard is one of criteria for I18n team to decide to migrate to Storyboard (FYI: discussion on I18n team - [1]). From my very brief investigation, it seems that adding I18n support on html pages like [2], extracting translation source strings to pot files, syncing with Zanata [3] with powerful infra support [4] would make Storyboard translatable with translating to multiple languages by I18n team. Am I understanding correctly and can I18n team get help on such effort? With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003307.h… [2] http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/tree/src… [3] http://translate.openstack.org/ [4] https://docs.openstack.org/i18n/latest/infra.html

2 1

Retiring i18n-spec repository?
by Akihiro Motoki 06 Sep '18

06 Sep '18

Hi Frank and i18n cores, i18n-spec repository is never used since it is created almost two years ago. I would like to propose the retirement of the i18n-spec repository. The number of proposals was small so far and it would continue. If some proposal needs more detail explanation we can use the i18n repository. In addition, I think most folks do not check i18n-spec repository in a regular basis. Thought? Thanks, Akihiro Motoki (amotoki)

2 1

Indonesian translations on the edge whitepaper New!
by Cloud Suhartono 23 Aug '18

23 Aug '18

I do not see any Indonesian translation on the pot-translation [1] although I have done 100% for it on the master [2]. Can anyone help me ! Thank you - Suhartono - [1] https://translate.openstack.org/iteration/view/edge-computing/pot-translati… [2] https://translate.openstack.org/iteration/view/edge-computing/master/langua…

2 2

[I18n] Digest 2018/08/01
by Frank Kloeker 13 Aug '18

13 Aug '18

Hello, we are shortly in the beginning of the hot translation phase for Rocky. Few days ahead hard string freeze. We're well prepared. 1. Hard String Freeze In this period and around release we work on stable/rocky branch in each project beside main documentation. Branching is a creeping process, so please use Rocky Dashboard Translation from Zanata mainpage https://translate.openstack.org. Dashboard will be ongoing updated. 2. Whitepaper translation There are two whitepaper in the queue: for Edge Computing and for Containers. The first document is now in a new version available. This was required due the new publishing process. It's easy to convert with Translation Memory the new version from the old one. But there are still issues with publishing so I recommend to focus on project translation starting from next week. 3. PTL election This is also ongoing. See which candidates are running for Stein: https://governance.openstack.org/election/#stein-ptl-candidates 4. Translation Check Site I can announce the official sponsorship for this project by Deutsche Telekom. Hostname and credentials are the same: host: https://i18n.external.otc.telekomcloud.com/ user: i18n pass: Queens2018 There are additional services now in translation string sync: Horizon Dashboard Plugins, Designate, Sahara, Heat, Magnum, Trove. Sync is scheduled hourly. You can review the patch if you want to use your own: https://review.openstack.org/#/c/586867/ 5. Extra-ATC Status My apology because I was too late for collecting the data and propose the Extra ATC. This is mostly approved now: https://review.openstack.org/#/c/586751/ 6. Status Project Doc Translation There is no update. You can translate the openstack-ansible project in Zanata, but at the moment there is now way to push back the strings into project repo. Depends on https://review.openstack.org/#/c/581000/ Any questions or remarks? Please join our next I18n Office Hour, Thursday, 2018/08/02 13:00 UTC in #openstack-i18n (https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting) Please note: There is a spam attack in progress on FreeNode IRC, so channel mode is set +r (registered nick required). kind regards Frank

3 6

I18n ATC status
by Frank Kloeker 07 Aug '18

07 Aug '18

Hello, during the approval process for Extra-ATC in I18n we experienced one issue again: Foundation membership. Your ATC status for contribution is out of question, but for elections of PTL/UC/TC/anything is Foundation membership absolutely required. If you are using for Foundation membership and Zanata the same e-mail address, then you're fine. But if these addresses are different, it's required to configure the e-mail address for Zanata registration as second e-mail address in your Foundation membership profile. You can check your collected status on https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics#Rocky_cycle_.282018… many thanks Frank

1 1

Re: [OpenStack-I18n] [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation
by Ian Y. Choi 02 Aug '18

02 Aug '18

Hello Sebastian, Korean has also currently 100% translation now. About two weeks ago, there were a discussion how to include the list of translators per translated document. My proposal is mentioned in [1] - do you think it is a good idea and it is under implementation, or parsing the name of translators in header lines on po files (e.g., four lines on [2]) would be better idea? With many thanks, /Ian [1] http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.… [2] http://git.openstack.org/cgit/openstack/i18n/tree/doc/source/locale/de/LC_M… Frank Kloeker wrote on 7/31/2018 6:39 PM: > Hi Sebastian, > > okay, it's translated now. In Edge whitepaper is the problem with > XML-Parsing of the term AT&T. Don't know how to escape this. Maybe you > will see the warning during import too. > > kind regards > > Frank > > Am 2018-07-30 20:09, schrieb Sebastian Marcet: >> Hi Frank, >> i was double checking pot file and realized that original pot missed >> some parts of the original paper (subsections of the paper) apologizes >> on that >> i just re uploaded an updated pot file with missing subsections >> >> regards >> >> On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker <eumel(a)arcor.de> wrote: >> >>> Hi Jimmy, >>> >>> from the GUI I'll get this link: >>> >> https://translate.openstack.org/rest/file/translation/edge-computing/pot-tr… >> >>> [1] >>> >>> paper version are only in container whitepaper: >>> >>> >> https://translate.openstack.org/rest/file/translation/leveraging-containers… >> >>> [2] >>> >>> In general there is no group named papers >>> >>> kind regards >>> >>> Frank >>> >>> Am 2018-07-30 17:06, schrieb Jimmy McArthur: >>> Frank, >>> >>> We're getting a 404 when looking for the pot file on the Zanata API: >>> >> https://translate.openstack.org/rest/file/translation/papers/papers/de/po?d… >> >>> [3] >>> >>> As a result, we can't pull the po files. Any idea what might be >>> happening? >>> >>> Seeing the same thing with both papers... >>> >>> Thank you, >>> Jimmy >>> >>> Frank Kloeker wrote: >>> Hi Jimmy, >>> >>> Korean and German version are now done on the new format. Can you >>> check publishing? >>> >>> thx >>> >>> Frank >>> >>> Am 2018-07-19 16:47, schrieb Jimmy McArthur: >>> Hi all - >>> >>> Follow up on the Edge paper specifically: >>> >> https://translate.openstack.org/iteration/view/edge-computing/pot-translati… >> >>> [4] This is now available. As I mentioned on IRC this morning, it >>> should >>> be VERY close to the PDF. Probably just needs a quick review. >>> >>> Let me know if I can assist with anything. >>> >>> Thank you to i18n team for all of your help!!! >>> >>> Cheers, >>> Jimmy >>> >>> Jimmy McArthur wrote: >>> Ian raises some great points :) I'll try to address below... >>> >>> Ian Y. Choi wrote: >>> Hello, >>> >>> When I saw overall translation source strings on container >>> whitepaper, I would infer that new edge computing whitepaper >>> source strings would include HTML markup tags. >>> One of the things I discussed with Ian and Frank in Vancouver is >>> the expense of recreating PDFs with new translations. It's >>> prohibitively expensive for the Foundation as it requires design >>> resources which we just don't have. As a result, we created the >>> Containers whitepaper in HTML, so that it could be easily updated >>> w/o working with outside design contractors. I indicated that we >>> would also be moving the Edge paper to HTML so that we could prevent >>> that additional design resource cost. >>> On the other hand, the source strings of edge computing whitepaper >>> which I18n team previously translated do not include HTML markup >>> tags, since the source strings are based on just text format. >>> The version that Akihiro put together was based on the Edge PDF, >>> which we unfortunately didn't have the resources to implement in the >>> same format. >>> >>> I really appreciate Akihiro's work on RST-based support on >>> publishing translated edge computing whitepapers, since >>> translators do not have to re-translate all the strings. >>> I would like to second this. It took a lot of initiative to work on >>> the RST-based translation. At the moment, it's just not usable for >>> the reasons mentioned above. >>> On the other hand, it seems that I18n team needs to investigate on >>> translating similar strings of HTML-based edge computing whitepaper >>> source strings, which would discourage translators. >>> Can you expand on this? I'm not entirely clear on why the HTML >>> based translation is more difficult. >>> >>> That's my point of view on translating edge computing whitepaper. >>> >>> For translating container whitepaper, I want to further ask the >>> followings since *I18n-based tools* >>> would mean for translators that translators can test and publish >>> translated whitepapers locally: >>> >>> - How to build translated container whitepaper using original >>> Silverstripe-based repository? >>> https://docs.openstack.org/i18n/latest/tools.html [5] describes >>> well how to build translated artifacts for RST-based OpenStack >>> repositories >>> but I could not find the way how to build translated container >>> whitepaper with translated resources on Zanata. >>> This is a little tricky. It's possible to set up a local version >>> of the OpenStack website >>> >> (https://github.com/OpenStackweb/openstack-org/blob/master/installation.md >> >>> [6]). However, we have to manually ingest the po files as they are >>> completed and then push them out to production, so that wouldn't do >>> much to help with your local build. I'm open to suggestions on how >>> we can make this process easier for the i18n team. >>> >>> Thank you, >>> Jimmy >>> >>> With many thanks, >>> >>> /Ian >>> >>> Jimmy McArthur wrote on 7/17/2018 11:01 PM: >>> Frank, >>> >>> I'm sorry to hear about the displeasure around the Edge paper. As >>> mentioned in a prior thread, the RST format that Akihiro worked did >>> not work with the Zanata process that we have been using with our >>> CMS. Additionally, the existing EDGE page is a PDF, so we had to >>> build a new template to work with the new HTML whitepaper layout we >>> created for the Containers paper. I outlined this in the thread " >>> [OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing >>> Whitepaper Translation" on 6/25/18 and mentioned we would be ready >>> with the template around 7/13. >>> >>> We completed the work on the new whitepaper template and then put >>> out the pot files on Zanata so we can get the po language files >>> back. If this process is too cumbersome for the translation team, >>> I'm open to discussion, but right now our entire translation process >>> is based on the official OpenStack Docs translation process outlined >>> by the i18n team: >>> https://docs.openstack.org/i18n/latest/en_GB/tools.html [7] >>> >>> Again, I realize Akihiro put in some work on his own proposing the >>> new translation type. If the i18n team is moving to this format >>> instead, we can work on redoing our process. >>> >>> Please let me know if I can clarify further. >>> >>> Thanks, >>> Jimmy >>> >>> Frank Kloeker wrote: >>> Hi Jimmy, >>> >>> permission was added for you and Sebastian. The Container Whitepaper >>> is on the Zanata frontpage now. But we removed Edge Computing >>> whitepaper last week because there is a kind of displeasure in the >>> team since the results of translation are still not published beside >>> Chinese version. It would be nice if we have a commitment from the >>> Foundation that results are published in a specific timeframe. This >>> includes your requirements until the translation should be >>> available. >>> >>> thx Frank >>> >>> Am 2018-07-16 17:26, schrieb Jimmy McArthur: >>> Sorry, I should have also added... we additionally need permissions >>> so >>> that we can add the a new version of the pot file to this project: >>> >> https://translate.openstack.org/project/view/edge-computing/versions?dswid=… >> >>> [8] Thanks! >>> Jimmy >>> >>> Jimmy McArthur wrote: >>> Hi all - >>> >>> We have both of the current whitepapers up and available for >>> translation. Can we promote these on the Zanata homepage? >>> >>> >> https://translate.openstack.org/project/view/leveraging-containers-openstac… >> >>> [9] >>> >> https://translate.openstack.org/iteration/view/edge-computing/master/docume… >> >>> [10] Thanks all! >>> Jimmy >>> >>> >> __________________________________________________________________________ >> >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> OpenStack-dev-request@lists.openstack.org?subject:unsubscribe [11] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> [12] >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request@lists.openstack.org?subject:unsubscribe [11] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [12] >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request@lists.openstack.org?subject:unsubscribe [11] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [12] >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request@lists.openstack.org?subject:unsubscribe [11] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [12] >> >> >> >> Links: >> ------ >> [1] >> https://translate.openstack.org/rest/file/translation/edge-computing/pot-tr… >> >> [2] >> https://translate.openstack.org/rest/file/translation/leveraging-containers… >> >> [3] >> https://translate.openstack.org/rest/file/translation/papers/papers/de/po?d… >> >> [4] >> https://translate.openstack.org/iteration/view/edge-computing/pot-translati… >> >> [5] https://docs.openstack.org/i18n/latest/tools.html >> [6] >> https://github.com/OpenStackweb/openstack-org/blob/master/installation.md >> [7] https://docs.openstack.org/i18n/latest/en_GB/tools.html >> [8] >> https://translate.openstack.org/project/view/edge-computing/versions?dswid=… >> >> [9] >> https://translate.openstack.org/project/view/leveraging-containers-openstac… >> >> [10] >> https://translate.openstack.org/iteration/view/edge-computing/master/docume… >> >> [11] >> http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe >> [12] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > > 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

1 0

[I18n] [PTL] [Election] Candidacy for I18n PTL in Stein Cycle
by Frank Kloeker 25 Jul '18

25 Jul '18

[posted & mailed] https://review.openstack.org/#/c/585663/ This is my announcement for re-candidacy as I18n PTL in Stein Cycle. At first a quick review what we've done in the last cycle: 1. Zanata upgrade done. As one of the first community's we're running Zanata Release 4 in production. A big success and a great user experiense for all. 2. Translation Check Site done. We were able to win Deutsche Telekom as sponsor for resources, so now we are able to host our own Translation Check Site. From my point of view this solves different problems which we had in the past and now we can check translation strings very fast on our requirements. 3. Aquire more people to the team. I had great experiences during the OpenStack Days in Krakow and Budapest. I shared informationen what our team is doing and how I18n works in the OpenStack Community. I've got many inspirations and hopefully some new team members :-) What I mostly like is getting things done. In this cycle we should get ready project doc translations. We started already with some projects as a proof of concept and we're still working on it. To get that around, involve more projects and involve more project team members for translations is the biggest challenge for me in this cycle. On the other hand we have Edge Computing whitepaper and Container whitepaper on our translation plan. With a new technology in use to publish the translation results very fast on the web page. Beside that we have the OpenStack Summit Berlin in that cycle. For me a special event, since I live and work in Berlin. I expect a lot of collaboration and knowledge sharing with I18n and the OpenStack Community in general. That's my plan for Stein, I'm looking forward to your vote. Frank Email: eumel(a)arcor.de IRC: eumel8 Twitter: eumel_8 OpenStack Profile: https://www.openstack.org/community/members/profile/45058/frank-kloeker

1 0

Re: [OpenStack-I18n] Zanata user email from "alexanderloew2": Inquiry on Zanata
by Ian Y. Choi 15 Jul '18

15 Jul '18

Hello Alexander, I am checking your message now - a little bit late since your Zanata message is sent to me and Frank, and such request was classified as a spam in my mail box. https://docs.openstack.org/i18n/latest/glossary.html describes how to add translated words to the glossary and you can see i18n repository through http://git.openstack.org/cgit/openstack/i18n and https://github.com/openstack/i18n (mirrored site). With many thanks, /Ian Zanata wrote on 7/14/2018 5:13 AM: > > Dear Administrator, > > Zanata user "Alexander Loew" with id "alexanderloew2" has sent the > following message: > > ------------------------------------------------------------------------ > how can I add translation to the glossary? > ------------------------------------------------------------------------ > > You can reply to Alexander Loew at alexander.loew(a)innovo-cloud.de > > ------------------------------------------------------------------------ > > You are receiving this mail because: > You are an administrator > > This message generated by Zanata running at: > https://translate.openstack.org <https://translate.openstack.org> >

1 0

[docs][i18n][ptg] PTG infos on Etherpad
by Frank Kloeker 14 Jul '18

14 Jul '18

Hello, the Docs and I18n team will also present during the PTG in Denver. The rough plan told us on Monday/Tuesday. As usually we're in the same room and will use also the same Etherpad on [1], which I have shameless copied from the last PTG in Denver, so we have all this usefull links for Station 26 already there :) Please write down your topics and your possible participation. The Etherpad from the previous PTG is also linked as a reminder. many thanks Frank [1] https://etherpad.openstack.org/p/docs-i18n-ptg-stein

1 0

[I18n] IRC Office hours: 2018/07/05 13:00-14:00 UTC
by Frank Kloeker 11 Jul '18

11 Jul '18

Hello, good to be back. Still sorting emails, messages and things. Let's meet on Thursday in our team meeting in the new Office Hour format: 2018/07/05 13:00-14:00 UTC If you have anything to share please let us know on wiki page [1] kind regards Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

2 2

Re: [OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing Whitepaper Translation
by Jimmy McArthur 26 Jun '18

26 Jun '18

We are currently targeting June 25 for the initial version of the Edge whitepaper. However, I'll know more by EOW next. Cheers, Jimmy Ildiko Vancsa wrote: > Hi Akihiro, > > It is on our priority list to put up the translated versions in an online format as well as work out to have the .po files available. > > Jimmy is looking into it and will give an update once we got some progress. > > Thanks and Best Regards, > Ildikó > > >> On 2018. Jun 8., at 10:14, Akihiro Motoki<amotoki(a)gmail.com> wrote: >> >> Hi all, >> >> # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML. >> # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML. >> >> What is the next step of the translation of the edge computing white paper with RST? >> My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works. >> I would like to move this forward and am happy to help the setup of a repo if needed. >> >> Where can we discuss this? >> The edge computing group meeting is not listed at http://eavesdrop.openstack.org/ and I don't know when and where it happens. >> >> [1] https://amotoki.github.io/edge-computing-whitepaper/ >> >> Thanks, >> Akihiro >> >> 2018年5月29日(火) 23:37 Akihiro Motoki<amotoki(a)gmail.com>: >> Hi Ildiko and all, >> >> I am happy to hear that HTML-based publishing is now on the table :) >> I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. >> RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. >> I am happy to help setting up a new doc infrastructure and/or publishing translations. >> >> Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. >> Hopefully we can get a good conclusion for further similar cases. >> >> Thanks, >> Akihiro >> >> >> >> 2018年5月29日(火) 23:19 Ildiko Vancsa<ildiko.vancsa(a)gmail.com>: >> Hi Akihiro and All, >> >> Thank you for your efforts on helping with publishing the white paper in additional languages. >> >> I talked to Ian and Frank last week about this topic and the conundrum on the Foundation side whether or not to do the print version for the translations as that is what slows down the process a lot due to the design work it requires. >> >> We got to the conclusion with our team from the Foundation (cc’ed Allison, Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need to clarify now on the process and as Jeremy indicated the licensing as well. >> >> Thanks, >> Ildikó >> >> >>> On 2018. May 29., at 15:50, Jeremy Stanley<fungi(a)yuggoth.org> wrote: >>> >>> On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: >>> [...] >>>> NOTE: Anyway I need to grant it from the foundation because CC >>>> Attribution-NoDerivatives 4.0 International license does not allow >>>> me to share translations without permission. I updated this files >>>> only for discussion and will close this soon. >>> [...] >>> >>> It seems like this is a really poor choice of license as it's >>> impairing open collaboration. Even Creative Commons suggests that >>> the CC BY-ND license is unsuitable for free cultural works: >>> >>> https://creativecommons.org/share-your-work/public-domain/freeworks/ >>> >>> We should see about getting this changed to CC BY like is used for >>> other collaborative works produced by our community. >>> -- >>> Jeremy Stanley >>> _______________________________________________ >>> openstack-sigs mailing list >>> openstack-sigs(a)lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> _______________________________________________ >> openstack-sigs mailing list >> openstack-sigs(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> _______________________________________________ >> Edge-computing mailing list >> Edge-computing(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing >

1 1

[Bug 1778474] [NEW] 安装和配置 in Installation Guide
by Jack Wong 25 Jun '18

25 Jun '18

Public bug reported: 注解教程使用带有``mod_wsgi``的Apache HTTP服务器来服务认证服务请求，端口为5000和35357。缺省情况下，Kestone服务仍然监听这些端口。然而，本教程手动禁用keystone服务。拼写错误缺省情况下，Keystone服务仍然监听 ** 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/1778474 Title: 安装和配置 in Installation Guide Status in openstack i18n: New Bug description: 注解教程使用带有``mod_wsgi``的Apache HTTP服务器来服务认证服务请求，端口为5000和35357。缺省情况下，Kestone服务仍然监听这些端口。然而，本教程手动禁用keystone服务。拼写错误缺省情况下，Keystone服务仍然监听 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1778474/+subscriptions

1 0

Re: [OpenStack-I18n] [Openstack-sigs] Edge Computing Whitepaper Translation
by Akihiro Motoki 08 Jun '18

08 Jun '18

Hi Ildiko and all, I am happy to hear that HTML-based publishing is now on the table :) I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver. RST based process is used much in the community and translation publishinng of project docs which Ian and us are working on will make the continuous publishing easier. I am happy to help setting up a new doc infrastructure and/or publishing translations. Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one. Hopefully we can get a good conclusion for further similar cases. Thanks, Akihiro 2018年5月29日(火) 23:19 Ildiko Vancsa <ildiko.vancsa(a)gmail.com>: > Hi Akihiro and All, > > Thank you for your efforts on helping with publishing the white paper in > additional languages. > > I talked to Ian and Frank last week about this topic and the conundrum on > the Foundation side whether or not to do the print version for the > translations as that is what slows down the process a lot due to the design > work it requires. > > We got to the conclusion with our team from the Foundation (cc’ed Allison, > Jimmy and Wes) to do HTML-based publishing to reduce this overhead. We need > to clarify now on the process and as Jeremy indicated the licensing as well. > > Thanks, > Ildikó > > > > On 2018. May 29., at 15:50, Jeremy Stanley <fungi(a)yuggoth.org> wrote: > > > > On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote: > > [...] > >> NOTE: Anyway I need to grant it from the foundation because CC > >> Attribution-NoDerivatives 4.0 International license does not allow > >> me to share translations without permission. I updated this files > >> only for discussion and will close this soon. > > [...] > > > > It seems like this is a really poor choice of license as it's > > impairing open collaboration. Even Creative Commons suggests that > > the CC BY-ND license is unsuitable for free cultural works: > > > > https://creativecommons.org/share-your-work/public-domain/freeworks/ > > > > We should see about getting this changed to CC BY like is used for > > other collaborative works produced by our community. > > -- > > Jeremy Stanley > > _______________________________________________ > > openstack-sigs mailing list > > openstack-sigs(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >

4 6

I18n on Superuser Magazine
by Frank Kloeker 08 Jun '18

08 Jun '18

Hello, Lauren (Sell) was very friendly to publish an article on Superuser about I18n work and my presention during European OpenStack Days: http://superuser.openstack.org/articles/i18n-update/ https://twitter.com/OpenStack/status/1004758210497085441 I would also thank the team that we're reach the project at this point and providing so much for the community. thx Frank

1 0

[I18n] IRC Office hours reminder: June 7th at 13:00-14:00 UTC
by Ian Y. Choi 07 Jun '18

07 Jun '18

Hello all, I18n team previously had team meetings but decided to have office hours instead [1]. Please feel free to come to #openstack-i18n IRC channel and ask and/or discuss anything on translation, internationalization, and/or localization issues on projects. Although I18n PTL is now busy on attending OpenStack Days in Europe by the of June [2] (He makes himself really internationlizated by attending to many offline events in Europe!), I am available this week and can serve as a co-chair with the aggrement of I18n PTL :) With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-i18n/2018-April/003238.html [2] http://lists.openstack.org/pipermail/openstack-i18n/2018-May/003239.html

1 0

Attendees for the PTG Denver 2018
by Frank Kloeker 07 Jun '18

07 Jun '18

Good morning from Budapest, today is OpenStack Day in Budapest and I'll hold a presentation about our project and community work in general. Only to give a sign of life ;) As a second I've got a reminder about PTG planning in Denver later this year, I think September. I wouldn't be there because of time and travel cost. My idea would be a virtual meetup or midcycle sprint. But if anyone really wants to be in Denver, let me know. I can reserve the room for the team and will coordinate the time planing (which days). kind regards Frank

2 1

Edge Computing Whitepaper Translation
by Frank Kloeker 29 May '18

29 May '18

Hello I18n Team, maybe as you know beside the project teams there are also working groups in the OpenStack Community. One of them is the Edge Computing Working Group. This group produced a whitepaper which described the essence of Edge Computing and want to translate that to spread knowledge and the Edge Community. I think thats the point where we can help. I uploaded the document on [1]. If you have some time and spend some efforts in this topic please go ahead, any language translations are welcome. The completion date is in 2 weeks. many thanks Frank please note: the document is only available with the document link on [1]. The link in the language list doesn't work in this Zanata version. [1] https://translate.openstack.org/iteration/view/edge-computing/master/docume…

5 6

[I18n] [Docs] Forum session Vancouver
by Frank Kloeker 24 May '18

24 May '18

Good morning, just a quick note when packing the suitcase: We have a Docs/I18n Forum session on Monday 21th, 13:30, direct after lunch [1]. Take the chance to discuss topics about project onboarding with translation or documentation, usage of translated documents or tools. Or just come to say Hello :-) Looking forward to see you there! kind regards Frank (PTL I18n) [1] https://etherpad.openstack.org/p/docs-i18n-project-onboarding-vancouver

6 23