PSC Meeting 2025-05-09: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(grass-xxx mailing list wording fine-tuning)
(more details added)
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:

Revision as of 21:14, 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 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 grass-web references from the website
      • We should add a “Contact us” something to the website → improve website footer
      • 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).
      • 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 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 (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/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 concerning the PSC description were included.
    • 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.
  • Conda
    • Huidae built a Linux conda package, but without FHS (Filesystem Hierarchy Standard)
    • 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 want 3 types: format=json (WIP), --json (implemented), --json-interface-description (not yet implemented)
  • New branding:
    • Wiki:
      • logo and favicon were updated by MN
      • svg file in the corner? To be checked by MN -> looks terrible
      • 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
      • 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:
        • obsolete everything and then select what to keep,
        • go topic by topic
        • obsolete everything that was not edited in the last 3 years, maybe with a bot extension?
        • To be discussed further
  • 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.