PSC Meeting 2024-08-09: Difference between revisions

Revision as of 10:04, 12 August 2024

The proposed topics to be discussed are:

Action points from previous meeting: PSC_Meeting_2024-05-10
PSC Elections 2024:
- Vero will show the compiled list of voters
GSoC projects status
Upcoming events participation
Release schedule
- https://github.com/OSGeo/grass/milestones
How to deal with keeping or not old manual pages?
- https://grass.osgeo.org/grass82/manuals/ --> replace with Apache redirect to 8.4?
- https://grass.osgeo.org/grass83/manuals/ --> no red redirect box yet (MN prepares PR)
- policy to be developed
Open RFCs:
- Release procedure: https://github.com/OSGeo/grass/pull/2815
- Release policy: https://github.com/OSGeo/grass/pull/3673
New RFC about C/C++?
Feedback from QGIS migration to discourse
Topics postponed on our last meeting:
- PR procedures
- Status of the too many open PRs
- POSE project update
Outreach:
- Update GUI gallery screenshots at https://grass.osgeo.org/learn/gallery/#user-interface

Action points from previous meetings:
- Document GitHub teams and how to move people between teams. VP will take care of this.
- Comments on Release procedure and Release policy RFCs: VP, AP and VA will un-draft the PRs, MN will review.

Voters list:
- Since the criteria on which we agreed does not yielded the expected results, we will extend the period further back to 2016, i.e., contributors from 2 PSC mandates, and also to contributors that have participated in community meetings or PSC.
- Write the announcement about the elections with a call to contribute to get on the voters list.
- VA will take care of these 2 items.

GSoC projects status:
- All students doing well, final evaluation is by the end of August.

Attendance to upcoming events:
- FOSS4G NA: VP, HC and Corey White.
- AGU: VP, AP, HC, MB, Caitlin Haedrich.
- FOSS4G international: VA.

Release schedule:
- MN and all: review open PRs and issues for 8.4.1 and move to 8.5 if needed.

Documentation:
- Discussion was if to remove old versions manual pages (all but stable and stable -1) or not, or if to avoid having a version in the url at all (have grass-stable as real links and not redirects as now).
- Since there's an upcoming change of documentation from html to md, this will be discussed again once the md docs and infra are in place because technology might then allow us to keep all versions as a side bar and let users pick like in Python docs.

RFCs:
- See above under action points from previous meeting.
- RFC about C/C++: VA pings Nicklas in the GH issue.

Migration to discourse:
- VA shared Regis feedback.
- We agreed to do the migration of dev list first and use it as a playground and test case to then move forward with the other grass mailing lists.
- MN will create the SAC ticket requesting the migration.
- AP will send a pre-announcement to dev list communicating our plan to migrate.

GUI screenshots in the website:
- Some cleanup happened already.
- MB will share screenshots of his own (done).

Community meeting report
- Done and published in the website already. Social media posts next week (VA).
- MN will send it to FOSSGIS.
  - √ here
- VA will send it to OSGeo board and add the link into the sprint budget request wiki (done).

POSE project update to PSC:
- VP will send a poll to find a 2-hour time slot in the upcoming two weeks ideally.

@@ Line 85: / Line 85: @@
 ** Done and published in the website already. Social media posts next week (VA).
 ** MN will send it to FOSSGIS.
+*** {{done}} [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2024#Report_nach_dem_Event here]
 ** VA will send it to OSGeo board and add the link into the sprint budget request wiki (done).