Hi @annakrat and GRASS mentors,
Excited to see GRASS participating in GSoC 2026 under the NumFOCUS umbrella.
I’ve recently started contributing to GRASS Addons to get familiar with the codebase and workflows. So far, my contributions include:
-
Working on Issue #1071 (grass-addons): improving module interface consistency in
v.boxplot, including adding arotate_labelsoption and deprecating a legacy flag. -
Contributing to Issue #830 (grass-addons) related to Landsat Collection 1 deprecation:
-
Updated defaults in
i.landsat.qato encourage use of Collection 2 datasets -
Opened PR #1559 (grass8) which passed all CI checks.
-
Through these, I’ve been learning:
-
GRASS module interfaces and option/flag standards
-
Python-based GRASS addons
-
Documentation updates and backward-compatibility considerations
-
Git/GitHub workflow, CI, and code review process
For GSoC 2026, I’m particularly interested in projects involving:
-
Python tooling and maintenance
-
Improving usability and consistency of GRASS modules
-
Adding tests and modernizing existing code where possible
I plan to continue contributing with small but meaningful fixes and improvements while exploring areas where I can make sustained contributions.
I’d appreciate any guidance on:
-
Which areas/modules would benefit most from newcomer contributions before proposal season
-
What maintainers value most when evaluating GSoC proposals for GRASS
Thanks for your time and for maintaining such a welcoming project.
Best regards,
Arth Patel