 Good afternoon. Pleasure seeing you. So we have such a wonderful crowd. To attend our session, learn, grow, and succeed in Kubernetes contributions, I'll start with a round of introduction. I feel that KubeCon is like a big gathering event of netizens, you know. We sit in front of the computer all day, and after meeting up, we don't know who is who. So I'll start with myself. My name is Zhang Wenjia. I work in Google as a software engineer. I contribute to Kubernetes SDE and GKE. Sorry for the, you know, slip of tongue. My name is Li Xiang. I contributed to several projects. SED is the first one. And later on, I participated in final permissions, Kubernetes, and Rocket, and some others. I participated and involved some of them. Let me add, Li Xiang is a modest guy. He's the founder of SED. So a lot of contributions indeed. My name is Xu Chao. I get up ideas called CZ Xu Chao. I only involved in Kubernetes. Most of them, APN, involved related projects. My name is Ren Yu Chen. I contribute to the open source Kubernetes product for storage related programs. So every time to attend KubeCon, I'm exhilarated. I used to stay in an enclosed space to do the things, to do the daily mundane concerns. But in KubeCon, we saw so many people gather from different corners of the world and offer your insight to discuss the same product, the development, the application. I think for Kubernetes as an open source product, it's because of its unique glamour that I've attracted so much wonderful crowd. So every time I learn a lot from KubeCon. And this time, it's actually the third time. And the first time was also in Shanghai last year. It was the first KubeCon in China. And then the second time was held in North America. And the third time is in Shanghai again. I'm very happy. How many of you attended the Shanghai KubeCon before the last year? I don't know if you noticed that the organizing committee has selected the timing quite well. So last year, the KubeCon was when the crab was popularizing themselves. So a lot of crabs. But this is not the most exciting thing for me. So every half a year, or every several months I attend the KubeCon. And I'll find that for the Kubernetes growth, you can see it for yourself. The growth of the community, the growth of each community member. So for some of them, they just barely knew the concept of the Kubernetes. And my boss told me to attend the KubeCon because my company is about to use it. And indeed, we find that it's very good. And we grow from a participant to a contributor to a member. So this growth are amazing. So today I'm very excited to have invited so many renowned players in this field to share in Kubernetes their story. Just now mentioned that Kubernetes as open source product exemplifies uniqueness. I'd like to throw a question to you, to our audience. For you in your software career, besides the Kubernetes, can you talk about some of the products you developed? Or compared with this product, what is the unique features of the Kubernetes? Who's about to make the start? I'll make the start. Initially, I do EBCD project. And on QS, we are from the same startup team. So we did some open system. It's also open source project. So Kubernetes compared with this open source product, it's a platform product. It's a platform project. So it integrates synchronize as many cloud resources. And this is very interesting because it's a platform. There will be many participants involved contributing to the project and making it a community driven project. Initially, people look at Kubernetes as a QS and Google involved. And because of so many cloud provider and Microsoft engaged in it and other big players. So this is a very interesting project. It's growing bigger and bigger. It's also a platform based. So it offers a lot of upstream capabilities. It's a platform for platform builders. It's also incubating some other platforms like the service mesh. It's a platform. And we can see in building a kinetic project. This is also very interesting. The Kubernetes ecosystem is further expanding a more derivative platform. So this is one of the Kubernetes biggest glamour. It attracted so many researchers to further the platform. Thank you. I have little experience in other open source projects. I can only compare some of Google's in-house products. For me, Kubernetes open source and it involves many different participants and contributors. It attracts wider attention and it requires very good communication skills to talk to different developers. And at the end of the day, the end product is good. Compared with Google's in-house products using Kubernetes, for one, there will be more languages and communication processes and it's easier for development. The environment people are discussing online while in Google, you must find the right experts to obtain good comments. That's it. Thank you. I used to database-related projects like some RIDIS. I think Kubernetes is compared with other projects. Primarily, the architecture is flexible, agile, so in terms of scalability, it's easier. It's a platform-based project. It's easier to build anything you want on the platform. As an open source project, compared with what you develop in-house, the user expectations are different and you have different teammates jointly developing the platform. There are pros and cons, of course, and I mentioned that the Kubernetes itself has some uniqueness, unique features, and Hong Chao mentioned some for you as developers. In developing a software, what is the easiest and most challenging thing when developing Kubernetes? We will start from the other way around. I think for Kubernetes, because the ecosystem is relatively mature, just like Chao has mentioned, there are a lot of contributors, lots of documentation, so it's easier. You have to search materials, literature and people. The most challenging thing is because it's scalability, it's good scalability, so some of the way are ego, so you have to address these issues. For me, it's a bit challenging. In developing the project, we met many issues related to performances. I think the most challenging thing, some has mentioned that Kubernetes has a good scalability, I was in charge of an API, so it provides scalability. Speaking of scalability, we must consider how to maintain its future, upgradable. Design-wise, it's difficult for people to reach consensus. With the simplest component, I cannot think of for now. I think it's easiest to think for a Kubernetes project. You don't need to write PBT, you don't need to report, the requirements, the specs are there. You only need to take references and find out how many are needed. It's a simple procedure. The most challenging thing is that the project itself uses many aspects. You don't know how the users are using the system. Maybe you want to improve on some aspects that you deem as worthy, as useful, but you must from a user perspective. Another point, just like Chuchang mentioned, the Kubernetes is based on the APS server. If you want to change, modify this bit, it will be very challenging. If we make the already highly scalable platform more scalable, it will be a challenge. Before the talk started, I asked several questions to understand people's whether people have started some thinking. I find that most of them are beginners. Most of them have never written code in Kubernetes. So for beginners, in fact, easy spots, they are much more than challenging spots. If they can all learn how to write open source code, there's no reason that you cannot excel. They encounter issues that you will also encounter and you can search these problems online and find your answer, like a code convention. You only need to check the open source language. Another thing, another good point, don't panic if you make mistakes because no one knows what the user cases of others look like. Even if you make mistakes, no one is concerned will be mad at you that why have you not considered it in the design phase. So for learners, for fresh beginners, it's a good way to contribute to a product like this and it will grow and your growth pathway, you will learn much quickly how to use Kubernetes compared with other products. And also there's a lot of testing involved and many people reporting bugs to you. Next, we're going to get into details. When you come to Kubernetes, what kind of contribution you can make and what kind of approach you can play in Kubernetes. I found most of you have used the Kubernetes since you have paid for the tickets unless you've used it. If you are a user of Kubernetes, you're already a contributor to it. If you have any questions about it when you're using it, for example what kind of things it failed to satisfy your need, then maybe you need to figure out yourself and you can promote an issue. You can set up an issue and ask questions there. In this way, you are helping Kubernetes to become better. Next, we can have a look at the community page here. Apart from being a user to set up any issues, what else you can do in this community. On the first level is the members of Kubernetes. Before being the members, you've already contributed before you become a member. However, it has some requirement to be a member of Kubernetes. It's not a big requirement. It's not that difficult. There are two reviewers of the sponsors to their roles in Kubernetes are reviewers. And you have made some contribution to the project. It has submitted some of the PR. Of course, there are some people who reviewed the PR for you. And the reviewers during this process will have their own opinions on you that whether you have achieved the membership requirements and whether you have achieved the membership level. Next, then is a reviewer, a prover, subproject owner in the document link. They also have some detailed introduction very detailed description about each of the roles and also the steps to become different roles. I also want to ask you as our guest which role did you start and during your journey, what kind of change you have experienced ? I think when I contribute to Kubernetes you haven't set up those roles since 2014 because the project of Kubernetes and just announced and I'm interested in it. I'm also one of the people interested in it because I'm writing another thing called ETCD and I'm looking at it just to find some useful tools and also make some contribution and our company work on another project called FLIT maybe similar to to use it in system D and system to start a container but do not have a good orchestration capability like Kubernetes and it's like Kubernetes has a better abstraction on some concepts and services. So not just myself to clarify this to devote it to the Kubernetes and start to give up the original flicks and eventually Kubernetes has become a Kubernetes focus coming so we started to contribute more project to it than the network and also have designed another project that is originally port for the Kubernetes originally when we build the Kubernetes team we have done a lot of work mainly focusing on security because a lot of enterprise user and has authorization model it's just on the early stage so we have more progress on security and it's for the extension we also done a lot of work at that time it's called password source it was still called this name and we also have been so that we can make this ecosystem more thriving and prosperous because we are always thinking how can we make more contribution to this community so that the community will be more active and more projects are able to run on Kubernetes and the barrier will be lower for many people so that it can satisfy more needs of the user scenarios and we started to use Kubernetes in 2015 it's Kubernetes 1.0 and my first start was in Google at that time and the first few months we are modifying different documents but do not do a lot of contribution but gradually the first contribution is to arrive some calls on it to recover some bugs then I work on some small projects and then on ATM to work on some more difficult things and now we feel that when people making contributions would be different from a few years ago like the Kubernetes 6 organization also have a lot of projects and we also working on the storage migration and the contribution is not on Kubernetes and we also welcome all of you to work on these projects I think I'm a little bit later than them at that time because our company want to migrate our own application to Kubernetes started from modifying some incidences and debugging and then I started to be familiar with the coding and also I'm interested in storage so under some of the guidance for example some of the key contributor there I started to design some features and contribute my own code thank you very much we can see all of them started from a small point for example the testing documents or anywhere you're interested in or you have seen the PR and review it and then you found that maybe you can improve it and specify some of those lines that you are not satisfied with and why you write it in a different way etc to start is not that difficult to start easily and you can make your own contribution with your own capability since then we can talk about something more specific how can we learn growth as a seed with the Kubernetes code and what kind of information that could be useful to us and what kind of things can help us many people may not know that and also it's very touching a lot of people apart from writing codes or making contribution to Kubernetes they also have done a lot of work to the community for example there are some in some of the events that can help everyone like in different kind of documents that can help us they are trying all methods to help each others and this is not loaded I want to show you the information of the community you can zoom in a bit and on the repository of the Kubernetes communities there are different kind of useful information and all of them started from that of course when they started their contribution you haven't found this even two years ago we did not see that much in the recipe for example communication it can tell you different fields that you can contribute in for example YouTube we do and also the six special interest group when KBS become bigger there will be different aspects so now it has developed into different six if you are interested you can join the special interest group and each of the six group will have the community meet up meeting and different kind of conferences you can join them and some social media as well like Twitter and Slack overflow and also in China maybe you will find some local events here as well or local website and Slack channel Slack channel you can communicate with the members of the communities on Slack and there are different type of issues all the questions and all of the issues that you said will be managed for example when we don't issue there is a box graph meeting every week there were two meetings that is focusing on special interest groups for all the new private issues and PR so all of these issues set up will be managed and reviewed and now it has been public and everyone can join it if you are interested in any of these PRs or issues you can join it and review it next is how you review these documents and office hours and meetings as well every month there are a lot of meetings if you do not know where to get this information you will only find those schedules that are too tight for you to follow just like what I mentioned there are different kind of special interest group you can follow or join if you are interested because now we are in China I also want to ask another question that in China or Asia communities what are the characteristics and challenges here I know shocker and Yichuan you are now in China and compare with North America China will have its own features first is the time different time zones so the meetings of this secret group will be mixed by them maybe they need to add some extra time for it if you have any opinions maybe you can communicate with us I think the challenge is a lot first is the time zone difference next is the language difference when you are writing because we have quite high requirements when you describe it and people want it to be concrete and specific, clear it will have some requirements and thirdly the domestic colleagues in these communities will be a bit shy so and for the foreign colleagues they would like to propose some of the simple very easy books or issues but for the domestic colleagues they will show this situation and also in the foreign community they will have more frequent communication and even the daily meet-up but in China I think the frequency is lower and the sharing channels are limited some of the like Huawei, Alibaba may be able to host some of the monthly meet-up and tell them your opinions and also allocate some of the things you want to do in Kubernetes because we hope it to be a community driven project if we are not able to reflect these voices in the community then it's very difficult for us to promote development of the community so we should have more meet-ups in China I think for me there are two challenges like Wenja has mentioned the first challenge is about the meet-ups they are following the U.S. time zone so for their morning we are one or even 12 a.m. so it's difficult for us to attend their meet-ups actually maybe to do some reasons some of the overseas stuff because of the internet or maybe some other reasons we cannot get our hands on them so for some KPI related materials we must acquire some special means so for me maybe the U.S. maybe there are some other ways to address this so we can get our hands on these materials easier Alibaba is trying to transfer these materials to some of the Docker image we are also doing localization for the home hub because when in the home there are many images and trust in Google store we are trying to do the localization so if you have any other special needs feel free to talk to our team we are more than willing to help the domestic community how about Chow we are based in the States so what's your take on this by attending tubecom or your daily lives in your communication with domestic developers what's your take on this situation I think in China as a contributor it's a very practical thing I saw actually I collaborated with a lot of domestic contributors so step by step you join the community first you should win the trust and that is by doing more stuff starting from simple box fixing gradually step by step people will trust you so I didn't see any biases against Chinese contributors and I don't think language is a problem personally I think for US people although they perceive your English pronunciation as somewhat problematic but they still get you last year was the first Chinese tubecom and this year is the second time so during the one year time you can see and also on the Cuban ads report that the contributors PR coming from China is getting greater and rapidly how many companies in China and how many developers in China there are this trend is there one thing I have realized when preparing this slide Cuban netizens community on their web page there are many language options, Germany French English but there's no Chinese so from this simple thing we can start with providing simple translation so there's a lot of things to contribute so this topic for one it's about experience the audiences will tell us as beginners some of the things to be mindful about and second as Chinese developers and users if you have any thoughts don't take please don't reframe for mentioning it because it's a trifle for you but whatever the subject matter feel free to shoot so that it can attract attention and be addressed actually we have a special interest group called our Contribute Experience with the hope to enhance people's experience we have one minute left so I'd like to ask if you have any questions thank you for sharing with us I'm interested for you in open source how many time will you invest weekly for developers they have their work and open source project this project is only their part time occupation actually this is a question for many of the audiences they share this question the previous company actually I work as full time open source developer engaging in other projects now I switch to another company most of my time were spent on internal platform development and of course I will spend some time on open source now I don't have that much spare time but still there are some no some spare time each day it's not saturated as long as you're interested you always find some time to do it I think I'm a lucky guy my company paid me to do open source so I don't need the additional investment but for some period of time there were some I was working on some in-house open source project so I will not be investing too much time on another open source project so there are some time limit indeed previously I was a full time open source developer and in Alibaba I have a lot of time to do open source related stuff not necessarily writing code but some other generic stuff so I have some time for that stuff so my feeling is that people can't find some time to do open source and there will be a significant self-improvement by participating in open source project than engaging in corporate affairs because it's a joint effort made by many I don't think we have time for another question so how about this after that offline feel free to approach us and ask questions I should have prepared a contact information for us now I've already done thank you