[[TOC]]
= PSC Meeting 2024-02-09 =

== Participants ==

* Anna Petrasova
* Vaclav Petras
* Helmut Kudrnovsky
* Markus Neteler
* Helena Mitasova
* Huidae Cho
* Michael Barton
* Martin Landa
* Veronica Andreo

== Agenda ==

The topics proposed are:

* Review [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20231110 past minutes] and action points
* PSC elections in 2024 
  * See https://lists.osgeo.org/pipermail/grass-psc/2023-December/002780.html
  * Discussion and decisions from Feb 2021: https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203#Electiondebrief
* GSoC 2024
* Student grant
  * Linda
* Budget
  * Treasurer changed. Thanks Markus and Vaclav!
  * Budget was submitted in Dec 2023.
  * State of budget tracking: see [https://wiki.osgeo.org/wiki/Election_2023_Candidate_Manifestos#What_your_interests_are_in_terms_of_the_board_3 Vicky Vergara's OSGeo board candidate manifesto]
* Future events
  * FOSSGIS, 20-23 March (https://fossgis-konferenz.de/2024/)
  * Tennessee Geographic Information Council (TNGIC), 9-11 April (https://www.tngic.org/annual-conference-2024-)
  * FOSS4G Europe, 01-07 July (https://2024.europe.foss4g.org/)
  * useR! — International R User Conference, 8-11 July (https://user2024.r-project.org/)
  * Next GRASS GIS virtual and in person sprint
    * Budget request for OSGeo contribution submitted in Dec 2023  
    * Around FOSS4G Europe?
* Releases
  * 8.3.2 RC cycle started
  * 8.4.0 planned for April (how about anticipating this a bit?)
* Access rights reformed on !GitHub (Vaclav)
  * Unified structure for teams with write and triage access
    * Historical Subversion committers now have triage access (not write)
    * Current teams are grass-write, grass-addons-write, grass-website-write, grass-promo-write, grass-maintain, grass-admin, grass-triage, grass-discussion-moderators ([https://github.com/orgs/OSGeo/teams/?query=grass list of teams])
* PR procedures updated (Vaclav)
  * At least one review from a person with write access required
    * anyone can still leave reviews which can be taken into account by the reviewer with write access
    * discussions which have a Resolve button need to be resolved
  * A button to easily update the the PR branch from main (merge or rebase)
  * A button to enable automatic merging of PR once reviews are done and checks passed (aka auto-merge)
* Status of open PRs - Martin?
  * Issue: https://github.com/OSGeo/grass/issues/3235 (Set up rules for managing PRs)
  * Proposal: https://github.com/OSGeo/grass/discussions/3396
  * Related discussion: https://github.com/OSGeo/grass/discussions/3364
* Documentation:
  * manual: how to continue with Markdown support (Martin?)
* POSE project
  * state and what's next
* Renaming Location to Project
  * https://lists.osgeo.org/pipermail/grass-user/2023-December/083478.html
* grasswiki authentication
  * https://trac.osgeo.org/osgeo/ticket/2966 (waiting for Robe)
* potential Discourse migration
  * See thread: https://lists.osgeo.org/pipermail/discuss/2023-December/040016.html
* Changes in mailman configurations
  * currently stopped as too invasive, see osgeo-discuss list in Jan 2024
* Linux Professional Institute invitation. See: https://lists.osgeo.org/pipermail/grass-web/2024-January/005154.html
  * MN is in contact
* Inquiry on Partnership for FOSS4G
* Pending RFCs and RFC procedure

== Minutes ==

* Edouard Choniere, new core contributor and github maintainer, joined the meeting and introduced himself to PSC. Welcome @echoix!

* Past minutes action points:
  * VP spoke to Michael Smith and opencollective profile is fixed
  * A PSC motion and request is needed so OSGeo treasurer adds OSGeo credit card to weblate, MN's personal card is beeing used now. 
  
* Motion: Ask OSGeo to put their credit card on weblate instead of MN's personal one.
  * motion passed (8/9)
  * **Action**: Ping OSGeo treasurer with the request.
    * solved and works

* PSC elections:
  * We'll do the elections in the fall so we have a chance to discuss and decide on topics raised by Hernan in https://lists.osgeo.org/pipermail/grass-psc/2023-December/002780.html.
  * **Action**: Vero will write Hernán about this. ''Done''.

* grasswiki authentication - done
  * OSGeo-ID support successfully implemented and tested: see https://lists.osgeo.org/pipermail/grass-announce/2024-February/000185.html

* GSoC 2024:
  * Anna created the ideas page and submitted it: https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
  * Luca got access through new OSGeo-ID support.
  * Huidae has a potential candidate.
  * We all promote GRASS topics once OSGeo is approved as an organization.

* Budget
  * Not clear if OSGeo will approve our request yet, apparently they'll give only 3k per project. We requested 5k for the project and 5k from the sprint funds for a community meeting.
    * [https://wiki.osgeo.org/wiki/Board_Meeting_2024-02-06#OSGeo_Budget_2024 OSGeo wiki]: "OSGeo Projects: 28k $ to be approved. Projects that have not requested a budget will not get a default amount this year. The board will consider specific funding requests if needed. For the projects that asked for a budget, the limit is 2.5k $ this year."

* Student grants:
  * Anna suggested to remove deadlines to apply and keep the call open instead, suggesting a desired timing or dates when PSC will assess the proposals.
  * Linda's work on the history pane is going very well.

* Events
  * Who goes where?
    * FOSSGIS.de March 2024 in Hamburg (MN)
    * TNGIC April (Vero-Caitlin)
    * FOSS4G-Europe July 2024 in Tartu (Vero)
    * FOSS4G World in Brazil (Vero?)
  * Community meeting date: 
    * Second half of June or second half of July; suggested dates: 14/06 until 19/06, 21/06 until 26/06, or 12/07 until 17/07.
    * **Action**: Martin will check with CTU again, but we can anyway try to search/think of other places. NCSU place in Prague seems not available/difficult to get (?). 
    * We'll continue discussions and definitions via email.

* Releases:
  * 8.3.2: MN suggests to release asap as it is overdue.
    * Point releases every 3-4 months.
  * 8.4.0: MN suggests to release it end of Feb.
    * New changes in GUI need testing before release, ML did and will heavily test it. **Action**: All test 8.4!
    * Prepare for 8.4.1 in case of emergency
    * There are a lot of macOS fixes, better experience than 8.3
    * Merge Linda’s work and location-to-project rename 

* Github access rights/permissions:
  * Now 14 people have write access, inactive (less than 25 commits in last year) svn access people are restricted, new rules for merging (review is required from someone with write access), merging requires passing at least some checks and all conversations solved. 
  * The idea of auto-merge is to merge ahead of time as long as all requirements are met.
  * Update with merge or rebase work, but merge is preferred because all is preserved. 
  * **Action**: Document this somewhere, e.g. contributing.md.
  * **Action**: VP: Check if subsequent changes dismiss old reviews.
    * Done: Configuration updated. Reviewable changes now dismiss stale reviews. (Change in the code turns old approving review into a comment and new review is needed for merge or auto-merge to happen.)

* Documentation
  * GRASS docs are falling behind, many pages lack examples and screenshots
  * Suggestion: migrate HTML docs to markdown; MN already did some testing.
    * We have now –md-description in g.parser to auto-generate the module description in markdown
  * Next is to convert all html pages to markdown
    * Use mkdocs (or similar) style then as it offers build-in search engine
  * Jupyter notebooks with examples stored with modules would make running examples and testing so much easier

* Discourse migration
  * Apparently (young) newcomers do not use mailing list, we see a decline in subscriptions.
  * In theory, discourse can be used as the mailing list after first sign up in discourse and configuration. See [https://forum.comses.net/top?period=daily example]. There have also been attempts to make cross posting possible.
  * We all agree that keeping our history is most relevant. MN mentioned mbox with all history file can possibly be imported, currently under investigation.
  * mailman3 ([https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ example archive], also [https://discussion.fedoraproject.org/c/news/5 Fedora mailman3]) which looks more modern than mailman2 is for some reason not in the table of OSGeo-SAC
    * OSGeo-Ticket: Migrate mailing lists to Mailman3: https://trac.osgeo.org/osgeo/ticket/3028
    * MN's comment in the Trac ticket on mailman3 also arrived on discourse: https://discourse.osgeo.org/t/osgeo-3028-migrate-mailing-lists-to-mailman3/4698/2
  * We will wait until issues are solved, especially history and proper cross-posting. **Action**: Meanwhile we can all experiment by subscribing to some category, eg. OSGeo-SAC. 

* POSE project:
  * Corey leading an effort to do more than 65 interviews. NCSU team will report to PSC on the results of this effort. They will send an invitation to a meeting.
  * Vero will be working within the project from March 1st until August 30th.

* Linux Professional Institute invitation: 
  * MN is in contact with them, he has an interview on Feb 20th.
    * interview done and in editing pipeline of LPI

* Inquiry on Partnership for FOSS4G: 
  * VP will speak to them.

* Postponed: 
  * PR procedures and status of the too many open PRs
  * Pending RFCs and RFC procedure