GeoTools / GeoServer PMC meeting - 2024-07-16Attending
-
Torben Barsballe
-
Jody Garnett
-
Gabriel Roldan
-
Austin Joachim
-
Marc Risney
-
Kevin Smith
-
Andrea Aime
-
Peter Smythe
Actions from prior meetings:
-
[TODO] Torben: @ignore failing ogr-jni and vsi tests
-
[TODO] Torben: Update supported GDAL version in docs
-
[TODO] Add flag to fail imageio-ext-gdal tests if GDAL bindings aren’t
found
-
[DONE] Jody: Reject recent geoserver-security join attempt: This is a
volunteer list with no possibility to subscribe. Please contact
geotools-devel if you wish to volunteer.
-
[DONE] Jody: Add something to our developers guide for
geoserver-security list (in addition to SECURITY.md note)
Agenda
-
release schedule check-in
-
snowflake alpha
-
repo.osgeo.org
-
dev guide update(s)
-
FOSS4G Europe feedback
-
Discourse migration
-
chitchat
Actions
-
Jody: request or setup discourse channels (for screenshots)
release schedule check-in
Ian is set for Thursday release:
-
mapfish-print-v2 update (if we can)
-
would be lovely to have a v3 migration plan, or to lift and drop into
geotools codebase
snowflake alpha
We have alpha release ready for review: congrats!
-
Austin and Marc presenting
-
geometry and geography types supported
-
discussion about JDBC datastores, what is most recent?
-
the core has the most recent tests, each plugin grabs them…
-
how much work to stay up to date?
-
have a look at history of an example:
https://github.com/geotools/geotools/commits/main/modules/plugin/jdbc/jdbc-mysql
-
discussion on how community participation support works
-
things like oracle and so on that require infrastructure to test
against attract less involvement
-
postgis and others get funding for new features and maintain all the
time
community modules and maintenance:
-
modules maintained outside eventually peter out … have not had any long
term maintained extensions
-
community modules offer on ramp and public review
-
geotools plugin is LGPL (permissive)
-
extensions get on the “basic maintenance” activities like refactors and
api changes
online tests
-
would need some sponsorship from snowflake to provide a server to run
against
-
https://github.com/geotools/geotools/blob/main/.github/workflows/oracle_online.yml
-
online tests are only run if ~/.geotools/snowflake.properites found with
connection details
-
what about
https://blog.localstack.cloud/2024-05-22-introducing-localstack-for-snowflake/
chris:
-
May be able to set up a CI/CD testings: 1 credit for 1 hour of compute
-
how much use? Up to the developers …
-
github workflow for each pull request
-
nightly builds
-
weekly online tests
repo.osgeo.org
repo.osgeo.org had some trouble
-
reached a number of components limitation → artificial warning to
encourage sales pipeline
-
nexus ran out of space
-
check hsql or postgresql?
-
based on 30 users, it was 4k a year for commercial
-
we could get it down to under 10 users and requote
-
OSGeo and geoserver do not have enough sponsorship for this game …
each file is a “component” and pom and so on is listed as a component
-
jody adjusted clean up policies to get under 100,000… not a long term fix
-
alternative: we could split up into distinct instances for each repo
Can we just move on? Keep an eye on it …
dev guide update(s)
-
security policy: feedback
-
Discussion about including a POC in disclosure
-
POC when it is in the exploit tools?
So system admins can double check their instance is patched …
-
CVE reached more people so the approach is a success
-
geoserver-security-list-participation
<https://docs.geoserver.org/latest/en/developer/policies/security.html#geoserver-security-list-participation>
-
Use of Jira placeholder?
app schema updates?
-
jody tried updating docs as it was app schema was confusing
-
[GEOT-7616] Postgis_Data_ref_set.sql updates for modern PostGIS releases
<https://github.com/geotools/geotools/pull/4841>
-
has a few off topic qa changes describing test data since app schema
does its own thing
FOSS4G Europe feedback
Basic GeoServer workshop: well attended! Went well.
-
Some folks with newer (java 17 or java 21) had trouble
-
Removed marlin to continue with workshop
-
GeoServer includes a newer marlin because it is better / faster /
fixes
Styling workshop also went well.
-
folks comfortable with editing style by hand
-
qgis geocat bridge demoed, generates good looking styles
-
aside: arcgis pro bridge is now available (on new website
https://www.geocat.net/bridge/)
Presentations:
-
State of GeoServer: thanks Ian and Andrea
-
EO presentation was very popular, standing room, with STAC and WCS and
so on
sponsorship? we need to ask more often …
aside:
-
presentation on geoserver monitoring was really nice
Discourse migration
https://github.com/geoserver/geoserver/wiki/GSIP%E2%80%90225%E2%80%90working
Q: Do we set up a category for GeoServer then subcategories for users,
developers, etc? Or different categories for each?
-
Original proposal suggests different categories for each
-
After more experience with Discourse, subcategories seem better - let’s
go with this
-
Jody will update GSIP-225
<https://github.com/geoserver/geoserver/wiki/GSIP-225> accordingly
-
See
https://discourse.osgeo.org/t/how-would-you-like-to-add-new-categories-for-projects-or-committees/28330/16
action:
-
jody: request or setup discourse category (for screenshots)
-
Peter: create PR for all pages with references to mailing list
chitchat
rest api duplicate post? Associate a user with a group twice → 409 response
code is correct
-
if we make this change we break backwards compatibility? Is it worth it …
-
xml: succeeds and returns 200 → so change to 409 would break things
-
jdbc: throws an exception, 500 → so change to 409 is helpful
-
Peter: Would like to return a 200 (make jdbc the same as xml)
-
Andrea : In controller before associating the user with a group check if
the association is already there → 409
-
Then you have no concern about about producing a primary key violation
from JDBC backend
-
how about 204 (no content) meaning it’s idempotent?
solution:
-
check first: if association is already there then return success, … less
breakage, everyone happy?
about evolving rest api?
-
we were early, so the rest api does not follow modern conventions / good
practices
-
so if we do a new one we would do something v2 :)
marlin: https://github.com/geoserver/geoserver/pull/7760
-
Marlin author likes geoserver as showcase of latest
ogcapi:
-
gabe thanks everyone for their replies, continue
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
