PSC Meeting 2024-08-09 - Revision history

Neteler: added Topics for next meeting

2024-09-04T11:53:58Z

added Topics for next meeting

← Older revision		Revision as of 11:53, 4 September 2024
Line 99:		Line 99:
	* POSE project update to PSC:		* POSE project update to PSC:
	** {{done}} AP 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]]

Neteler: discourse SAC ticket opened

2024-08-22T13:56:03Z

discourse SAC ticket opened

← Older revision		Revision as of 13:56, 22 August 2024
Line 81:		Line 81:
	** VA shared Regis feedback.		** 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.		** 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.		** MN will create the SAC ticket requesting the migration of grass-dev.
	** ~~AP will send a pre-announcement to grass-dev list communicating our plan to migrate~~.		*** {{done}} https://trac.osgeo.org/osgeo/ticket/3255

	* GUI screenshots in the website:		* GUI screenshots in the website:

Veroandreo: /* Minutes */

2024-08-20T20:00:01Z

Minutes

← Older revision		Revision as of 20:00, 20 August 2024
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:

Veroandreo: add done checks

2024-08-12T16:07:12Z

add done checks

← Older revision		Revision as of 16:07, 12 August 2024
Line 76:		Line 76:
	* 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:
Line 89:		Line 89:
	** TODO: create PR to add more screenshots.		** TODO: create PR to add more screenshots.

	* Community meeting report		* Community meeting report:
	** {{done}} 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.

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

Neteler: DONE: GRASS GIS 8.3 manual needs a box, pointing to G84 as current stable

2024-08-12T13:47:35Z

DONE: GRASS GIS 8.3 manual needs a box, pointing to G84 as current stable

← Older revision		Revision as of 13:47, 12 August 2024
Line 67:		Line 67:

	* Documentation:		* 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).		** 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.

Neteler: /* Minutes */

2024-08-12T11:34:50Z

Minutes

← Older revision		Revision as of 11:34, 12 August 2024
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).		** 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.

Line 74:		Line 76:
	* 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.		** MN will create the SAC ticket requesting the migration of grass-dev.
	** AP will send a pre-announcement to dev list communicating our plan to migrate.		** AP will send a pre-announcement to grass-dev list communicating our plan to migrate.

	* 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).		** VA will send it to OSGeo board and add the link into the sprint budget request wiki {{done}}.

	* POSE project update to PSC:		* POSE project update to PSC:

Neteler: /* Agenda */

2024-08-12T11:30:41Z

Agenda

← Older revision		Revision as of 11:30, 12 August 2024
Line 28:		Line 28:
	* How to deal with keeping or not old manual pages?		* 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/grass82/manuals/ --> replace with Apache redirect to 8.4?
	** https://grass.osgeo.org/grass83/manuals/ --> no red redirect box yet (MN ~~prepares PR~~)		** https://grass.osgeo.org/grass83/manuals/ --> no red redirect box yet (MN debugs)
	** policy to be developed		** policy to be developed
	* Open RFCs:		* Open RFCs:

Neteler: submitted https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2024#Report_nach_dem_Event

2024-08-12T10:04:18Z

submitted https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2024#Report_nach_dem_Event

← Older revision		Revision as of 10:04, 12 August 2024
Line 85:		Line 85:
	** Done and published in the website already. Social media posts next week (VA).		** Done and 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]
	** VA will send it to OSGeo board and add the link into the sprint budget request wiki (done).		** VA will send it to OSGeo board and add the link into the sprint budget request wiki (done).

Veroandreo at 13:51, 11 August 2024

2024-08-11T13:51:21Z

← Older revision		Revision as of 13:51, 11 August 2024
Line 85:		Line 85:
	** Done and published in the website already. Social media posts next week (VA).		** Done and published in the website already. Social media posts next week (VA).
	** MN will send it to FOSSGIS.		** MN will send it to FOSSGIS.
	** VA will send it to OSGeo board and add the link into the sprint budget request wiki.		** VA will send it to OSGeo board and add the link into the sprint budget request wiki (done).

	* POSE project update to PSC:		* POSE project update to PSC:

Veroandreo at 18:47, 9 August 2024

2024-08-09T18:47:14Z

← Older revision		Revision as of 18:47, 9 August 2024
Line 1:		Line 1:
			__TOC__

	== Participants ==		== Participants ==

Line 67:		Line 69:

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

	* Migration to discourse:		* Migration to discourse:
	** ~~Vero~~ 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 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.		** MN will create the SAC ticket requesting the migration.
Line 82:		Line 84:
	* Community meeting report		* Community meeting report
	** Done and published in the website already. Social media posts next week (VA).		** Done and published in the website already. Social media posts next week (VA).
	** MN will send it to FOSSGIS		** MN will send it to FOSSGIS.
	** VA will send it to OSGeo board and add the link into the sprint budget request wiki.		** VA will send it to OSGeo board and add the link into the sprint budget request wiki.