 So, let's start our session and the title is how to hold upstream training in Japan and get new contributors. Here title has triple exclamation marks, okay? At first, introduce ourselves. So I'm Akishito Ino from Japan. I joined the Kubernetes community at the end of 2018 and keep on contributing to around the C-crafter life cycle and C-contributor experience also. And this dog icon is used on my guitar as me, okay? And Kaisa. And I'm Xie Zie from also from Inishi, Japan, currently working on the Japanese translation or for dashboard and website. And although I've just joined the community for only one year, but I really learned a lot and felt a lot during this whole process from our community members. And also a big thanks for my boss, Motou-san, and also Imo-san, and also other upstream training members. Thank you. And I introduced what is the Kubernetes upstream training. It also called new contributor workshop on the Kubernetes upstream community. In this training, the training runs two topics. And first, further is Kubernetes community, further is CIG, special interest group, further is the approver, reviewer, further is the owner's file, something like that. And second, how to start contributing to that. PR workflow on GitHub, further is you can use, where is the code at, something like that. And next, trainees exercise hands-on about progress creation to merging on sandbox repository in Kubernetes community. We explained these topics in Japanese. We held this training at public event in Japan eight times in almost three years. That's why my session title has triple exclamation marks. So I will have quadruple exclamation mark if I go the next Kubernetes session in next year. This is the event list. We held the training. You can notice about the training went on online from 2020. I think many people know the reason why. But please wait. I'll show you about the details in latter half of this session. All of these events held on Japan and mainly focused on cloud native fields. So trainees is highly motivated to contribute to Kubernetes community, I think. We share our experiences about the training to upstream community two times. First on 2019 and next on 2022. Yes, that was almost one month ago. Kaisen co-presenter in this session presented on Kubernetes contributor summit to 2022 Detroit. And today, there are many Kubernetes folks in this QVD also. So please feedback about this session on any channels, Twitter, Thrux, of course, face-to-face. Okay, introduction is over. We go main content. I take that on to Kaisen, please. Thank you. So now I'm going to talk about why we run the Kubernetes upstream training in Japan. So here we have to mention the reasons that prevent people from drawing our community. First, it's the language barrier. Compared with people in Europe and United States, people in Eastern countries are actually not used to speak English. However, it seems like everyone in the community communicating English and mastering English seems like the only way to better integrate into the team. And second is the cultural barrier. In community, everyone is expected to speak up actively, bring storm together and draw conclusions through this whole communication process. However, Japanese people tend to think a lot before they speak and therefore may miss the opportunity to state their opinion. And this leads them to think more. It's kind of a vicious cycle that will cause them to be more and more afraid to speak up. And that's why we hold this training. We want to encourage more and more people to get involved into our community. For those who are interested but don't know where to start, our trainings offer an opportunity to walk them through the whole process of making contributions. And at the end of the day, most of them will go home with their very first full request. And we also want to make friends and solve problems related to Kubernetes in Japan in the language we are used to. And the most important part is we want to deliver the following message is that even if you are not fluent in English, you can say anything. If everyone in community is very kind, so don't be afraid to start. And next is about how to hold this training. You might sound familiar since you probably already doing something similar every day. So there are five steps to go. First, you communicate with CIG contributor experience folks on Slack in advance. Next, prepare the practice environment where people can make contributions during the training without affect other Kubernetes projects. And we always do this by creating a directory for our training or an area in Kubernetes CIG slash contributor playground report through with support request. Then there are some works about organizing trainers. Trainers should be one of the Kubernetes CIG organization members so that we can review and merge trainees for request. So we have to add trainers into the owner's file under our training directory. And after that, we prepare our training text and share it with the trainees in advance. We have some improvements and updates in our contents right now and we are going to share it in the latter slides. At last, inform trainees about the homework. The trainees also have some homeworks to do. For example, they need to create a GitHub account and install it in their laptop. Try to get used to it if they have the time and clone the playground repository I just mentioned. And join the official Kubernetes Slack. Thank you, Kaisan. And here, I would like to share the improvements in Japanese training. There are some accesses as it's about time, content, organize the training, and others. The first is a topic about time. There are a lot of things we want to share. But the truth is, we don't have much of time. In our case, the training is half a day, about four or five hours. So we have to make some cutbacks. For example, we can take hands-on session for Kubernetes, trash Kubernetes modification, building, and testing process. But those are very time-consuming. For such contents, we have to give up the hands-on session and only introduce it briefly. The practical session we can offer now is to create pro-request in contributor playground repository. That's the sandbox repository in the Kubernetes community. On our first two trainings in 2019, the training was held within the main event. But some people were unable to participate in our training, because there was a lot of overlap with other sessions. So we changed the training to a crooked event. Next topic about content. Prepare training text in our language, and share it with trainees in advance. In our case, since we basically speak Japanese at our event, Kubernetes upstream training. Or Kubernetes has a SIG. Or Kubernetes community has inclusive with better than exclusive, like that. But in order to help the trainee integrate better into Kubernetes community in the future, we also some tips for English communication. And the first one is frequent phrases. I'm facing same issue, and did, did, needs, and what do you think, and shrug. And the second is emoji. This is great for non-native English speakers, I think, because we need to have a few time for creating English phrases, even if there is small things. We can express our emotion, for example, plus one, okay, congratulations. Just one click, thanks to great emoji culture. Also there are requests that they would like to know the actual state of development. So we added introduction to the development environment of Kube Spray, Website, and Dashboard, which is actively area of the trainers. We especially think that documentation and translations are a good place to start contributing. So we emphasize that in our training. Actually we know some trainees who contribute to translate. Please very appreciate. Next, CLA, Contributor License Agreement. The CLA sign was a pitfall in our trainings, because it is two complex steps. But after easy CLA introduced, trainees become to sign CLA on easy way. That's truly easy, literally. We updated that document for the trainees to use easy CLA sign process. Thanks for the Kubernetes community folks, especially a safe contributor experience who introduced easy CLA this year. Trainee may not be ready for their corporate CLA right away. They need to coordinate with their company. So we introduced them individual CLA at first. I would like to introduce the improvements about the communication channel. First we prepare Slack channel and use them in our training. JP Dev channel is for asking technical help and for review request. And JP Mentoring is for asking help about community activities. To motivate trainees, we asked trainees to express their enthusiasm in advance on Slack channel. It will be first step to join Kubernetes community. We took photos and made it public, so that they are aware that they became a member of the community. And for about a week after the training, our follow-up is carried out until the trainees' progress is merged. Also, we made video and published to YouTube. Then created ad-hoc directory. So the trainee can take training on demand style. And more, we tackle to the COVID-19 situation. Back in 2020, the situation is so bad that people can't leave their homes. So we have no choice but to hold our events online. Actually, to be honest, we were worried at first because we don't have any experiences as an online trainer. However, we have to do it online. So we've been practicing the ingenuity and improvement that we can think of. At that time, we could only prepare a Zoom meeting, so we use it. As of now, we know that we have a few options to connect with our audience in Zoom. That is, meeting, webinar, and a breakout room. With the webinar, when attendees want to share their screen with us, we have to take a few extra steps, like raising hand and promoting to the panelist. It can take a five before the trainee share it. Also, breakout rooms require a few extra steps to share with all of the attendees. We found that cross-interaction is possible in the meeting style, then in the webinar and breakout room. Currently, various functions have been added to Zoom, but we do not want to raise the barriers to the trainees. So we continue to use only the basic meeting functions. The key here is to create an atmosphere where everyone can talk and chat. And we make all training resources available for the trainees' preparation. This allows trainees to refer to the material from our previous event and also to review the context anytime they want after the event. As trainees, our workload is also reduced because of it. Here are some pros and cons. And the pros first, no travel expenses. The first pros is that there are no travel expenses. It means that the barriers to participate is rewards. People with limited travel budget like students can participate. And next, location and the situation free. Also, trainees can participate in their own location and situation. There is a trainee who doesn't have a quiet room, so participate from his car. Even people who are raising child children could participate. Next, physical and time-wise friendly. People who are not strong in physical can participate. These are very helpful in expanding our community. Also, these are same for trainees. The above advantages are also of right to us. No need to prepare the venue. The event leader does not need to arrange the venue for this online training. Share everything with each other instantly. Many useful online tools help sharing everything with everyone each other instantly. More practical for contributors. And we found that online training is more practical for contributors. We are a contribute to Kubernetes community by online communication. The online training is the same model. These items are pros, but sometimes we want to meet people in person, communicate with them in their real resolution and feel them warmth. I think this is just one cons. Next, stats and practical tips. A maximum of 40 trainees were allowed. Many trainees came to the online training than in person. The trainers were getting busy handling a lot of pre-request in the training. However, during that time, the trainees tried to various pro commands, commented on other trainees' pre-request and had various experiences. Also, we could see interaction between trainees. The percentage of pre-request merged was significantly higher online than in person. The trainees who participate online and in a co-created event, they have clearly positive intention. That's the reason of these results, I think. And here are practical tips. Motivate, encourage and support trainees in the local language. Online training is more practical for contribution. Share resources in the open source model. Use actual events. Use actual environments. Training on GitHub. And lastly, Future France. Let me introduce our Future France. As you can see on the screen, Okinawa Open Days 2022 will be held in a hybrid environment, which is new challenge for us. We would like to share how the training in hybrid goes on and improvements if we get a chance. And in order to make our training more and more helpful, we are also constantly looking for new ideas. For example, our training slides are outdated, so we should keep up with content on Kubernetes.dev. One of the problems we are facing right now is our trainers all come from the same company. I really appreciate and welcome if Kubernetes project contributors from other organizations can join us as trainers. We are also planning to raise up some business-friendly projects or issues for our trainees. So they won't struggle so much with how to get started and will be more likely to keep contributing. And we are constantly looking for new ideas to improve our training. Finally, I would like to say big thanks. Thanks for the contributing experiences, folks, and we have to contact on track in advance. Thanks so much for the assistance we are able to hold the training successfully in the previous years under their kindly help. And also big thanks to the event organizers who invited us. It's all from us. Thanks. Arigato gozaimashita. Thank you for your great job and presentation and I have two questions. One, what is your value or purpose of holding upstream training for your business and how many trainers continue to contribute? Thank you. You have two questions, I think. And the first one, what is the business value of our companies, right? Yeah, our company uses a lot of OSS in production products. So we need to make OSS community have more diversity and more sustainability. That's why we're holding training in Japan, I think. And the second one is how many trainers continue to contribute, right? Actually, we have the data, but we actually haven't counted them. It's not like we forget to do that. We actually do that on purpose. It's because that we think, since contributors always do make contributions at their spire time, so it's all up to them. So we can't force them to do any contributions. But yeah, I think it will take a long time. It's all about the mind-changing to make more and more people to get interested in our Kubernetes projects. So it should take a long time and we are actually currently working on it. And yeah, like the purpose I just mentioned at the former slides, at this moment, our purpose is that if there are anyone that want to get involved into the community, we are always here to help. I hope that answered your question. Thank you so much. Thank you. As a one-note maintainer, I'm very encouraged. Thank you. Thank you for the question. And any other questions? Any other questions? Thank you for your presentation. I'm currently kind of SRE position. I'm just sure that how contribute to that, those core technology of the Kubernetes, so from the user side, do you have anything, have those kind of the user side activity to contribute to the core side? Can you understand my question? I just want to confer that is that means that is there any contributors in our community working on sort of core function? From user perspective. Sorry. Thank you for the question. Thank you for the question. I think it's not the direct answer, but we have our text in our trainings, and we introduce very, very many things, so you cross-type all, so you have applications, so you have deployment or something like that. And we explain that role of each six. And I explain the trainees. So just choice and fit in your business work. And because the trainees should choose the best area of Kubernetes. Maybe close to discussion about what is best position for your trainees. Yes, try to discuss after this conference. Thank you. That is enough. Thank you so much. Thank you. Any other questions? Okay, so one more question. I think your activity is very nice to increase developer in Japan. By the way, the number of cloud-native application user in Japan is still low. This is obvious in Gartner's statistics. Could you tell what we should do to increase the business user of cloud-native applications? Do you have any ideas? It's a big issue, I think. But in my opinion, cloud-native engineer should contribute to the OSS. And because OSS user use the cloud-native technology in... Sorry. Talk after this session. Okay. Thank you very much. Thank you so much. Thank you.