 Thank you so much for coming to How to Localize Kubernetes Documentation. We call this a guide for everyone because this is really a really 101 session on A, what localization is, but also how you can get started in helping participating localization of the Kubernetes docs. To get started, I'd like to introduce ourselves. Actually Divya, please take it away. Okay. We are only some of the co-chairs of SIGDocs because we couldn't obviously get the entire SIG here. I'm Divya and I work as a senior technical advance listed SUSE, and most of the time I'm pretty much on the SIGDocs channel as well. I'm one of the co-chair of SIGDocs. Natalie, do you want to go ahead? Yes. I am also one of the co-chairs of SIGDocs. Currently just hanging out in my home, not working on anything else right now, but that might change in the future. As a co-chair of SIGDocs, Divya and myself and our one missing co-chair who has a talk at exactly the same time in a different SIG, which is Ray Lajano, the three of us helped to organize a lot of the process and admin and a lot of the technical approvals required around what we do around docs. For those who aren't familiar with SIGDocs, we own the Kubernetes website and all of the written words that you see there, not only in English, but as you'll soon find out in all of the other languages that we have the docs available into. Just a second, I'd also like to give a shout out to our technical leads who are not featured here, unfortunately, because we have quite a few of them. There are a bunch of technical leads and localization leads, and we have a whole team that manages this. It's not just us three. We are the administrative heads, but there are a lot of other heads in the room too. Great. To get started today, we want to go through just quickly what you're about to learn. First, what is localization? That's something that I like to look at this because we talk about translation, but it's more than that, so we'll go into that in a second. We'll go into how you can start a localization, and they'll also be looking at what localizations exist and how you can contribute to those that exist currently today. English is a localization too. I mean, it's the default language for our docs, but at the same time, it's also somewhere where you can get started and take part as well. Finally, we'll just summarize everything we've just said and give you a quick rundown of where you can find us so that if you've got any questions or want to get started, you'll know where to go. Okay. What is localization? Firstly, I want to point out that all of the flags that I've put on the screen in front of you is actually all of the languages that we have our docs translated into. We're going to go into a bit of a list of those later on. But localization is the actor translating and maintaining the documentation that we have for Kubernetes into your native language. The word native language is really important here because we really do rely on contributors who know how to possibly translate a term that may actually have many words that could be used, many phrases that could be used in a certain translation. We want our docs, which are used by people all around the world, to actually learn about and use Kubernetes. We need them to be as accurate, technically accurate, and then language-wise accurate as possible. So localization really is about doing translating and maintaining docs in your native language. Kubernetes itself is a global project. It's a global project that we want users from all around the world to be contributing to using and helping to maintain. And so we find it really important to have docs in the languages that folks can access. And fortunately, I was about to use the other word, but fortunately, what that means is that we need a community of those native speakers to actually help us maintain and create those docs so that they can have a better time and users around them can have a better time in adopting and learning Kubernetes. So localization is not just about translation. It's about community. It's about doing a lot of work, but then it's also about helping users adopt and welcoming them into your native community as well. So it really is more than just making the words different, and that's why we really focus on localization as a term, as opposed to merely translation. So we this year specifically had a lot of interest in terms of wanting to start new localizations. We've got communities from Bulgaria. We have communities who speak Tamil. We have communities who speak Turkish, who are really, really interested in getting docs in their language. And that's just three of the interesting docs groups that are currently in the process of helping to translate documentation right now that are really interested. But we often get this question about how to get started. And I mentioned previously the word community. And that is really the first step in terms of getting started with a localization branch and launch. We need folks who are not only gonna work together, but actually gonna approve each other stuff. Before I principle, we really use this in docs as well. You need at least two people who can help getting community started so that you can work together and start those translations. And finding community can be really, let's say, intimidating or hard. And so we, as SIG docs, have started the localization sub-project to really help with this, where you can come to the folks who lead the sub-project. You can speak to them about your questions. We have monthly meetings, which I'll have on the screen later, so that you know where you can gather to actually help get started with community. We don't want you to do it alone, but we want to support you as much as possible, but also give you as much autonomy so that you can actually get started with the work and feel like you're owning those parts of the docs that you're helping to translate and maintain. So the first step is finding community. It doesn't just take a day or two. This is the tough part. We can never put a timeline on this, is getting folks who wanna be involved and then trying to get them involved consistently. It's a problem challenge, I should say, that we constantly have, even with the English docs. So it's something that we also wanna support you with too. So getting started with community is our first step. Next, what we wanna do is we want you to get involved in the localization meetings as well. We want you to actually, if we say you wanna create community, then we want you to already join the one that exists. We think that that's a really logical next step. And that community meets monthly. I've got it on the screen here. The first Monday of every month at 1500 UTC, we try and use a time zone that can be translated for everyone every place in the world. And we understand that you're not always going to be available for those meetings. So we are very big on async communication as well. And we'll have later the channel listed for where you can join this. But joining our mailing list, of which we've got linked in the slides and we'll upload them to Shed afterwards. So you'll have those links available. Joining the mailing list, you'll get the invitation to those meetings so that you'll know they're on your calendar when to join. Once you've got the invite, the meeting agenda is open. You can add anything to the agenda to come and chat with us whether it's questions about getting started, who you want to lean on to get help with certain process steps. That is the place to get started to. So finding community one, joining our meetings two. What else do you need to get started with a localization? Now this is a really, really important step. We have a lot of interested people who want to get started with humanities. And they think localization in terms of creating docs is the first step to do that. But we, as I mentioned, we have an interesting challenge around consistency of contribution with not just docs, but throughout the project. And it's something that open source projects in general are constantly looking at helping to try and drive. And so what we want to do is make sure that folks who are starting a localization, which is putting your hand up to maintain a set of documentation that is only readable by people who speak that native language and read it, are contributing to the project already and possibly in a consistent way, consistent in your frame of interpretation of course. And so we want you to be Kubernetes org members already before you can start the localization. The other reason too, actually, is because to be able to approve PRs, you need that access. So it's kind of like a bit of a forcing function, but in a good way, because we want you to own those localizations and we want you to own that work. But we also want you to show that you're contributing already so we can trust you with that ownership. And you've already kind of shown that by contributing to the project in some way already. And the great ways that you can contribute to some of the localizations first as that contribution step to show that you're ready to take on localization on your own. So we've linked here how you can become a Kubernetes org member. TLDR is your sponsored by two folks in the community, us and SIGDocs often sponsor people and we're happy to get you to come into the channel and link the PRs that you've done so that we can put that sponsorship request in. And then you're ready to go. So that's the third step really that we wanted to highlight here about what you need to do to start. We want interest, community, we want your involvement, and then we want your contributions already. We really wanna see you contributing to the project in any way possible so that we can hand over that trust of owning a localization. All right, I'm almost done, I promise. The last little part here we've got in planning the localization law. It's a couple more process steps. So localizations, we use the ISO 6391 standard for our country codes, language code, should I say. And so you'll see in the channels that will list very soon the way to find your code. We've linked here, but as an example, English is EN, Chinese is ZH, Ukrainian is UK. Hindi. Hindi, H-I, thank you. And so we use those codes as a way to create the branches that we need to create, but also for the localization Slack channels too. And so once you've found community, where can you gather? We can get you to create a Slack channel with your right code and you can get your community gathered in that place so you can type and speak in your native language if you wish there. You can really kind of get yourself started and organized as well. And we also want you to be translating or the minimum required content before we get your localization published. That's the other last kind of process step that we have. It's where we really say, hey, if you want to show your community how to use Kubernetes, this is the minimum docs that will be required to read and know about. And one of those very importantly is the code of conduct. So we've got that there too. That's another area of translation that we find really, really important. Do you want to add anything before I move on? No, I think that's pretty much it. All right, so we mentioned that Kubernetes is a really, really big global diverse project. The SIG docs leadership even is diverse. The three of us are in three different time zones. Really surprised that we're awake together, actually. Yes. That's because we are in Amsterdam. That's true, very, very, very true. But we have someone on the West Coast of the US. I'm in Europe, Divya's in India. So we rely a lot on Async and we rely a lot on really living the values of the globality and diversity. So that means we have a lot of localizations in existence right now as a representation of that. And I'd like to hand over to Divya to tell you more. Thank you. So you may ask how many number of localizations do we have currently? We have 14 of them, one of which actually went live I think last year, we'll be delving a bit into Hindi. The localization that went live last year after a lot of efforts because I believe Natalie actually mentioned before, right, that finding your community, finding your tribe to build a localization is one of the most challenging aspects that you could go through while actually starting up a localization. So these are the current localizations that are live. We have a lot of interest in Turkish Tamil and Bulgarian localizations. And we hope to get them out of the door sooner rather than later. But again, finding your community is really hard. So that being said, how do you contribute to existing localizations? Because you cannot start your own localization without being an existing Kubernetes org member. So why not actually become a Kubernetes org member by contributing to an existing localization? And English is one of them. So if you are already familiar with Kubernetes or if you're even just getting started, we really appreciate your points of view on how we could make the documentation better, whether that's clarifying how a particular concept is explained or whether that's making a minor typo edit. It's highly appreciated that you contribute to an existing localization first, get that Kubernetes org membership, and then if you want to sign up to start your own localization. But before all this starts up, you obviously need to sign the Contributor License Agreement. So that's the very first step. And then you go ahead and find your community. So there are Slack channels existing for live localizations and localizations that are doing the work for going live. And you can find them by their Slack channel name that is scuba net ease dash docs dash the code that we just saw a couple of slides back. Then the next step is to join the SIG docs and the SIG docs localization mailing lists and attend the monthly localization meetings because those are really, really good avenues to actually clarify your doubts because it's a group of folks who are already working on the same stuff. So it's easier for them to clarify and answer your queries. And I spoke about Hindi localization and how we went live last year. So let's have a little bit of a look at that. So it's our very first localization in the Dev Nagri script. And it was launched last year on the August 31st. We had a lot of roadblocks getting this out of the door initially because this was a localization that laid dormant before even I joined the project, which was in 2020, three years before. So when I joined in, this was one of the first Slack channels I remember joining because it had the Hindi ISO code and I was like, but there's nobody here. So what happened was I ended up when the chance came and when the people actually came up to ask me whether I'd be willing to actually help lead, not lead, but help form a community or help form the tribe around Hindi docs. I was like, great. It's absolutely awesome that we have something like that. So we started the efforts, I think in late 2021 that so the efforts culminated and they're still ongoing because docs are never done. They update every release cycle and unfortunately or fortunately for us, tracking those changes is a lot of manual effort currently. So people leading the localization are required to actively track the docs that change per cycle and put out issues for them, ask contributors to come and chip in and this is an ongoing effort. It doesn't really stop at the localization going live. So this is a bit about the Hindi localization and just as an FII, every localization in our documentation website has a different process. Like the process that we follow at the Hindi localization is not the same process that the Chinese or the Korean localizations follow. So we give that autonomy to actually follow whatever fits your community best as a translation medium. A huge shout out to the other members of the leadership team within the Kubernetes Hindi localization, Anubhav is a fellow approver and if you were wondering if there was any way that we could demonstrate how the contribution ladder works in the localization, Vithal and Bishal recently joined the reviewers team on the Hindi localization after demonstrating consistent efforts. So they are really, really good examples of how you embody the concept of actually doing the work before you're given the role. So those two are like the huge shout outs I'd like to give here because they've been very, very instrumental in getting a lot of the stuff updated and approved and out of door after the localization went live. So that's a shout out from my side. And we are now at the real end of our presentation and we'd like to actually look at some of the common FAQs that are thrown away mostly on the maintainer channel. So the very first one is can you become a Kubernetes org member with just localization efforts? So, yes. Yes, but there should be an asterisk, terms and conditions apply. And the reason this is is because we have a lot of interested folks in localization that wanna work on their localization native language but because you have to translate their minimum required content before it's live on the site, technically those contributions don't count because the PRs aren't merged to main. And so we really do need you contributing elsewhere, maybe in other localizations first, for that Kubernetes organization membership to be able to be valid before the rest of the work can kind of begin. So that's something that, yes, localization work does count but for live languages only. Yeah, a good way like I said before is to start just contributing to the English website itself because it's huge. You're bound to find some typo, some error and as much as I'd like to say that we're perfect, we not. So there will be an error, there will be a typo, there will be a grammatical error somewhere that you can find and you can contribute. You can just get started by contributing to that. And then maybe once you have sustained contribution effort, we can, you can reach out to one of us on the SIGDoc Slack channel, which we shall be demonstrating on the slides. And let us know about your contribution so that we can improve your membership. You'd definitely, you'd be surprised at how many people spell Kubernetes wrong. Yes. You can absolutely just look through the docs of the English site and find those as your first contributions, absolutely. The next one is where can I ask or who can I ask for help, really? Because the project is really huge. So the first step I would say is to post on SIGDoc's localizations. That's the Slack channel that's open for the localizations subproject on the K8 Slack. Your points of contact and I would highly recommend not DMing them because that's something that I generally face an issue with. I would highly recommend not asking your questions in private. You should generally post in public so that you are able to, you know, solve the doubts that you have, but that might just not be your doubt alone. It might be doubts that other people have to. So first would be, you know, pinging the SIGDoc's localization Slack channel. And then, you know, if there is no response for a really long amount of time, then go ahead and ping them separately. But those are the people. And if you can also cross-post to SIGDoc's, which is the Slack channel for the main doc's website, but that's, I guess, in the next slide, so of where to find us. So you can find us on the mailing list. And this is hyperlinked and will be available on Shared. So that is the reason why I've not written the link here. So you can find us on our mailing list. We also meet bi-weekly on Tuesday. It's currently at 11.30 p.m. my time. So I'm not awake, but Natalie and Ray are. So they will be available. We also host an APAC-specific call as well, but most of y'all will not be awake and probably are not gonna attend that call. So. But that is monthly as well. Yes, but that is monthly and on the fourth Wednesday of every month. And of course, these are the Slack channels, SIGDoc's localization for the localization sub-project and the main Slack channel for our SIG, that is SIGDoc's. And I guess that is pretty much it. So please scan the QR code. And if you have any questions, we'll be happy to answer them right now. Let us know if you have questions. Oh, yeah, in front. So you had mentioned that you need to be a contributor and an existing org member. Are workings where it's org membership? Do those contributions need to be in SIGDoc's? Great question. No. You can contribute to anywhere in the project. SIGDoc's does not require you to be a documentation expert to contribute to docs. The requirement in terms of localization is we want you to be a native speaker of the localization that you're owning. So that is kind of a hard requirement. And that's the requirement is you tell us and we believe you. So we're not really checking your localization credentials there, but you can be contributing to any part of the project. We have a lot of SIGs that need your help. I'm going to say a couple right now. SIGnodes, SIG CLI, SIGK, it's in front. They all need your help. SIG Auth as well, for sure. And so, and there's a lot of different ways to help too. It doesn't have to be docs based in those SIGs. It can be, especially if you're a Go developer, please come on down and help us. And you can contribute in any SIG in any way first. At most projects I know definitely need help with project management. We are also looking for help. So that is a separate discussion altogether, but yes. More questions? More questions. Going once. Okay. I think we're good. Thanks everyone for coming. Thank you. Divya did say don't DM us, but I mean for Kubernetes purposes, if we're still, I mean for the KubeCon purposes, if we're still around, you want to chat to us, that's okay. Yeah. I think is my Slack DMs are currently, you know, they're really bad in a really bad state after KubeCon. So if you want to chat, I'm like right around here. So please, please be free. My DMs may not be in a very good position after KubeCon, so that's fine. Thank you.