Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2022, 1 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Removing Language Barriers for Spanish-speaking Professionals - Rael Garcia Arnés & Victor Morales

Description

Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Removing Language Barriers for Spanish-speaking Professionals - Rael Garcia Arnés, Red Hat & Victor Morales, Samsung Electronics

In 2020 the Apache Software Foundation Community published a survey[1] which suggests that language can be one of the major barriers to contribute to any open source project. According to some estimates[2] in Latin America, open source technologies will grow five times in the coming years. Talented professionals, students and enthusiasts demand access to documentation written in their own language. That's why the Spanish documentation team has been participating in different initiatives to help others to contribute into the translation process. During this session, it's going to be shared what the Kubernetes Spanish documentation team has been accomplished and walkthrough the process to translate and contribute to the CNCF documentation. The prime audience for this sessions are spanish-speaking professionals and enthusiasts willing to participate in improving the CNCF documentation. They will understand the workflow to submit documentation changes and help to participate in the localization process. [1] https://cwiki.apache.org/confluence/download/attachments/158865837/The%202020%20ASF%20Community%20Survey%20-%20Readout%20%281%29.pdf?api=v2 [2] http://www.latinamerica.tech/2019/11/12/latins-contribute-little-to-open-source-software/

A

uh This presentation is going to be in english, so I will try to do my best. um I know that this is a the last day of the conference. So I know most of us are very tired, so we try to make us as many as as much as interactive as possible. So the title for this presentation is removing language barriers for spanish speakers professionals, but the topic applies for any any particular language.

A

So I'm going to um in this presentation I'm going to show what we have been done in in multiple areas or air force that we have it so coming from from a place from a country where english is not the first language. um I know that is tough for for for some professionals, especially for students to start like inc participating and interacting in all technologies.

A

So what we have been trying to do is create material helping. All of them. Try to um you know, provide uh kubernetes community days, uh meetups all those things in order to help them to to be part of this. uh This movement so well, uh who I am I'm victor morales I work for samsung.

A

I have been working for several open source projects like openstack, open, nfv, onapp and now cncf. um During all these years. I have learned a few things and most of the open source guidelines applied for all of these projects, and it is not a deception so and my partner in crime which, sadly, he couldn't made it as israel raelis also um well. He works for for red hat. All his information is here, so he's very approachable, and you can be him in all the the possible ways.

A

I know that he he would be happy to to answer questions and try to help all this so well. I want to start this presentation with this quote from nikita, so which is very important, like uh they told us multiple times like uh contributing to any open source project or any particular community. It's not only about like coding, so there are multiple ways like you can um like. Provide.

A

Videos, like I mentioned, like participating in the the meetups so but something I like to highlight about this quote is: is helping so and helping has two two ways like so one of the ways is like um receiving um the help from others and the other one is providing help. So I'm going to try to cover like those those those directions in in the helping, um so I'm going to start receiving help so for receiving help. We have plenty of resources like um you can go to a star overflow. You can check that topic.

A

You can find a lot of answers and questions. So if you want to get deep on all this, you can also go to the to the projects you can review the the pr's. You can try to find information review the source code. You can do a lot of all these things. All the meetups, all the all the community meetings are recorded and posted in the in the community in the kubernetes community channel.

A

So most of those resources, given that they have impoverished, is pretty easy for for students or for someone who is not speaking english to access them and and take the time to translate them and or using tools like google translator to to to understand what what is happening so another one is like, like slack or um or participating in the in the community like uh attending the the meetings.

A

It's a little a bit tough because yeah you need that level of interaction and the last the last link here is is is one in one of those which is very interesting is like is: is the discus um kubernetes io, which uh we're we have like a particular topic where you can ask all these questions in spanish? In plain spanish, you can ask them. I have this particular question regarding how to set up kubernetes or like if I can use this setup or using.

A

um I don't know both limits things like that, so you and the idea is uh the indicator that I'm trying to say here like so there is a plenty of materials, and also it is in spanish. So I mentioned before, like slack so as the at least in in slacking kubernetes. We have these two channels so we're our spanish speakers like um answering questions and you can reach all of them and and ask any question you don't have to be.

