How I achieved Rank 46 in ECSoC’26 through consistent open-source contributions, mentorship, and hands-on learning.
Sumit Tiwari · B.Tech CSE Student at PW IOI Pune
ECSoC’26 Achievement: Rank 46 · 98 Merged Pull Requests · 14 Projects · 35-Day GitHub Contribution Streak
About me
I am Sumit Tiwari, a second-year B.Tech Computer Science and Engineering student at PW IOI Pune, interested in software development and open-source collaboration.
My journey through the European Summer of Code–style open-source program, ECSoC Elite Summer of Code 2026, culminated in securing Rank 46 among approximately 13,000 participants, with 822 active contributors.
Throughout the program, I achieved 98 merged pull requests across 14 projects and maintained a 35-day GitHub contribution streak.
These results came from a process of continuous learning. I began by developing my understanding of collaborative software development during my first internship. I then explored open source, learned how to contribute to established repositories, and gradually became more confident working with real-world codebases.
This is the story of that journey, the people who helped me along the way, and the lessons I will carry into my future as a software developer.
1. Where it started: My first internship at PW LeapX
My introduction to collaborative software development began with my first internship as a Frontend Developer at PW LeapX.
Before the internship, most of my experience came from learning programming concepts and building projects. Working with a team introduced me to the practical side of software development.
I learned how developers use Git and GitHub to manage changes, create branches, submit pull requests, and collaborate on shared codebases. I also gained experience building responsive user interfaces and working within an established development workflow.
One of the most important lessons was understanding that contributing to a software project requires more than writing code. You need to understand the requirements, respect existing conventions, communicate with your teammates, and make changes that fit the project.
That experience sparked my interest in contributing to projects beyond my own work.
I began exploring open-source programs, including GirlScript Summer of Code, with the goal of eventually becoming an active contributor.
At the time, I understood the basics of development workflows, but I had yet to experience the complete process of contributing to projects maintained by an external community.
2. Discovering ECSoC’26
I discovered ECSoC Elite Summer of Code 2026 while browsing LinkedIn.
The opportunity to work on real projects, learn from experienced developers, and contribute to open-source communities immediately interested me. I registered for the program, looking forward to applying what I had learned.
However, I quickly realised that knowing Git and GitHub was only the starting point.
I needed to understand how to identify suitable repositories, select issues, communicate with maintainers, follow contribution guidelines, and prepare pull requests that met a project's requirements.
Even simple questions could be challenging at first. Which issue should I work on? How should I approach a maintainer? What should I do when I encounter an unfamiliar part of a codebase?
I realised that becoming an effective open-source contributor required practical experience and a willingness to learn independently.
Rather than treating these challenges as reasons to wait, I began looking for ways to understand the process and get involved.
3. Learning through the PW IOI open-source initiative
Around the same time, PW IOI introduced an initiative to help students explore open source and contribute to real-world projects.
With guidance from Abhinav Awasthi Sir and Aaksh Meruva Sir, I developed a better understanding of how open-source communities operate.
I learned how to explore repositories, understand project documentation, identify appropriate issues, communicate with maintainers, and follow the pull request workflow.
Their guidance helped me connect what I already knew about development tools with the practical steps required to contribute to an existing project.
I began exploring repositories independently, reading their code, and identifying issues that matched my current skills while giving me opportunities to learn something new.
This changed my approach to learning software development. Instead of waiting until I felt completely prepared, I started working on real problems and learning from the process.
4. My first merged pull request
My first merged pull request was an important milestone because it gave me my first real experience of contributing to a project maintained by other developers.
While exploring a repository, I found an issue I believed I could solve. I commented on it, received the assignment, and started working on the implementation.
After submitting my pull request, I waited to see whether the maintainer would accept my changes.
Since this was my first contribution, I was naturally uncertain about the outcome. I wanted to know whether my solution met the project's requirements and whether I had approached the problem correctly.
My pull request was merged just one day later.
That experience gave me the confidence to continue contributing.
It showed me how an individual contribution, even a small one, could become part of a larger project. It also helped me understand the value of carefully reading an issue, working within an existing codebase, and following the project's contribution process.
After that first merge, I started approaching open source differently. I became more willing to explore unfamiliar repositories, investigate problems, and learn through implementation and review.
My first merged pull request did not make me an expert, but it gave me a reason to keep improving.
5. Building consistency across open-source projects
Throughout July and August 2026, I continued contributing to open-source projects and became increasingly comfortable with collaborative development.
Each repository introduced its own structure, conventions, and expectations. Understanding an unfamiliar codebase often required reading documentation, tracing existing implementations, investigating related files, and testing potential solutions.
Not every issue was straightforward, and progress was not always immediate. Balancing contributions with my academic responsibilities also required planning and discipline.
I continued working through these challenges, treating each issue as an opportunity to improve my understanding of software development.
During this period, I maintained a 35-day GitHub contribution streak.
The streak reflected my effort to stay engaged with development consistently. Some contributions involved more investigation than implementation, while others required me to understand an existing feature before making a change.
Over time, I became more comfortable navigating repositories, debugging code, following project conventions, and responding to feedback from maintainers.
I also developed a better appreciation for code review. A pull request is not simply a submission; it is part of a collaborative process in which the solution can be examined, discussed, and improved.
These experiences helped me develop a more systematic approach to solving problems.
6. ECSoC’26 results and achievements
My efforts culminated in securing Rank 46 in ECSoC Elite Summer of Code 2026.
The program had approximately 13,000 participants, including 822 active contributors.
My achievements during the program were:
| Metric | Achievement |
|---|---|
| Final ECSoC’26 rank | 46 |
| Approximate program participants | 13,000 |
| Active contributors | 822 |
| Merged pull requests | 98 |
| Projects contributed to | 14 |
| GitHub contribution streak | 35 days |
Each milestone represents a different part of my experience, from exploring repositories and understanding issues to submitting contributions and learning through code reviews.
Securing Rank 46 is an achievement I am proud of, particularly because I began the journey with limited practical experience in open-source contribution workflows.
The progress I made throughout the program strengthened my confidence in working with unfamiliar codebases and collaborating with developers outside my immediate academic environment.
I see this ranking as a milestone in my development journey and a foundation for the work I want to do next.
Explore my ECSoC’26 journey:
7. Recognition from PW IOI
One of the highlights of this journey was having my achievement featured on the PW IOI Instagram page.
For me, this recognition was an encouraging reminder of the value of practical learning and participation in open-source communities.
As a student, I believe opportunities to work on real-world projects are an important part of developing engineering skills. Experiences like ECSoC’26 help students apply what they learn, understand collaborative development, and discover areas in which they want to grow.
I appreciate PW IOI for encouraging students to pursue these opportunities and for supporting learning beyond the classroom.
You can view the feature here:
View my ECSoC’26 feature on PW IOI's Instagram
Visit the official PW IOI website
I hope sharing my experience encourages other students to explore open source and take their first steps towards contributing to projects.
8. What I learned from ECSoC’26
The most valuable part of ECSoC’26 was the practical experience I gained throughout the program.
Understanding existing codebases
Contributing to an established project requires understanding its structure and existing implementation before making changes. I learned to spend time investigating a problem rather than immediately jumping into the code.
Learning through code review
Feedback from maintainers is an important part of collaborative development. Reviews help contributors understand project expectations and improve their solutions.
Staying consistent
Maintaining a contribution streak taught me the value of regular effort. Progress can be gradual, especially when working on unfamiliar problems, but continued practice builds experience.
Communicating with maintainers
Open-source development involves collaboration. Clear communication, thoughtful issue discussions, and following contribution guidelines help contributors work more effectively with project communities.
Becoming comfortable with unfamiliar problems
Not every issue matches something you have already learned. I became more comfortable researching unfamiliar concepts, exploring existing implementations, and working towards a solution step by step.
These lessons have influenced how I approach software development, and I intend to continue applying them to future projects.
9. Looking ahead
As a second-year B.Tech Computer Science and Engineering student at PW IOI Pune, I want to build on the foundation I developed through ECSoC’26.
My focus is on contributing to more open-source projects, taking on technically challenging issues, and strengthening my understanding of software engineering practices.
I also want to continue learning from experienced developers and collaborating with communities that build and maintain useful software.
Open source has given me a practical way to apply my knowledge, learn from feedback, and work on problems beyond the scope of my individual projects.
I look forward to continuing this journey, building better software, and making meaningful contributions to the developer community.
Acknowledgements
I would like to express my sincere gratitude to Abhinav Awasthi Sir and Aaksh Meruva Sir for their guidance and for helping students understand the practical aspects of open-source development.
I am also thankful to PW IOI for encouraging students to explore opportunities beyond the classroom.
My appreciation goes to the ECSoC’26 community, the maintainers who reviewed my contributions, and the developers whose projects provided opportunities to learn and collaborate.
Every issue I worked on and every review I received contributed to my growth throughout this experience.
Final thoughts
When I first explored open source, I was still learning how to identify issues, work with unfamiliar repositories, and submit contributions that met project requirements.
By the end of ECSoC’26, I had achieved 98 merged pull requests across 14 projects, maintained a 35-day GitHub contribution streak, and secured Rank 46.
I am proud of these results, but I value the experience behind them just as much. The journey helped me become more confident in approaching unfamiliar problems and gave me a clearer understanding of collaborative software development.
I am still learning, and there is much more I want to explore.
If there is one lesson I would share with students considering open source, it is this: start with what you know, be willing to learn what you don't, and give yourself the opportunity to improve through practice.
My ECSoC’26 journey is one milestone in a much longer path, and I look forward to what comes next.
Connect with me
I enjoy connecting with developers, students, and open-source contributors who are interested in learning, building projects, and collaborating with the community.
- GitHub: github.com/sumittiwari1302
- LinkedIn: linkedin.com/in/sumit-tiwari-b18701380
- Instagram: @sumittiwari8259
- ECSoC’26 Profile: View my contributor profile
Thank you for reading about my journey.
#ECSoC26 #OpenSource #GitHub #SoftwareEngineering #PWIOI #StudentDeveloper #OpenSourceContribution
Top comments (0)