- OpenStack-I18n - lists.openstack.org

[Bug 1821656] [NEW] 启动一个实例 in Installation Guide
by lee 25 Mar '19

25 Mar '19

Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. error msg: ERROR oslo_messaging.rpc.server UnsupportedVersion: Endpoint does not support RPC version 5.0. Attempted method: build_and_run_instance when i build instance ,it is always in buiding If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:14 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/launch-instance.h… ** 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/1821656 Title: 启动一个实例 in Installation Guide Status in openstack i18n: New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. error msg: ERROR oslo_messaging.rpc.server UnsupportedVersion: Endpoint does not support RPC version 5.0. Attempted method: build_and_run_instance when i build instance ,it is always in buiding If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:14 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/launch-instance.h… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1821656/+subscriptions

2 1

[ptl][I18n][election] PTL Candidacy for Train
by Ian Y. Choi 12 Mar '19

12 Mar '19

Hello, I am writing to announce my PTL candidacy of I18n for Train release. I served the PTL role on Ocata and Pike cycle, and have been great memory with last three release cycles with Frank who did so wonderful PTL activities. During Train cycle, I would like to do and collaborate with team members: * Helping to continue previous nice work (e.g., translation checksite, user-survey translation) * Investigating with Zanata's health and possible alternatives [1] * Communicating with translators and language coordinators * Sharing the voice from OpenStack teams with I18n team * Clean handover to the next PTL or discussing with team's direction (e.g., to a working group) I want to add the fourth part - as Frank wrote non-candicacy [2], it would be so great if the project gets fresh air. I don't think I am the part of fresh air since I also stayed in I18n team a lot like Frank. But it seems that I18n team needs more transition and hand-over period for a new PTL, or more discussion with team members might be needed to think about our team's direction such as changing the team status from an official team to a working group. With many thanks, /Ian [1] https://www.redhat.com/archives/zanata-devel/2019-February/msg00000.html [2] http://lists.openstack.org/pipermail/openstack-i18n/2019-March/003367.html

1 0

Missing PTL candidate, only 5 hours remaining
by Jeremy Stanley 12 Mar '19

12 Mar '19

There are just 5 hours remaining in the candidate nomination period for the "Train" cycle PTL election. If you want to make sure the OpenStack Technical Committee doesn't need to take special action due to lack of a candidate and are willing to lead the I18n team through the upcoming development cycle, please don't delay in following our instructions to nominate yourself: https://governance.openstack.org/election/#candidates -- Jeremy Stanley

1 0

[I18n] PTL Non-Candidacy
by Frank Kloeker 07 Mar '19

07 Mar '19

Hello, following the release calendar PTL self-nomination starts today and I would like to announce my non-candidacy for the Train cycle. We reached a lot in the last three cycles: - Continous translation of OpenStack core projects - Translating whitepapers and User Survey for OSF - Setup translation check server and extend functionality - Start project doc translation We had a great time last year during Berlin Summit in Germany. Now it's up to rotate PTL role as it's thought to get fresh air in the project. I'm still part of the community and available for help as I18n and Docs core. But I also want to do something with research in AI/Machine Translation, to find useful use cases in the project. I would like to thank everyone who supported me over the years. It was a great experience and I can recommend it for everyone :) kind regards Frank

3 3

Re: [OpenStack-I18n] [I18n] PTL Non-Candidacy
by Ian Y. Choi 05 Mar '19

05 Mar '19

