From amotoki at gmail.com Wed Sep 5 16:59:10 2018 From: amotoki at gmail.com (Akihiro Motoki) Date: Thu, 6 Sep 2018 01:59:10 +0900 Subject: [OpenStack-I18n] Retiring i18n-spec repository? Message-ID: 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) From ianyrchoi at gmail.com Thu Sep 6 01:46:25 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 6 Sep 2018 10:46:25 +0900 Subject: [OpenStack-I18n] Retiring i18n-spec repository? In-Reply-To: References: Message-ID: <9b04f6ef-a73f-ddc1-b7df-872e69b8f904@gmail.com> Thank u for raising this issue. The repository was created almost two years ago, since I thought when I was PTL that I strongly believe that following all OpenStack-ways (e.g., spec & blueprint, task management such as Launchpad or Storyboard) makes OpenStack teams healthier and it would apply to I18n team. But it seems that interacting a lot with non-friendly (just perspective from translators) tools to I18n team is one of barriers using such toolings. I am still on the party making use of development-friendly tools in I18n team - Internationalization is not only translation but also includes all of effort on how translation is managed with multiple OpenStack artifacts and such management requires some of development and management knowledge (not too much, I think I18n cores can follow well on such knowledge), but it is definitely fine to use tools which more I18n team & core members are friendly. Besides, for the perspective of task management, I think migrating Launchpad to Storyboard in I18n team would have advantages - more user-friendly and GUI based user interface would make I18n team healthier and IMO Storyboard can be used instead of i18n-specs repository. With many thanks, /Ian Akihiro Motoki wrote on 9/6/2018 1:59 AM: > 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) > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From ianyrchoi at gmail.com Thu Sep 6 02:06:34 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 6 Sep 2018 11:06:34 +0900 Subject: [OpenStack-I18n] [storyboard] [I18n] Can Storyboard web pages be translatable to multiple languages? Message-ID: 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.html [2] http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/tree/src/app/stories/template/list.html#n26 [3] http://translate.openstack.org/ [4] https://docs.openstack.org/i18n/latest/infra.html From fungi at yuggoth.org Thu Sep 6 17:33:19 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 6 Sep 2018 17:33:19 +0000 Subject: [OpenStack-I18n] [storyboard] [I18n] Can Storyboard web pages be translatable to multiple languages? In-Reply-To: References: Message-ID: <20180906173318.7z5ojmvgfieq6jq6@yuggoth.org> On 2018-09-06 11:06:34 +0900 (+0900), Ian Y. Choi wrote: > 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. [...] As also discussed in #storyboard I think this is an interesting idea, particularly for organizations who may want to use StoryBoard deployments where most users are fluent in one of those other languages (and perhaps not at all with English). I do think interface translation is potentially useful for the OpenStack community's storyboard.openstack.org service too, though we'll want to keep in mind that for most of the projects hosted there English is explicitly preferred to increase collaboration (same as with most OpenStack community mailing lists, IRC channels, code review and so on). We may discover that we need to find ways to point out to people, particularly those arriving there for the first time, that they should file stories in English if at all possible even though the interface may be presented in their personally preferred language instead. I've added this topic to https://etherpad.openstack.org/p/sb-stein-ptg-planning and am looking forward to seeing you in Denver! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From aeng at redhat.com Sun Sep 9 23:47:25 2018 From: aeng at redhat.com (Alex Eng) Date: Mon, 10 Sep 2018 09:47:25 +1000 Subject: [OpenStack-I18n] Farewell from Zanata Message-ID: 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 at gmail.com Linkedin: https://www.linkedin.com/in/alex-eng-sin-loon -- ALEX ENG -------------- next part -------------- An HTML attachment was scrubbed... URL: From eumel at arcor.de Tue Sep 11 09:57:31 2018 From: eumel at arcor.de (Frank Kloeker) Date: Tue, 11 Sep 2018 11:57:31 +0200 Subject: [OpenStack-I18n] Farewell from Zanata In-Reply-To: References: Message-ID: <6b85e8a487622b00877903bf52c4c457@arcor.de> Hi Alex, saw your message also on zanata-ml. It's a pity. Best of luck for you and thanks for all your kindly support in the past. kind regards Frank Am 2018-09-10 01:47, schrieb Alex Eng: > 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 at gmail.com > Linkedin: https://www.linkedin.com/in/alex-eng-sin-loon > > -- > > ALEX ENG > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From jftalta at gmail.com Tue Sep 11 18:57:34 2018 From: jftalta at gmail.com (JF Taltavull) Date: Tue, 11 Sep 2018 20:57:34 +0200 Subject: [OpenStack-I18n] Farewell from Zanata In-Reply-To: <6b85e8a487622b00877903bf52c4c457@arcor.de> References: <6b85e8a487622b00877903bf52c4c457@arcor.de> Message-ID: Hi Alex, It was a real pleasure to talk with you during OpenStack summits. I hope we will meet again someday. Wishing you all the best, Jean-Francois Le mar. 11 sept. 2018 à 11:57, Frank Kloeker a écrit : > Hi Alex, > > saw your message also on zanata-ml. It's a pity. Best of luck for you > and thanks for all your kindly support in the past. > > kind regards > > Frank > > Am 2018-09-10 01:47, schrieb Alex Eng: > > 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 at gmail.com > > Linkedin: https://www.linkedin.com/in/alex-eng-sin-loon > > > > -- > > > > ALEX ENG > > _______________________________________________ > > OpenStack-I18n mailing list > > OpenStack-I18n at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ianyrchoi at gmail.com Wed Sep 12 23:38:16 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 13 Sep 2018 08:38:16 +0900 Subject: [OpenStack-I18n] Farewell from Zanata In-Reply-To: References: <6b85e8a487622b00877903bf52c4c457@arcor.de> Message-ID: Hello Alex, I was in OpenStack PTG event on Mon & Tue, and have just come back to Korea - sorry for my late message. We promised on a short-walk during OpenStack Austin Summit in 2016 that we would see each other in future, but it definitely seems that different geographical locations prevent us from physically seeing each other. I should have been to OpenStack Sydney Summit last year to co-present so a nice presentation [1] and discuss more with you and Patrick. I really hope that we will see each other in future somewhere. Thanks a lot for your contribution on Zanata development and your encouragement for OpenStack I18n team to best use Zanata in OpenStack development - one of best use cases as well as translate.zanata.org and fedora.zanata.org . I wanna share our good memory with some pictures during OpenStack Summits : https://photos.app.goo.gl/xEQc72NrGsykNX3v5 . And of course, best wishes on your change and future! With many thanks, /Ian [1] https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20007/how-zanata-powers-upstream-collaboration-with-openstack-internationalization JF Taltavull wrote on 9/12/2018 3:57 AM: > Hi Alex, > > It was a real pleasure to talk with you during OpenStack summits. > > I hope we will meet again someday. > > Wishing you all the best, > > Jean-Francois > > Le mar. 11 sept. 2018 à 11:57, Frank Kloeker > a écrit : > > Hi Alex, > > saw your message also on zanata-ml. It's a pity. Best of luck for you > and thanks for all your kindly support in the past. > > kind regards > > Frank > > Am 2018-09-10 01:47, schrieb Alex Eng: > > 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 at gmail.com > > Linkedin: https://www.linkedin.com/in/alex-eng-sin-loon > > > > -- > > > > ALEX ENG > > _______________________________________________ > > OpenStack-I18n mailing list > > OpenStack-I18n at lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From eumel at arcor.de Sun Sep 16 09:01:26 2018 From: eumel at arcor.de (Frank Kloeker) Date: Sun, 16 Sep 2018 11:01:26 +0200 Subject: [OpenStack-I18n] [I18n] Stein translation plans and prio Message-ID: 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) From 1792867 at bugs.launchpad.net Mon Sep 17 06:23:17 2018 From: 1792867 at bugs.launchpad.net (wangjianqiang) Date: Mon, 17 Sep 2018 06:23:17 -0000 Subject: [OpenStack-I18n] =?utf-8?b?W0J1ZyAxNzkyODY3XSBbTkVXXSDlronoo4U=?= =?utf-8?b?5ZKM6YWN572u6K6h566X6IqC54K5IGluIEluc3RhbGxhdGlvbiBHdWlkZQ==?= Message-ID: <153716539723.8724.188762385612823674.malonedeb@soybean.canonical.com> 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-guide/source/nova-compute-install.rst URL: https://docs.openstack.org/liberty/zh_CN/install-guide-ubuntu/nova-compute-install.html ** 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-guide/source/nova-compute-install.rst URL: https://docs.openstack.org/liberty/zh_CN/install-guide-ubuntu/nova-compute-install.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1792867/+subscriptions From ianyrchoi at gmail.com Thu Sep 20 04:09:04 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 20 Sep 2018 13:09:04 +0900 Subject: [OpenStack-I18n] [openstack-dev] [docs][i18n][ptg] Stein PTG Summary In-Reply-To: <20180919163703.32ec748555e59bd2984a542e@redhat.com> References: <20180919163703.32ec748555e59bd2984a542e@redhat.com> Message-ID: <44520f86-4807-398a-fa48-94230d2d3673@gmail.com> 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-translation-support [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.html [7] https://docs.openstack.org/infra/openstack-zuul-jobs/jobs.html#job-openstack-tox-docs [8] https://www.openstack.org/user-survey [9] https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center [10] https://www.openstack.org/containers/leveraging-containers-and-openstack/ [11] https://docs.openstack.org/i18n/latest/official_translator.html#atc-status-in-i18n-project [12] https://governance.openstack.org/uc/reference/charter.html#active-user-contributors-auc [13] https://docs.openstack.org/i18n/latest/release_management.html [14] https://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-data/rocky.yaml [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.html [20] http://lists.openstack.org/pipermail/openstack/2018-September/046937.html [21] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003314.html [22] https://www.dropbox.com/sh/2pmvfkstudih2wf/AAAG2c6C_OXorMRFH66AvboYa/Docs%20%2B%20i18n 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 at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev From cloudsuhartono at gmail.com Thu Sep 20 13:48:53 2018 From: cloudsuhartono at gmail.com (Cloud Suhartono) Date: Thu, 20 Sep 2018 20:48:53 +0700 Subject: [OpenStack-I18n] [openstack-dev] [docs][i18n][ptg] Stein PTG Summary In-Reply-To: <44520f86-4807-398a-fa48-94230d2d3673@gmail.com> References: <20180919163703.32ec748555e59bd2984a542e@redhat.com> <44520f86-4807-398a-fa48-94230d2d3673@gmail.com> Message-ID: Hi Ian, You show us the Indonesian translations at the [1][2][3][4][5]. Thank you very much /Suhartono [1] https://www.openstack.org/user-survey/survey-2018/landing?lang=id_ID [2] https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center [3] https://www.openstack.org/containers/leveraging-containers-and-openstack/ [4] https://docs.openstack.org/id/ [5] https://docs.openstack.org/i18n/latest/id/release_management.html Pada tanggal Kam, 20 Sep 2018 pukul 11.09 Ian Y. Choi menulis: > 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-translation-support > [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.html > [7] > > https://docs.openstack.org/infra/openstack-zuul-jobs/jobs.html#job-openstack-tox-docs > [8] https://www.openstack.org/user-survey > [9] > > https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center > [10] > https://www.openstack.org/containers/leveraging-containers-and-openstack/ > [11] > > https://docs.openstack.org/i18n/latest/official_translator.html#atc-status-in-i18n-project > [12] > > https://governance.openstack.org/uc/reference/charter.html#active-user-contributors-auc > [13] https://docs.openstack.org/i18n/latest/release_management.html > [14] > > https://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-data/rocky.yaml > [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.html > [20] > http://lists.openstack.org/pipermail/openstack/2018-September/046937.html > [21] > > http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003314.html > [22] > > https://www.dropbox.com/sh/2pmvfkstudih2wf/AAAG2c6C_OXorMRFH66AvboYa/Docs%20%2B%20i18n > > > 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 at lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ianyrchoi at gmail.com Mon Sep 24 14:32:26 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Mon, 24 Sep 2018 23:32:26 +0900 Subject: [OpenStack-I18n] [openstack-dev] [docs][i18n][ptg] Stein PTG Summary In-Reply-To: References: <20180919163703.32ec748555e59bd2984a542e@redhat.com> <44520f86-4807-398a-fa48-94230d2d3673@gmail.com> Message-ID: <519edc78-2085-3eb8-ff6b-d1640eae9dd2@gmail.com> Wow thanks a lot for your additional summary on Indonesian translation! With many thanks, /Ian Cloud Suhartono wrote on 9/20/2018 10:48 PM: > Hi Ian, > You show us the Indonesian translations at the [1][2][3][4][5]. > Thank you very much > /Suhartono > > [1] https://www.openstack.org/user-survey/survey-2018/landing?lang=id_ID > [2] > https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center > [3] > https://www.openstack.org/containers/leveraging-containers-and-openstack/ > [4] https://docs.openstack.org/id/ > [5] https://docs.openstack.org/i18n/latest/id/release_management.html > > Pada tanggal Kam, 20 Sep 2018 pukul 11.09 Ian Y. Choi > > menulis: > > 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-translation-support > [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.html > [7] > https://docs.openstack.org/infra/openstack-zuul-jobs/jobs.html#job-openstack-tox-docs > [8] https://www.openstack.org/user-survey > [9] > https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center > [10] > https://www.openstack.org/containers/leveraging-containers-and-openstack/ > [11] > https://docs.openstack.org/i18n/latest/official_translator.html#atc-status-in-i18n-project > [12] > https://governance.openstack.org/uc/reference/charter.html#active-user-contributors-auc > [13] https://docs.openstack.org/i18n/latest/release_management.html > [14] > https://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-data/rocky.yaml > [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.html > [20] > http://lists.openstack.org/pipermail/openstack/2018-September/046937.html > [21] > http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003314.html > [22] > https://www.dropbox.com/sh/2pmvfkstudih2wf/AAAG2c6C_OXorMRFH66AvboYa/Docs%20%2B%20i18n > > > 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 at lists.openstack.org?subject:unsubscribe > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >