GeoTools / GeoServer PMC meeting - 2021-05-25### Attending
Andrea Aime
Jukka Rahkonnen
Kevin Smith
Torben Barsballe
Jody Garnett
Actions from last meeting:- TODO: Kevin is going to fix gwc release.rb using xpath or something
-
Kevin will look at GWC website upload
-
Jody: Assign a new port for LDAP testing (since we made a new release)
-
Jody: Start planning CITE Sprint- with a remote sprint a couple days a week for the month of June?
Agenda1. GeoServer Release Page Generation
-
WMS time and caching headers (from ml)
-
GeoServer 2.19.1 release status
-
OGC-API Sprint this week!
-
GeoServer CITE Planning September?
Actions- Jody: Send 2.19.1 release announcement to ML
GeoServer Release Page Generation
Will reduce manual work of creating release pages:
-
Working fine for Andrea (local Jekyll, tried to open random download pages, they are there, seem to be working).
Subsequent update generates download page:
-
Some testing from Brad, updated README.md with clarifications on bundle install step
What is next?
-
Q: About github actions?
-
May ask Michel for some CSS cleanup?!
-
Migrate release pages for 2.9, 2.8, 2.7, 2.6, 2.5, 2.3, 2.2 … if we want them listed on download page
-
I noticed terrible workarounds in javascript to javascript to post-process some output! These I am sure can be removed …
WMS time and caching headers (from ml)
Thread on the mailing list: “Time WMS “magic” and caching sometimes at odds, new config to handle the situation”
What about cases where data near the present is changinging, e.g. with time set to the day only that changes throughout the day and then becomes static?
-
Maybe a candidate for a future capability?
-
What about mismatch without the nearest match enabled? What happens in that case? GWC caches anyways? Any error?
“No Nearest match” could be renamed to “Failed nearest match” or “Out of range match”.
GeoServer 2.19.1 release status- Release is available online
- Jody to send email next
OGC-API Sprint this week!
Sprint is https://www.ogc.org/ogcevents/may-2021-ogc-api-virtual-code-sprint
Wednesday
-
Andrea: set up some sample data:
-
Can ask OGC cost sharing if use the sample data
-
Check on tiles, styles, maps, …
-
Michel: catching up on styling
Thursday
- Jody will set up a separate download, …
Friday
- Demo to sponsors etc…
Topics to keep an eye on:
-
CQL is evolving, perhaps check in with how close it is to ECQL?
-
JSON encoding that GeoTools json-cql probably won’t work and can be removed
GeoServer CITE Planning
PR is still in feedback:
Docker image:
- Please test docker image for local development
How do folks feel about September?
- Perhaps too close to foss4g?
How about October?
- Ask on the list …
Fundraising:
-
We already have funds from prior fundraising
-
Should we ask for additional sponsorship?
-
Is it useful to have funding for a sprint, what we need are people
-
How do feel about cost sharing arrangement
-
GeoNetwork does something similar for their sprints …
-
This would help organizations sending staff …
-
May or may not help individuals attending on their own steam …
-
Approach:
-
Ask organizations attending how much they plan to spend like OGC does
-
Use the number of staff provided / amount spent to define baseline
-
Use this as a baseline for distributing any cost sharing from sponsors
-
Send the same amount to individuals etc… use email rather than invoice
-
How about - to qualify
-
Coordinate with sprint planning, to avoid everyone working on the same spec
-
Contribute a pull request during the course of the sprint (even docs)