Beyond the First Commit: My Journey to Rank 46 at ECSoC’26
From discovering open source to contributing 117 merged pull requests across 16 projects — a journey shaped by curiosity, collaboration, continuous learning, and consistency.
Khushi Shah
B.Tech Computer Science and Engineering | PW IOI
Professional Profiles
- GitHub: shahkhushi0307
- LinkedIn: Khushi Shah
- Instagram: @_khushishah_03
ECSoC’26 Resources
Introduction
Open-source development offers something that traditional academic learning often cannot fully replicate: the opportunity to work on real-world software, collaborate with distributed developer communities, understand existing codebases, and contribute to projects used by others.
My journey into this ecosystem began with curiosity and limited practical experience. I had an interest in software development, but I was still learning how collaborative development worked beyond individual projects and academic assignments.
Participating in Elite Coder Summer of Code 2026 (ECSoC’26) became an important turning point in that journey.
By the conclusion of the program on August 31, 2026, I had achieved 48th rank among approximately 13,000 participants and 822 active contributors, with 117 merged pull requests across 16 open-source projects and a 35-day GitHub contribution streak.
These achievements represent months of technical exploration, problem-solving, code reviews, collaboration, and consistent effort.
However, the most meaningful part of this experience was not the final ranking. It was the transformation from someone unfamiliar with open-source contribution workflows into an active contributor capable of navigating multiple repositories and collaborating with project maintainers.
This is the story behind that transformation.
01. The Foundation: My First Industry Experience
I am a B.Tech Computer Science and Engineering student at PW IOI. My initial exposure to collaborative software development came through my first internship at PW LeapX as a Frontend Developer Intern.
The internship introduced me to practical development workflows and provided an opportunity to work in a team environment.
Alongside frontend development, I gained experience with:
- Git and GitHub for version control and collaborative development.
- Working with team members on shared development tasks.
- Understanding project requirements and implementation workflows.
- Building and improving frontend interfaces.
- Participating in a structured software development environment.
This experience gave me a foundation for understanding how software is developed collaboratively.
As I became more comfortable with GitHub, I started exploring public repositories and learning about open-source communities.
I was particularly interested in the opportunity to contribute to existing software, learn from experienced developers, and understand how large projects evolve through community collaboration.
At that stage, I was looking forward to participating in GSSoC. I had the motivation to contribute, but I still needed practical exposure to the open-source contribution process.
02. Discovering ECSoC’26: Taking the First Step
My introduction to ECSoC’26 came through a friend who suggested that I register for Elite Coder Summer of Code 2026.
Initially, I was uncertain about participating.
Although I had some development experience, I lacked a clear understanding of how open-source programs operated in practice. I was unfamiliar with repository selection, issue assignment, maintainer communication, contribution guidelines, and the pull request review process.
I was interested in participating, but I questioned whether I had sufficient experience.
A friend's encouragement helped me overcome that hesitation. Instead of waiting until I felt completely prepared, I decided to register and learn through the experience.
That decision marked the beginning of my ECSoC’26 journey.
The registration itself was straightforward. Understanding how to make meaningful contributions was the real challenge.
I needed to learn how to identify suitable projects, understand their technical requirements, navigate unfamiliar codebases, and submit changes that met the expectations of maintainers.
03. Building Technical Understanding Through PW IOI
An important part of my preparation came through an initiative introduced by PW IOI to encourage students to explore open-source development.
Through this initiative, I received guidance from Abhinav Awasthi Sir and Akash Meruva Sir.
Their mentorship helped me understand the practical aspects of contributing to open-source projects, including:
- Exploring repositories and understanding their architecture.
- Reading documentation and contribution guidelines.
- Identifying issues suitable for contribution.
- Understanding GitHub workflows and pull request procedures.
- Communicating effectively with project maintainers.
- Incorporating review feedback and improving implementations.
This guidance helped me connect my existing development knowledge with the actual practices followed by open-source communities.
I began approaching repositories more systematically, studying their structure, understanding the technologies they used, and identifying issues where I could make meaningful contributions.
I am sincerely grateful to both mentors for their guidance and for helping me develop the confidence to begin contributing.
04. The First Merged Pull Request
The transition from learning about open source to making an actual contribution was an important milestone.
After exploring several repositories, I identified an issue that aligned with my technical understanding and expressed my interest in working on it.
Once the issue was assigned, I began examining the relevant code, understanding the existing implementation, and identifying the changes required to address the problem.
Like most first-time contributors, I had several concerns.
Would my implementation satisfy the acceptance criteria? Had I understood the issue correctly? Would the maintainer approve the changes?
Nevertheless, I completed the implementation and submitted my first pull request.
The pull request was merged the following day.
That first successful merge was a defining moment for me.
It provided practical validation that I could contribute to an existing project, understand its requirements, and deliver changes that met the maintainer's expectations.
More importantly, it changed how I viewed open-source development.
I realised that contributing to an established project requires much more than writing code. It involves understanding context, respecting existing architecture, following development standards, communicating clearly, and responding constructively to feedback.
My first merged pull request gave me the confidence to explore more repositories and take on increasingly challenging contributions.
05. Expanding My Contributions Across Projects
Following my first successful contribution, I decided to remain actively involved throughout ECSoC’26.
During July and August, I consistently explored new repositories, analysed open issues, worked on implementations, and submitted pull requests.
Contributing across multiple projects exposed me to different codebases, development practices, technologies, and engineering approaches.
Each repository presented a different learning opportunity.
Some contributions required understanding unfamiliar project structures. Others involved debugging existing implementations, analysing requirements, or modifying code while maintaining compatibility with established functionality.
The review process also became an important part of my learning.
Maintainers frequently provided suggestions, requested refinements, or highlighted areas where implementations could be improved. Incorporating this feedback helped me develop a stronger understanding of code quality, maintainability, and collaborative engineering.
Balancing contributions with academic responsibilities was another significant challenge.
There were periods when managing college assignments and development work simultaneously required careful planning and discipline.
Rather than focusing only on the number of contributions, I gradually developed a more consistent approach to learning and problem-solving.
During this period, I also maintained a 35-day GitHub contribution streak, reflecting my commitment to making continuous progress.
06. ECSoC’26: Achievements and Milestones
By August 31, 2026, my participation in ECSoC’26 had resulted in several milestones that I am proud to share.
Key achievements
| Achievement | Result |
|---|---|
| ECSoC’26 Global Rank | 48 |
| Merged Pull Requests | 117 |
| Open-Source Projects | 16 |
| GitHub Contribution Streak | 35 days |
| Total Program Participants | Approximately 13,000 |
| Active Contributors | 822 |
Securing 48th rank was a significant achievement, but the numbers alone do not capture the complete experience.
Each merged pull request represented an opportunity to understand a problem, analyse an existing implementation, develop a solution, and collaborate with maintainers.
Contributing to 16 different projects strengthened my ability to adapt to unfamiliar codebases and work across different development environments.
The experience also helped me become more independent in identifying problems, researching solutions, and implementing changes.
Most importantly, it reinforced my understanding that technical growth comes through consistent practical engagement.
07. Recognition by PW IOI
One of the most memorable highlights of this journey was having our ECSoC’26 achievement featured on the official PW IOI Instagram platform.
Being recognised by the institution's official platform was a meaningful moment, particularly because PW IOI had also played an important role in providing the learning environment and guidance that helped me begin my open-source journey.
The recognition made the achievement even more special and highlighted the importance of encouraging students to participate in practical learning opportunities beyond the classroom.
I am grateful to PW IOI for supporting initiatives that expose students to real-world development practices, technical communities, and opportunities for professional growth.
Official recognition:
View the ECSoC’26 Feature on PW IOI's Official Instagram
Visit the Official PW IOI Website
08. Technical and Professional Learnings
Beyond the final ranking and contribution statistics, ECSoC’26 helped me develop several skills that will remain valuable throughout my software engineering journey.
Working with existing codebases
I developed greater confidence in navigating unfamiliar repositories, understanding existing architecture, identifying dependencies, and making changes within established project structures.
Version control and collaborative workflows
Regular contributions strengthened my understanding of Git, GitHub, branches, commits, pull requests, and collaborative development practices.
Code quality and maintainability
Working with maintainers and responding to reviews helped me understand the importance of writing clean, readable, maintainable code that follows project conventions.
Technical problem-solving
Different issues required different approaches to debugging, research, implementation, and testing. This improved my ability to approach unfamiliar technical problems systematically.
Communication and collaboration
Interacting with maintainers helped me understand how to communicate technical decisions, clarify requirements, discuss implementation approaches, and respond professionally to feedback.
Discipline and time management
Maintaining regular contributions alongside academic responsibilities strengthened my ability to manage time and work consistently toward long-term goals.
These experiences have helped me develop a more practical understanding of software engineering and collaborative development.
09. Advice for Students Beginning Their Open-Source Journey
For students who are interested in open source but are unsure about where to begin, my biggest recommendation is to start with what you already know and build from there.
You do not need to master every technology or understand every aspect of software engineering before making your first contribution.
Start by becoming comfortable with Git and GitHub. Explore repositories that interest you, read their documentation, understand their contribution guidelines, and identify issues that match your current skill level.
Do not hesitate to ask maintainers for clarification when necessary.
Your first contribution may require several attempts. Your pull request might receive review comments, and your implementation may need modifications before it is accepted.
These are normal parts of collaborative software development.
Instead of viewing feedback as rejection, treat it as an opportunity to improve your technical understanding.
Most importantly, focus on learning rather than comparing your progress with someone else's achievements.
You do not have to be an expert to contribute to open source. You have to be willing to learn, collaborate, and improve with every contribution.
10. Acknowledgements
This journey has been shaped by the support, encouragement, and guidance of several individuals and communities.
I would like to express my sincere gratitude to:
- My friend, whose encouragement motivated me to register for ECSoC’26 when I was initially hesitant.
- PW LeapX, for providing my first internship experience and introducing me to collaborative software development.
- PW IOI, for creating valuable learning opportunities and encouraging students to participate in open-source initiatives.
- Abhinav Awasthi Sir and Akash Meruva Sir, for their mentorship, guidance, and support in helping me understand the open-source contribution process.
- Open-source maintainers and developer communities, for reviewing my contributions, sharing constructive feedback, and providing an environment for continuous learning.
I am thankful to everyone who contributed to this experience and helped make it a memorable milestone in my journey.
Looking Forward
ECSoC’26 has been an important milestone in my development journey, but I consider it a foundation for what comes next.
The experience has strengthened my interest in open-source software development and encouraged me to continue contributing to meaningful projects, exploring new technologies, and collaborating with developers across different communities.
From being uncertain about my first contribution to achieving 48th rank, this journey has reinforced an important lesson: progress begins when we are willing to step beyond our comfort zone and learn through experience.
117 merged pull requests. 16 open-source projects. A 35-day contribution streak. One transformative learning experience.
These milestones represent not only what I accomplished during ECSoC’26, but also the skills, confidence, and perspective I gained along the way.
I look forward to building on this experience, taking on new challenges, and contributing to the open-source ecosystem in the future.
The journey continues.
Connect With Me
I welcome opportunities to connect with developers, open-source contributors, technology enthusiasts, and communities working on meaningful projects.
- GitHub: github.com/shahkhushi0307
- LinkedIn: Khushi Shah
- Instagram: @_khushishah_03
Top comments (0)