PSC Meeting 2024-05-10: Difference between revisions

Revision as of 13:16, 13 May 2024

The topics proposed are:

Review past minutes and action points
Motion: Approve Support Letter for LoC of FOSS4G 2025 Hiroshima (VP)
- Should the letter say "Approved by PSC motion on May 10, 2024."?
Google Summer of Code 2024: We got 4 students! Thanks to mentors!
OSGeo credit card for OSGeo Weblate (VP and MN)
Budget, ledger (VP)
- Tracking community meetings
  - The project contributes from OC.
  - People contribute to project's OC (to the sprint through the project).
- Tracking OSGeo budget
- Tracking Open Collective contributions
- Tracking Open Collective extras (payment processor fees, financial contributions to OC)
Community meeting in Prague
- GRASS_Community_Meeting_Prague_2024#Agenda agenda
- GRASS_Community_Meeting_Prague_2024#Participation participants
- funding
- social activities?
RFCs:
- release policy
- release procedure
PR procedures and status of the too many open PRs
Release 8.4
Participation in upcoming conferences/workshops
Update on POSE?
Transition to discourse.osgeo.org
...

from previous meeting:
- Markus' private credit card removed from weblate and replaced with that of OSGeo
- document GitHub teams and how to move people between teams - not done yet
Approved Support Letter for LoC of FOSS4G 2025 Hiroshima
GSoC 2024 discussed, there is a prepared news item to be released later this month
Budget:
- track separately money from OSGeo, in the past this hasn’t been tracked
- tracked in google drive use OSGeo nextcloud folder as our archive
Plan code sprint 2025 - May seems to be good, more planning during community meeting
Upcoming PSC elections
- who votes:
  - who has write access to GRASS repositories
  - who contributed to Transifex/Weblate
  - PR (merged?) contributors
  - we can't include financial contributors, we don't have their emails
  - folks mentioned in contributing files
RFCs - all please provide comments about the content
8.4 release
- go through 13 left PRs
- goal release before community sprint in June (Prague), create branch next week
discussion about supporting 7.8
- officially we don't support it anymore, too old, but we accept bug fixes and help with release
- potentially implement notification about old/newer version when you open GUI
move discourse.osgeo.org - wait for QGIS to finish transition, Vero will ask Regis about their timeline
forgot to mention:
- Documentation work group met this week (Vero, Anna and 3 other community memebers) to discuss tutorials

@@ Line 51: / Line 51: @@
 * Budget:
 ** track separately money from OSGeo, in the past this hasn’t been tracked
+** tracked in google drive use OSGeo nextcloud folder as our archive
 * Plan code sprint 2025 - May seems to be good, more planning during community meeting
 * Upcoming [https://trac.osgeo.org/grass/wiki/PSC#Elections PSC elections]
@@ Line 59: / Line 60: @@
 *** we can't include financial contributors, we don't have their emails
 *** folks mentioned in contributing files
-<!-- OSGeo nextcloud folder - use as our archive, copy files over -->
 * RFCs - all please provide comments about the content
 * 8.4 release
-** go through [https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.4.0 15 left PRs]
+** go through [https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.4.0 13 left PRs]
 ** goal release before community sprint in June (Prague), create branch next week
-<!-- implement notification about old GRASS -->
+* discussion about supporting 7.8
+** officially we don't support it anymore, too old, but we accept bug fixes and help with release
+** potentially implement notification about old/newer version when you open GUI
 * move discourse.osgeo.org - wait for QGIS to finish transition, Vero will ask Regis about their timeline
-<!-- work group meeting -->
+* forgot to mention:
+** Documentation work group met this week (Vero, Anna and 3 other community memebers) to discuss tutorials
 == Next meeting ==