I18n (Internationalization) OpenStack Summit | Vancouver 2018 - - - PowerPoint PPT Presentation

I18n (Internationalization)

OpenStack Summit | Vancouver 2018 - Project update

FRANK KLOEKER IAN Y. CHOI

May 22, 2018

IRC: eumel8 IRC: ianychoi SPEAKERS:

Agenda

• Introduction of I18n team
• Queens facts
• I18n Guide
• Zanata Upgrade Ubuntu 4.3.3
• Translating User Survey
• Translating Edge Computing Whitepaper
• Translation Check Site
• Rocky Goals
• During Rocky - Language dropdown menu

Frank Kloeker

• Technology Manager Cloud Applications at Deutsche

Telekom

• Project Team Lead I18n
• Team member I18n (DE)
• Docs Core Member
• Participant in different Working Groups and SIG’s
• Founder of Cloud-Kindergarten
• Kontakt: Frank.Kloeker@telekom.de
• Profile: https://www.linkedin.com/in/eumel

@eumel_8, github.com/eumel8/ blog.eumel.de

Ian Y. Choi

• Involving in KOSSLab (Korea Open Source Developer Center)

as an open frontier (developer with open sources)

• Previous I18n Project Team Lead (Ocata, Pike)
• Team member I18n (Korean - ko_KR)
• Korea User Group Leader (Jan 2017 - Dec 2018)
• Mentor for Docs & I18n on Upstream Institute

(2017 Boston, 2018 Vancouver)

• E-mail: ianyrchoi@gmail.com
• Profile: https://www.linkedin.com/in/ianychoi/

@ianychoi, github.com/ianychoi http://www.sdndev.net/ Tokyo Design Summit (Oct 2015)

Mission statement

The mission of OpenStack I18n team is to make OpenStack accessible to people of all language backgrounds, by enhancing OpenStack software internationalization, providing translation, maintaining a translation platform and managing translation process for better quality of

• utcomes.

I18n facts in Queens

• 87 modules touched (+ 87 %)
• 17 languages supported (+/- 0)
• 55 active translators (-14 %)
• 7 companies support (- 22 %)

OpenStack I18n Guide

Highlights:

• How to contribute as translator in OpenStack
• How to join a language team
• Handling translation bugs
• I18n tooling and translation infrastructure
• PTL guide (new)
• Team activities with releases
• Translatable and available in 6 languages

https://docs.openstack.org/i18n/latest/

Zanata upgrade to version 4.3.3

• Fresh and faster dashboard
• SImplify installation (Wildfly 10 without extra modules)
• Auto-upgrade database schema
• Bugfix and extend REST API (user stats, project settings
• Cross-Project between I18n, Infra-Team and Zanata-

Developer-Team

Translating OpenStack User Survey

• In 7 languages available
• From the idea a very good user experience, but very

low usage. Work on translating reports

• Announced at OpenStack Summit Vancouver

Translating Edge Computing White Paper

• In 7 languages available
• Very good user experience
• Announced at OpenStack Summit Vancouver

OpenStack Translation Check Site

• Cross-Project: I18n, OpenStack Ansible, Horizon
• Provides Horizon Dashboard for translators to check

translated strings

• Sync periodically strings between translation server

and check server

• Realized with OpenStack Ansible (OSA)
• Extension of the os_horizon role
• Portable and easy to install for everyone

During Rocky - Language dropdown menu

https://docs.openstack.org

I18n goals in Rocky

• Project doc translation
• Whitepaper translation
• Acquire new language teams

See you in

Berlin!

@OpenStack

THANKS.

Questions?

• penstack
• penstack

OpenStackFoundation

I18n mailing list

• http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

IRC

• #openstack-i18n IRC channel
• More information on IRC: https://wiki.openstack.org/wiki/IRC

I18n IRC meeting

• #openstack-meeting at 07:00 / 13:00 UTC (alternate) Thursday
• More information:

https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting

DOCUMENTATION

Project Update, OpenStack Summit Vancouver

May 2018

Mission statement

The documentation team provides guidance, assistance, tooling, and style guides enabling OpenStack project teams to produce consistent, accurate, and high-quality documentation.

➡Migrated content to project team repos. ➡Updated docs site structure and retention policy. ➡Added new guides under the Docs umbrella project. ➡Continued improving our docs toolchain.

During the past two cycles...

➡Since Pike: A new unified structure for projects’ documentation. ➡https://docs.openstack.org/doc-contrib-guide/project-guides.html ➡docs.openstack.org/$project-name/$series/

• install/
• contributor/
• configuration/
• cli/
• admin/
• user/
• reference/

The migration of project documentation

➡Completed in Queens ➡http://specs.openstack.org/openstack/docs- specs/specs/queens/retention-policy.html ➡Stop deleting content from the docs site based on the content’s age. ➡Mitaka content was restored. ➡No support or bug fixes for the content will be provided.

Updated retention policy

➡The general guide to contributing to OpenStack: https://git.openstack.org/cgit/openstack/contributor-guide ➡Documentation for suggested combinations of OpenStack components: https://git.openstack.org/cgit/openstack/constellations

New guides under the Docs umbrella project

➡The new Project Testing Interface for building docs: https://docs.openstack.org/pbr/latest/user/using.html#pbr-setup-cfg ➡Automating configuration and CLI reference documentation with Sphinx extensions, and more: https://docs.openstack.org/doc-contrib-guide/doc-tools/scripts.html

Improved docs toolchain

How to give feedback?

➡Bugs @ Launchpad.net:

• Project teams
• openstack-manuals and other docs repos

➡Mailing lists:

• openstack-dev

➡IRC:

• openstack-doc @ Freenode

How to contribute?

Documentation Contributor Guide → Quickstart ➡https://docs.openstack.org/doc-contrib-guide/quickstart.html

@OpenStack

Q&A

Thank you!

• penstack
• penstack

OpenStackFoundation