Name: Sakir Ahmed
Tell us about yourself:
I’m a CS student pursuing BTech in AI, I came across pgRouting while contributing on grass GIS and spent time going through the project history, past student wikis, and the contribution process. The mix of graph algorithms, C++, and PostgreSQL is exactly the kind of work I want to get into.
Any OSGeo projects and communities you are involved in:
I’ve been contributing to GRASS GIS (OSGeo). My work has been focused on the test suite migration converting legacy shell based tests to pytest for the t.rast.mapcalc module
(PRs #6948 and #6897 and also #6967).
This involved migrating shell tests to pytest, setting up proper GRASS session fixtures, using the Tools API, writing assertions for map counts and temporal types, and handling teardown correctly across CI environments.
I went through multiple review cycles with maintainers (petrasovaa, ninsbl) which taught me a lot about how the project expects tests to be structured.
In pgRouting, I submitted PR #3063 which enabled the clang-tidy cppcoreguidelines-explicit-virtual-functions check and fixing violations across C++ headers was merged and added to the release 4.1.0 milestone.
What do you want to learn / contribute:
PR #3063 got me familiar with pgRouting’s C++ internals for the first time. I want to go further learn how a full algorithm gets built into the codebase end-to-end, from the C++ core to the SQL interface, docs, and tests. The GSoC project feels like the right way to do that properly.
Tech Stack:
- Languages: C++, Python, SQL, JavaScript, HTML5
- Databases: PostgreSQL (plpgsql), MySQL, MongoDB
- Frontend: React
- Tools: Git, docker, kubernetes
Links:
- GitHub: sakirr05 (sakirr) · GitHub