GeoTools / GeoServer PMC meeting - 2026-02-24
Attending
- David Blasby
- Jody Garnett
- Gabriel Roldan
- Kevin Smith
- Peter Smythe
- Cécile Vuilleumier
- Pierre Mauduit
Actions from prior meetings:
- done: Peter can make a CITE landing page (to replace this) with the new sticker, and thanking sponsors/in-kind
- done: Andrea small spring 7
proposalmail for the record (mail here) - done: Peter static image of gs3 gauge update website and blog posts
- Action: jody Make an email or proposal about this so we have a wider discussion about choice of mkdocs for 2.28.x (https://github.com/geoserver/geoserver/wiki/GSIP-221 updated, sending to discourse).
Agenda
- GS3 Update
- UI/UX Updates
- Arm64 docker images
- Mkdocs
- ChitChat
Actions
GS3 Update
Dependency updates ongoing. Removed some dead code in GWC for previews never got used.
Cloud storage dependency hell across imageio-ext, gwc and 3 providers, AWS, Azure, Google. Each one of them wants a different version of Netty, which in turn results in more dependencies.
For a long time, we split the 3 providers in vanilla geoserver and Gabriel tried a “dependency converge” approach in GeoServer cloud.
Now new PRs to use a centralized BOM to manage these dependencies, and an approach that replaces Netty with other HTTP clients (that’s the role of Netty in the cloud deploys).
- https://github.com/tileverse-io/cloud-dependencies-bom
- https://github.com/geosolutions-it/imageio-ext/pull/355
- https://github.com/GeoWebCache/geowebcache/pull/1480
- Working on assembly descriptor update since the dependencies are changing
- Gabriel managed to perform manual tests from Start.java, working on assemblies and then testing the result zips interactively
- After this the modules should be ready for pending
- More testing?
- Big COG performance issue (with system variable workaround)
- Requester pays flag missing (breaks STAC catalogs usage). (at least for AWS, unsure if other providers support something similar)
- GeoServer cloud - updating to spring boot 4, removal of memory blob store and so on
UI/UX Updates
- Work is underway, see gs3-theme branch for progress. Still too early to preview!
- Working on menus, responsive sizing
- Discussion about table reducing to cards when not enough width
- A fun css approach needs to generate magic columns
- A lot of casual tables for layout are being convert to flexbox
- https://github.com/geoserver/geoserver/pull/9113 (in progress) - validate HTML files add <div class=<fname>. Possible issues with multiple <wicket:panel> <wicket:fragment> <wicket:extension>
- Quite a few wicket pages have a single panels
- However some are fragments and extensions and a bunch different components (ie WPS request builder)
- Fragments are designed not have a class around, they are component that you normally stick in a component, like a table row … or input element
- Extensions, every time you takes base page you extend it
- Also editor page tabs, and service page contributions, …
- It is hard to identify a wicket component, no easy fix or convention, …
arm64 docker images
- https://github.com/geoserver/docker/pull/263
- images pushed -> https://docker.osgeo.org/#browse/browse:docker:v2/geoserver/tags/3.0.x (and nightly, etc)
- New job geoserver-release-docker-github - Jenkins (available for testing) can replace geoserver-release-docker - Jenkins
- Can we advertise this with GS3?
Q: Is it the same image names? Or different image names…
- Same tag, different architecture (platform) are now available
- Note the -gdal variant for each tag
Mkdocs
- Updated proposal: https://github.com/geoserver/geoserver/wiki/GSIP-221
- Latest PR: https://github.com/geoserver/geoserver/pull/8876
https://geoserver.org/geoserver/en/user/extensions/authkey/#installation
Shows {{ release }} - we need to turn on macro processing for that page?
Here is the example: https://geoserver.org/geoserver