Loading…

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Design Summit [clear filter]
Monday, April 15
 

9:50am

Design Summit 101

Is this your first OpenStack summit? Unlike most conferences, you are invited to participate and play an active role. But... where to start? The rationale and the organization that allows such a unique collaborative design will be explained. This is your chance to get answers and get the best of it!

During this session we will let the attendants know some details about the summit, including who will be attending, different tracks and purposes, which sessions/talks are the most suitable for beginners and how they can participate. This short introduction will be followed by a a lively presentation of the most common situations and how to behave when facing them. It will be a miniature experience of a first participation to the summit.


Speakers
avatar for Victoria Martínez de la Cruz

Victoria Martínez de la Cruz

Software engineer at Red Hat, Red Hat
Victoria is a software developer at Red Hat and core member of Trove and Zaqar projects. She is a former GNOME Outreach Program for Women intern and Google Summer of Code intern. She is FOSS passionate and loves to help newcomers to get involved with OpenStack.
avatar for Loïc Dachary

Loïc Dachary

Developer, SecureDrop
Loïc Dachary has been involved with the Free Software Movement since 1987, when he started distributing GNU tapes to the general public. In 2017 he became a core developer for SecureDrop to help journalists communicate with their sources securily and anonymously. In the past de... Read More →


Monday April 15, 2013 9:50am - 10:30am
B119

11:00am

Restructure documentation
The original documentation layout for OpenStack was designed a couple of years ago. We have created a lot of documentation, and learnt much about how our various users interact with it. We now also have a new book: the OpenStack Operations Guide. Due to these issues, we should restructure the documentation for greatest effectiveness.

This should address bugs like:

https://bugs.launchpad.net/openstack-manuals/+bug/1110137
#1110137 "running openstack" guide is exhaustive to the point of being past useful


Blueprint:
https://blueprints.launchpad.net/openstack-manuals/+spec/restructure-documentation

Fledgling ideas on the wiki:
https://wiki.openstack.org/wiki/Blueprint-restructure-documentation

(Session proposed by Tom Fifield)


Monday April 15, 2013 11:00am - 11:40am
B119

11:50am

Review Operations Manual and Plan Future Work
Now that we have an Operations Manual at http://openstack.booktype.pro/openstack-operations-guide/ I'd like to discuss it's current state and how we'd like to work on it. Covers these blueprints:
https://blueprints.launchpad.net/openstack-manuals/+spec/openstack-operations-manual
https://blueprints.launchpad.net/openstack-manuals/+spec/deployment-template

(Session proposed by Anne Gentle)


Monday April 15, 2013 11:50am - 12:30pm
B119

1:50pm

Translation management enhancement
1. Role based translation management

The access to OpenStack in Transifex is set as "Free for all". Any logged-in (registered) user can submit translations to it. Git review is used to review the translation. The current solution has some disadvantages:
Git reviewers might not understand non-English languages;
Even we can invite some non-English speakers to review the patch, the feedback of reviewers are not easily gotten by translators. The "Free to all" allows any registered user to upload a PO file with his translations to Transifex, which might cause regressions.

Setting limited access to OpenStack project in Transifex may be better. After changing to limited access, there will be a team for each language. There are three different roles in the translation management: translators, reviewers and coordinators.

We need to discuss:
- The requirements of a coordinator. The coordinators are the lead of a translation team. They are responsible for the translation team set up and the control of quality and progress.
- How to gather groups around with permissions the way translators want?`

2. how to leverage professional translations?

Since some companies start the productization of OpenStack, they may generate professional translation assets, both for messages and documents. If the companies want to contribute these translations, how to handle the relationship between community translation and professional translation?

Possible ways:
- Use the professional translation as translation memories
- Use the professional translation instead of community translation
- Anything else?

Which one is the best way?

(Session proposed by Ying Chun Guo)


Monday April 15, 2013 1:50pm - 2:30pm
B119

2:40pm

Documentation for Newly Integrated Projects
The Ceilometer and Heat projects have recently become integrated projects under the OpenStack umbrella. Both teams have a combined goal of starting to work more closely with the documentation team, now that we're official. I am proposing this session to ask for help in getting up to speed on doc processes, etc. as well as for us to discuss what documentation is already done.

(Session proposed by Doug Hellmann)


Monday April 15, 2013 2:40pm - 3:20pm
B119