[[TOC]] = PSC Meeting 2023-08-11 = == Participants == * Anna * Vaclav * Markus * Michael * Huidae * Helli * Vero == Agenda == The topics proposed are: * Past events * Community meeting Prague 2023 aftermath * Send press release to OSGeo.JP * Translate press release to German and send to FOSSGIS e.V. * Add (and/or link) press release to the [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023#Report_and_press_release meeting wiki page] (template section Report and press release) * State of reimbursements (do we need to nudge anyone?) * waiting for FOSSGIS e.V. treasurer: MN has written again to finanzen fossgis de * waiting for OSGeo treasurer * FOSS4G 2023, [https://talks.osgeo.org/foss4g-2023/talk/KLVT3W/ State of GRASS GIS, Martin Landa] (done, [https://www.youtube.com/watch?v=olRSbZ1UpJI&t=1475s video], [https://ctu-geoforall-lab.github.io/grass-gis-talk-foss4g-2023/foss4g2023.html slides] [https://github.com/ctu-geoforall-lab/grass-gis-talk-foss4g-2023 slides source]) * Future events * FOSS4G North America 2023, Baltimore, MD, Oct 23-25 (3 talks, 2 workshops) * FOSS4G-Asia 2023 Seoul (Nov 28 - Dec 2) * [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo Community Sprint 2023], Nov 6-9 (OSGeo Annual Code Sprint, Vienna, Big Data from Space) * Next GRASS GIS virtual sprint * Next GRASS GIS in-person sprint * Release 7.8.8 completed: * News item needed for web site: https://github.com/OSGeo/grass-website/pull/377 * Call for student grants? * Determine topics: * Convert manuals to markdown and use readthedocs/mkdocs style * Have some "technical writing" topics? * homogenization of man pages needed * more examples and reproducible screenshots (generated with notebook, see https://github.com/OSGeo/grass/issues/2594) * improve intro pages in manual * write task oriented articles: vector cleaning, digitizing, raster cleaning, raster resampling * Emphasize mentoring. * Releases and backports * Which branches are we backporting to? * 7.x is now frozen, given that 7.8.8 is out * supported: 8.2 + 8.3 * What releases we are planning for which branch? * When to do 8.4.0? * Community, sponsors, and support at the website (ideally, do the actual work) * How to properly finish >5 years of discussion about location versus project? * [https://github.com/OSGeo/grass/pull/2993 PR 2993 wxGUI: Rename location to project (2023)] * [https://grasswiki.osgeo.org/wiki/GRASS_GIS_at_OSGeo_Community_Sprint_2022#Discuss_naming_and_presentation_of_GRASS_GIS_data_hierarchy GRASS GIS at OSGeo Community Sprint 2022] * [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup Proposals for a new GRASS GIS startup mechanism (2018-2020)] * [https://lists.osgeo.org/pipermail/grass-dev/2018-June/088531.html grass-dev: a proposal to rename "location" (2018)] * [https://lists.osgeo.org/pipermail/grass-dev/2018-March/087870.html grass-dev: Brainstorm about new GRASS GIS startup (2018)] * [https://lists.osgeo.org/pipermail/grass-dev/2015-January/073157.html grass-dev: New splash screen for GRASS GIS 7? (2015)] (Turned into redesign and rename discussion) * Review and update Open Collective * People in [https://opencollective.com/grass?slug=grass#category-ABOUT Our team] * only Martin is missing. * Item in [https://opencollective.com/grass/contribute Become a contributor] * About text which make case for sending money to GRASS GIS (not just for using it). * Start collecting reports on physical artifacts * involve Peter Löwe * Come up with an official way to add items to [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ Google Scholar profile]. * RFCs * Merge [https://github.com/OSGeo/grass/pull/3120 PR 3120 RFC: Version Numbering is adopted] * Merge [https://github.com/OSGeo/grass/pull/2816 PR 2816 RFC: Python Language Support] * Number RFC files in the source code? (Overall, RFC procedure seems to be missing.) * Pending: [https://github.com/OSGeo/grass/pull/2815 PR 2815 RFC: Release Procedure] * Pending: [https://github.com/OSGeo/grass/pull/2813 PR 2813 RFC: Errata] == Minutes == * Location is becoming project * We are doing the rename * Create issue for the overall rename (VP) * Review the roadmap (MB)