[Geoserver-devel] mkdocs updates and before/after

2024-02-27 Thread Jody Garnett 
Good evening GeoServer community,

To start out with I would like to thank everyone who has signed up and
tested a few pages:

   - Alexandre Gacon
   - Peter Smythe
   - Andrea Aime
   - GeoSpatial Techno
   - Marcus Lingenfelder


With their help we about 1/4 of the way through reviewing the pages:

   - We identified a consistent problem with complicated tabes not
   rendering (tables with. Nested notes and figures), these are now processed
   into definition lists.

   
https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#primary-configuration-file
   - Definition lists are styled to look like tables (see what I did
   there!) which works out great for documenting step by step instructions
   where field entry is needed.
   https://jodygarnett.github.io/geoserver/
   - Examples that change based on version and release are correct (big
   improvement, you can now cut and paste command line examples):
   https://jodygarnett.github.io/geoserver/installation/docker/
   - The download, download extension and download community modules
   external links look good (we can give it the nice appearance like the
   docker page later):
   https://jodygarnett.github.io/geoserver/extensions/geopkg-output/install/


While I think we are through the big problems I still need to ask for your
help:


   1. I would like to ask 10 volunteers
   2. If everyone can review 30 pages each we will be done
   3. Lots of pages can be reviewed in under 1-2 mins:
   - locate a row that "needs review"
   - click on the "origional" link and open in an other tab
   - click on the "migrated" link and open in an other tab
   4. Swap between the pages to check
   5. If they are the same (no content is lost), update the review column
   to be done
   6. If they are different change "needs review" to describing what is
   different:
   - many pages will have "block quotes" when none were intended (this is
   something we need to fix by hand before conversion)


*Popular request BEFORE / AFTER *

Reviewers asked to "see the markdown" that was generated.

   - Each page has a view source button at the top showing the generated
   markdown
   - Links to both the original rst and generated md are now available in
   the review spreadsheet


*Sign up sheet*

I am going to be focused on the 2.25-RC release candidate this week; but I
would like to check back next week with a list of things to fix.

The sign up spreadsheet is here: mkdocs review

(open
spreadsheet and ask for edit access).

Please reply if you have any questions - I appreciate your help.

Thanks to my employer, and GeoCat Live product, for the opportunity to work
on this activity.
--
Jody Garnett
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GeoServer 2.25-RC0 PR roundup

2024-02-27 Thread Jody Garnett 
I have a small PR for this weeks release-candidate:


   - https://github.com/geoserver/geoserver/pull/7444
   - https://osgeo-org.atlassian.net/browse/GEOS-10438


This changes the default behaviour entity resolution allow list, something
I have  been intended to do for several release cycles now.
--
Jody Garnett
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] PSC meeting notes, February 27th 2024

2024-02-27 Thread Andrea Aime 
GeoTools / GeoServer PMC meeting - 2024-02-27Attending

   -

   Peter Smythe
   -

   Jody Garnett
   -

   Torben Barsballe
   -

   Andrea Aime
   -

   Jukka Rahkonen
   -

   Kevin Smith


Actions from prior meetings:

   -

   [Done] Peter: create a sed script to fix email addresses in sourceforge
   lists export
   -

   [Blocked] Jody: setup a github workflow to use dependency submission API
   


Agenda

   -

   Discourse
   -

   2.25-RC Release coordination
   -

   Markdown migration update
   -

   Coordinated Vulnerability Disclosure stuffs
   -

   WFS GetFeatureResponse API change
   -

   Making ENTITY_RESOLUTION_ALLOWLIST default

Actions

   -


Discourse

Peter was able to send an updated mbox to Vicky, we await a test instance.

Wider OSGeo response has been:

   -

   finally!
   -

   huh why I like lots and lots of email

2.25-RC Release coordination

Jody is set to release this week - thanks for everyone reviewing.

Anything waiting:

   -

   Jody owes Niels a review
   -

   Gabe large catalog load improvement is almost ready:
   https://github.com/geoserver/geoserver/pull/7421
   -

   Entity Resolution Allow below
   -

   GetFeatureResponse API
   -

   Stream of MapML pull-requests coming including vector tiles coming in


Q: Is the mkdocs change needed for the release candidate?
A: It would be nice to complete this and push out along side 2.25.0 release.


Q: Can alex help?

A: Release candidate is a poor introduction, but Jody will ask for help
writing the release announcement.
Markdown migration update

Status and collaboration opportunities here:

https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit#gid=0


List-table issue, Jody working on it. Looking good according to Andrea:
https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#index-and-configuration-file-creation


If you want to see markdown check branch (not a space for collaboration,
just a way to check the current progress in markdown syntax):

Checkout:

   -

   https://github.com/jodygarnett/geoserver/tree/mkdocs-preflight-test


   -

   Follow instructions here
   https://jodygarnett.github.io/translate/translate/migrate/
   -

   todo: Jody can un gitignore the docs folder so people can see

Coordinated Vulnerability Disclosure stuffs

Peter needs access to the vulnerabilities page (done)


Set to announce alongside 2.25.0 release.

Making ENTITY_RESOLUTION_ALLOWLIST default

See https://github.com/geoserver/geoserver/pull/7444

Jody would like this for release, contains update instruction note.
WFS GetFeatureResponse API change

https://github.com/geoserver/geoserver/pull/7428

Andrea has some feedback:

   -

   if you do not return the supplier the api change will be minimal
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel