PSC Meeting 2024-08-09: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(added Topics for next meeting)
 
(5 intermediate revisions by 2 users not shown)
Line 51: Line 51:
** 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.  
** 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.
** 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.
** VA will take care of these 2 items {{done}}


* GSoC projects status:
* GSoC projects status:
Line 62: Line 62:


* Release schedule:
* Release schedule:
** MN and all: review open PRs and issues for 8.4.1 and move to 8.5 if needed.
** 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:
* 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).
** 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.
** 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:
* RFCs:
** See above under action points from previous meeting.
** See above under action points from previous meeting.
** RFC about C/C++: VA pings Nicklas in the GH issue.
** RFC about C/C++: VA pings Nicklas in the GH issue. {{done}} via email.


* Migration to discourse:
* Migration to discourse:
** VA shared Regis feedback.
** 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.
** 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.
** MN will create the SAC ticket requesting the migration.
** AP will send a pre-announcement to grass-dev list communicating our plan to migrate.  
** AP will send a pre-announcement to 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:
* GUI screenshots in the website:
** Some cleanup happened already.
** Some cleanup happened already.
** MB will share screenshots of his own (done).
** MB will share screenshots of his own {{done}}.
** TODO: create PR to add more screenshots.


* Community meeting report
* Community meeting report:
** Done and published in the website already. Social media posts next week (VA).
** {{done}} published in the website already. Social media posts next week (VA).
** MN will send it to FOSSGIS.
** 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}} [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).
** {{done}} VA will send it to OSGeo board and add the link into the sprint budget request wiki.  


* POSE project update to PSC:
* POSE project update to PSC:
** VP will send a poll to find a 2-hour time slot in the upcoming two weeks ideally.  
** {{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"