PSC Meeting 2025-05-09: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
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.

Revision as of 19:40, 11 May 2025

Participants

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

Agenda

The topics proposed are:

Minutes

  • 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 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.
    • tutorials contributing guide: a 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)
    • 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.
    • There will be a PSC meeting during the summit: Friday 23, 5pm CET, 11am ET. Calendar invite sent.
  • New docs:
    • 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.
    • Only some Python examples do not work, but that should be solvable.
    • 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)
  • 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
        • 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
      • Ideas on what to do with all the content we have on the media wiki:
        • obsolete everything and then select what to keep,
        • go topic by topic
        • obsolete everything that was not edited in the last 3 years
  • 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.
    • OSGeo-SAC related ticket to install Matomo. Anna will revive it and Vashek will ask Howard.
    • Corey offered to sponsor it as OpenPlains
    • The paid option is around USD 500 yearly
  • GSoC:
    • We got only one student this year, he'll work on the JSON project.