GeoTools / GeoServer PMC meeting - 2024-09-24
Attending- Torben Barsballe
-
Jody Garnett
-
Jukka Rahkonnen
-
Kevin Smith
-
Andrea Aime
Actions from prior meetings:- Jody: GeoServer Blog post for GeoServer 3
- Gabriel: Outstanding PRs for 2.26.0 - imageio-ext, workspace admin
Agenda- Release announcement
-
Vulnerability disclosure
-
Docker challenges
-
Discourse geoserver-devel
-
Build Server
-
Wicket
-
GeoServer 3
Actions- Torben: Update Jenkins to JDK 17
Release announcement
Draft PR here: https://github.com/geoserver/geoserver.github.io/pull/220
In a pretty good spot, a few more things to add before publishing
Vulnerability disclosure- We have removed H2 defaults; can we figure out how to disclose and on what release etc…
- action: Andrea to schedule a breakout meeting next monday? (done)
Docker challenges- https://github.com/geoserver/docker/pull/85
- build broken?
Docker build is broken:
[0m [91m+ echo Installing GeoServer 2.26.0 89
- mv /tmp/geoserver /usr/local/tomcat/webapps/geoserver
[0mInstalling GeoServer 2.26.0 89
[91m+ mv /usr/local/tomcat/webapps/geoserver/WEB-INF/lib/marlin-0.9.4.8.jar /usr/local/tomcat/lib/marlin.jar
[0m [91m+ mv /usr/local/tomcat/webapps/geoserver/WEB-INF/lib/postgresql-42.7.3.jar /usr/local/tomcat/lib/
[0m [91m+ mkdir -p /opt/geoserver_data/
[0mRemoving intermediate container bf0f9a32388a
—> e4545328a384
Step 46/58 : COPY $GS_DATA_PATH $GEOSERVER_DATA_DIR
—> 3f89639601a2
Step 47/58 : COPY $ADDITIONAL_LIBS_PATH $GEOSERVER_LIB_DIR
parent snapshot sha256:8c5cab6a3ebbdaf852ea1e83aec10d89b70ee64785f45ef324ca0ef788042bfc does not exist: not found
Build step ‘Execute shell’ marked build as failure
Release was run manually as a consequence, seems to have run into another problem
From the mailing list (release thread)
Your manual build of the Geoserver container seems to have gone wrong. The Geoserver version is 2.25.2 and the architecture is arm64.
docker run docker.osgeo.org/geoserver:2.26.0
Unable to find image ‘docker.osgeo.org/geoserver:2.26.0’ locally
2.26.0: Pulling from geoserver
Digest: sha256:f47225a2650ee231a2ef1a20b81f18ece06081028e5e8f5dd4d162ba90ca1fe7
Status: Downloaded newer image for docker.osgeo.org/geoserver:2.26.0
WARNING: The requested image’s platform (linux/arm64) does not match the detected host platform (linux/amd64/v2) and no specific platform was requested
Welcome to GeoServer 2.25.2
Oh no - Jody did this by hand (as build server is broken as above).
Action: Jody to re-release 2.26.0 after the meeting.
We’ve also got this PR, which may be related to some of the original build server issues (see comments)
Discourse geoserver-devel
Are we comfortable on discourse now?
-
poor: email footers get strange as markdown
-
great: folks are finding discussion from 4 years ago and being helped, or asking for clarification
action: jody would like to move geoserver-devel to discourse … next week? Send note to geoserver-devel today in case of tears.
Build Server
Upgrade to Jenkins and JDK 17
action: Torben will look at this after 2.26.0 - likely Sept 26 or 27
Wicket 9
Peter has not found any show stopping problems when testing 2.26-M0.
The key change (suggested by Andrea) is to default to “warnings” on content-security-policy (rather than failure). It also continues to use the dialog support that is still available in Wicket 9.
Plan:
-
Step 1: Merge in the wicket 9 PR after to 2.26.0 goes out today
-
Step 2: Ask folks to gradually resolve CSP warnings page by page:
-
move JS to header at top of page, or move to separate file
-
move CSS inline style to geosever.css or similar
-
Then ask for public testing of 2.27.x nightly
-
Keeping in mind there are LOTS of warnings!
-
Step 3: Move to GSDialog replacement
-
David made a lot of progress and it looks good (see video)
-
aside: For anything really terrible (due to okay cancel workflow) we may have to rework user experience into pages
GeoServer 3
Jody has a proposal: https://github.com/geoserver/geoserver/wiki/GSIP-226
-
so many changes 3.x is a good idea
-
change to tagging on branch (normal) rather than tagging off branch (something wonderful we invented)
-
rest/v1 forward to rest/
-
Is this okay here or should it be a separate proposal…
-
data directory backwards compatibility maintained? Yes
-
Any change would be a separate proposal…
Chitchat- demo of vector tiles updates
-
mvt community module: open map tiles data 75GB (free for non commercial usage)
-
mbstyle: used for styling
-
but with local sprites! to avoid URL checks
-
style group mbstyle to gather them all together
-
geoserver using the vector tiles to render PNG tiles in your projection of choice
