PSC Meeting 2026-11-13: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(→‎Minutes: some clarifications added)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Participants ==
== Participants ==


* TBD
* Helli
* Anna
* Vashek
* Nicklas
* Paulo
* Linda
* Vero
* Huidae
* Corey
* Markus
* Alen (invited)


== Agenda ==
== Agenda ==
Line 9: Line 19:
* Review action points from previous meetings
* Review action points from previous meetings
* Soeren's contribution: https://github.com/OSGeo/grass/discussions/8168
* Soeren's contribution: https://github.com/OSGeo/grass/discussions/8168
* PSC elections aftermath: Thanks Markus, welcome Corey!  
* PSC elections aftermath - Thanks, Markus; welcome, Corey!  
** Election new PSC chair
** Election of new PSC chair
* Release
* Release 8.6
* Contributor's list
* Contributors' list files in the repo
* Alen's proposal for 2027 Community Meeting
* Alen's proposal for 2027 Community Meeting
* Suggestion to have separate developer meetings
* Suggestion to have separate developer meetings
== Minutes ==
'''1. Review of past minutes'''
* Reimbursements for the Community Meeting 2026 are done. NumFOCUS has not received the money from FOSSGIS e.V. yet.
* NumFOCUS small development grant: Linda applied but has not received a reply.
* NumFOCUS is going through another internal transition.
* Website and infrastructure:
** [Action] Corey to ping the OSGeo SAC people in the Matrix channel regarding Matomo.
'''2. PSC Elections 2026'''
* Election page: https://grasswiki.osgeo.org/wiki/PSC_Election_2026
* Results: https://grasswiki.osgeo.org/wiki/PSC_Election_2026#Results_3
* Notes from Hernán (CRO) on the election aftermath: https://lists.osgeo.org/pipermail/grass-psc/2026-November/003138.html
* '''Motion: Anna as new PSC chair. Motion passed.''' Congratulations Anna!
* [Action] Vero to compile a list of chair tasks and credentials to hand over to Anna.
* [Action] Publish a news item with the election results, and a separate one to thank Markus Neteler for his 25 years on the PSC.
'''3. Developer meetings and GRASS office hours'''
* Proposal to hold developer meetings separate from PSC meetings, to foster human interaction in times of AI contributions, discuss the development roadmap, and do actual work together.
* Proposal for GRASS office hours every two weeks. These will be open meetings, ideally including people outside the core development team and the PSC, potentially at different times of the day to reach people in different time zones.
'''4. GRASS Community Meeting 2027'''
* Alen presented the proposal to host and organize the 2027 GRASS community meeting in Ljubljana, with OSGeo Slovenia.
* Proposed dates: June 26 to July 2, 2027, or July 10 to 17, 2027.
* Two venue options are under consideration.
* OSGeo Slovenia has a certain budget to cover accommodation. Discussions about sponsors and meals are ongoing.
* [Action] Corey to ask AGU editors, and possibly others, about supporting the event.
'''5. Rewrite of the temporal framework'''
* Sören's proposed rewrite of the temporal framework: https://github.com/OSGeo/grass/discussions/8168
* The PSC is fine with AI-written, human-reviewed code, but the contribution should be split into reviewable chunks. Revision by devs is the bottleneck.
* Sören's involvement is needed during the merging process.
* One option is to merge the tests first, to see what breaks and what remains to be done.
* [Action] Vashek to contact Sören and propose a video call.
** Done. We met Sunday morning, Nov 14.
'''6. Release 8.6'''
* Releases will be discussed in the new developer meetings, possibly starting with a December 2026 meeting.
* Nicklas is working on relative paths to finalize work on CMake/FHS.
'''7. Addons builds for Windows'''
* Proposal to build Windows add-ons in CI as a release, so assets can be uploaded directly from CI and there is no need to upload from GitHub to the GRASS website server.
* The same approach could help with uploading documentation to the server, removing the need for a GitHub token and for logic to guess the latest CI artifact.
'''8. Security'''
* A company has been reporting security issues found in GRASS. A private Signal group has been set up to handle these reports.
'''9. Contributor list'''
* There are currently four lists of authors/contributors in the codebase, and none of them are up to date.
* A procedure is needed to define who counts as an active contributor or developer, and when and how someone stops being included in the citation file.
* Proposal: include in CITATION.cff the people who are active in the current GRASS development team. For example: people who have at least n PRs merged in the last development cycle. This differs from the criteria for voters in PSC elections.
'''10. Other issues'''
* Vashek would like to step down as treasurer. We will create the budget in December and then decide on a new person for the role.
** [Action] Vashek to schedule the budget meeting for late November or early December.
* OSGeo/grass-mcp was mentioned: https://github.com/OSGeo/grass-mcp.
* [Action] @all: Corey, requested help with reviewing open website PRs. Corey will update the website to reflect the new PSC.