A

You have to explain all these questions in in english, so someone is going to answer. Obviously this is an open source project. So all the people who are there like are volunteers, so just be patient about that. So, okay, but now that's that's one of the the the the things that we are receiving help from from others. So but the most important thing is like, as I mentioned before, these communities is on top of contributors. Helping people from are helping others to to participate and responding answers.

A

So what I'm going to dig now is in the process to contribute. So it's returning back what we have received. So what we use mostly in the in our presentation, is trying to explain how the kubernetes working from from top to bottom. So we start like with these different groups. So basically, we have the six, which are the special interest groups. So basically, there are multiple organizations working in a common project to a specific topic so and we have the the the working groups, which are more like a group of discussions.

A

So, for example, in my case, I participate in the cnf working group where, basically, we discuss things like how to work.

A

The best practices for defining network functions, something very interesting for telcos, and also we have the user groups which are like the the place where like doesn't fit, that doesn't the topic that doesn't fit on any of the previous ones, most of them they are like treating in that way in the public way and the communities where the communities is more like a close groups where, like they discuss more sensitive topics, which require a little bit the discretion of the the topic.

A

So just to give an example or a picture of the different um six uh working groups that we have it.

A

This is just a sample of all of them and- and those are like in different categories like like you- can navigate or like take a look so but but there is a plenty of them I mean this is just just one one sample of those things so, as you can see like the the sig dogs is over there, so basically they are focusing generic documentation and, and the team part which is part of the translation, belongs to that to that six.

A

So now that we know the different areas that where we can participate and we can contribute so it's important to mention that there is like a a contributor letter. So obviously you can you can as a as I mentioned before, so you can generate um videos or you can participate in the meetups.

A

So you can be an speaker all those these things and doesn't all of this participation doesn't require uh to sign something, but if you want to um grow in in your involvement in in the open source, so there are different stages where you can start like, for example, if you submit your patch, so you can, you need to become a member. So eventually, if you participate more like more, you can start becoming reviewer approver.

A

So the idea is to encourage anyone just to not stay in there, like, like a spectator like going and taking more responsibilities in that particular.

A

Area so well, how can you start like? Okay, I know that there is a different six and my my expertise, maybe is in network or uh in documentation. So what is next? What I have to do so the first recommendation is, is just being a spectator like just trying to understand, attend the meetings.

A

Maybe um just ask a few questions just trying to be just try to be there like, I mean it's not expecting just investing your time, just trying to understand what is happening so and probably this is something that um is very intimidating, but it is not. It is. This community is very welcome, so.

A

I provide a few resources. I mean in this case it's the list of the the six. If you want to code, there are multiple libraries of kubernetes also there's a way to to participate and the interesting of this slide. It means is mainly that the last one which described about the the the non-code contributions so, which is one of that I was mentioned before, like um like, like documentation so.

A

There is also material like especially the contribution experience seek, which is um has been developed, a lot of information about the process and all the best practices and the steps that you have to follow. There are videos regarding that, but one other important thing is like mentorship, so if you- and probably it is something that as a as a latin americans, maybe we don't have like a culture part of the culture that that there is a mentorship program that you can access to them.

A

You can raise your hand, and you can ask for for that- to participate in this. So if you know about this, it's totally free and I mean- and it doesn't require too much to to be there.

A

So what else? um Again I mean we are still in the discovery in phase like um so in in these phases. What is the recommendation going in the in the issues? Try to look for something like um with that particular labels. um So, for example, help is needed or a fierce first issue.

A

So most of the time like maintainers are trying to um require help, so they try to catalog some of the issues with those particular labels in order to to be easier for newbies to to participate and and to contribute, and also it's a good source for for uh mentors to to help mentees to to to to address all these questions. So if you are shy like and you don't want to have a mentor or for any case, so that's another way to that, you have to do it um and read the docs.

A

So we have dogs, we have dogs, so there is a lot of documentation. So um don't be. Take your time read the documentation. They haven't spent a lot of time producing all this documentation so and the positive thing I mean, if you discover that something is missing. Maybe it's time to propose a change or submit like a particular topic and documentation is a great way to start.

