Hi GRASS folks ... Abhimanyu here!

GRASS GRASS developer
1

I’m Abhimanyu Gupta (Abhi-d-gr8 on GitHub), a 3rd-year B.Tech student at LNMIIT .

I found GRASS through the NumFOCUS GSoC umbrella and wanted to introduce myself now that I’ve started contributing. My approach has been to learn the project by doing the work end-to-end getting the workflow running, picking up real issues, opening PRs, and going through the review/CI loop. I deliberately tried to push as far as I could on my own first…it helped me understand the codebase and the expectations around style, tests, and review.

Over the last few days I’ve opened a few PRs across GRASS and the GRASS website:
https://github.com/OSGeo/grass/pull/6927
https://github.com/OSGeo/grass/pull/6930
https://github.com/OSGeo/grass/pull/6984
https://github.com/OSGeo/grass-website/pull/589

Some of these have already received review (including from @annakrat and @wenzeslaus ), and I’m continuing to incorporate feedback.

I’ll also admit I probably pinged Anna a bit too much early on while I was getting oriented so I’m genuinely grateful for the patience and guidance. Things are starting to click now, and I want to be more intentional about contributing in the areas that matter most.

Going forward, I’m most comfortable in C/C++ and I’m exploring GSoC, but my main priority is to become a consistent, dependable contributor. Since there are many possible directions, I’d appreciate guidance on where sustained work would be most useful right now specific modules needing attention, test coverage gaps, CI reliability, or ongoing refactors that would benefit from extra hands.

If there’s an area where I can take ownership of a small stream of work and keep shipping improvements over time, I’d be happy to align with that.

Thank You for reading ,
Abhimanyu

2

Thanks for your contributions so far! Please be patient with reviews and iterations on the PRs. You are welcome to apply for GSoC (as long as NumFOCUS is part of it, the org applications are not done yet). But we are definitely looking for long-term contributors!

Beside bug fixes, you can always find a tool and write or expand a test, improve documentation, run cppcheck, or provide review to another PR.

3

I’ll be patient with reviews and iterations, and focus on contributing consistently over time. For now, I plan to strengthen tests and documentation around the areas I’ve already worked on, and also start reviewing other PRs to better understand the codebase and ongoing work.

If there’s any particular tool or area where extra attention would be especially useful right now, I’d be happy to focus there. Otherwise, I’ll keep picking up issues organically and improving things step by step.

On a side note, I’ve been running into some local setup issues on my end (macOS, M3 Air), particularly with installing GRASS via osgeo4mac … I keep hitting an undefined method 'cellar' for an instance of BottleSpecification error despite following the installation steps from scratch and trying a few suggestions from others. I’m still digging into it and will sort it out, but wanted to mention it in case this is a known issue.

Thanks again for your guidance and I am looking forward to contributing more!