 Hi. Good evening, everyone. Before we start, a short introduction about me. So I am a finally undergraduate at National Institute of Technology, Rourkela, majoring in biomedical engineering. Basically my background is non-CSE and I am a self-taught programmer. It's been one year since I have been contributing to Kubernetes. Let's start. So how it started? Basically it all started with LFX mentorship, which happens in three quotes a year, where I was a mentee under one of the CNCF sandbox project called KiosMess, where my work was to add more features to the AWS Kios feature that is already present there. But the caveat was when I started with this mentorship, I had no idea what is Kubernetes and what is a container orchestration. So, but I had to work on a tool that uses Kubernetes as an end user. So I started learning it. And at that, during that time, the QCon EU happened and I met a lot of folks. I knew where the community types. I joined the Slack channels, the place where the developers of StreamDev interact. But the problem I had there was I wasn't able to understand much of the conversation that is taking place. Though I tried to ask questions, but there were few jargons that were quite unclear for me. And then this KCD Bangalore happened where there was an amazing session on the code walkthrough, which is still relevant for me. Whenever I find any doubts with the source code of Kubernetes, I go through that video and you get all the jargons like KPs, PRR, all this. I got introduced to that and met some of the amazing folks with whom I work day-to-day now and we meet weekly basis in the community. So the key elements that I found as a beginner was mentoring, second was perseverance. And third and most important was the courage to ask the right questions in the community and get your doubts cleared. As a beginner, when we start contributing, we usually ping the reviewers, the approvers, and we ping them in the DMs. But why it is discussed in the community is when you ask a question in the group, not only it gets cleared swiftly, but also if any other person has the same doubt, gets help. And people know that you are active and you are working on something and whenever we need help, we could get on to you and it also develops a sense of trust for you in the community. So when I talked about how mentoring is important, we talked of LFX mentorship that I was part of where I learned about Kubernetes as an end user part. I love the project that I start contributing to it. But when we come to Kubernetes in the upstream part, there is something called group mentoring that I was part of south of Paris for mentoring me there. I was part of this mentoring cohort where our work was basically to help with the community management part. And we were given tasks every week to go through the issues in the case last case last community repository, trace them and help them. So then comes one such issue, which was, you know, it was opened by Dems on February 27. I put this four picks to show you the timeline of how issues get solved in Kubernetes. And so this all this issue was regarding developing and category scenario that would help newbies who are coming to community, but are not able to clear the threshold of setting up the Kubernetes code in the local system. So we wanted to give them a more real time preview of how this thing work, how to set up how to set up the code that lies in the case last case in your local system and start contributing. So I assigned myself to this to this issue on August 30th. I worked myself. I worked myself. And we did a cross collaboration. We took help from comp comps and say Contributex to do the copy editing. And we came up with a contributor category. And I hope I want you all to check out this contributor category repository that is present at Kubernetes six repository where we are trying to develop scenarios that would help upstream depths, the depths, the people who are contributing actively to Kubernetes and who don't have enough resources at the beginning to get the feel how things work. So all, all through this, all through this journey, one thing I learned as you know, before assigning an issue, try to understand the subjects of the issue, because what happens when we start, we look for good first issues. But the problem is most of the people try to solve the issue rather than comprehending what the issue is and what is the larger picture of the issues. And that's where most people, the journey of most people stops as a contributor. When we don't comprehend, when we don't try to understand what we are solving, they don't clear the threshold of good first issues. So whenever stuck, do us for help if you're not able to understand the issue forms we have in throughout the Kubernetes repository is very intuitive for someone to understand what that issue is saying. And if you're trying to solve it, do, do communicate itself with the, with the community members. And when I say communication is the key, there is an advantage we have is in every Kubernetes community meeting, the first five minutes goes as a session for introducing new contributors. And that, that comes as a very good ice breaking session for anyone new to gain confidence and ask questions, ask your doubts in the community meeting and don't burn out and be regular since this, this whole talk was for any students, any grads like me who are unlike the people who are doing day to day job have more bandwidth, we could spend more time. And if you come regular to community meetings, at least listen and you, you, you become a part of the flow and that helps that helps you in identifying issues in identifying parts where you could help. So shout out to all the people with whom I work with who have mentored me and it has helped me immensely in my career. And thank you everyone for helping me and motivating me to contribute. That's it. Thank you.