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)
• 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
    • Stepping Down
    • Dissolution of PSC
• Revisit PSC election procedure
  • add a candidate campaign period between nomination and voting: candidates should express what they plan to do if elected
• PSC: assign roles to the PSC members
  • see PSC/Roles

Open Motions

These entries need a vote from the committee members.

• RFC 4: Release Procedure

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

Resolved issues

For motions, see PSC Motions.

2017:

• ​T-shirts funding for GRASS GIS Community Sprint at FOSS4G-Europe 2017 + motion tbd
• ​Printing stickers and flyers funding for FOSS4G-Europe 2017 + ​motion result, passed 4 Aug 2017
• ​T-shirts funding given as a present to GRASS GIS original founders + ​motion result, passed 15 June 2017
• ​Genova Community Sprint funding, passed 21 Apr 2017.

2016:

• Election 2016

2013:

• GRASS GIS - 30th birthday upcoming! MN is in contact with Jim Westervelt to identify the "precise" date. So we want to celebrate that all over the globe :) And on other planets, too, since we support extraterrestrial coordinate systems.
  • Prepare new promo material. Best would be to get designer(s) for it.
  • Better populate the ​GRASS GIS videos on YouTube - make it a channel?
  • https://grass.osgeo.org/news/27/15/30-years-of-GRASS-GIS-development/
• Revisit the license of the Web pages and manual pages. It may be appropriate to change to a Creative Commons license which are widely accepted now.
• Moritz Lennert suggests: have some reflection on release strategy and notably GRASS 7 release. Maybe we could at least envisage some form of technology preview release that would allow us to where we stand.

2012 and older:

• Election 2012
• RFC1: Project Steering Committee Guidelines (Adopted)
• RFC2: Legal aspects of code contributions (Adopted)
• RFC 3: PSC Voting Procedures (Adopted)

Motions

• PSC Motions

Discussions

• GRASS on koders.com: 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