[[Category:PSC]]
[[Category:PSC]]

Latest revision as of 16:30, 16 November 2026

Participants

  • Helli
  • Anna
  • Vashek
  • Nicklas
  • Paulo
  • Linda
  • Vero
  • Huidae
  • Corey
  • Markus
  • Alen (invited)

Agenda

The topics proposed are:

  • Review action points from previous meetings
  • Soeren's contribution: https://github.com/OSGeo/grass/discussions/8168
  • PSC elections aftermath - Thanks, Markus; welcome, Corey!
    • Election of new PSC chair
  • Release 8.6
  • Contributors' list files in the repo
  • Alen's proposal for 2027 Community Meeting
  • Suggestion to have separate developer meetings

Minutes

1. Review of past minutes

  • Reimbursements for the Community Meeting 2026 are done. NumFOCUS has not received the money from FOSSGIS e.V. yet.
  • NumFOCUS small development grant: Linda applied but has not received a reply.
  • NumFOCUS is going through another internal transition.
  • Website and infrastructure:
    • [Action] Corey to ping the OSGeo SAC people in the Matrix channel regarding Matomo.

2. PSC Elections 2026

3. Developer meetings and GRASS office hours

  • Proposal to hold developer meetings separate from PSC meetings, to foster human interaction in times of AI contributions, discuss the development roadmap, and do actual work together.
  • Proposal for GRASS office hours every two weeks. These will be open meetings, ideally including people outside the core development team and the PSC, potentially at different times of the day to reach people in different time zones.

4. GRASS Community Meeting 2027

  • Alen presented the proposal to host and organize the 2027 GRASS community meeting in Ljubljana, with OSGeo Slovenia.
  • Proposed dates: June 26 to July 2, 2027, or July 10 to 17, 2027.
  • Two venue options are under consideration.
  • OSGeo Slovenia has a certain budget to cover accommodation. Discussions about sponsors and meals are ongoing.
  • [Action] Corey to ask AGU editors, and possibly others, about supporting the event.

5. Rewrite of the temporal framework

  • Sören's proposed rewrite of the temporal framework: https://github.com/OSGeo/grass/discussions/8168
  • The PSC is fine with AI-written, human-reviewed code, but the contribution should be split into reviewable chunks. Revision by devs is the bottleneck.
  • Sören's involvement is needed during the merging process.
  • One option is to merge the tests first, to see what breaks and what remains to be done.
  • [Action] Vashek to contact Sören and propose a video call.
    • Done. We met Sunday morning, Nov 14.

6. Release 8.6

  • Releases will be discussed in the new developer meetings, possibly starting with a December 2026 meeting.
  • Nicklas is working on relative paths to finalize work on CMake/FHS.

7. Addons builds for Windows

  • Proposal to build Windows add-ons in CI as a release, so assets can be uploaded directly from CI and there is no need to upload from GitHub to the GRASS website server.
  • The same approach could help with uploading documentation to the server, removing the need for a GitHub token and for logic to guess the latest CI artifact.

8. Security

  • A company has been reporting security issues found in GRASS. A private Signal group has been set up to handle these reports.

9. Contributor list

  • There are currently four lists of authors/contributors in the codebase, and none of them are up to date.
  • A procedure is needed to define who counts as an active contributor or developer, and when and how someone stops being included in the citation file.
  • Proposal: include in CITATION.cff the people who are active in the current GRASS development team. For example: people who have at least n PRs merged in the last development cycle. This differs from the criteria for voters in PSC elections.

10. Other issues

  • Vashek would like to step down as treasurer. We will create the budget in December and then decide on a new person for the role.
    • [Action] Vashek to schedule the budget meeting for late November or early December.
  • OSGeo/grass-mcp was mentioned: https://github.com/OSGeo/grass-mcp.
  • [Action] @all: Corey, requested help with reviewing open website PRs. Corey will update the website to reflect the new PSC.