Hello Frank, I could not imagine our recent three release cycles in I18n team without you. I have been really happy to work with you, and I am sure that we as one team have done lots of interesting and valuable work. Also, I sincerely believe that I18n activities have spreaded much more globally with your great leadership. Let's stay together in the part of the community :) With many thanks, /Ian Allison Price wrote on 3/5/2019 3:58 AM: > Frank - > > Thank you so much for all of your work as the i18n PTL for the past few cycles. You lead a lot of really important initiatives that continue to be very valuable for the global community. > > Thank you! > Allison > > > >> On Mar 4, 2019, at 12:38 PM, Frank Kloeker <eumel(a)arcor.de> wrote: >> >> Hello, >> >> following the release calendar PTL self-nomination starts today and I would like to announce my non-candidacy for the Train cycle. We reached a lot in the last three cycles: >> >> - Continous translation of OpenStack core projects >> - Translating whitepapers and User Survey for OSF >> - Setup translation check server and extend functionality >> - Start project doc translation >> >> We had a great time last year during Berlin Summit in Germany. >> Now it's up to rotate PTL role as it's thought to get fresh air in the project. >> I'm still part of the community and available for help as I18n and Docs core. But I also want to do something with research in AI/Machine Translation, to find useful use cases in the project. >> >> I would like to thank everyone who supported me over the years. It was a great experience and I can recommend it for everyone :) >> >> kind regards >> >> Frank >> >

2 1

[I18n] Team meeting Feb 28 2019 16:00 UTC
by Frank Kloeker 27 Feb '19

27 Feb '19

Hello, after my vacation I want to make the I18n team meeting on Thursday, 28th of Feb and hopefully I'll be there on time. There are several topics on the agenda [1]. Feel free to add your topics too. kind regards Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

1 0

ATC codes for Denver?
by Robert Simai 26 Feb '19

26 Feb '19

