 I love that intro. All right, welcome everyone to the second session of .edu, a cloud native TV show. I'm Kunal, your host. And today we have some really interesting folks with us in the community. So in the last session, we got so many questions. So we weren't able to answer all the questions, but we got so many questions like, hey, how do you contribute to such nice projects? How do you make sure that as a beginner, you're able to contribute? What are the prerequisites? You had questions related to various mentorship programs that CNCF has. We also talked a little bit about the shadows program. By the way, the shadow applications are open right now. So we'll talk more about that later, how you can apply and everything. But let's talk a little bit more about all the questions that we had previously. So we were asking, hey, this is such a large code base. How can I contribute? Or how do we get started with non-code contributions? What are the various ways which I can help out? So I thought like, let's, for this show, let's get some of the students who have been really active in the cloud native projects, for example, Kubernetes. So let me bring them on stage. We have Arsh and Madhav here with us. Hey, Arsh, hey, Madhav, thanks a lot for joining. Really appreciate it. Cool. So that's what we're gonna be talking about today. So we're gonna be talking about how Arsh and Madhav as students contributed to Kubernetes, what their journey was like. And answer all of your questions that you can also get started. We'll also be sharing some resources with you that will help you in getting started with being a contributor. But yeah, without further ado, before we jump into the agenda, let's do some introduction. Arsh, would you like to go first? Sure. Hi, folks. I'm Arsh. I'm currently pursuing and in my third year of engineering, I've been involved in the community for like the last six months. I was introduced to it as part of the Linux Foundation membership program, which I've been with Kubernetes. And then I did Google Summer of Code. I'm currently doing Google Summer of Code with CMCF. Yeah, that's been it. Like, let's see, what are we up to last week? Madhav, do you want to go next? Thank you for sharing, Madhav. Would you like to go next? Yeah, hi. I'm Madhav. I am currently a fourth year student in my final year of engineering. I got into Kubernetes and the community around early Jan, or mid-Jan. And since then, I've been involved in various other parts of the community, and just helping on wherever I can. So before, you both are students. And see, I'm a student as well. And most of the people who are joining are students. Before we jump into the project-specific stuff, would you like to maybe share how you got started with open source? How did you learn about what is open source, and what motivated you to get started? Maybe we can start with Madhav. Sure, yeah. So how I got started with open source was, so I was basically very lucky to have, like I had two, three friends of mine who were already into this space. Like, not Kubernetes exactly, but like, they were into open source and the whole idea that we had behind it. So I was, they used to talk about that in my book, because this was really cool and it sounds fun. So we were like, okay, let's do it, like, let me try and explore it a little bit. But exploration took about a year or two. And like, nothing happened until then, but everyone, the one thing I noticed was that everyone's just there to help you, no matter what. There might be rare exceptions, but like, in general, the trend is such that everyone's there to help you. But, and then we got together, we started like a student community in our college and things just sort of took off from there because people helped each other get started. And it was a lot of, it was a lot of good things. And like, I see some of my friends in the chat right now, as well. And so that's how I basically got started in open source, but the way I got started in Kubernetes specifically, that was like, there are a few folks in the community. So like, you might have heard of them, Nikita Nabaroon, Divya, all of them. So they do like a new contributor workshop every now and then. So that's how I got started. That happened in Jan. And that was the time I joined the Kubernetes life. Wanna get started in the Kubernetes. That's all there is to it. Cool, yeah, I can totally relate with that and shout out to all the amazing people who help, you know, beginners in getting started. We will be sharing about those resources before, like afterwards. And if we move forward, it would be great if you all could also follow the Twitch channel because Cloud Native TV has a lot of amazing TV shows, you know, related to the cloud native world. So we have like technical workshops and all the other amazing podcasts. So make sure you follow and share. And yeah, Arsh, how about you? So when I joined college, I wasn't like, I didn't have anything in particular and I didn't even know if I wanted to program. But yeah, first thing I heard all these fancy stuff like CPU, DSA, open source and everything. So everything just comes bombarded at me. So I took my time. I did something like, I did some DSA for a month. I tried my hand at code forces for a month. I created a GitHub account and I started exploring a month. So while I hated the first two, this I thoroughly enjoyed because I was like, wow, like if I write something and people are actually using it and someone was giving me feedback. And then I just like sort of automatically fell in love with the process. This was the first time I was like interacting with a community which was like not limited in space. And that sort of feeling felt excellent. And then I have been like just sticking around project to project and that's how it happened. Plus one for the CP point, I also did not choose the CP route just because of that feeling. I also wanted to, let's say I was intrigued by writing code being used by people around the world. So I agree with the CP point. I'm also not a CP guy. Well, for those of you who are joining, CP means competitive programming. If you're not aware of it, but cool. All right, well, that is great. So let's talk a little bit more about Kubernetes, right? So you started with open source was, was Kubernetes the first project that you got involved with or? No, so I like, I didn't even like know about, I heard the word Kubernetes, but I was mostly familiar with the web. So I looked for organizations which were using that exact one of those organizations. I was like contributing for a month or two. And I asked them, like I wanted to contribute more to the project like, is there something which I should learn? So they said that yeah, Kubernetes would be good to learn. So from then sort of started, I started learning about Docker Kubernetes. And then I wrote some blogs about it. And I was writing these blogs for myself because I was like, at least, this is like a formalized notes for me. That is what it was. But some folks read those blogs and like they offered me an internship in one of the CNCF projects. And then people like in the CNCF place are in general like very helpful and kind. So they told me that there's this mentorship program applied to it. And that's how Kubernetes happened for me. And mother, you mentioned that you were in contact with your friends, we're talking about kids and stuff. As well, quickly touch up on the point, like you know, as you mentioned. So you said something very nice which was that the blogs were actually for you. And that is something that a lot of people ask like, hey, why would I want to write a blog if there's already content available for that? So I was like, you're not writing it for like other people. I mean, obviously, if you share your knowledge, it's helping other people, but it's also helping you. So it does not mean that if a blog is already there on Q and it is, you cannot write a blog on kids. Definitely. And like you mentioned, we'll talk more about that later. Like you got an literally like an internship opportunity via your contributions. Is that correct? Yeah. So that's exactly like something that happened with, you know, I see a lot of folks including me who choose the open source route as students in order to get internships and job opportunities and placements and whatever. Because an open source is like the proof of work, right? So if you're doing good work in the community, you have your entire code based on GitHub, you are networking with people from around the world. Why wouldn't they give you opportunities if you are doing good work? That's why we have all the mentorship programs. Madhav, would you like to share something related to that? Yeah. So I think my first open source contribution in general. So basically throughout my college life, I was all over the place. Like I had polar interest, like just like completely opposite like North Pole, South Pole days. So during initial years of college, I was into something known as quantum computing a lot. So I contributed a few like very small code changes to this quantum computing project. And from there, I was like, okay, this is kind of fun. Like I didn't, I was yet to fully experience the helpful aspect of open source, but I experienced like what my code is going into like this software is like all over the world. Like how crazy is that I'm just sitting at home. I'm like a second year student. I don't know what's going on, but like this seems cool. Then I started like talking to a lot of people this that and then my interest if it was like the system side of things. So I got really, really into just like computer systems in general. So like be it at the kernel level or like be it at the higher levels or like cloud and distributed, any of those. Like I used to have a lot of fun with that. And that's something important, right? Like just have fun with it. And I was having fun with like all of these projects. And then I wasn't involved with any such project until this year, but like in the middle, we were running a few open source projects of our own. And that sort of helped me gain a lot of perspective because what I realized was even though we were just like second year students not fully understanding a lot of things, whatever we built, we got people who were like senior developers like send in contributions because they thought that what we were doing was interesting or fun. And I'm like, okay, this is really cool. Doesn't really matter if you're a student or like you're this extremely experienced person in the industry. It's just that people are, you have knowledge to share that are people to consume that knowledge and then there's the back and forth which happens. So I'm like, okay, now I want to be associated with something I don't know what. And like I stumbled onto Kubernetes because someone used to like talk about it. I'm like, okay, this sounds interesting and I looked it up. And I looked it up and like, this is so complicated. I don't know if I can do this. So I waited six months after that and then in Jan finally I'm like, okay, let's just join this lack and say, hi, what's the worst that could happen? So then that's why I got started. There's a very good point you mentioned which was related to contributing to your own projects as like open sourcing your projects and getting other people to contribute. There's something I've seen like in many students like you have your let's say final year project and you get it graded and everything. And then that project is not looked after at all. Or let's say sometimes there are some hackathon projects so you make a really nice hackathon project and then you let's say after the hackathon is over, project is done. The good thing you can do is maybe you can choose to open source that and see if other people would like to contribute. Thanks a lot for sharing both of you and get good. I think just to add to that what Malak said something very important was like, I personally feel like in open source you should try to find the thing which interests you like he said if the systems for him. So for me like while I was contributing to organizations which were like related to web development and all, I wasn't like really liking the entire stack and all and like when I started learning Kubernetes that was also not because like I thought that I would get something out of it. I was just like genuinely curious about what this fancy word everyone is using. So yeah, just to add to that like if you want to purchase something specific that's very good. Yeah. Speaking of the fancy word, a lot of people are asking about it. Can you tell us a like brief about Kubernetes and what is Kubernetes? I think mother does the best so much better than me. Sure. So I'm sorry to assume, but like I'm hoping folks know what a container is at least. Okay, let's not assume anything at all, right? Let's start from like ground zero. So just like think of a container as you are running Hello World, let's say you're running a Hello World program but you don't want your Hello World program to like just like go out of control, but you also want it to be run anywhere you want. So you like slap boundaries around it. You put boundaries around it and you make sure that it runs. You are giving it to someone and you're ensuring that okay, you run it this way and it will run. So just think of containers as like a way to package some program that you've written and run it basically wherever you choose to with other very important added benefits like constraints and things like that. So what Kubernetes does is it's basically a container management platform. So if you read like the GitHub description of the Kubernetes repository, it will read it's a production grade container scheduling system. So what that basically means is if you have a machine that is something running like something like your website which you want people to see, but let's say your website grows really, really popular really, really fast, you can either buy a more powerful machine, you can go on buying more powerful machines but that's not really going to help you after the point because it for financial reasons or like more powerful machine might not exist after a point. So what you can do is you can work with smaller machines but you can have a lot of them. So you can run, applicate your website on all of these machines and then you can like share all of the incoming traffic which is coming in. And to do all of this, you need to make sure that these applications that are supposed to be run need to be actually placed on these different machines that you have. That's what Kubernetes is on like a very, very extremely oversimplified level is it's a container scheduling system which is a production grade. And when it's a production grade, I mean like it's used by a lot of companies in production currently. So that's what Kubernetes does for you. And it does it in like really, really interesting very, very cool ways. So if you are interested in that, there are like a lot of great talks on that. So I can help with links. Yeah, we can definitely check out all the, you know, if you just YouTube as well like Kubernetes tutorial, I'm sure you'll find a lot of nice resources. Let's talk a little bit more about the contribution part. So one point is like using the project and the other point is actually contributing to it. So how did that happen? Ash, maybe you can go first. Yeah, so since folks are getting started I think it's good if you have first basic, just basic understanding like a little more than what Madhav said about the project. And it's definitely much easier to contribute to it. But so using Kubernetes as a student, you can just like play around with mini cube and kind and all, I think that is what we can do at our level right now. But yeah, contributing specifically to Kubernetes, I think it is much easier compared to other open source projects, especially because of like all the helpful folks around here. So for me like contributing, I did not, I was just learning it, contributing happened automatically. Like when I grew interested and I came to know about that Linux Foundation mentorship program. So I talked to Dems and everyone in the community and that's how I sort of got into contributing to Kubernetes. Thanks a lot for sharing, Ash. Madhav, would you like to share your experiences as well? Sure. So like Ash said, there's not a lot of things you can do as a user of Kubernetes if you're a student. But like a lot of times when you ask people how to get started, the advice you'll get is first be an end user, but that might not be possible if you're a student and that's totally okay. Both sides of the story are perfectly valid. But if you're a student, one thing I would say is, try to make sure that the project that you're contributing to, like in our case it was Kubernetes, but in your case it can also very well be something else. But just try to make sure that the project you're contributing to interests you in some way or the other. So for me personally, I was just having fun with it, like trying to understand how Kubernetes works as a system, trying to understand the architecture of Kubernetes, like why does it work the way that... Because when you get started, you hear these different terms in Kubernetes and you just wonder like, why did they decide to build it this way? And like why this, why that? So I was just like on a witch hunt for all of these answers. And that got me really interested in a lot of things. And I was like, okay, this is really, really fun for me. And this is really, really interesting. And throughout that process of like trying to learn, that's how basically contributing also started. So like this, I would say, try to make sure that contributing is like a... It's the aftermath of your learning in the project basically, not the other way around. So just like have fun with the project if you're a student. And then once you do, you'll be able to understand, because one of the biggest barriers in contributing is understanding the issues itself. If you go and see Kubernetes, the issues page right now, like if assuming you don't really know a lot of things in Kubernetes, you won't even understand what's going on there. Like you won't understand the terms. And this was me for like a good half year. And trying to learn about Kubernetes just at least helps to understand what discussions are going on and what conversations are taking place. And once you know that you can offer help, even if issues aren't opened up, you know what needs to be worked on. You can say that, hey, I know this needs to be worked on. Can I please help with this? So that way it sort of becomes relatively easy. And I really love the... Now you're saying I just really love the point you mentioned related to, it took you like months and months because it's not going to happen overnight. It is going to take time. Most of the time you're just gonna be sitting in meetings, like the SIG meetings, just observing what all things are going on and all these things. But yeah, are you saying something? I was just saying that Madhav has a really cool talk on how Kubernetes works. It's on the Kubernetes Bangler channel, so you can check that out. But yeah, completely agree with the sitting as a fly on the wall in the meetings. I think that's one of the analogies James gives. But you just have to observe just more down stuff you won't understand and learn about it. Because that is where the actual learning will happen. If you just observe and see what all things are happening in SIG meetings and stuff, we'll talk more about SIGs later. People like Arsh mentioned, Madhav mentioned. A lot of people will be there to help you, basically. Getting a lot of questions regarding the prerequisites. So let's talk about prerequisites first and then we'll talk about what the actual contributions can be as a first-time contributor. So let's talk a little bit more about the tech stack point of view prerequisites. Arsh, maybe you would like to share. Honestly, I feel like pre-requisites every is a value you're setting for yourself and you should not do that. Just jump in. You would not understand anything. You would not understand 90% of the stuff. Google, ask. And that is how this barrier, you don't need to have this pre-requisites barrier and create it that I will learn this first, learn this first, learn this first and then start contributing. Just go ahead, at least that's my take on pre-requisites. Yeah, totally agree with that. Learn on the go, basically. So even if you know 30% to 40% or whatever the tech stack is being used, you can learn while contributing. You can also start with non-code contributions which many people are sharing in the chat. Another question, like if we ask as a follow-up is, so you started as first using Kubernetes and learning about it and then how did you, this is a question we get quite a lot. How do you understand such a large code base? You don't, like I don't understand the large code base. I only know the parts, I don't know the parts I am working on, I think. True. Take it into pieces. There's a reason it's divided into modules and packages. So you don't have to like, know how every single file is. You don't have to go through every single line of every single file. It's not, no, it's not possible, like checking out every file and stuff. Cool. Let's talk a little bit more about then your first contributions, right? So maybe if you could share a little bit about that, how that started. Madhav, would you like to go next? Sure. So this is a nice segue. So I have like a small personal experience to share from the like the first one. So my first contribution was, like a lot of people's first contribution was fixing a broken link that I found while trying to explore what's up and like what's going on in Kubernetes. So if you are new to Kubernetes, check out the community repo. That's the knowledge repository of all the SIGs that, so SIG stands for something on a special interest list. We'll come to that later as well. But that's the knowledge repository of everything everyone is working on. So I thought, okay, this might be a good place to start. So that's where I found a broken link. I sent a PR to fix it. And one very, like one thing that I've realized and like someone also has, how do you get familiar with such a large code base, right? So one thing is that when you send in that small contribution also, so if you think that fixing a broken link is possibly insignificant or like correcting a typo somewhere is insignificant, that's not the case. Because what you, what I did was, and this was like really helpful for me. So when I fixed the broken link somewhere, I was, I made sure to read above and below that line, which I fixed. So what I did was, okay, I'm fixing a broken link, but what am I fixing to? Like, what am I fixing here? It doesn't really, I'm fixing something, but I don't know why am I fixing, like what is this document telling me? So get that context. It doesn't matter what you're doing. Every small thing that you try and do for the community, it'll give you like a lot more in terms of what you learn. So for example, there was some small thing that was there in the Kubernetes repo and you had to add like a if condition, that's this one, two, three lines add addition. Might seem insignificant, but through that contribution, I learned one full part of like that particular component, how it works. And that's how you sort of like go on learning more and more about how these code-based components work and you get so much more context over time. And that's really helpful as well. I totally agree with the examples you gave and that's another questions we get like quite often are, can you suggest me some beginner-friendly open source project to contribute to? I mean, you can contribute to large open source projects as well, I mean, they have beginner-friendly issues for a reason. So it's not like you cannot contribute to big open source projects as a beginner. So I personally would recommend directly jumping on to such projects, if you have some development experience, because it's not just about coding, open source, it's much more about coding. It's also about the community and all these other things. Yeah, this is true. There's like, you can search on YouTube, Kubernetes contributor workshops. There are a lot of recordings available on YouTube as well, if you want to dive deep into like SIG and stuff. So they're like contributor workshops. But Ash, would you like to share something? Related to this, I think like, I just remember that you were talking about the code there's been too big and how to learn. There are also code walkthroughs which happen in the Kubernetes lab. So if you join the Indepth channel, you'd see pinned in the description, the past recordings about self code way, which boils down to basically if you're stuck, ask for help. There are so many people willing to help you that part of the code, yeah. Cool. And one more thing, for like any, like if you're first familiarizing yourself with the project, I think test cases is a really great way to start. It can either be like for the contribution part or understanding how the project flow is working or whatever. You can look at the test cases. Personally, it helps me quite a lot. But yeah, you can definitely try it out if it helps you all as well. Cool. So next thing we have on the agenda is when you first started out, right? Did you face any blockers and how you resolve those blockers? Anyone can take this. Ash, you would like to go? Yeah, go for it. Blockers, I mean, I don't remember any specific blockers because I still face so many blockers every day. And my agenda approach to blockers is that I spend some time on my own googling and if I'm able to figure it out, that's great. But if I don't, then I just try for help once again. No particular blocker comes to mind, Maru, do you have a story on this? So one thing, this isn't really a materialistic blocker, but just something I personally felt or faced. So I was very lucky to realize this and someone told this to me very early in the community. So basically, Kubernetes does this thing called Meta Contributors. So on one of those sessions, one of the contributors who was there, they said something very, they said one, like I don't remember anything else on the session, but this one thing, like it's really stood out for me. They said, non-response is not rejection. And this is something that a lot of people face in the community and also might not feel very positively about. So basically, a lot of people working in the Kubernetes community are busy folks. And if you reach out to anyone for help, it's very much possible that they will get back to you two, three days later or they might not get back to you at all. And that's completely okay. People aren't obligated to get back to you. And considering and keeping this in mind, the best thing that you can do as someone who wants help or is asking someone else for help, please always do your initial homework before asking for help. Don't DM someone asking that, hey, can you help me get started? Like get started with what, like I will be more than happy to help you out. But if you tell me that, hey, can you help me get started with so-and-so thing? These are my interests. And this is basically what I've looked at so far. I'll at least be in a better position to point you towards more specific resources. Or if I can't help you out, I can at least tell someone else or like refer you to someone else. So like, they can help you out better. And this is not just for asking help. So if you're working on an issue, for example, you don't really get a response on your PR or something like that, or you have a question. So you DM the person on Slack, but you don't say, hey, I'm not able to figure this out, can you help me? It's always, it always helps a lot. If you tell, hey, I've tried so-and-so, this is what failed, this is what I think. But I feel like I'm not fully understanding this correctly. Could you please help me out over here? Could you point me to what I could look at or understand this better? And it's always better to ask for resources that can help you understand that better rather than the answer for the question you're looking for. Because that way, again, you get to learn like a whole other thing that you previously didn't, right? And that's what's the fun part of this, like this community is a lot of fun and gender. So, and this is the same thing holds for if you message in like a Slack channel also, like no one's going to, people might not reply with like the whole answer. If you give them some context, you might get some response back with helpful links, please. So that sort of helps a lot. Yeah, could not agree more on that point. Asking, help us help you basically, help them help you. So if you just ask the vague questions and most probably like, you're not going to get much beneficial answers. I really like the point you mentioned related to they're going to share the resources is not like directly the answer because that's going to help you grow. Totally agree with that point. Communication is key, especially in like open source and remote work. Arsh, would you like to add on to that? Totally agree with it, just like adding on to it. Like people are very busy and sometimes like even if you like tag someone and do your homework and everything and you don't get a response, don't take that person, it might just be that person is like super busy and they like so many messages and conversations happen that it gets lost. So just don't take that to add anything. But do your homework, yeah. And just like I should also mention this since this conversation came up, this does not mean that it's not okay to reach out. Please reach out. What I'm saying is it's okay if the response gets delayed by a some amount and it's okay if you don't know enough to have that context, you can very well say, please can you help me get started? There are resources for you to, for people to get started even if you don't have an initial context. So it's okay to even ask that. But just as a general rule of thumb, just keep these points in mind. That's pretty much it. So as usual, all of those things which you think about when you think about the COVID-19 community, like extremely helpful people, warm and welcoming, they're all very much intact. But yeah, so just don't be afraid of like reaching out basically. And if you don't get a response, this is probably the reason. And in order to maximize your like chances to get a response, ask questions in public. So that's also a great, great point. There's another question, like there are so many SIGs and channels. Sometimes it seems to be over. I mean like which SIGs work to follow. So how did you decide which SIG you wanted to be a part of? So for me, I didn't like go SIG hunting that I want to be this, but that is also totally valid. Like if some SIG aligns with your interest then definitely go for it. I was just like looking at what is there to be done. And then if like you get to know about something and then I looked for the corresponding SIG and attended their meeting. So I took the approach of from the issues to SIG, but going looking for a SIG which aligns with what your interest is that is also perfectly valid. And you don't have to catch up with every SIG, that is not possible. Just don't get overwhelmed. Sticking with a SIG in a big time like that, sticking with it for one or two months and if you're getting a sponsor then just like, I have literally gone to SIG meetings and said that is there something I can help with? Let me know. Couple of things there was nothing to do, but I kept going and when stuff popped up like, I got to know about it and so that's what I did. I just shared a link in the chat. It's basically of all the SIGs. And if you join any of the mailing list, you will get calendar invites. So you can attend the meetings. Everything you'll get in your invite only. SIG is basically a special interest group for the contributor experience, for like APIs and docs and everything. Cool. There was one more thing I wanted to ask was, so you all are like your current students. So it's sort of like a very general question, but still it was like, people ask this quite a lot of times. How has contributing helped you? Like both in terms of let's say technical skills and the people skills like the soft skills part. So maybe Martha, you would like to go first? Sure, yeah. So definitely in terms of technical skills, it's just like, I feel like the way I write code now is influenced a lot by the way Kubernetes code exists. So for example, like extremely verbose function names and like extremely well documented code. And so that is just something that I feel like, it's so important that I was very thankful that I got influenced by that part of contributing. Another thing is you learn a lot of technical skills along the way. So it might not even be Kubernetes specific. So if you are, for example, making code contributions, that was the case for me. So I learned a lot of things related to Golang, for example, through like, why is writing code? So things like, how do I benchmark code? How do I write certain things in terms of interfaces and things like that. And but also if you're working in terms of non-code contributions, there that way also you get to learn a lot in terms of your soft skills. And this works for code contribution results. For in terms of soft skills, you get to know about how do I ask for help in a way that I get a response back? By that I mean, how do I ask for help knowing that the opposite person is busy but also that I've done my initial research and how do I make sure that I present what I've done in an advocate way to make sure that I'm getting my point across? Because I used to have a very, very difficult time getting my point across initially. So I used to say something, they used to reply back and it was like, oh, sorry, I don't think I was clear enough. So that sort of back and forth was there initially, but then as time goes on, you sort of learn how to communicate better and ask people better and things like that. So that helped me quite a lot over here from contributing. Awesome. Well, thanks a lot for sharing. We got a lot of nice people asking some questions related to which is some beginner-friendly sakes or whatever. And check out SIGDocs, SIG Contribux. You can attend the meetings. You can attend the marketing meeting of SIG Contribux. Have some nice things. You can get started with non-code contributions. But let's share a little bit more about some of the programs that students can be a part of, as we promised. So let's talk a bit more about the LFX mentorship program. The applications for that are going to start, I believe, this month. It's the third one for this year, like the fall one. I'll share the link in the description, but till that time, Arsh, would you maybe like to share your experiences? Yup, so while I'm familiar, like three or four active programs are run by CNCF, which is like the LFX mentorship program which happens three times a year. Google Summer of Third, which happens in the summer. Outreach, which I'm not so familiar with, when and what happens, if anyone knows, then please add on. And Google season of course, that has also happened once a year. So what do you want me to add in terms of these programs? Yeah, then maybe just share your experiences and like how you applied and what you got out of it. I believe it's also not just open for students. I think it's open to everyone. So like even if you are graduated, working somewhere, I think you can still apply. I definitely know that it's focused for beginners, like for beginners who want to get started in contributions. But yeah, I mean, if there's anything else you would like to add, that'd be great, but otherwise we can move forward. Yeah, my experience has been like incredible with both the programs because like I already said, like people not just incubators, but in the CNC ecosystem in general, are like super nice and super welcoming and they help out. And I guess like some common things which people have is ask is like, they don't set blockers for yourself, like I'm in my second year or something. I don't know about this or something. So honestly, like for my Google Summer 4 project, it was using Terraform AWS. I hadn't touched those. I didn't know what they were. My situation would be like just look at the project list and talk to the people, like if you're interested, like you will be able to learn what the texts are. That is not the top part. Just communicate and that's all. Yep, thanks for sharing, Harsh. Madhav, you were saying something? Yeah, just like one more thing I would want to add. So I remember like Harsh had a really nice way that he like got into LFX. So I remember he had like a whole proof of concept thing ready for his application before he applied. So like if you can share about that, I feel like that was really nice. Like a nice way to go about it. Yeah, so I wanted to apply and I talked to Dems again. So I feel like incredibly lucky that I had Dems as my mentor. In general, I got introduced to so many good people and made friends with them. I think that adding to like what you have benefited and all like skills and everything is there. Honestly, like making friends is super awesome. I like the friends you make in the community and having a place where you can belong. That is like the biggest addition to me in terms of like open source and things. So for my LFX application, like I talked to Dems and I understood about the project. And then I basically like tried seeing that can this be like done, can I like do it on a smaller scale? Basically proof of concept, created a proof of concept and I tried that. And that is totally in the opposite direction of what the project is today. But that at least sort of, I was not even familiar with Golang that much. So it sort of helped me learn Golang and everything there. Yeah, that was awesome. Thanks a lot for sharing, Arsh. I really appreciate it. For people who are asking to sum up, how do we get started? Check out the links that we shared in the chat related to various six. Try learning about the projects. You can also check out the, if you don't want to contribute to let's secure it is, but some other project. So many other projects, Prometheus and Thanos and other projects. So you can check it out on the CNCF projects list. If you just Google CNCF projects, you'll find it. The insights that we mentioned in this session hold true for every project. Like asking good questions, being active, attending the meetings, asking questions, not going to happen overnight. It's going to take a few weeks or months. Don't need to understand the entire code base. Just learn while contributing. If you have basic understanding, just learn while contributing. Make sure you follow the cloud native channel on Twitch and check out all the other cloud native TV shows as well. But yeah, I sent all the links in the channel. And then you can also look at the Kubernetes contributor summit where there's a much more detailed section about SIGs and everything. Last thing I also want to share is the Shadows program applications are open right now. So Kubernetes has its new releases, the version releases. Recently we have 1.22. So next is 1.23. So the release team of Kubernetes basically recruits a number of people and trains them for each release to be release leads for the next role. So basically, if you want to contribute to, let's say, in a particular release, a lot of things go. So for example, documentation, communications part, release notes, a buck triage, CI signal. So you can apply it to be a shadow in any one of these roles. And you're going to be basically mentored by your team lead who's going to be mentoring you related to how things actually function when a new Kubernetes release happens. So for example, most recently, for 1.22, I was a shadow for communications comms. So I learned about how we interact with other people like enhancements and stuff, and work on documentation, feature blogs, and all these other things. So the application for that is open right now. If you can just, how do I find the link one second? I think Dimz shared about it. So you can check out Dimz's Twitter. He shared about it. You can just find it on the Twitter of Dimz. But yeah, here we go. I'll just share it in the chat again one second. There you go. So this is the link. You can apply it. And one thing I would like to share is when I applied, I got rejected like once and twice. So after that, only tip I can give you. Navarone shared this with me. And he told me, be specific. What do you want to do? Why do you want to join? Be specific in the rules. That helped me quite a lot. And I was already contributing to CIC Contribux. So previous contributions, I believe also help a little bit. Ash and anyone else who would like, mother would like to add on to something to that? No, so I don't really have too much experience with the release or the shadow program. But as like Navarone in the chat mentioned and you mentioned, you don't really, it's totally OK if you're a business, if you want to apply for a shadow role. It's totally OK. That's fine. If you want to know about the program, you can check out Navarone's already in the blog post. But in general, you have to sum up the best thing. If you're starting with Kubernetes, the best resource at this point would be the new contributors workshop that you would find on the Kubernetes regular YouTube channel. And just join the in-depth Slack channel on the Kubernetes app. You'll find resources and you'll find us there. Awesome. And just like if anyone is new to the in-depth channel, when you join, drop a high. It's totally OK. If you're not comfortable with it, but I would highly recommend doing it because you would have already sent your first message in the community. And that holds for quite a lot. And so just make sure you say hi and introduce yourself. Yeah, and ask good questions. And don't be afraid to ask questions in-depth channel, people who are asking. Yeah, it's shared over here. Thanks a lot for joining, Arsh and Madhav. I think a lot of insights were shared, more than enough for people to get started. We shared the resources, how to get started, shared about some tips and resources and links and everything. Once again, to sum up, it's not going to happen overnight. You're going to be required to give in time and efforts and stuff and be patient. And yeah, that is pretty much about it. Thanks a lot for joining, folks. Really appreciate it. And for everyone else as well, do check out some other Cloud native TV shows. Make sure you give the follow button for the Cloud native channel. Would really appreciate it. And yeah, that is pretty much about it. We'll see you in the next session with another session for the students. But till that time, you can definitely explore all the other amazing shows that are running. Once again, thanks, Arsh and Madhav. Really appreciate it. Lots of insights being shared. Any closing remarks you may have? Thank you for having us and thank you for joining and hope to see everyone around in the community. Most definitely. Thanks, everyone. Have a great day and a good night. And great day from where you are joining. Bye. Bye-bye.