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

Open issues

• define concept for backport labels on GitHub: we need labels with indication of specific versions, as done in GDAL
• 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
  • see PSC/Roles
• ongoing Marketing campaign

Open Motions

These entries need a vote from the committee members.

• RFC 4: Release Procedure
• RFC 5: GRASS GIS Errata (Draft)

Discussions

These entries do not need a formal vote.

• License issues of translation support through ​Rosetta - alternatively consider ​pootle (maybe on OSGeo infrastructure)
• discuss use of transifex for some languages
  • We use transifex since 2017: ​https://www.transifex.com/grass-gis/
  • Meanwhile we migrated to weblate in 2022: ​https://weblate.osgeo.org/projects/grass-gis/

Resolved issues and motions

Motions

• PSC Motions

Discussions

• 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 ​https://github.com/github/renaming
• 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 koders.com: recommendation to do so. Now available ​here