A

And now, regarding the different languages: okay, well, we have the documentation we we are in this particular case. We are talking about how to translate things uh from english to different languages.

A

So in the particular case for the kubernetes documentation, there is like a from the slack perspective. We have a lot of channels, so in this case we are the second one, the kubernetes dot x. So- and mainly the idea of this, this particular group is- is to try to translate the previous documentation that I mentioned in in in in spanish. So uh we have. We need a lot of people.

A

uh The documentation is constantly evolving and also it's a good way to start like getting involved in open source because, as you're going to see later, the the the contribution process is pretty much the same, like any other, any other change that we have to submit so.

A

So well, this is also another few links that we have it. So we we we have vrs, we have um slack channel, and so it's clear this is more like a call for action to participate in all all of these things. um So there are.

A

There are four things that you have to keep in mind when you are going to try to participate in the translation, so the first one is very obviously because you have to sign the the cla, the cli, so the cli there are basically two types you use you have to sign as an individual or as a part of the configuration, so don't feel overwhelmed is is just part of the process is nothing that protecting the the source code. You can read all the cli, um it's just one step.

A

The process is quite simple, so the the other thing is like, especially in the kubernetes um in the kubernetes documentation um website, you're required to at least to understand a little bit go. Google sorry, google is a platform that is used to generate the html, so the documentation is written in markdown.

A

So google is like tool that we are using to deploy the website, so this is just to know in the tooling, is not mandatory to know google or to deploy it or to use it, but it it's good to have it it's good to have it. At least that idea.

A

Obviously, a little bit con understanding about git and github, so it's very well to have it and you will require to have a at least a github account. So without all of this is not possible and the other tool that I want to also mention is netify um is: is it's not important that you know or to understand what is happening, but it is good to know that that it is used during the process and- and you you're going to see the the impact that has in in all these its contribution.

A

So well, let's go through the steps to to contribute to the documentation.

A

So the first thing that you have to do as an most of the github projects, so you have to do a fork. So what what a fork means is just basically creating a copy from the the main project into your own account. So in this case, what we are going to fork is like the kubernetes website, so we are creating a copy in our own account, and this diagram is showing, like the the workflow, that the support- or maybe you haven't, seen before, so basically, what you have to do.

A

You have to clone your changes in your local computer. So in this case a website you clone it locally. So you start working the translation.

A

I mean it doesn't care if you start like using translator, translation tools as long as you read it and you make sure that everything is covered, so you have to create a branch locally submit or create your commit, and your own branch push your your branch in your fork, um cop or copy of the project and from there you have to do a pull request.

A

So usually that's the workflow that you have to do what we have been created is uh we have created an issue in order to avoid two people working the same concept or the same page. So that's the way that we used to coordinate efforts. So before doing all these things, I encourage you to raise your hand and say well. I want to work in this particular volumes or in storage on any particular topic. In that way, we are going to make sure that no one is translating exactly the same.

A

The same website.

A

So after you made the pull request, feedback is started, especially for for reviewers, so any any any feedback that you receive you have to like going through through the same process, so maybe create a new comment in your law in your copy, submit to your own account as long as you keep the pr open. All these changes are going to be reflected, so don't frustrate because we are humans. We take time to review the things and and and obviously everybody has their own priorities and and and schedule.

A

So so don't rush and don't try to push reviewers to push to. To put your change um to to main so again, pretty much explain the the process is just using the command line, if you prefer it. So, as you can see in this case, they are was doing like a clone from the website repo.

A

So, as you notice here from riley, is doing a clone from his own copy. So in that, in that way, the pointer that you have to origin is is his his own account. So he started like doing the translation.

A

um He created a a branch in this case he's currently a local branch. He started working probably translate something normal, regular development process changes. Add those changes make a commit.

A

There are multiple best practices for doing like a a commit message. Well known, so I was encouraged to take a look so once that you have all these things. uh This is something personal I prefer like to test things locally. In this case, you can install google, if you have it. I mentioned before. Google is like tool for deploying. So all these instructions are like just a way to test all these things. I mean. I say that it's not mandatory to do to do all these things, but it is.

A

