GeoServer PSC meeting notes, Feb 10th 2026

GeoServer GeoServer Developer
, , ,
1

GeoTools / GeoServer PMC meeting - 2026-02-10

Attending

  • Torben Barsballe

  • Cécile Vuilleumier

  • Jukka Rahkonen

  • Peter Smythe

  • Andrea Aime

  • Jody Garnett

  • Kevin Smith

Actions from prior meetings:

  • Jody: Write blog post for 2026 Sponsorship, update wiki page, etc..

  • action: Peter can make a CITE landing page with the new sticker, and thanking sponsors/in-kind

  • action: Andrea small spring 7 proposal for the record

Agenda

  1. GS3 Update

  2. UI/UX Proposal

  3. AI Policy Chat

  4. Chit Chat

Actions

  • peter: static image of gs3 gauge update website and blog posts

  • jody: make an email or proposal about this so we have a wider discussion about choice of mkdocs for 2.28.x

GS3 Update

aside:

  • The crowdfunding graphic is broken? Perhaps permission change on spreadsheet

    • action: take a static image as the spreadsheet is done, update website and blog posts

Spring 7 is merged! Milestone 2 is completed

  • this is great :slight_smile:

What is next:

  • Milestone 3: Delayed a bit until April 18th

  • Milestone 4 (this is new): for the integration topics like GeoNode

What are we doing with the delay:

Other updates:

  • Cecile: SQLite updates is working on it

    • Andrea confirms this is annoying, primary keys not supported in batch, sigh…

    • Breakout discussion on details, …

    • Problems creating two tables in a test and locking on itself

  • Alessio: Major work done on OIDC as a replacement for previous implementations

    • Q: Is this backported to 2.28.x?

    • It would be possible, but perhaps no longer due to change of spring security version due to spring 7 change

    • No the PRs are not backported

  • Gabe: Has GeoServer Cloud working already, ported to Spring Boot 4, nice work!

UI/UX Proposal

https://github.com/geoserver/geoserver/wiki/GSIP-238

Jody is working with Stephano on this PR, discussed in previous meetings, now a GSIP

Discussion:

  • how much javascript?

    • We are fine for now, Stephano is an expert, but long term we will have some things to maintain. Example not using bootstrap flex, give us some other javascript for responsive UI resizing

  • what do you mean make room for OGC API Services?

    • Make a page for “Features”, with tabs for “General”, “WFS”, “OGCAPI”

AI Policy Chat

GDAL and others are making AI Policies:

  • We have been pretty informal so far

  • Other projects are being hit with AI Generated Junk PRs and are making a policy in response

    • we want to be clear to not waste maintainers time with pull requests that you do not understand yourself

GDAL has:

  • https://github.com/OSGeo/gdal/pull/13880

  • This is a good start, let GDAL finish and then revisit this topic, in case they make good progress.

  • Jukka offers perspective that it is okay close these PRs,

    • GDAL set up policy to make this clear

    • Google summer code

GeoServer:

  • Not sure of need right now, …but we see having it in place could be useful

  • We do get security vulnerabilities reported this way, and they are annoying, and more importantly not effective. See presentation where auto report was correct, but no action occurred until a human was in place to explain impact etc…

sidebar on google summer code:

  • Yes GeoTools and GeoServer have history of taking part, mixed results, …

    • Beneficial for student, Ian was good at this :slightly_smiling_face:

    • Mixed tracked record of keeping the resulting code

    • Our real goal is to keep a developer after the program finished

  • Other OSGeo projects, pgrouting for example, have good experience

Chit Chat

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

  • Work in progress, for example needs a better PR title

  • Ability to disable service versions

mkdocs:

  • tables within tables are the trouble?

    • Can we start rewriting the rst?

    • To fix table, un-indent, but that breaks numbering (for example)

  • Image mosaic looks better: https://geoserver.org/geoserver/en/user/data/raster/imagemosaic/configuration/

  • But other problems remain, developer guide wicket development page

    • notes in tables for example

  • Image + caption can end on the same line?

    • we can do two spaces after the image, then that will act as a
      tag

  • Q: Can we leave 2.28 as RST? But it makes backporting harder

    • This would simplify a lot of the challenge

    • however backport bot would not longer work for 6 months

      • We could break PR into change, and doc-change, …

  • Q: Could we accept the 2.28.x with glitches after the change?

    • We would have trouble with docs that update screen snap, and update the markdown changes

    • huh, backporting docs that includes screen snaps would always cause conflicts

  • https://github.com/petersmythe/translate

    • AI “improved” fork :slight_smile:

Action:

  • jody: make an email or proposal about this so we have a wider discussion about choice of mkdocs for 2.28.x