 Good afternoon, ladies and gentlemen. Welcome to this session. I'm Yinchuan Guo from IBM China. I have an English name, Davy. You can call me either way you like. So the gentleman's stand aside is Tom for Field. He's a community manager. He also spends many times with OpenStack, IATN team. So I will have this opportunity to have the talk with him. So I'm from OpenStack, IATN team. The mission of my team is to support OpenStack to become a globalized software. So in this talk, I will cover below questions. What is a successful global community? What have been done in OpenStack and what will be done in the future? So before I started, I will spend a little time on the background introduction. I think maybe most people, maybe most of you may understand this worth, internationalization, localization, globalization. But I will just give a short introduction to make sure we are on the same page. So internationalization is a process of designing software application to make it easily adapted with many languages and regions without any code change. So localization is a process to adapt software with specific regions and languages. So by adding some region-specific components and translating the text. So globalization is a combine of these two. So internationalization is done once when we design the software and implement the software. So localization can be done once you want the software to be adopted to a certain region. So next I will start the talk. What is a successful global community? How to make a successful global community? So I think there is no doubt that OpenStack is a global community. The picture here shows the countries with members in OpenStack Foundation in October 2013. So you see OpenStack has membership among all over the world. So next page, we also have global users. The picture here shows the WebAccess data reported on September. So you see the United States is the biggest visitor to the website. But it's only 30%. So around 70% of the visitors to the website are from the country, which don't speak English, maybe. So OpenStack also has global meetings and user groups. We all know this summit is the first summit to be hosted in outside the U.S. And the percentage among half of the attendees to the summit speaking English and half are not speaking English. So there are around maybe 70 user groups in the website now. So OpenStack has global people. So how about the content? The items I listed here are the regular content in many regular communities. So you'll see software and documents and some promotion materials. For example, our website, our newsletter release notes or something like that. And we also have some tools for community collaboration for example, the wikis and blocks. So do we need all of these contents to be globalized? What's the priority? So maybe some people can argue that OpenStack is an infrastructure level software. It's like an operation system. So people who play with OpenStack may be familiar with English, may be able to write and read in English. But to tell you the truth, I'm a well educated people in China. I have been in a U.S. company for eight years. But if you let me to choose between Chinese language, Chinese document and the English document, I will prefer Chinese document. So reading Chinese document by Chinese people is more easier to make them understandable and to save them time. So here I did an investigation of the famous software communities. So the top line are the regular contents of a community. And the first column is the well-known global communities like Ubuntu, Mozilla, LibreOffice, GNOME, MediaViki, Android. So you'll see Ubuntu is a well-globalized community. There are software and there are documents. There is a Chinese website and there is a Chinese Wiki website for Ubuntu to contain many documents and many useful information. So Ubuntu also have teams named as local community teams. Local community teams will help Ubuntu to do the local promotion and translation. So Mozilla is also a well-globalized community. The website of Mozilla supports tons of languages. So if you think about how many countries use Firefox, you may understand the situation. So the interesting is Android. Android is a platform. So actually the website of Android is not translated at all. But we all know Android can support internationalization to this application running on the Android. And the user interface and the messages are translated in Android. So based on this information, we look into this slide again. So I will mark user interface, messaging, user documents, and the website as a top priority to be translated and globalized. So developer documents, distributed messages, and the Wikis are well to help them globalize. Okay, so I will transfer to Tom to introduce what we have done. Thank you, Daisy. And Daisy has been very kind because she's given me all of the awesome slides to present because the internationalization team of OpenStack has already been quite successful thanks to her work and the work of many people around the world. So I want to run through with you some of our successes. You may have heard of the OpenStack Operations Guide, a book that was produced in a sprint style designed to handle operators to get them up to speed on how to build OpenStack clouds or operate them. This book has been fully translated into Japanese and there are a couple of other languages which are about 70% of the way translated. So right now there are people reading this book in Japanese and it's a 50,000 word book. So this was an amazing achievement of the team. However, the big success for us in the internationalization team was actually to learn about the process for translating books and how it's different from translating strings and code. For example, when you're translating a book you require a lot more context, especially if you're going through the review process to try and determine the quality of the translation. And so the Japanese team invented a system to fix some inadequacies in our tooling to enable this book to be translated and reviewed to a very high quality of language. The other one that you may have seen in the release notes is in the Havana release we've translated the dashboard into 12 different languages. And this is the work of many, many, many people around the world, some of whom worked right into the late evening before release to get these done. And it was a really successful demonstration of how for a code project we were able to create a community around certain languages and translate strings so that nowadays people can, just simply from a drop-down box, select the language that they want to interact with OpenStack in. Sorry, you need to take a photo? Okay, cool. All these slides in the video should be available online. Another success is recently OpenStack Foundation launched a site called Ask OpenStack where anyone could come and ask and answer questions about anything to do with OpenStack. And we decided to try and experiment and make a localized version of this in the Chinese language because as you saw on the statistics that Daisy presented, we have a lot of users who speak the Chinese language coming to our website. And this was actually an example where the OpenStack Internationalization team was able to join another community and help get their translation efforts up to the 100% mark or close to it so we could use their software. Perhaps one of the biggest successes and the foundation for all of these activities is the tool chain. We have a really good tool chain that enables us to go from the code into a translation system and back again. So it means that right now today, whenever someone checks in a code patch or a new document into OpenStack, it's automatically uploaded into a system that translators can then see those strings and immediately start translating. And that happens automatically with every single patch. Similarly, once the translations have been completed, the system will again automatically download those translated strings and put them back in the repository. And we've closed the loop there so that we can make translations available very quickly and we can make the strings available to be translated very quickly. And this was developed in-house mainly by Daisy and has given us a lot of flexibility to change the way that we work depending on how the developers are going. But by far the biggest success we've had is the team and the growth of the team. We have now more than 200 people involved in OpenStack translation. Some of these people may actually not be part of other parts of the OpenStack project at all and in fact are just people who enjoy translating or enjoy language. And this is one of the big differences of this team. It's actually pretty much mostly volunteer-based which makes it very different to the development team where the majority of people are actually paid to work on OpenStack. And so we're really benefiting from people who have skills in multiple languages and are able to join the translation team easily through the interface. And as a result of starting to put a bit more formality around this team and give the internationalization team a place to rest and communicate a weekly meeting, we're now translating more than 100,000 words a month which is effectively translating two copies of the operations guide every month. And that's looking to continue and increase over time. So I now want to just go quickly into a bit about what we've done this week. It's very convenient that we're the final session of the entire conference because we can talk to about the particular sessions we had in the Design Summit. We had four sessions this time in four different tracks amazingly. Translation didn't have its own track at this point but we'll talk a bit about that later. So the first one was Publishing Translated Documentation on the documentation track, specifically talking about full manuals and books rather than code strings. And we had a really robust discussion around how that works and came to the conclusion that documentation is very different to code strings and needs especially a different review process. So we're going to set up something like a staging server where partially translated documents can be viewed. So you can review translated strings in context. Similar to the model that the Japanese team used with the Operations Guide. We also had a session on the Internationalization Policy of Messages. So up until this session, every single message in the code was treated with the same priority, which means a user-facing message and a debug log message were both given the same weighting in terms of translators. We determined that actually user-facing messages should have a higher priority for translation than debug log messages and these kind of things. So we've decided to implement in Oslo a categorization of those messages, which we can use to prioritize a particular message. In addition, when it comes to translating log files, we've determined in order to make them searchable when they are translated into other languages, we need to implement a message ID system for log files. The third session we had was translation tools and scripts from the infrastructure track. This is predominantly about that tool chain we saw before that goes between the code, the translation system, and back. We looked at some of the gaps we've got right now. So we determined, thanks to Ryan over there, that our wiki already has the translate functionality enabled, which means we can easily turn that on and start translating some of the important pages on the wiki that people need. We've also determined that since TransFX is now a closed-source system, meaning we can't extend it to meet our needs, we are starting to look at the open-source alternatives and we've decided to try and work with all of the different open-source translation software to all communities to raise feature requests and try and get those to the same standard that we're having with TransFX today, eventually planning to move on to an open-source platform. And finally, just before this session, we had the Ice House release schedule and coordination session. And we're very pleased with the response from all of the project technical leads in terms of supporting the internationalization effort, giving it an appropriate amount of time for string freeze and translation to happen. We're also aiming to get better communications after the string freeze if there is a need to change a string to pipe that through the internationalization team to ensure that we have complete translations. So I now want to invite Daisy back up from the stage to explain the vision for OpenStack internationalization. So Han wants me to give you a vision of what we are going to do in the future. So for me, I'm going to focus on three items, teaming, tooling, and globalization. So we now have OpenStack IATN team, so most of the team members are translation team coordinators. We all know that internationalization is more than translation. We also want to cover the OpenStack software itself internationalization. So we would like to invite more developers to join this team, and we would like to rename our translation team, for example, maybe China translation team to China localization team. So we also would like to invite developers to join our localization team to support not only translation but also some of the localized work in OpenStack software. So as to tooling, we would like to run a translation platform to support the translation of all the staff in OpenStack community, and we will use the integration tools to do the automation integration with OpenStack infrastructures like the JIT, the website all the weekend. So as to the globalization, of course we will work on the translation, and we will do an IATN test and a report to figure out the gaps in OpenStack internationalization area. So then we will know what are missed in OpenStack. And as a follow-up of the design summit, we will enable the message IDs and separate the message into different domains. So we definitely want more people to join IATN team. So if you are developers, we warmly want you to join our team to work on OpenStack IATN. So OpenStack is a software with a great future. You can go together with this future to, you can go with this software to see how it can be, how it grows a well-globalized software. And if you are a translator, of course you want to join. If you are not good at developer, maybe you are not want to translate, but you can also join us as a tester. We also, you just need to run a laptop with your localized setting and run OpenStack and report bugs to us. So Tom will introduce the official program in OpenStack community. So during the Havana cycle OpenStack technical committee determined that there was a need to recognize projects in addition to just the projects that were producing code in some form or way. And in essence, this idea of OpenStack programs was born. So OpenStack programs are simply efforts which are essential to the completion of our mission. And our mission in OpenStack, as I've written there, is to produce the ubiquitous open-source cloud computing platform. And even if you just stop that mission there, you can see straight away that if we are going to be ubiquitous open-source cloud platform, we need to be globalized, we need to be internationalized, we need to be localized. And so I believe that during the Ice House Summit, the internationalization team will request to become an official program of OpenStack. And hopefully that will go well and we'll get the recognition that we can get most off of the internationalization team and get our own summit track, for example. We don't have to go to four different tracks to talk about what we need to. But I believe this is the final slide, Daisy, and you have the text for this, didn't you? Yeah. Yeah. So we want to keep learning, keep growing, and keep working. We've gone through a very, very dramatic change over the past six months in terms of understanding of the needs for internationalization and localization in OpenStack. We've learned a lot about review and tool chain and how to bring community together. And we want to build on that to keep that community growing, keep the momentum up, keep up with the 1,600 software developers who are working to make OpenStack successful around the world. And above all, we're practical people, so we're just going to keep working and keep doing this every day. Thank you, Tom. Sorry. Very good. I believe we now have some time for questions. Yeah. So any questions, comments, suggestions? Right. Right. Yes. Yes. We should have translated these slides into 10 different languages. That's correct. Okay. We'll upload that to TransFX after this talk. Sorry. There was another question. Yes. So we've got people which are really active in more than about 20 or 30 different countries, but there are some less active in even more countries. So yes, we welcome everyone in any kind of languages. And we've also, for example, if you look at the Spanish language, we've had some requests from our friends in Mexico to have a particular localization of Spanish for Mexico in addition to Spanish. So there's lots of flexibility and lots of options and we definitely welcome you. So I believe in Japan, you have a guy called Matoki-san and he's taken up the role of a language coordinator for Japanese. You can either approach him directly or you can just sign up yourself on the TransFX website or you can post on the mailing list introducing yourself. It's whatever is convenient for you. So some countries like Japan have a really well coordinated translation effort and translation team. Other countries just rely on people finding the website themselves and starting translations without any effort. So we can introduce you directly after the presentation, if you wish. I'm paid by IBM. We actually have already had some companies support us. IBM has contributed a significant number of translations. Friends at DGT in Vietnam have contributed a significant amount of translations. The guys at Cloud1 in France are contributing things. So we are getting bits and we're finding that, yes, having it. But I think most of the translators are working in their spare time. And it also, like for some of the languages most populous countries, for example, Napoli or maybe BASC or something like this, it will be challenging to get commercial support. But yes, you're right. We should also continue to investigate commercial support. It seems like everyone wants to sleep and or have a party. And the good news is you have 13 extra minutes to do that. We've said everything we wanted to say. Thank you so much for coming. Thank you.