 Welcome folks for my talk for lightning talk. I'm excited but a little bit nervous, but yeah, here I am So yeah So we'll be focusing my lightning talk will be from my experience from being a noise to a captain contributor and empowering my all opportunities which I or contribution which I made in a cloud native communities So talking about me myself. Yes, pinplay. I'm a contributor at captain alongside the DevOps and cloud enthusiast and open source contributor so yeah Every one of our everyone over here have came across the whole CNCF landscape and each of us No, it's a last and have a lot of I can say section in which we need to redirect and we need to go So it's a overwhelming response of beginner folks who want to contribute to CNCF But it's like a vast ecosystem and a complex one So they are unable to navigate in which part we didn't need to contribute So if we see all the challenges that we are free that I faced alongside All open source contributor facing first week's first is complexity and overwhelming whenever folks get introduced to a project It's whole code base is large and each of them has their own Well, well this well based code bases alongside its complexity is used and it's overwhelming for each of us Second finding right project for me. It was such as the same thing. I came across GSOC I was contributing to a specific project. I was unable to make it But it was irrespective of that I keep on contributing to the project And yeah, it was the great way for me to find a better way for a better project for my overwhelming response second communication if we talk about Communication having a clear communication with other maintainers and folks is a much part in communicating or a contributing to a specific organization in the CNCF ecosystem third lack of experience being open source newbie each of us have Zero experience but to gain experience and to have a larger impact inside the org Understanding the whole code base Implements a lot of functionality Overcoming the challenge and the third is the mentor role assigning or having a mentor in which direction We can we can need to go is really really beneficial for us so that the maintainer can communicate and can help us to Resolve our doubts. So if we talk about all the challenges over here, there's one particular solution in which we can implement There's that is meeting the maintainers for me All these challenges were resolved while attending the weekly and the monthly meetings talking to the maintainers Having a consecutive feedback getting associated with the maintenance and each of the mentor which I have met in captain or Are always supportive each of them basically help me to Overcome all my doubts and issues which I have been assigned and I have been contributing to So if we talk about the opportunity which I basically started contributing I started contributing from an odd code contribution by resolving some error in contributing guide alongside adding some sessions or Making a brief documentation on some particular topic then move on to contributing to the code documentation working on operator part having some make file issues and at last having a collaborative way to Particularly resolve an issue and to talk with other maintainers. So if we see In my journey, it was like from getting my first PR merge after two to three trials It was basically a small PR refactoring a contributing guide Till to becoming a member in captain or after consecutive months of hard arch I can say working together with the maintenance and resolving issue It was a fruitful journey for me because I was able to learn a lot of things So if I need to draw some of the practical tips I need to implement to other folks who can who can make the best Contributing the projects. So first I can say start small because none of what you have I can say experienced developer each of them has started from a small base to have and have reached a higher heights second have clear communication having clear communication with maintainers so that they can understand an issue Providing with a lot of information to them. So they can able to resolve a issue is a plus point per So for that do join the slack have come up with the do attend the weekly meetings with the maintainers Third practice empathy because each of us over here are doing their own work and each of us are human So having a practice I can say empathy which each of them and alongside a new contributor by joining showcase them the Empathy towards them third seek guidance if you have any issue regarding a particular topic Do talk to the maintainers do talk to the whole community because in the CNC I have seen that whole maintenance community supported and collaborative So no one over here basically there too I can say question you each of will be there to help and associate to with you to inspector any doubt you have Forth, I can say document your journey because it's really helpful for you to getting for understanding from what you started And from where you have been reaching are going and all of these I would like to some of that all of this contribution basically pay you forward and for me It was for the same starting from the base of contributing to I can say not good contribution And then speaking on this stage representing my experience. It was a great experience for me. So, yeah, thank you from my side