GeoTools / GeoServer PMC meeting - 2024-01-16### Attending- Torben Barsballe
-
Jody Garnett
-
Peter Smythe
-
Gabriel Roldan
-
Jukka Rahkonnen
-
Andrea Aime
Actions from prior meetings:- Andrea: Look into JIRA license limit
- Brad: Give the OK on the Wicket 9 Upgrade
Agenda- Proposal: SQL Encoding of Vendor Provided Custom Functions
-
Release Planning
-
Roadmap coordination
-
Sponsorship updates
-
User-list / Discourse discussion
-
Security Vulnerabilities update/review
-
HTML GetFeature encoding with Freemarker templates
-
Jitsi Issues
-
geowebcache domain name was not renewed
Actions- action: Reopen ContentDataStore API ticket GEOT-7509 to update affected docs
-
Action: Wait for Carsten to read the above SQL Function discussion, and we can discuss further in email
-
action: Make a https://trac.osgeo.org/ right away to ask osgeo to purchase domain name (https://trac.osgeo.org/osgeo/ticket/3121#ticket)
-
Action: Peter: create roadmap placeholder pages so we can list in-kind interested parties and sponsors
-
action: Andrea creating a ticket for SF mailman download
-
action: Jody to reply to email topic on getfeature freemarker encoding
Proposal: SQL Encoding of Vendor Provided Custom Functions
Proposal from email: https://github.com/geotools/geotools/wiki/SQL-Encoding-of-Vendor%E2%80%90Provided-Custom-Functions
Q: Is this the change to the ContentDataStore canProcess(filter) kind of thing?
A: No, it was only an API change to main (no need to backport) so that got merged.
-
Um, did this update the content datastore tutorial? Um no …
-
action: Reopen ContentDataStore API ticket to update affected docs please …
Discussion:
-
Jody would like to avoid functionality that only works in PostGIS (for example?) to avoid breaking WFS.
-
Apparently this is already the case with some placeholder functions (KNN for example)
-
Why? Because then the WFS GetCapabilities advertises functionality that “does not work” (this is somewhat a limitation of the WFS standard)
-
Still the approach could be okay for GeoTools Java programmers, but does it really affect GeoServer?
What to do?
-
SLD already has a mechanism for this? Providing a “fallback value” if the function is not available in that context …
-
We could use the marker interface to avoid listing these functions in WFS GetCapabilities
Goal is to make the SQL generation / encoding extensible:
-
seems okay; but is “per datastore”
-
even that should be fine as long as their is a java fallback so it can be listed in WFS GetCapabilities
-
If there is no fallback java implementation? Do not list in WFS GetCapabilities, but could be used in SLD (if there is a fallback value for safety)
The limitations about exact function name match?
- that is not so good as different databases may have different function names, or small SQL snippets …
Jody: WIth the changes above I think this could be a good addition…
Action: Wait for Carsten to read the above SQL Function discussion, and we can discuss further in email
Release Planning
Jody volunteering to do the release this week, see https://github.com/geoserver/geoserver/wiki/Release-Schedule
aside: new graphic for https://geoserver.org/roadmap/ is cute
mkdocs
No I do not have mkdocs ready but you can look: http://jodygarnett.github.io/geoserver/
download is a challenge:
-
within in a docs folder a relative link,
-
linking to stuff outside of docs?
-
We have like 400 examples of this
-
link to raw github on the branch or something.
-
Or use ant to prefetch everything into the docs folder? snippets allows an “include” folder which would be appropriate?
-
See https://jodygarnett.github.io/geoserver/introduction/license/
Roadmap coordination
What is going on:
-
Wicket 9 upgrade if ready (2.25.x be ideal if we can coordinate it)
-
ImageN: Andrea joined email list, needs to be nominated for commit access
-
spring-framework-6: gabe started looking at it
Can we coordinate with Brad to get Wicket upgrade in time for 2.25.x release cycle?
-
Brad outlined something technical about wicket upgrade and said not to test yet?
-
New security feature of the browser, which disables inline styles, …
-
result is need to removing inline styles
-
What is needed:
-
Brad to enjoy summer vacation in Australia
-
Setup a planning document, or wiki page, to outline plan for the year - so people can help
-
We will wait to seek Brad’s guidance, and then setup a google document / spreadsheet to coordinate:
-
complete the changes to remove inline styles and script form each page
-
release a milestone release (or use a nightly build)
-
recruit user-list and volunteers to do A/B testing of each and every page
-
Wicket 10 model/window is getting removed?
-
Wicket 9 offers a more low-level thing
-
Good idea to do this rewrite before Wicket 10 and can be a separate PR
ImageN:
-
Andrea started looking at consequences for JAI-Ext project
-
Has reached out to ImageN devel list, and will need to be nominated for commit access
spring-framework-6
-
Gabe started looking at this with an experimental branch? To assess amount of work
-
WFS Compatibility tests fail? Maybe an online test failure
-
Lots of mechanical changes (ant / sed)
-
PR draft: https://github.com/geoserver/geoserver/pull/7351 to explore discuss options
Remark: the deegree project is doing something similar, their roadmap: https://github.com/deegree/deegree3/issues/1464
- very interesting! note ImageN transition (https://github.com/deegree/deegree3/issues/1628)
Sponsorship updates
We are getting offers of in-kind assistance - which is more directly useful than financial support 
Q: When we setup page for each activity we should list names / logos (whatever is desired) for these organization
But there is not much we can do with people until we have a plan? Wicket / OIDC / spring-framework / ImageN / etc…
Action: Peter: create roadmap placeholder pages so we can list in-kind interested parties and sponsors
User-list / Discourse discussion
There is a ticket: https://trac.osgeo.org/osgeo/ticket/3104
I think it is a good idea?
- start with user list specifically
Jody: I could not get the mailman API to grab the archive as documented by SF?
Trying the documented approach results in: “The mailing-list mbox was not found.”, even using an admin level account.
Probably need to make a SF ticket to request assistance.
- action: Andrea creating a ticket for SF mailman download
Security Vulnerabilities update/review- A number are ready for review /
- Steve Ikeoka has provided fixes for many of these that can now be applied
Q: How to get these reviewed? It would be good to review before release this week
Ideas:
-
review breakout meeting?
-
review before release?
HTML GetFeature encoding with Freemarker templates
Andrea has email on this topic, but no reply yet
- action: Jody to reply to email topic on getfeature freemarker encoding
Jitsi Issues
We encountered several brief Jitsi outages during this meeting - if these issues reoccur in future meetings we should open a ticket with OSgeo SAC (?)
update: OSGeo System Admin committee was rebooting server at the time of our meeting, and is going to look at doing some kind of bot to provide warning
geowebcache.org domain name
We do not really know who was owning this and let it expire…
- https://trac.osgeo.org/osgeo/ticket/2416 domain name transfer
http://www.geowebcache.org ← name cheap is a domain register (ask osgeo.org to buy it NOW)
https://geowebcache.osgeo.org/ ← this works and is populated
action: Make a https://trac.osgeo.org/ right away to ask osgeo to purchase domain name (https://trac.osgeo.org/osgeo/ticket/3121#ticket)
NameCheap is setting minimum bid of: $200
Update: Three is a transfer code needed, so Planet has a limited time to renew before it is available for general purpose. OSGeo SAC has reached out to Planet to once again try and arrange a transfer.