GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PDT tomorrow

Reminder that the next PMC meeting is scheduled for tomorrow, July 1, at 18:30 CET.

Cheers,
Torben

It is a public holiday here so I will just attend briefly to check in!

GeoTools / GeoServer PMC meeting - 2025-07-01

Attending

  • Torben Barsballe
  • Andrea Aime
  • Peter Smythe
  • Cécile Vuilleumier
  • Jody Garnett

Actions from prior meetings:

  • [image]gabe: some small update for dev guide, updating conf.py by hand no longer needed
  • [image]Volunteer needed: postgis testing github workflow action
  • [image]Juan: Review new OAuth PR for GS3 activity
  • [image]All: Vote on open proposals if you haven’t already
  • [image]Peter: Cite test proposal - Coordinate payment, add blog post, update site
  • [image]Jody: make a blog post covering FOSS4G workshops and presentations (see below)

Agenda

  1. CITE tests, OGC API Tiles and certification
  2. GeoServer 3 progress
  3. Two weeks to FOSS4G EU
  4. Java 17 incoming
  5. OAuth2 PR merged

Actions

  • [image]Check on the “GSIP 233 - community release” proposal and see if passed.
    jody: Take an action to reword “commuityRelease” as a new option, rather than a reduction of the modules qualifying for nightly build.
  • [image]Torben: Download NGINX access logs, provide to Peter to extract community module stats

CITE tests, OGC API Tiles and certification

Peter has heard back from OSGeo, we are waiting on OGC process:

  • 11 days ago certification submitted
  • no feedback from OGC yet

Andrea:

  • PR for OGC API Tiles!
    • Won’t work on production version of engine, but this is fixed on the beta
    • Community module, so not in position to certify for real yet?
    • We can still submit , with disclaimer about beta used for testing
  • OGCAPI Process - going to be a while
    • two reference implementations are the same one working around bugs
    • echo process used for certification

GSIP 233 - community release

No voting since this proposal was revised for feedback - Jody will make a new thread

Move list of candidates to appendix at the end, so that casual readers won’t take this as a firm commitment.

Further discussion on what merits a community release - proposal includes a higher threshold of requirements for publishing as part of the communityRelease build

  • Raises the barrier to entry for publishing WIP modules too high
  • However, we also have modules that have been sitting in communityRelease state for years with no active development (but often still a small number of users)
  • There’s also a persistent issue of (potential) users complaining about the inaccessibility of these modules and wasting community members time

Q: Do we have download stats for community modules?

we may be able to parse nginx access logs

Action: Torben to download, and provide to Peter

For 17 Jun - 1 Jul:

Top 5 IP addresses:

GeoServer 3 progress

Updates

  • OAUth2 - call for extensible API
  • Java 17 - ready to merge
  • ImageN - foss4g eu sprint incoming

FOSS4G-EU presentation draft available.

Two weeks to FOSS4G EU

  • Many presentations, jody should write blog yet!
  • code sprint for ImageN
  • Might have a light PMC meeting that week.

Java 17 incoming

The PRs are ready:

  • Can we merge now
  • Found some issues with formatting (app-schema integration test modules not in release / communityRelease and were missed

OAuth2 PR merge?

Lets try and get this merged before Java 17 changes come through, to avoid merge conflicts.

  • Need an approval, Alessio will check!
  • We can do API changes and so on after merged
  • Cecile was testing Keycloak and current extension

That is very interesting graph:

  • 80.121.204.253: Bernegger GmbH, Austria / Deutsche Telekom AG address space
  • 4.228.124.71: Microsoft Datacenter Brazil São Paulo
  • 4.228.128.195: Microsoft Datacenter Brazil São Paulo
  • 201.55.6.213: CIA Proc. de Dados do Estado de S Paulo - PRODESP, Brazil
  • 218.234.104.56: SK Broadband Co Ltd, Korea

And as expected OIDC is the most popular community module, was surprised to see MongoDB placing second.