It is better if you make sure that everything is working. So if google is not in solid, you can use style and by the way there are some make instructions. So we have tried to simplify the process to to deploy things locally.

A

So once that you deploy things, you can verify that your translation, the portion that you have translated it is there if everything is okay, so far so good. So you you can push your changes to your your own branch in your repo and and from there you create the pull request. So explain it twice.

A

So this is a the most common error that you can see, especially for fierce contributors, so which means is like um that you haven't signed the ci cla so right, so um it's very simple, so you only have to do click, one click, so that is going to redirect to the to the website.

A

So from that website you have to read the the cli. I mentioned two types like individual contributor or like from corporation once that everything's go once that you have signed the the cli, the the ci process is going to trigger so, and the most important thing is here is is regarding the the last step regarding nutify.

A

So why is this important because well before going going, that most of the reviewers are not going to um take a look at your change? If everything is green, so so make sure that everything is passing once it is passing, the reviewers are going to start like taking a look, because that's the way that wait, the one way to avoid wasting time. So the last step is regarding netify. So with netify you, what you can do is you can check the or take a look of the preview of your change in a public accessible website.

A

So again, it's just making sure that all the changes are there. Everything is working as expected so and the process started. So as a our reviewers, we check the the the pr we comment. We make suggestions back and forth changes.

A

The last thing we put multiple levels in this case a gtm which means looks good to me. So usually we require like a multiple reviewers, to take a look and give and put those labels.

A

So once that everything is good, we have multiple people who has reviewed your change. It is approved.

A

The the the pr is approved, which means is, is triggering more more processes and final is merge, which, which means is your change, is going to be part of the kubernetes main branch and obviously those changes are going to be deployed in in production. So so your changes, what you have translated, is going to be as part of the main website.

A

So the last thing that I want to just talk about is another translation initiative that we have it. So this is more oriented to cncf.

A

So basically, we have two resources- or in this case the slack where we you can access to or connect contact us to us and the calendar or weekly meetings are in tuesdays, so it's 15, 30 utc.

A

So so, and we have two main other initiatives or or documents that we are trying to translate. The first one is regarding security. In this case, carol is leading this effort she is proposing- and this is not following.

A

The previous process is mainly a a google docs web document where people are putting the translation and saying all these things and the other one is a recent one, and the cncf has a glossary so and in this glossary um basically, we have multiple terms where we try to explain with uh single words the several concepts like devops or containers, or things like that. So this is also a good project or good way to start like contributing and and participate a translation.

A

So you also provide the the links for for this um in case that you want to to contribute. Any contribution is welcome so, and I guess all of this is done so thanks so.

A

So any any question any.

A

So, in your opinion to be a good contributor, what is the time commitment for it? Like we have families, we have jobs, well, yeah, it's kind of tricky question, um so probably my suggestion is um make sure that whatever that is your cadence or your piece, you can keep it because I notice that you know a lot of energy people try to contribute they the first few um weeks they they very happy with the contribution, but this is this is like a this is not a race.

A

It's a marathon so so find that guidance that you have it like. Maybe choose pick one day: maybe fridays mondays whatever that works for you and and just book that particular day. So the important thing here is like because you have to demonstrate your commitment, so no one in any open source community wants to see someone who throws the source code and leave it even if the code is amazing.

A

So so what they want to see is commitment so because, if something is broken, who is going to fix it? So um so that's probably my recommendation just choose whatever that works for you. Thinking about like um a roadmap from two two years, or something like that, so um so you would think like two two hours a week, uh one full day a week, yeah, probably maybe one or two hours per day. You can start with that one. So as long as you can see, maybe you can increase the time and say well.

A

Maybe I can spend more time on this so and also the idea of documentation is, as I said before, like this is a very low entry level. So so this opens the opportunity for like once that you manage all these things like starting contributing to to the client or, like the the different components, are going to be very easy because at least you manage the basics.

A

A

A

So, of course, I encourage you to to join to it and to a channel and participate in this and try to at least work together as a community, and we struggle with trying to find volunteers.

A

So it's it's always like a welcome to have extra hands on on this, and I will be around like for any any other thing. So thank you.