[[TOC]]
''This page contains the agenda of the [wiki:PSC 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 [https://lists.osgeo.org/pipermail/grass-dev/2017-February/thread.html#84239 here])
 * [wiki:RFC/5_Errata RFC 5: GRASS GIS Errata] (Draft)
 * Revisit PSC renewal procedures
   * compare for example terms of the [http://docs.geoserver.org/latest/en/developer/policies/psc.html Geoserver PSC], especially regarding
     * ~~Future PSC members~~
     * Dissolution of PSC
 * PSC: assign roles to the PSC members
   * see [[wiki:PSC/Roles]]
 * [[Marketing]] campaign
=== Open Motions ===

''These entries need a vote from the committee members.''

 * [wiki:RFC/4_ReleaseProcedure RFC 4: Release Procedure]
 * [wiki:RFC/5_Errata RFC 5: GRASS GIS Errata] (Draft)

=== Discussions ===

''These entries do not need a formal vote.''

 * ~~License issues of translation support through [https://launchpad.net/products/grass6 Rosetta] - alternatively consider [http://pootle.wordforge.org/ pootle] (maybe on OSGeo infrastructure)~~
 * ~~discuss use of transifex for some languages~~
   * We use transifex since 2017: https://www.transifex.com/grass-gis/

== Resolved issues and motions ==
=== Motions ===

 * [wiki:PSC/Motions PSC Motions]

=== Discussions ===

 * ~~To enable or not to enable !GitHub Discussions as an additional channel (see discussion [https://lists.osgeo.org/pipermail/grass-dev/2021-January/thread.html#94849 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 [http://www.koders.com/info.aspx?c=ProjectInfo&pid=43B43LPYNXCC4K8PGELQYTZR5A here]~~
 * Add GRASS to Canonical's Rosetta translation project?[[BR]]
 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?[[BR]]
  Update 2007: It appears that Canonical changed their [https://launchpad.net/legal Terms of use] of Rosetta