Hi, I'm not sure if I'm the only one (maybe I didn't do enough :-) but I seem to be missing my ATC code to be used for the Denver Summit. Not decided if I'm going there but my peers reminded me there's a deadline tomorrow, then prices go up. Typically Jeremy Stanley sends these but before I bug them: Anyone else has got it? Was there any change regarding translators and ATC codes that I've missed? -- Thanks, Robert

3 3

releasenotes translations, IRC meeting today (or next)
by Robert Simai 20 Feb '19

20 Feb '19

Hi, as suggested by Frank I've put a topic for today's (or the next) IRC meeting, about the usefulness of release notes translations: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting -- Thanks, Robert

2 2

[I18n] Meeting on Demand
by Frank Kloeker 05 Feb '19

05 Feb '19

Hello Stackers, in the past we changed often the format of our team meeting to find out the right requirements and the highest comfort for all participants. We cover different time zones, tried Office Hours and joint the docs team meeting as well, so we have both meeting behind each other. At the end there are no participants and from I18n perspective also not so much topics to discuss outside the translation period. For that reason I want to change to a "Meeting on Demand" format. Feel free to add your topics on the wiki page [1] for the upcoming meeting slot (as usually Thursday [2]) or raise the topic on the mailing list with the proposal of a regular meeting. We will then arrange the next meeting. many thanks kind regards Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting [2] http://eavesdrop.openstack.org/#I18N_Team_Meeting

1 0

New Extra-ATC status
by Frank Kloeker 05 Feb '19

05 Feb '19

Dear I18n team, the governance page was updated and have now the new data available: https://governance.openstack.org/tc/reference/projects/i18n.html#extra-atcs kind regards Frank

1 1

Re: [OpenStack-I18n] Container Whitepaper translation is stuck
by ha-miyamoto＠kddi.com 24 Jan '19

24 Jan '19

Hi all, Thank you for all of your support. I wait for a while until corn jobs finished. Many thanks, Hajime Miyamoto -----Original Message----- From: Ian Y. Choi [mailto:ianyrchoi@gmail.com] Sent: Thursday, January 24, 2019 8:49 AM To: Frank Kloeker Cc: 宮本元; jimmy(a)tipit.net; openstack-i18n(a)lists.openstack.org; sebastian(a)tipit.net Subject: ***フリーメール*** Re: [OpenStack-I18n] Container Whitepaper translation is stuck I have just seen that Sebastian made a commit to add Japanese language for container whitepaper translation target: https://github.com/OpenStackweb/openstack-org/commit/26f033d385fe6c9b1924e6… . Thanks a lot, Sebastian! Not sure what the next step is to finally land this patch, but it might be 1) moving master branch to production branch in the repo or 2) waiting for a batch (like cron) job Hajime: the publishing process is related with the repo what I mentioned, which is different from official OpenStack repos mentioned in https://docs.openstack.org/i18n/latest/infra.html . If you are interested in publishing process, please come to I18n meeting to discuss with other translators. With many thanks, /Ian On Wednesday, January 23, 2019, Frank Kloeker <eumel(a)arcor.de> wrote: Hello, the publishing process for the whitepapers are completely different as the common OpenStack projects. @Sebastian, @Jimmy: Can you take a look, please? I think for a new language you have to setup something in CMS. many thanks Frank Am 2019-01-23 09:36, schrieb 宮本元: Does anyone know the difference between white papers and other documents? Any help will be welcome. Thanks. Hajime Miyamoto -----Original Message----- From: ha-miyamoto(a)kddi.com [mailto:ha-miyamoto@kddi.com] Sent: Thursday, January 10, 2019 12:47 PM To: 'openstack-i18n(a)lists.openstack.org <mailto:openstack-i18n@lists.openstack.org> ' Subject: [OpenStack-I18n] Container Whitepaper translation is stuck Hi, I am currently trying to translate and publish Container Whitepaper[1] in Japanese language, but the publishing process seems to be not good. We have completed its translation, but its publication is stopped as so far. I assume publication procedure is proceeded automatically when Zanata[2] indicator show 100% , but it have never been proceeded. Does anyone help us to proceed, if whitepaper translation needs manual steps. Other translated docs have been already published in Korean, German and Indonesian languages. [1]https://www.openstack.org/containers/leveraging-containers-and-openstack/ <https://www.openstack.org/containers/leveraging-containers-and-openstack/> [2]https://translate.openstack.org/iteration/view/leveraging-containers-open… <https://translate.openstack.org/iteration/view/leveraging-containers-openst…> BR, Hajime Miyamoto _______________________________________________ OpenStack-I18n mailing list OpenStack-I18n(a)lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n> _______________________________________________ OpenStack-I18n mailing list OpenStack-I18n(a)lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n> _______________________________________________ OpenStack-I18n mailing list OpenStack-I18n(a)lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>

1 0

Container Whitepaper translation is stuck
by ha-miyamoto＠kddi.com 23 Jan '19

23 Jan '19

Hi, I am currently trying to translate and publish Container Whitepaper[1] in Japanese language, but the publishing process seems to be not good. We have completed its translation, but its publication is stopped as so far. I assume publication procedure is proceeded automatically when Zanata[2] indicator show 100% , but it have never been proceeded. Does anyone help us to proceed, if whitepaper translation needs manual steps. Other translated docs have been already published in Korean, German and Indonesian languages. [1]https://www.openstack.org/containers/leveraging-containers-and-openstack/ [2]https://translate.openstack.org/iteration/view/leveraging-containers-open… BR, Hajime Miyamoto

4 3

[Bug 1812967] [NEW] 网络选项2：私有网络 in Installation Guide
by WangLei 23 Jan '19

23 Jan '19

Public bug reported: ###### 在``[linux_bridge]``部分，将公共虚拟网络和公共物理网络接口对应起来： [linux_bridge] physical_interface_mappings = provider:PROVIDER_INTERFACE_NAME 将``PUBLIC_INTERFACE_NAME`` 替换为底层的物理公共网络接口。请查看：ref:environment-networking for more information。 ###### "PROVIDER_INTERFACE_NAME" "PUBLIC_INTERFACE_NAME" Which one is it? This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:15 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/neutron-contro… ** 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/1812967 Title: 网络选项2：私有网络 in Installation Guide Status in openstack i18n: New Bug description: ###### 在``[linux_bridge]``部分，将公共虚拟网络和公共物理网络接口对应起来： [linux_bridge] physical_interface_mappings = provider:PROVIDER_INTERFACE_NAME 将``PUBLIC_INTERFACE_NAME`` 替换为底层的物理公共网络接口。请查看：ref:environment-networking for more information。 ###### "PROVIDER_INTERFACE_NAME" "PUBLIC_INTERFACE_NAME" Which one is it? This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:15 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/neutron-contro… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1812967/+subscriptions

1 1

[Bug 1810882] [NEW] Inappropriate Chinese translation of image status
by Launchpad Bug Tracker 07 Jan '19

07 Jan '19

You have been subscribed to a public bug: latest horizon version Inappropriate Chinese translation of image status: Currently, status "Active" is translated into "使用中" , which means "in use". But, it should be "可用的", which means "available". ** Affects: openstack-i18n Importance: Undecided Status: New -- Inappropriate Chinese translation of image status https://bugs.launchpad.net/bugs/1810882 You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n.

1 0

[Bug 1810882] Re: Inappropriate Chinese translation of image status
by Akihiro Motoki 07 Jan '19

07 Jan '19

Translation bug should be fixed in https://translate.openstack.org/. ** Project changed: horizon => openstack-i18n -- 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/1810882 Title: Inappropriate Chinese translation of image status Status in openstack i18n: New Bug description: latest horizon version Inappropriate Chinese translation of image status: Currently, status "Active" is translated into "使用中" , which means "in use". But, it should be "可用的", which means "available". To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1810882/+subscriptions

1 0

[I18n] No team meeting
by Frank Kloeker 02 Jan '19

02 Jan '19

Hello, due the vacation period the I18n team will also skip the next team meetings. Our next appointment will be 2019/01/10 07:00 UTC in #openstack-meeting. Enjoy the time and a Happy New Year! Frank

3 3

Storyboard translations
by Frank Kloeker 20 Dec '18

20 Dec '18

Hello, in the case you'll miss the team meeting [1] today, I would like to mention the Storyboard Translation. Storyboard [2] is a project and task management tool built and used by the community. We can make that multi-language capable on our translation platform on [3]. Please spend some time for translation. If some languages are available we will try to import that on the target platform. many thanks Frank [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting [2] https://storyboard.openstack.org [3] https://translate.openstack.org/project/view/storyboard

1 0

[i18n] Team meeting Thursday 07:00 UTC #openstack-meeting
by Frank Kloeker 12 Dec '18

12 Dec '18

Hello, just a reminder, we want to start this week with our new meeting format with combined meeting between I18n and Docs team. Next meeting would be start Thursday 07:00 UTC in #openstack-meeting. Logistic to see on [1]. Agenda is posted on [2]. Please add your topics if you want to discuss I18n things. kind regards Frank [1] http://eavesdrop.openstack.org/#I18N_Team_Meeting [2] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

1 0

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

06 Dec '18

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

2 1

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

28 Nov '18

translation should be fixed in the translation platform (translate.openstack.org).[1] Horizon is not related. Removing horizon from the affected project. [1] https://docs.openstack.org/i18n/latest/ ** No longer affects: horizon -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1794401 Title: Suspend Instance and Shelve instance have same name in French Status in openstack i18n: New Bug description: In the french version for Horizon, "Suspend Instance" and "Shelve instance" are both called "Suspendre l'instance" To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1794401/+subscriptions

1 0

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

28 Nov '18

This looks like a translation bug. Forwarding to openstack-i18n. ** Also affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1794401 Title: Suspend Instance and Shelve instance have same name in French Status in openstack i18n: New Bug description: In the french version for Horizon, "Suspend Instance" and "Shelve instance" are both called "Suspendre l'instance" To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1794401/+subscriptions

1 0

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

19 Nov '18

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

4 3

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

16 Nov '18

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

2 4

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

30 Oct '18

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

3 2

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

30 Oct '18

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

3 4