PSC Meeting 2024-08-09: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
m (→‎Agenda: add open rfcs links)
(added Topics for next meeting)
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__TOC__
== Participants ==
== Participants ==


TBD
* Anna Petrasova
* Vaclav Petras
* Veronica Andreo
<!-- * Helmut Kudrnovsky -->
* Markus Neteler
* Helena Mitasova
* Huidae Cho
* Michael Barton
<!-- * Martin Landa -->


== Agenda ==
== Agenda ==


The proposed topics to be discussed are:
The proposed topics to be discussed are:
* Elections: Vero will show list of voters
* Action points from previous meeting: [[PSC_Meeting_2024-05-10]]
* GSoC students
* PSC Elections 2024:
** Vero will show the compiled list of voters
* [[GRASS_GSoC_Ideas_2024#Accepted_ideas|GSoC]] projects status
* Upcoming events participation
* Upcoming events participation
** FOSS4G NA
** [https://www.foss4gna.org/ FOSS4G NA 2024]
** AGU
** [https://www.agu.org/annual-meeting AGU 2024]
** FOSS4G International
** [https://2024.foss4g.org/en/ FOSS4G 2024 Brazil]
* 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 debugs)
** policy to be developed
* Open RFCs:
* Open RFCs:
** Release procedure: https://github.com/OSGeo/grass/pull/2815
** Release procedure: https://github.com/OSGeo/grass/pull/2815
** Release policy: https://github.com/OSGeo/grass/pull/3673
** Release policy: https://github.com/OSGeo/grass/pull/3673
* New RFC about C/C++?
* New RFC about C/C++?
* Feedback from QGIS migration to discourse
* Feedback from QGIS migration to [https://discourse.osgeo.org/c/qgis/11 discourse]
* ...
* Topics postponed on our last meeting:
** PR procedures
** Status of the too many [https://github.com/OSGeo/grass/pulls open PRs]
** [[NSF POSE Project 2023-2025 Timeline|POSE project update]]
* Outreach:
** Update GUI gallery screenshots at https://grass.osgeo.org/learn/gallery/#user-interface


== Minutes ==
== Minutes ==


* 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 {{done}}
* 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:
** all: review open PRs and issues for 8.4.1 and move to 8.5 if needed:
*** G8.4.1: https://github.com/OSGeo/grass/milestone/23
*** G8.5.0: https://github.com/OSGeo/grass/milestone/22
* Documentation:
** GRASS GIS 8.3 manual needs a box, pointing to G84 as current stable
*** {{done}} by MN in https://github.com/OSGeo/grass-addons/pull/1168, see
**** https://grass.osgeo.org/grass83/manuals/
**** https://grass.osgeo.org/grass83/manuals/addons/
** 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 Apache 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. {{done}} via email.
* Migration to discourse:
** VA shared Regis feedback.
** We agreed to do the migration of grass-dev list first and use it as a playground and test case to then move forward with the other grass mailing lists.
** AP will send a pre-announcement to grass-dev list communicating our plan to migrate.
*** {{done}} ​https://lists.osgeo.org/pipermail/grass-dev/2024-August/096338.html
** MN will create the SAC ticket requesting the migration of grass-dev.
*** {{done}} https://trac.osgeo.org/osgeo/ticket/3255
* GUI screenshots in the website:
** Some cleanup happened already.
** MB will share screenshots of his own {{done}}.
** TODO: create PR to add more screenshots.
* Community meeting report:
** {{done}} 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]
** {{done}} VA will send it to OSGeo board and add the link into the sprint budget request wiki.


* POSE project update to PSC:
** {{done}} AP will send a poll to find a 2-hour time slot in the upcoming two weeks ideally.


== Topics for next meeting ==


* Social media: consider to stop feeding our account on X


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

Latest revision as of 11:53, 4 September 2024

Participants

  • Anna Petrasova
  • Vaclav Petras
  • Veronica Andreo
  • Markus Neteler
  • Helena Mitasova
  • Huidae Cho
  • Michael Barton

Agenda

The proposed topics to be discussed are:

Minutes

  • 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.
  • Documentation:
    • GRASS GIS 8.3 manual needs a box, pointing to G84 as current stable
    • 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 Apache 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. √ via email.
  • GUI screenshots in the website:
    • Some cleanup happened already.
    • MB will share screenshots of his own √ .
    • TODO: create PR to add more screenshots.
  • Community meeting report:
    • √ published in the website already. Social media posts next week (VA).
    • MN will send it to FOSSGIS.
    • √ VA will send it to OSGeo board and add the link into the sprint budget request wiki.
  • POSE project update to PSC:
    • √ AP will send a poll to find a 2-hour time slot in the upcoming two weeks ideally.

Topics for next meeting

  • Social media: consider to stop feeding our account on X
Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=PSC_Meeting_2024-08-09&oldid=27942"