PSC Meeting 2025-05-09 - Revision history

Neteler: added :Category:PSC

2025-06-17T16:57:35Z

← Older revision		Revision as of 16:57, 17 June 2025
Line 105:		Line 105:
	* GSoC:		* GSoC:
	** We got only one student this year, he'll work on the JSON project.		** We got only one student this year, he'll work on the JSON project.

			[[Category:PSC]]

Neteler: Wiki logo (svg) done

2025-05-12T14:35:16Z

Wiki logo (svg) done

← Older revision		Revision as of 14:35, 12 May 2025
Line 83:		Line 83:
	** Wiki:		** Wiki:
	*** logo and favicon were updated by MN		*** logo and favicon were updated by MN
	*** svg file in the corner? To be checked by MN -> ~~looks terrible~~		*** svg file in the corner? To be checked by MN -> done
	*** review the Wiki landing page and redo it		*** review the Wiki landing page and redo it
	**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website		**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website

Neteler: more details added

2025-05-11T21:14:03Z

more details added

← Older revision		Revision as of 21:14, 11 May 2025
Line 49:		Line 49:
	** tutorials contributing guide: a [https://github.com/OSGeo/grass-tutorials/pull/16 PR] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).		** tutorials contributing guide: a [https://github.com/OSGeo/grass-tutorials/pull/16 PR] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).

	* Hosting of GRASS server at OSL - Oregon University using OSGeo infrastructure hosted there.		* Hosting of GRASS server at [https://wiki.osgeo.org/wiki/OSL OSL - Oregon University] using OSGeo infrastructure hosted there.
	** OSL funding is at risk. We have no action item as OSGeo will handle this, but we will keep an eye on it in case we need to take action.		** OSL funding is at risk. We have no action item as OSGeo will handle this, but we will keep an eye on it in case we need to take action.
	** News: Seems the next year is again funded.		** News: Seems the next year is again funded ([https://osuosl.org/blog/osl-future-update/ OSL blog]).

	* NumFOCUS status update: The main reason to go with them is that they provide invoices when someone donates to the project, while OSGeo is not willing to do so, and we are missing some funding/sponsoring opportunities because of that. Also, NumFOCUS brings new funding options.		* NumFOCUS status update: The main reason to go with them is that they provide invoices when someone donates to the project, while OSGeo is not willing/legally able to do so, and we are missing some funding/sponsoring opportunities because of that. Also, NumFOCUS brings new funding options.
	** Contract draft: edits to PSC description were included.		** Contract draft: edits concerning the PSC description were included.
	** OSGeo cannot remain our fiscal host; it will be NumFOCUS; but we can still use the OSGeo money via reimbursements as usual.		** OSGeo cannot remain our fiscal host; it will become NumFOCUS; but we can still use the OSGeo money via reimbursements as usual.
	** Once the agreement is signed, we’ll meet with their Finance department and go through NumFOCUS onboarding.		** Once the agreement is signed, we’ll meet with their Finance department and go through NumFOCUS onboarding.

	* Conda		* Conda
	** Huidae built a Linux conda package, but without FHS		** Huidae built a Linux conda package, but without FHS (Filesystem Hierarchy Standard)
	** The Windows conda package is not stable, probably a CMake issue		** The Windows conda package is not stable, probably a CMake issue
	** There are 2 open issues: conda for Linux and Windows, CMake for Windows		** There are 2 open issues: conda for Linux and Windows, CMake for Windows
Line 75:		Line 75:
	** Corey is working on syncing branding among the website, docs, and tutorials		** Corey is working on syncing branding among the website, docs, and tutorials

	* JSON: theoretically we ~~have~~ 3: format=json (WIP), ~~–json~~ (implemented), ~~–json~~-interface-description (not implemented)		* JSON: theoretically we want 3 types: <code>format=json</code> (WIP), <code>--json</code> (implemented), <code>--json-interface-description</code> (not yet implemented)

	* Releases:		* Releases:
	** 8.4.2 in some weeks		** 8.4.2 in [https://github.com/OSGeo/grass/milestone/27 some weeks]

	* New branding:		* New branding:
	** Wiki:		** Wiki:
	*** logo and favicon were updated		*** logo and favicon were updated by MN
	*** svg file in the corner? To be checked by MN		*** svg file in the corner? To be checked by MN -> looks terrible
	*** review the Wiki landing page and redo it		*** review the Wiki landing page and redo it
	**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website		**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website
	*** Ohloh/OpenHub Project Widget is broken: let’s remove it		*** Ohloh/OpenHub Project Widget is broken: let’s remove it -> done
	*** Ideas on what to do with all the content we have on the media wiki:		*** Ideas on what to do with all the content we have on the media wiki:
	**** obsolete everything and then select what to keep,		**** obsolete everything and then select what to keep,
	**** go topic by topic		**** go topic by topic
	**** obsolete everything that was not edited in the last 3 years		**** obsolete everything that was not edited in the last 3 years, maybe with a bot extension?
	**** To be discussed further		**** To be discussed further

	* Website SEO issues:		* Website SEO issues:
	** Our search engine ranking is partially penalized at time. See: https://github.com/OSGeo/grass-website/issues/513		** Our search engine ranking is partially penalized at time. See: https://github.com/OSGeo/grass-website/issues/513
			** TODO: a volunteer to fix the issues noted in the ticket

	* Website analytics:		* Website analytics:

Neteler: grass-xxx mailing list wording fine-tuning

2025-05-11T20:43:19Z

grass-xxx mailing list wording fine-tuning

← Older revision		Revision as of 20:43, 11 May 2025
Line 41:		Line 41:
	* From previous meeting:		* From previous meeting:
	** mailman migration to discourse:		** mailman migration to discourse:
	*** The grass-user mailing list has been migrated to Discourse. We ~~can now~~ close grass-web that receives spam mostly.		*** The '''grass-user mailing list''' has been migrated to Discourse.
	~~***~~ Markus will ~~disable~~ it ~~and put~~ into read-only mode		*** We will close the '''grass-web mailing list''' that receives spam mostly. Markus will put it into read-only mode, after an announcement to the list.
	*** Anna will remove it from the website		*** Anna will remove grass-web references from the website
	*** We should add a “Contact us” something to the website → improve website footer		*** We should add a “Contact us” something to the website → improve website footer
	*** For now, we keep the grass-psc list on mailman, but we are considering merging it to GRASS developer in Discourse, as subscribers are pretty much the same (that is, close down the mailing list). We also keep grass-announce on mailman.		*** We decided to change the '''grass-stats mailing list''' and '''grass-translation mailing list''' mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission, after an announcement has been sent to the list explaining the alternative(s).
	*** We decided to change the grass-stats and grass-translation mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission.		*** For now, we keep the '''grass-psc mailing list''' list on mailman, but we are considering merging it to GRASS developer in Discourse, as subscribers are pretty much the same (that is, close down the mailing list). We also keep grass-announce on mailman.
	** tutorials contributing guide: a [https://github.com/OSGeo/grass-tutorials/pull/16 PR] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).		** tutorials contributing guide: a [https://github.com/OSGeo/grass-tutorials/pull/16 PR] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).

Veroandreo: /* Minutes */

2025-05-11T19:45:19Z

Minutes

← Older revision		Revision as of 19:45, 11 May 2025
Line 82:		Line 82:
	* New branding:		* New branding:
	** Wiki:		** Wiki:
	*** logo, favicon updated		*** logo and favicon were updated
	*** svg file in the corner? To be checked by MN		*** svg file in the corner? To be checked by MN
	*** review Wiki landing page and redo it		*** review the Wiki landing page and redo it
	**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website		**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website
	*** Ohloh/OpenHub Project Widget is broken: let’s remove it		*** Ohloh/OpenHub Project Widget is broken: let’s remove it
Line 91:		Line 91:
	**** go topic by topic		**** go topic by topic
	**** obsolete everything that was not edited in the last 3 years		**** obsolete everything that was not edited in the last 3 years
			**** To be discussed further

	* Website SEO issues:		* Website SEO issues:
Line 96:		Line 97:

	* Website analytics:		* Website analytics:
	** There's the GFOSS.it Matomo instance, but we do not have much control over it, only MN has a user account, via Luca D.		** There's the [https://2022.foss4g.org/matomo/ GFOSS.it Matomo] instance, but we do not have much control over it, only MN has a user account, via Luca D.
	** OSGeo-SAC related ticket to install Matomo. Anna will revive it and Vashek will ask Howard.		** OSGeo-SAC related [https://trac.osgeo.org/osgeo/ticket/2830 ticket] to install Matomo. Anna will revive it and Vashek will ask Howard.
	** Corey offered to sponsor it as OpenPlains		** Corey offered to sponsor it as OpenPlains
	** The paid option is around USD 500 yearly		** The paid option is around USD 500 yearly

Veroandreo: /* Minutes */

2025-05-11T19:40:53Z

Minutes

← Older revision		Revision as of 19:40, 11 May 2025
Line 45:		Line 45:
	*** Anna will remove it from the website		*** Anna will remove it from the website
	*** We should add a “Contact us” something to the website → improve website footer		*** We should add a “Contact us” something to the website → improve website footer
	*** For now we keep grass-psc list on mailman, but we are considering merging it to developer in ~~discourse~~ as subscribers are pretty much the same (that is, close down the mailing list). We also keep grass-announce on mailman.		*** For now, we keep the grass-psc list on mailman, but we are considering merging it to GRASS developer in Discourse, as subscribers are pretty much the same (that is, close down the mailing list). We also keep grass-announce on mailman.
	*** We decided to change the grass-stats and grass-translation mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission.		*** We decided to change the grass-stats and grass-translation mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission.
	** tutorials contributing guide: a [[https://github.com/OSGeo/grass-tutorials/pull/16 PR]] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).		** tutorials contributing guide: a [https://github.com/OSGeo/grass-tutorials/pull/16 PR] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).

	* Hosting of GRASS server at OSL - Oregon University using OSGeo infrastructure hosted there.		* Hosting of GRASS server at OSL - Oregon University using OSGeo infrastructure hosted there.
Line 54:		Line 54:

	* NumFOCUS status update: The main reason to go with them is that they provide invoices when someone donates to the project, while OSGeo is not willing to do so, and we are missing some funding/sponsoring opportunities because of that. Also, NumFOCUS brings new funding options.		* NumFOCUS status update: The main reason to go with them is that they provide invoices when someone donates to the project, while OSGeo is not willing to do so, and we are missing some funding/sponsoring opportunities because of that. Also, NumFOCUS brings new funding options.
	** ~~contract~~ draft: edits to PSC description were included.		** Contract draft: edits to PSC description were included.
	** OSGeo cannot remain our fiscal host; it will be NumFOCUS; but we can still use the OSGeo money via reimbursements as usual.		** OSGeo cannot remain our fiscal host; it will be NumFOCUS; but we can still use the OSGeo money via reimbursements as usual.
	** Once the agreement is signed, we’ll meet with their Finance department and go through NumFOCUS onboarding.		** Once the agreement is signed, we’ll meet with their Finance department and go through NumFOCUS onboarding.
Line 65:		Line 65:
	** Instructions to test: https://github.com/OSGeo/grass/issues/5067		** Instructions to test: https://github.com/OSGeo/grass/issues/5067

	* GRASS Developer Summit at Raleigh (agenda schedule)		* GRASS Developer Summit at Raleigh ([https://grasswiki.osgeo.org/wiki/Talk:GRASS_Developer_Summit_Raleigh_2025 agenda schedule])
	~~add topics: website footer~~		** Remote participation? We decided async work is better according to previous years experiences, but we could define a time slot for a call with folks contributing remotely.
	~~remote~~ participation: async, ~~meet devs, use one~~ slot for a call		** There will be a PSC meeting during the summit: Friday 23, 5pm CET, 11am ET. Calendar invite sent.
	~~psc~~ meeting during the summit: Friday 23, 5pm CET, 11am ET
	~~https://grasswiki~~.~~osgeo~~.~~org/wiki/Talk:GRASS_Developer_Summit_Raleigh_2025~~

	* New docs		* New docs:
	https://grass.osgeo.org/grass-devel/manuals/		** They are up and looking great: https://grass.osgeo.org/grass-devel/manuals/
	~~automatic~~ upload from CI to the web server is WIP, needs GHA		** Automatic upload from CI to the web server is WIP, needs GHA.
	~~only~~ some ~~python~~ examples do not work, but solvable		** Only some Python examples do not work, but that should be solvable.
	Corey working on syncing branding among the website, docs, and tutorials		** Corey is working on syncing branding among the website, docs, and tutorials
	JSON: theoretically we have 3: format=json (WIP), –json (implemented), –json-interface-description (not implemented)
			* JSON: theoretically we have 3: format=json (WIP), –json (implemented), –json-interface-description (not implemented)

	* Releases:		* Releases:
	8.4.2 in some weeks		** 8.4.2 in some weeks

	* New branding		* New branding:
	Wiki:		** Wiki:
	logo, favicon updated		*** logo, favicon updated
	svg file in the corner? To be checked by MN		*** svg file in the corner? To be checked by MN
	review Wiki landing page and redo it		*** review Wiki landing page and redo it
	Ohloh/OpenHub Project Widget is broken: let’s remove it		**** highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website
	~~Wiki View statistics~~		*** Ohloh/OpenHub Project Widget is broken: let’s remove it
	~~Views total: 52,672,541~~		*** Ideas on what to do with all the content we have on the media wiki:
	~~Views per edit: 1,856.56 <- pretty ok~~		**** obsolete everything and then select what to keep,
	Ideas:		**** go topic by topic
	obsolete everything and then select what to keep,		**** obsolete everything that was not edited in the last 3 years
	go topic by topic
	obsolete everything that was not edited in the last 3 years
	~~highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website~~

	* Website SEO issues:		* Website SEO issues:
Line 100:		Line 96:

	* Website analytics:		* Website analytics:
	** There's the GFOSS.~~it’s~~ Matomo instance, but we do not have much control over it, only MN has a user account, via Luca D.		** There's the GFOSS.it Matomo instance, but we do not have much control over it, only MN has a user account, via Luca D.
	** OSGeo-SAC related ticket to install Matomo. Anna will revive it and Vashek will ask Howard.		** OSGeo-SAC related ticket to install Matomo. Anna will revive it and Vashek will ask Howard.
	** Corey offered to sponsor it as OpenPlains		** Corey offered to sponsor it as OpenPlains
	** ~~Paid~~ option is around USD 500 yearly		** The paid option is around USD 500 yearly

	* GSoC:		* GSoC:
	** We got only one student this year, he'll work on the JSON project.		** We got only one student this year, he'll work on the JSON project.

Veroandreo: /* Minutes */

2025-05-11T19:28:29Z

Minutes

← Older revision		Revision as of 19:28, 11 May 2025
Line 48:		Line 48:
	*** We decided to change the grass-stats and grass-translation mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission.		*** We decided to change the grass-stats and grass-translation mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission.
	** tutorials contributing guide: a [[https://github.com/OSGeo/grass-tutorials/pull/16 PR]] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).		** tutorials contributing guide: a [[https://github.com/OSGeo/grass-tutorials/pull/16 PR]] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).

			* Hosting of GRASS server at OSL - Oregon University using OSGeo infrastructure hosted there.
			** OSL funding is at risk. We have no action item as OSGeo will handle this, but we will keep an eye on it in case we need to take action.
			** News: Seems the next year is again funded.

			* NumFOCUS status update: The main reason to go with them is that they provide invoices when someone donates to the project, while OSGeo is not willing to do so, and we are missing some funding/sponsoring opportunities because of that. Also, NumFOCUS brings new funding options.
			** contract draft: edits to PSC description were included.
			** OSGeo cannot remain our fiscal host; it will be NumFOCUS; but we can still use the OSGeo money via reimbursements as usual.
			** Once the agreement is signed, we’ll meet with their Finance department and go through NumFOCUS onboarding.

			* Conda
			** Huidae built a Linux conda package, but without FHS
			** The Windows conda package is not stable, probably a CMake issue
			** There are 2 open issues: conda for Linux and Windows, CMake for Windows
			** HC will resume work on it next week
			** Instructions to test: https://github.com/OSGeo/grass/issues/5067

			* GRASS Developer Summit at Raleigh (agenda schedule)
			add topics: website footer
			remote participation: async, meet devs, use one slot for a call
			psc meeting during the summit: Friday 23, 5pm CET, 11am ET
			https://grasswiki.osgeo.org/wiki/Talk:GRASS_Developer_Summit_Raleigh_2025

			* New docs
			https://grass.osgeo.org/grass-devel/manuals/
			automatic upload from CI to the web server is WIP, needs GHA
			only some python examples do not work, but solvable
			Corey working on syncing branding among the website, docs, and tutorials
			JSON: theoretically we have 3: format=json (WIP), –json (implemented), –json-interface-description (not implemented)

			* Releases:
			8.4.2 in some weeks

			* New branding
			Wiki:
			logo, favicon updated
			svg file in the corner? To be checked by MN
			review Wiki landing page and redo it
			Ohloh/OpenHub Project Widget is broken: let’s remove it
			Wiki View statistics
			Views total: 52,672,541
			Views per edit: 1,856.56 <- pretty ok
			Ideas:
			obsolete everything and then select what to keep,
			go topic by topic
			obsolete everything that was not edited in the last 3 years
			highlight PSC and Events categories because that’s the current usage, and remove other links that are already on the website

			* Website SEO issues:
			** Our search engine ranking is partially penalized at time. See: https://github.com/OSGeo/grass-website/issues/513

			* Website analytics:
			** There's the GFOSS.it’s Matomo instance, but we do not have much control over it, only MN has a user account, via Luca D.
			** OSGeo-SAC related ticket to install Matomo. Anna will revive it and Vashek will ask Howard.
			** Corey offered to sponsor it as OpenPlains
			** Paid option is around USD 500 yearly

			* GSoC:
			** We got only one student this year, he'll work on the JSON project.

Veroandreo: /* Minutes */ add discussion about previous meeting points

2025-05-11T19:12:04Z

Minutes: add discussion about previous meeting points

← Older revision		Revision as of 19:12, 11 May 2025
Line 39:		Line 39:
	== Minutes ==		== Minutes ==

	* ~~TBD~~		* From previous meeting:
			** mailman migration to discourse:
			*** The grass-user mailing list has been migrated to Discourse. We can now close grass-web that receives spam mostly.
			*** Markus will disable it and put into read-only mode
			*** Anna will remove it from the website
			*** We should add a “Contact us” something to the website → improve website footer
			*** For now we keep grass-psc list on mailman, but we are considering merging it to developer in discourse as subscribers are pretty much the same (that is, close down the mailing list). We also keep grass-announce on mailman.
			*** We decided to change the grass-stats and grass-translation mailing lists to read-only mode to reduce channel confusion. Markus will do this as he has permission.
			** tutorials contributing guide: a [[https://github.com/OSGeo/grass-tutorials/pull/16 PR]] is there, but it seems useless. Vero volunteers to work on it; we are still trying to figure out the workflow (i.e., what to commit and so on).

Veroandreo: /* Participants */ add participants

2025-05-11T18:56:45Z

Participants: add participants

← Older revision		Revision as of 18:56, 11 May 2025
Line 1:		Line 1:
	== Participants ==		== Participants ==

	* ~~TBD~~		* Anna Petrasova
			* Helmut Kudrnovsky
			* Huidae Cho
			* Linda Karlovska
			* Markus Neteler
			* Paulo van Breugel
			* Vaclav Petras
			* Veronica Andreo

	== Agenda ==		== Agenda ==

Wenzeslaus: /* Agenda */

2025-05-09T01:56:29Z

Agenda

← Older revision		Revision as of 01:56, 9 May 2025
Line 9:		Line 9:
	* Hosting of GRASS server at OSL, Oregon State University. See: https://osuosl.org/blog/osl-future/.		* Hosting of GRASS server at OSL, Oregon State University. See: https://osuosl.org/blog/osl-future/.
	* Financial Sponsoring via NumFocus. Status update.		* Financial Sponsoring via NumFocus. Status update.
			* Conda update
	* [[GRASS Developer Summit Raleigh 2025]], NC.		* [[GRASS Developer Summit Raleigh 2025]], NC.
	** Remote participation?		** Remote participation?