🌱 Before Google Summer of Code (GSoC): My Open-Source Journey Begins

Table of contents
- 👋 Introduction
- 🌟 About Me
- 🎯 How I Chose My Organization & Project
- 💻 What I’ve Done So Far
- 🔍 Why Visual Diagrams Helped
- 💬 Talking to Mentors & Writing the Proposal
- 📸 My GSoC Selection: A Dream Come True
- 💡 What I Learned & What’s Next
- 📚 How to Start Your Own GSoC Journey
- 🔗 Useful Links
- 📬 Let’s Connect!

@Credit - Kannupriya Kalra, Adrien Piquerez, Scala Center
👋 Introduction
Hello! I’m Vidisha Gawas, a third-year Computer Science student from Mumbai. I love working with Scala programming language, especially on tools that make developers’ lives easier. In 2025, I got a chance to join Google Summer of Code (GSoC) — a global program where students contribute to open-source projects over the summer, with help from experienced mentors.
I want to share my story about how I got into GSoC, the project I’m working on, and some tips for anyone who wants to try GSoC too. Don’t worry if you’re new to this; I’ll explain everything step-by-step!
🌟 About Me
I am currently in my third year of studying Computer Science at the University of Mumbai. My favorite programming language is Scala because I like its clean style and how it encourages writing safe and reliable code.
I enjoy learning about functional programming — a way of writing code that is easy to understand and less prone to bugs. I also love working on tools that help developers build better software.
Here are some quick facts about me:
I’m from Maharashtra, India.
I like contributing to open-source projects, which means helping improve software that everyone can use for free.
My email is writer.by.passion.123@gmail.com — feel free to reach out!
You can find my code and projects on GitHub and connect with me on LinkedIn.
🎯 How I Chose My Organization & Project
My GSoC journey began in late 2024 — around November or December — when I first learned about Google Summer of Code. The idea of contributing to real-world open-source projects with mentorship from expert developers instantly excited me. I wanted to apply my skills and learn more about Scala and developer tooling.
When I started exploring organizations, I was drawn to Scala Center because of its dedication to improving the Scala ecosystem and developer experience. As someone passionate about Scala, functional programming, and clean tooling, this was the perfect match for me.
I had seen Kannupriya Kalra’s talk explaining about GSoC and Scaladex in this video which was very informative and very easy to understand.
Among Scala Center’s projects, the Scaladex: Support for Compiler Plugins caught my eye immediately. Scaladex is the central index of Scala libraries, and I knew compiler plugins were a complex yet crucial part of the ecosystem that deserved better support. The challenge of improving artifact detection, versioning, and discoverability felt like a great way to deepen my understanding of Scala’s internals while contributing meaningful improvements for the entire community.
I also appreciated Scala Center’s active and welcoming community, clear contribution guidelines, and the chance to work closely with mentors who are experts in the Scala world. All these factors combined made this project an ideal opportunity to grow my skills and make a real impact.
💻 What I’ve Done So Far
Before GSoC officially started, I wanted to show that I could contribute. So, I worked on a pull request (PR) — a set of code changes I suggested for Scaladex.
This PR helped build the foundation for supporting compiler plugins. Here are the key things I did:
Improved Documentation:
I added clear explanations to the project’s README file about how plugin versions are handled. This helps others understand how to name and manage plugin versions correctly.Created Test Setup:
Tests are like little checks that make sure the software works correctly. I wrote some tests to check that plugin versions are detected properly.Made Visual Diagrams:
I drew flowcharts and class diagrams. These pictures show how the code works step-by-step and make it easier for others to understand.
This work made the codebase clearer and ready for bigger improvements later.
🔍 Why Visual Diagrams Helped
Sometimes code logic can be complicated. That’s why I made flowcharts that show how the software decides if a library is a plugin or not, based on version numbers. I also created diagrams of the main classes to explain how they fit together.
These visuals helped me and my mentors see the big picture and plan the next steps clearly.
Example:
#Issues that are fixed and explained through flow charts:
1)Flowchart for Documentation & Compiler Plugin Detection (README + BinaryVersion.scala)
💬 Talking to Mentors & Writing the Proposal
My mentors, Kannupriya Kalra and Adrien Piquerez, were really supportive throughout the process. They appreciated the work I had already done and encouraged me to enhance my proposal by making it clearer and more detailed.
During a call with Kannupriya Mam, we discussed the expectations for the Scaladex project, and she outlined a clear list of tasks I should complete before GSoC officially began:
Learn Scala thoroughly: She suggested I start with Rock the JVM’s YouTube course, but also gave me the flexibility to choose any Scala course that fit my learning style.
Understand the project context better: I watched her own talk explaining GSoC and Scaladex, which helped me grasp the project goals more clearly. You can surely give it a try!
Set up Scaladex locally: It was important to have the full project running on my local system to explore the codebase hands-on.
Review prior GSoC work: She shared a LinkedIn post linking to blogs, work logs, and videos from past GSoC contributors. This gave me real insight into what successful participation looks like.
Her positive feedback and these clear, actionable steps motivated me to put extra effort into preparing my proposal. Because I had already made contributions and showed genuine interest, it helped build trust with my mentors and gave me conidence heading into the program.
📸 My GSoC Selection: A Dream Come True
One of the most unforgettable moments in my journey was receiving the official GSoC selection email — seeing that “Congratulations!” message filled me with pride and joy. It was the result of months of dedication, learning, and support from my mentors and the community.
📧 Here’s a screenshot of my selection email:
But the excitement didn’t stop there!
When I visited the official Google Summer of Code 2025 Projects page, and searched for Scaladex, I saw my name listed under the Scala Center project — a moment I’ll never forget.
🌐 Here’s a screenshot from the GSoC website showing my project:
Being featured on the official website made everything feel real and reminded me how far I’ve come. This recognition also motivates me to give my best throughout the summer and make the most of this opportunity.
💡 What I Learned & What’s Next
Working on this project taught me many things:
Open-source is about teamwork — listening to mentors and other contributors helps a lot.
Writing good documentation and tests is as important as writing the code itself.
It’s better to make small, steady progress than try to do everything at once.
Always communicate early and clearly — it opens doors to help and guidance.
Now, I’m excited to start the next phase, where I will build full support for compiler plugins in Scaladex.
📚 How to Start Your Own GSoC Journey
If you want to try GSoC, here are some tips from my experience:
Start Early:
Explore the organizations and understand their projects well before applying.Join Community Chats:
Ask questions and introduce yourself. Most communities are welcoming!Make Small Contributions:
Fix a typo, improve docs, or write tests. This shows you’re serious and helps you learn.Write a Clear Proposal:
Explain what you want to do, how, and why it matters.
If you’re new and want more help, check out these videos — they explain GSoC simply:
🔗 Useful Links
My GSoC Project: Scaladex Compiler Plugin Support
GitHub Profile: github.com/vidishagawas121
Proposal Drive: My GSoC Proposal
Scala Center Project Repository: scalacenter/scaladex
📬 Let’s Connect!
If you’re interested in Scala, open source, or just want to talk about GSoC, feel free to reach out:
Email: writer.by.passion.123@gmail.com
GitHub: vidishagawas121
LinkedIn: Vidisha Gawas
Thanks so much for reading my story! I hope it helps you start your own exciting journey with open source.
Subscribe to my newsletter
Read articles from Vidisha Gawas directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by
