GeoTools / GeoServer PMC meeting - 2021-12-07Attending -
Torben Barsballe - Andrea Aime - Jukka Rahkonnen Actions from last meeting: - N/A Agenda 1. December release, 2.19.4 2. Keeping older builds running for six more months 3. Reformatter upgrade 4. Participation in Dec 21th meeting 5. GeoPackage community module upgrade Actions - Andrea to check for GeoSolutions availability to do 2.19.4 release - Jody to write proposal for GeoPackage community module upgrade December release, 2.19.4 Possibly GeoSolutions turn, Andrea will check in-house. Keeping older builds running for six more months No issue found during the meeting, extra load is negligible. 1 year cadence? Same points made on list. Reformatter upgrade Java 11 required for latest version (aside, latest Wicket too). https://github.com/geotools/geotools/pull/3697 Also, project closer to get un-maintained, fork pending: https://github.com/coveooss/fmt-maven-plugin/issues/105 Two Options 1. Apply patch with log fix to older release & use that for now 2. Migrate to a different formatting plugin 1. e.g. “spotless <https://github.com/diffplug/spotless/tree/main/plugin-maven>” format plugin. This is not actually as much as it sounds, as the underlying formatter is still the same, mainly just changes in how the plugin is invoked (pom + doc changes mostly) Leaning towards spotless because it’s better supported, but no strong opinion. Participation in Dec 21th meeting Andrea and Jukka will be around, Torben probably not. What about the others? Jody probably yes :-p GeoPackage Community Module Upgrade GeoCat has an opportunity to package this up as an extension for - yay! What is ready to be packaged up …. GeoCat will make a GSIP proposal. - Idea is to propose taking functionality into WFS, WMS and WPS modules directly (rather than have an extension) - Anything not ready can stay in the community module review - WFS: GeoPackageGetFeatureOutputFormat - good - WMS: GeoPackageGetMapOutputFormat - only okay, can generate too much stuff - Maybe if we reduced the zoom levels it could be safe, but the calculation is troubled - Now respects max rendering time - yay! - WPS: GeoPackage Process - Has a complex object as a single parameter - has its own geotools xml and bindings, and schema, ... - Ends up being slightly odd as result - Extensions - from test-bed experiment - GeoPackage Process refers to these directly - GenerlizedTables, PortrayalExtensions, SemanticAnnotations, … - These are good, but can stay as community module Aside: - WPS output download extension also geopackage also … - Has its own thing, does not use WFS GeoPackageGetFeatureOutputFormat - Importer does not handle geopackage yet Aside: - Grids are an RnD topic, may see some interest in the months ahead Chit-Chat Translations - Alexandre working on the translations file, storing it in the GeoServer git repository, Transifex is pulling from there (manually?) - Andrea has prepared language switcher - https://github.com/geoserver/geoserver/pull/5388
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
