GeoSever PSC meeting notes, Jan 28th 2025

GeoServer GeoServer Developer
, ,
1

GeoTools / GeoServer PMC meeting - 2025-01-28

Attending

  • Torben Barsballe
  • Peter Smythe
  • Jukka Rahkonnen
  • Jody Garnett
  • Gabriel Roldan
  • Andrea Aime
  • Kevin Smith

Actions from prior meetings:

  • [image]Jody to “2025 blog post” to the user forum? LinkedIn / Facebook / mastodon and highlight GS3 as a priority (please).
  • [image]Jody to follow up with SAC to see if he can help / hinder VM setup

Agenda

  • GeoServer 2.26.2 release
  • Build Server Certificate Notification Testing
  • GeoServer Cloud release schedule sync-up
  • CSP issues on main
  • GeoPackage CITE tests & current status
  • FOSS4G-EU 2025

Actions

  • [image]Torben: Turn off cert auto renewal, Andrea calendar reminder for March 1st.
  • [image]Gabe: Send for 2.27.x-cloud, 2.26.x-cloud integration branches to discourse
  • [image]CSP errors + environment, Peter and Gabe to follow up GEOS-11346
  • [image]CSP: Jody to document the application property (was missed when PR was merged)
  • [image]Jody: GeoPackage CITE ready for review, GeoPackage CITE test fixes by aaime · Pull Request #5066 · geotools/geotools · GitHub

GeoServer 2.26.2 release

Release is out: announcement

Do we have a volunteer for Feb 2.25.x maintenance: Peter!

How about 2.27.0: Gabe and Jody

Build Server Certificate Notification Testing

The build.geoserver.org certificate is currently valid through March 16, 2025.

Auto-renewal happens 30 days before expiry. Last time auto-renewal failed, I got an email notification 20 days before expiry.

private discourse is … working? Apply to join the group: https://discourse.osgeo.org/g/geoserver-builds

Test: wait for cert to “expire” and wait for notifications … expected: Late Feb!

  • Torben: Update the destination email and disable the cert auto-renewal before Feb 16
  • GeoServer-Builds: Expect notifications late Feb (26th…ish)
    • If we don’t get one, we can tinker with configurations and might see another notification a week later
  • Either way, re-enable cert auto-renewal before Mar 16

1600×486 118 KB

GeoServer Cloud release schedule sync-up

Q: What would it take to always be in sync?

A: need to apply some patches to jdbc-config, and donate some components back as community modules

How to avoid private forks:

  • GeoServer cloud does not have a release schedule, just “nightly” docker images
  • would like to shift to tracking GeoServer major releases
    • contribute patches back to GeoServer
    • “2.26.x-cloud” branch with patches applied - as a temporary measure
      • would be built in isolation, not published to nexus
    • 2.26.x branch when patches accepted

Aside:

  • Gabe: Catalog data directory stability, based on feedback, would be great for 2.27.x
  • Jody: OGCAPI-Features docs PR pending

Action:

  • Send for 2.27.x-cloud, 2.26.x-cloud integration branches to discourse

CSP issues on main

Content service policy “on by default” is being good testing…

  • i that it is finding problems
    • Some caching - refresh fixes
      • login / logout
    • Some actually broken
      • Layer Preview does not work, unless Control-F5 refresh
    • Layer editor
      • Cannot switch tabs; tone of developer errors

Ideas: Some differences between?

  • localhost, no proxy base URL, layer editor works
  • https with proxy in front, layer editor tabs do not works

Ideas: GlobalSettings HTTP mode

  • redirect, do not redirect, … no effect

Steve was fixing a lot of stuff, and we thought was ready…

  • but this is obviously not ready, so we should revert, …
  • can we help make this visible for Steve somewhere?
    • a cache buster… a url ?page=version
    • encrypt web admin URL providers … but not bookmarkable
      • did not fix layer editor
      • andrea has problems with this setting
  • Q: Can we make a docker compose to reproduce this problem for Steve
    • NGINX + Tomcat?

What kind of CSP errors:

  • it is getting some kind of “http” vs “https” differences

Actions:

  • do not revert, peter can continue with CITE tests using application property
  • jody: document the application property (was missed when PR was merged)
  • Gabe: has an docker compose example, so we can added ticket or discourse chat.

GeoPackage CITE tests & current status

https://cite.geoserver.org/geoserver

  • vm provided by osgeo :slight_smile:
features10 wms13 wms11 wfs20 wfs11 wfs10 wcs11 wcs10
cite-2.26.1 1.6: 2/2 passed 1.30: 2/4 passed, 1 failed 1.22: 6/6 passed 1.4: 12/13 passed 1.36: 4/4 passed 1.13: 7/7 passed 1.17: 0/3 tried 1.16: failed
cite-2.27.x 1.30: 3/4 passed 1.17: 0/3 tried 1.16: failed

WCS 1.0 version negotiation does not work; so needs a cut down war

CITE localhost testing:

  • ngrok: can make localhost https and online for CITE testing

geopackage CITE tests “ready for review”:

FOSS4G-EU 2025

  • workshops: open from 2 December 2024 until 19 January 2025
  • presentation: open from 2 December 2024 until 16 February 2025
  • academic: open from 17 January 2025 until 3 March 2025

Who is going? Want to do any talks…

2

Quick update: WCS 1.1 against 2.27.x now passes all 3/3 tests with no errors.

Not sure why it didn’t the previous times that I tried (and against 2.26.1)

1 Like