GSoC 2026 Introduction by Soham Babrekar

pgRouting pgrouting-dev
1

Hello pgRouting Community,

I’m Soham, an engineering student with a strong passion for open-source development. With a solid foundation in C++ and a drive to grow as a developer, I’m eager to start contributing to pgRouting and be a part of this vibrant community.

As I set my sights on GSoC 2026, I’m looking forward to engaging deeply with the project — learning from experienced contributors, understanding the codebase, and making meaningful contributions wherever possible.

I would be truly grateful for any guidance on how best to get started, recommended resources, or potential issues to begin with. Excited to collaborate and learn from you all!

Thank you for the warm welcome in advance.

Best regards,

Soham

2

Welcome @Sohamsig

Please review - GSoC Ideas: 2026 · pgRouting/pgrouting Wiki · GitHub

It’s still a work in progress but should be enough to give you an idea of what is expected.

3

Subject: Clarification on my previous PRs (Task 4) of the Intent of application

Hi Vicky Vergara, robe,

I wanted to clarify why I closed my last two PRs from Task 4: Get Familiar with C++. Both PRs were showing 41 files changed instead of just my intended .clang-tidy commit.

This happened because my branches weren’t truly “clean” — they included extra commits from develop/main in addition to my change. Git included these extra commits in the PRs, which caused the unexpected file changes.

I will create a new branch based on the latest upstream develop, cherry-pick only my .clang-tidy commit, and open a clean PR that shows only the intended changes.

Thanks for your understanding!

Best regards,

Soham

1 Like
4

Hello pgRouting Community,

I hope you are doing well. I am excited to share that I have completed all the tasks for the GSoC pgRouting application:

  • Intent of Application

  • Experience with GitHub & Git

  • Local Build of pgRouting

  • Familiarization with C++

  • Exploration of pgRouting functionalities

I have also started drafting my proposal according to GSoC guidelines, documenting all relevant issues, pull requests, and screenshots.

I am eager to contribute actively to pgRouting by exploring new features, fixing issues, and improving documentation. Any feedback or guidance on next steps would be greatly appreciated, as I am committed to making meaningful contributions.

Thank you for your time and support.

Best regards,
Soham Babrekar

5

Hi maintainers,
I wanted to share an update on my PR #3006. I’ve rebased it on the latest develop, aligned it with the recent .clang-tidy changes (by enabling cppcoreguidelines-use-default-member-init as suggested), and all CI checks are now green.

Please let me know if any further changes are needed from my side.
Thanks!

6

Hi @cvvergara,

My PR #3006 was closed and I understand the CI issues that were pointed out.
I’d like to continue improving my older PR #3003, and I will make sure to carefully double-check CI results and address any warnings before pushing further updates.

Please let me know if that’s fine.
Thanks for your guidance.

7

Hi @Sohamsig

The PR’s that were closed count for the task4, for GSoC purposes you are OK.
But from pgRouting point of view:
Sure thing, you can start all over if you want and make another PR.
This time try to make the PR when you are sure that everything is OK.
Start working by doing

git fetch upstream
git checkout upstream/develop
git switch -c the-new-branch-name

If you didn’t finish the work and continue on another day or just before making the PR

git fetch upstream

if you see that the upstream/develop had changes do the rebase

git rebase upstream/develop

and fix conflicts if any

Regards
Vicky

8

Thank you for the clarification and detailed guidance.
I will start from the latest upstream/develop, carefully reapply the changes, and open a fresh PR once I’ve verified that all checks pass and the code is fully aligned with the project guidelines.

I appreciate your feedback and the opportunity to improve.