PSC Meeting 2026-02-13

From GRASS-Wiki
Jump to navigation Jump to search

Participants

  • Anna
  • Vashek
  • Nicklas
  • Markus
  • Paulo
  • Linda
  • Helli
  • Huidae
  • Vero
  • Luca (guest)

Agenda

The topics proposed are:

  • Annual budget request submitted to OSGeo
  • Community Meeting - San Michele: date, planning, budget requests
  • Releases
  • GSoC
  • AI policy
  • Plan PSC elections/role changes for later this year (some of us have been in PSC since Feb 2021)
  • Budget
    • Where are we at time?
    • Fundraising efforts

Minutes

1. Budget

  • OSGeo:
    • The annual budget request was submitted. See https://wiki.osgeo.org/wiki/GRASS_Budget_2026. OSGeo has allocated $1,600 of the $2,000 originally requested. Budget for swags should be requested from the Marketing Committee, which is why they cut 400 USD.
  • Numfocus
    • Their interface for money is not as transparent as OpenCollective; there’s no public view of the contributors or the money we have in their bucket
    • We've been with them for a year now, and they are still not our fiscal hosts in Redbubble and OpenCollective. They are also going through a transition.

2. Community Meeting - San Michele

  • OSGeo allocated 2500 USD, originally requested 5500 USD. See: https://wiki.osgeo.org/wiki/GRASS_Community_Meeting_2026:_Budget.
  • By the beginning of March, Luca will meet FEM director, and we should then have an idea if we can stay at Convito in San Michele, so everything happens in San Michele, or if not, we search for university options in Trento, i.e., working rooms and housing.
  • [Action] Create a wiki for the event.
  • [Action] FOSSGIS e.V. request: will be handled by MN based on the one from 2024

3. Annual report 2025

  • Published as a news item on the website
  • It also served to meet the OSGeo requirement for budget request
  • Nice new writing style with mentions to people actually doing things, as well as funding

4. Releases

  • MN, NL, and Edouard had a branching session
  • New 8.5 branch: https://github.com/OSGeo/grass/tree/releasebranch_8_5
  • Waiting for Martin Landa to create the branch on Windows server
  • Jupyter integration should be ready soon and will be backported to 8.5, to be part of the release.
  • CMake is mostly functional, even for addons (those that were added), but documentation cannot yet be built with CMake.
  • NL requested us to test CMake: https://grasswiki.osgeo.org/wiki/Compile_and_Install_With_CMake
  • HC: Fixing issues in CMake for Windows.
  • FHS is not ready yet; there's a big PR waiting for after the release.
  • Conda: HC is working on a conda package for Windows.
  • Documentation: Materials for Mkdocs style is retiring, we should transition to a supported theme. Just maybe not for the 8.5 release.

5. GSoC

  • First year we participate under Numfocus if they are accepted
  • We don’t know how many students we’ll get; it’s not clear how it works with Numfocus (is there a GSoC liaison/responsible person as in OSGeo?)

6. GRASS website

  • There's a new version of packages and dependencies soon to be deployed
  • Build to be moved to github-actions. Then the artifact has to be uploaded to OSGeo server (limitation: it needs a token that expires yearly).
  • Corey to be added to the list of GRASS people with access to the OSGeo server
    • [Action] VP will invite him, then create the SAC ticket needed
  • conda missing from the download page, issue created
  • download logos were broken for > half a year (?) and nobody realized this, issue created

7. AI policy

  • Included in the main repo: https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#ai-use-policy
  • Simple - straightforward criteria that people might actually read, sort of guarantee/reference to close bad/meaningless PRs.
  • Anna wrote it in response to the huge amount of PRs we are getting lately that are clearly created with AI, with no further understanding of GRASS.
  • Many PRs are about tests, but they are not meaningful tests. It would be interesting to have instructions to create tests, so that contributors can train AI with instructions and create better tests.
    • Corey is preparing instructions for Copilot, so it has context for code writing/reviewing.

8. PSC elections

  • Some PSC members have been in PSC since Feb 2021, and as we decided back then, mandates should last max 6 years.
  • [Action] Start planning by July, during the Community Meeting.

9. Mailman

  • Move translation, grass-gui and grass-stats lists to read-only mode; make a last post saying we are closing it, and ask SAC to do so (keeping their archives).
Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=PSC_Meeting_2026-02-13&oldid=28804"