 Thank you. So hello everyone. I'm Aditya and I've been infrastructure and advocacy enthusiast. Please move on to the next slide. So I'll give you some background information on how I started participating and contributing to Jenkins Infra. So one day I just actually randomly attended the Jenkins Infra meeting and it was Mark and Garrett. I think they were discussing about some downtime in Jenkins and that is when I saw how how huge Jenkins is and the slide that was shown by Mark about Jenkins by the numbers. It does actually run once you feel how once you get the feel of how they are actually managing such a huge thing. It's awesome. It just blew my mind and I was like, okay, now I want to contribute and learn how to contribute to this. So yeah, the Jenkins Infra has a huge code base. Jenkins has more than 300,000 installations and it is really awesome when you see how it is distributed around the globe and every time there's a download it finds the nearest mirror and downloads from there. So it's just awesome. I cannot stop saying how mind-blowing I was and how awesome it is. So yeah, joining the infrastructure meeting, the calendar link is shared by Dheeraj in the chat. I think that would be the first step and that is the step I took as well. And there are many areas that need help and very recently and I would also like to add that I had no knowledge of how AKS upgrades are done. I paid with Danian and he was really helpful. He kind of held my hand through the process. We hop on to a, he hopped on a meeting and yeah, I shared my screen. He guided me what to do. I submitted my first full request for Infra and it is not even, I think it was two days back. I am pretty new at this as well. Yeah, Dheeraj, please can we move on to the next? Okay, so these are some steps that I follow and I recommend that any newcomer can follow to get acquainted and start contributing to Jenkins. So first of all, there's listening. So attending meetings, some are weekly, some are bi-weekly. I think that is how you get to know and even it is something from where you can understand, okay, is this something of my interest? Is this something that I can contribute to? Second is learning Jenkins, as Mark said before, it is completely Java development and Java was not even my, but it's still not even my primary software development programming language. I'm more of a Python person, but as you can see, I have a GSOC student here. So I do Java. I think willingness to learn is something very important over here. Then comes discussing, one need to be proactive, I guess. You need to ask questions in the Gitter channel during meetings, the mailing list. So discussing would be the next step, then pairing. I think everyone is really scared in the beginning when they are making their first comment, first pull request and pairing really helps where someone, some experienced person, maintainer of a plugin actually guides you through the whole process. So that is important. And then I would come to doing, you need to actually take that initiative and write code, not just code, actually, contribute. So the doing phase of it and finally reviewing and being a newcomer, you are again really scared when you are pressing that submit review button because what if you say something and it is too rude? What if it is not giving out enough information to the new contributor at the plugin you are maintaining? So that thing, and I just made one code review to the, on the project that I am working for Google Summer of Code, that is conventional comments plugin. And yeah, I was scared as well, but I was sure that even if I made a mistake, there are people having my back and yeah, everything will be fine. So I would like to encourage everyone to follow these steps and contribute.