I’m Aditya. I recently merged my first open-source PR (fixed a layout bug in GeoServer’s style editor), and I’m now looking to get involved with pgRouting, aiming toward a GSoC 2027 proposal.
I’ve cloned the repo and I’m getting a local build set up. I’d like to start with a small, well-scoped issue to properly learn the codebase — if there’s a good starter task you’d recommend, or something not currently listed on the public tracker, I’d appreciate a pointer.
Happy to share more about my background if useful. Looking forward to contributing.
Following up on your suggestion - I went through the pgRouting workshop end-to-end using real OSM data (Mysuru city) loaded into a local pgrouting_dev database, rather than just skimming through it. I worked through data.rst and graphs.rst, ran the exercises (vertex extraction, connected components, building the vehicle/walking network views), and got a real feel for how functions like pgr_extractVertices and pgr_connectedComponents behave on an actual dataset, not just toy data.
Along the way I picked up a batch of typos, broken RST link formatting, and an exercise-numbering inconsistency across the workshop files, so I opened a single PR covering all of them:
Would appreciate a look whenever you get a chance. Also still keen on a good-first-issue if one turns up — happy to hear from @cvvergara too, as you mentioned.
Thanks for pointing me here — it was a solid way to get properly oriented before jumping into the main codebase.