I have always wanted to participate in the LFX Mentorship program and here I am, graduated, writing this blog. These 3 months were amazing! This blog covers my experience in this mentorship.
What’s the LFX Mentorship?
“The Linux Foundation Mentorship Program is designed to help developers — many of whom are first-time open source contributors — with necessary skills and resources to learn, experiment, and contribute effectively to open source communities. By participating in a mentorship program, mentees have the opportunity to learn from experienced open source contributors as a segue to get internship and job opportunities upon graduation.”
If you are interested in participating in the LFX Mentorship programs, you can find more information at lfx.linuxfoundation.org/mentorship/guide.
My acceptance into the program
Once the application process began, I drafted a cover letter and I was contributing to TestGrid for some time which I included in my cover letter, which I believe helped me stand out from other candidates.
I want to emphasize that contributions matter a lot. If you are interested in a particular organization, I encourage you to find ways to contribute to their community or projects. This is a great way to show your interest in the organization and your ability to add value.
I applied to 3 organizations (Kubernetes, Harbor and Cortex), Kubernetes accepted me first, so my applications to the other two organizations were no longer considered.
So, what did you do during mentorship?
I contributed to CNCF - TestGrid: Frontend development inside Lit Component Framework project.
TestGrid's Core contributors Michelle Shepardson and Sean Chase were my mentors. I had weekly sync-up meetings with them. In this meeting, we reviewed the goals we set in our previous meetings, discussed the progress, reviewed PRs I made, and identified any new goals or objectives that I would like to work towards.
The first step was to set up an existing webapp with Tailwind, after searching it was found that having normal plain old CSS is suited for Lit Framework. Therefore, we decided to build our components on top of plain old CSS.
Next, I implemented the index of TestGrid which rendered dashboard and dashboard groups components. The image shows the end result of the index.
Implemented the onClick functionality to render particular dashboards when clicked on a dashboard group. Refer to this image:
After implementing the index, Sean asked me to write StoryBook and Unit tests, following the Test-Driven Development (TDD) methodology. This was my first time writing Storybook tests, and I found it to be a fun and rewarding experience.
I also decluttered the codebase by removing any unused or duplicate code.
The final task which revolved around fronted was to reiterate and improve the written tests.
After, implementing the index, there was some problem in the API structure which made the frontend do the heavy work. Hence, compromising the user experience.
After discussing it with my mentors we decided that the API structure needs to be improved and I was set to start my GO journey, was really excited!
I really want to thank Michelle and Sean (my mentors) as they helped me get familiar with every piece of information related to API and GO. Before actually working on the codebase, I read all the resources first and got familiar with protubufs and GO.
There were two tasks assigned to me;
Task1: (refer to issue #1199)
The frontend required to do heavy work because the dashboards were not linked to their respective dashboard groups. The solution was simple, just add a reference to every dashboard of their dashboard group. I updated the API proto, wrote the governing functions, and finally updated the tests.
Task2: (refer to issue #1200)
Currently, TestGrid doesn't have an endpoint that shows the config in a short and clear way. The information we get related to a particular tab is by fetching headers or rows. The end goal was to add a new endpoint that shows all the valid and important information related to the dashboard tab.
I started by creating a new resource in the API proto. Later on, I added the governing functions which fetch the equivalent data. Finally registered a new endpoint to the server.
What I Achieved and Scope for Improvement
I was having real fun working on this project and have closed 5 PRs and have 1 PR in progress.
Currently, the Task2 PR is still a work in progress, my goal is to complete the task and get the WIP PR merged.
I am also looking forward to contributing to Kubernetes in the future.
Is it difficult to get accepted into this?
I would say a big NO!!!
I personally started checking out the projects a few weeks before the applications started.
It is all about how willing are you to contribute to the community and learn new things which at the start might seem a little bit overwhelming. Before LFX, I was a beginner in GO but during my mentorship period, I worked on an API written in GO.
Don't hesitate, give it a try. You will learn a lot!
If you’re interested in joining the LFX Mentorship like I was, submit your proposal here!
Graduation and concluding it all!
After 12 weeks, I successfully graduated from the program-
I would like to express my sincere gratitude to the Kubernetes, LFX, and CNCF communities. Without their support, neither this project nor this program would have been possible.
Did you find this article valuable?
Support Ankur Patil by becoming a sponsor. Any amount is appreciated!