[[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) * 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 * 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 [[wiki:PSC/Roles]] === Open Motions === ''These entries need a vote from the committee members.'' * SVN write access to Ondřej Pešek as a new core developer * [wiki:RFC/4_ReleaseProcedure RFC 4: Release Procedure] === 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 == For motions, see also [wiki:PSC/Motions PSC Motions]. 2019: * SVN write access to Ondřej Pešek as a new core developer, passed 26 Jan, 2019 2018: * SVN write access to Stefan Blumentrath as a new core developer, passed Jan 30, 2018 2017: * SVN write access to Veronica Andreo as a new core developer, passed Jun 21, 2017 * [https://lists.osgeo.org/pipermail/grass-psc/2017-July/001736.html T-shirts funding] for GRASS GIS Community Sprint at FOSS4G-Europe 2017 + [https://lists.osgeo.org/pipermail/grass-psc/2017-August/001762.html motion result], passed 4 Aug 2017 * [https://lists.osgeo.org/pipermail/grass-psc/2017-July/001745.html Printing stickers and flyers funding] for FOSS4G-Europe 2017 + [https://lists.osgeo.org/pipermail/grass-psc/2017-August/001758.html motion result], passed 4 Aug 2017 * [https://lists.osgeo.org/pipermail/grass-psc/2017-June/001697.html T-shirts funding] given as a present to GRASS GIS original founders + [https://lists.osgeo.org/pipermail/grass-psc/2017-June/001710.html motion result], passed 15 June 2017 * [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Genova_2017 Genova Community Sprint funding], passed 21 Apr 2017. 2016: * [wiki:PSC/Election2016 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 [http://www.youtube.com/results?search_query=grass+gis 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: * [wiki:PSC/Election2012 Election 2012] * [wiki:RFC/1_ProjectSteeringCommitteeGuidelines RFC1: Project Steering Committee Guidelines] (Adopted) * [wiki:RFC/2_LegalAspectsOfCodeContributions RFC2: Legal aspects of code contributions] (Adopted) * [wiki:RFC/3_PSCVotingProcedures RFC 3: PSC Voting Procedures] (Adopted) === Motions === * [wiki:PSC/Motions PSC Motions] === Discussions === * ~~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