This page contains the agenda of the GRASS Project Steering Commitee.

Open issues

  • grass-dev: elect new core developers (define some criteria on the way)
    • e.g., must have at least one accepted/reviewed pull request
  • define long term support, which GRASS GIS versions? (see discussion here)
  • RFC 5: GRASS GIS Errata (Draft)
  • Revisit PSC renewal procedures
    • compare for example terms of the Geoserver PSC, especially regarding
      • Future PSC members
      • Dissolution of PSC
  • PSC: assign roles to the PSC members
  • Marketing campaign

Open Motions

These entries need a vote from the committee members.


These entries do not need a formal vote.

Resolved issues and motions



  • To enable or not to enable GitHub Discussions as an additional channel (see discussion here)
  • GitHub repos: renaming of our 'master' branch to a less insensitive name as 'main'. See
  • Solved for Election 2020: Revisit PSC election procedure
    • add a candidate campaign period between nomination and voting: candidates should express what they plan to do if elected
  • GRASS on recommendation to do so. Now available here
  • Add GRASS to Canonical's Rosetta translation project?
    Unresolved issue: a translation is a derivative and non-original work, and Canonical demands BSD-style copyright assignment of translations submitted through them (but not translations coming from the project). Could a translation back to english from one of those be a end-run around our copyright and the GPL?
    Update 2007: It appears that Canonical changed their Terms of use of Rosetta
Last modified 5 months ago Last modified on Jan 6, 2022, 4:32:40 PM
Note: See TracWiki for help on using the wiki.