 Hello, welcome to the Dockside in project update session here in Berlin, Germany. Some few words about the summit here. It's good to be here. It took at least three years from the proposal of the summit for the venue here in Berlin to the realization 2018. We had one year planning phase to make the summit to a very unique event. We had the hackathon last weekend to bring the people together and have some fun with hacking. We had the pub crawl last night, which you have hopefully enjoyed. So it's good to be here all with you 29 years after the fall of the wall. Without that, it wouldn't be possible that we all stay here together in the city cube. So please pay attention for the poster exhibition in the lunchroom on level one, which we have already prepared as the team for you and where you can see what happened since 1961 in Berlin. So now I switch over to the 2018 project update session, what had happened in the last release. So a short agenda, introduction of the 2018 team, some facts about Rocky, introduction of the project translation, some news about the translation check side, the goals for the Stein release and what happened in Stein in the first weeks. I'm Frank Luecker, technology manager at Cloud Applications at Deutsche Telekom. I'm the project team lead in the I-18 team, also the team member of the German translation team. Also, I worked as a doc score member in the documentation team, participant in different working groups and special user groups. I'm also the founder of the Cloud Kindergarten in the past. Some explanations about the work of our team. We have a mission statement. The mission statement is to make OpenStack accessible to people of all language backgrounds. We had this session before from the colleagues from Kölner. They translated documentation stuff from Chinese to English and in the other round. And that's also what we make in our team. Not only for the software, also for the documentation, or we had also things in the last cycle with some white paper translation like edge computing white paper or the container white paper. Some facts in Rocky. We experienced or counted some fewer numbers in the different KPIs. 64 modules were touched in that release. To compare to the Queen's release, minus of 27%, we're supporting 14 languages in Rocky and we have in Rocky 38 active translators. There are also big clots of translators, but there are almost 38 people there. And we work with the support of seven companies. Just to mention again, the Iating Guide, which we have, if you want to start, it's a good point to going there. It's on docs.org. Some highlights. There are how to start for contributing as a translator in OpenStack. It's explained how to join a language team, how to handle translation backs and explanation of our toolings and our infrastructure. There's also a PDL guide since the last cycle inside. If you're interested to be the next PDL, then you have to go to this guide. What we do about the releases is also explained there. This guide is also translatable and available in six languages. The main thing from the last cycle, also in this one, is the project translation. Maybe as you heard that the documentation for the project is moved out from the central place more in the project wayposts. And so we start with an early bird with three projects to translate the documentation of the OpenStack Ansible project of the OpenStack Helm and documentation of the horizon. We had good progress in all main languages in the different books like the user guide or the admin guide and the developer guide. And it's a little bit outdated. We work on build and publishing jobs because it's since few days already published. We see this in one of the next slides. The next, our translation check site. We have a check site where you can see in this picture also the horizon dashboard that works with fetch of the translated swings from the different projects in horizon and build and horizon dashboard on the fly with the new translated words and then you can check, make the sense in this menu or in this tab if you choose different words for different phrases. We have an official sponsorship of the TataCom for hosting this project. So it should be already available. And in the last cycle we had also some improvements and enhancements. So there are more modules inside which is shown on the dashboard. And the last thing we start with, let's encrypt support for the OpenStack Ansible project. So it's more like a cross project between different teams. Our goals for the Stein release, continue with project doc translation. We had, as you heard, three early bird projects. Of course, there are much more and we have to decide or to pre-arise which project on the next end, next in. The next idea is also the storyboards translation. The storyboard, maybe you heard it also on the summit, it becomes more attention on different points. It's momentary only available in English. And we want to start this also supporting this in different languages. And the last point also, we started this year some journeys to different OpenStack days in Europe and to acquire new language team members. So that we spread this more and more languages but also could put more people in language team, for example, also here in German. But I talked already about project doc translation. If you have, for example, in German our own landing page, it's in docs. There you can find, for example, the project doc translation and then OpenStack Ansible Documentation. And there's the link that the slides will be shared later on the menu page. Another thing also around the globe and the Korean translation, they had also a kind of meetup in Korea and translated with very many contributors, lots of things that is mentioned here. 18,695 words were translated in a very short time. I think this was one or two days for a meetup. And it's a very good progress. So the last thing also mentioned of the project doc translation and the comment Berlin, yeah. Some summaries we have our own mailing list for the IEDN team. We have our own IRC channel, OpenStack minus IEDN. And we have also an office hour weekly on Thursday at different times. If you have questions or interest, then can you join? So and then I would hand over to Petar for the documentation team. Thank you, Frank. So I am Petar Kovalsh. I work for Red Hat in the documentation department. And in OpenStack land, I've been the documentation in PTL since Queen's So joined the OpenStack community a little bit earlier than in Mitaka. But in recent years, our cycle is mostly leading the docs community. So this is our mission statement. Back in Pyke, we made the biggest change probably in the history of the documentation community in OpenStack. In that since we unfortunately lost many people, 80% of the team, we had to reorganize, we had to refocus from actually writing content to providing assistance to other parts of the community in writing content. So by assistance, I mean maintenance documentation infrastructure, maintaining the documentation tool in helping with the content organization, maintaining guidelines, style guide, glossaries, resources like that. But then again, we don't really have documentation writers on the team anymore. So it's mostly developers, it's mostly people interested in infrastructure. So it is now the role of individual project teams to develop content, to own their own content for their own project basically. The fact that we transferred the ownership of the project documentation to project teams is tied to the unified structure. We'll talk about it in the next slide. But this probably been the main work now done in the last two cycles. More recently, one of the last remaining pieces that we still had under let's say owned by our team was the operators documentation. There was a session earlier today in the other building with people interested in the operation documentation. So they set up their own team that the operators community set up their own team that now owns the operation guides. This is the high availability guide, architecture design guide, and the operations guide. So the work on those documents got restarted. And we hope to see some improvements there with the more streamlined workflow that will hopefully work better for the guides and for the guides who are interested in working on them from the operators community. So this is the unified structure that now project teams use. So projects like Keystone Nova, they all have the documentation in the tree organized per basic categories or groups, admin, installation, reference documentation, things like that. We also plan on migrating potentially no API documentation, maybe a list notes into the tree so that everything will be under docs slash something. With the exception of the formal documents for operators that I already spoke about, which are in their own repos now, they are migrating to their own repos. We used to have or we still have a big documentation repository called OpenStackManuals when we used to host all the formal guides. But now, as we gradually move the content out to other places, that repo now serves more as a place where we build the doc site and then we host the configuration for project guides. There are also changes happening in the documentation tools to change. So apart from the minor improvements over here and there, we also now accept patches from projects in a strategic focus areas for them to be able to reuse the documentation to change outside of OpenStack or outside of the official OpenStack documentation site. So if they, let's say, want to set up a third party documentation site using the Sphinx-based tool chain, probably tweaking the theme a little bit with their own branding. It's all open source. It's all released out there, but we now made a decision to officially accept the third party changes to the tooling, like, for example, to the theme package, OpenStackDocs theme, so that communities like StarringX can quickly deploy the tweaks without forking anything or maintaining some downstream patches. So as I said, we are now a community of people who basically are more like gatekeepers, basically, for the whole OpenStack community, but we are still a single team, and you can still reach out to us. We have bugs on Launchpad, so if you see anything related to the doc site, basic navigation that is not specific to the content of an individual project, you can file a bug against OpenStackManuals, the old big report that we still have. We don't have our own mailing list, so we use the main OpenStack developer mailing list for discussions. When we want to discuss something documentation-specific, we use the doc stack in SubjectLine so that people can quickly identify the topics related to general documentation questions, and we do have our own IRC channel OpenStackDocs on a free note. So for a quick question about things or for a quick question about how to set up project documentation for your project, how to do things like formatting, style questions, it's probably best to just ping the channel. Then writing an email. People are usually there and responsive. I talked about the guidelines, so the main guideline document will be the documentation, Contribute to Guide, there is a section, a quick start section that can get you started, it explains the basics of the documentation workflow that follows the code workflow. So we use Garrett, we use the same tools as when you submit code patches. This guidelines document also contains the style, stuff and other information related to it. So that will be it. We have another session later today. It is the very last session of the summit, so you surely want to come and join us at 5.10, I think on this floor. It will be a documentation and translation on the boarding session. So if you have a specific question, if you want to just join the fun, help with something, we are looking for, for example, designers, people interested in side design, because we have many ideas on how to improve the dock side, but we don't always have the skill sets, right? So anything related to documentation and translation, you are more than welcome to come join us at 5.10 p.m. today. So with that, we would like to thank you, and if you have any questions or just lunchtime. Okay, thank you.