GeoTools / GeoServer PMC meeting - 2022-09-27Attending

   -

   Torben Barsballe
   -

   Jukka Rahkonnen
   -

   Andrea Aime
   -

   Jody Garnett
   -

   Kevin Smith


Actions from prior meetings:

   -

   N/A


Agenda

   1.

   Welcome page
   2.

   2.22-RC release
   3.

   Exposing database column description in DescribeFeatures
   4.

   REST API and Swagger declarations
   5.

   pr-roundup/chit-chat

Actions

   -

   jody: contact michel about geoserver.css PR



Welcome page

Welcome page is "done" but not yet approved :)

Broken to PRs:

   -

   https://github.com/geoserver/geoserver/pull/6122 [GEOS-10058] Welcome
   Page Layout
   -

   https://github.com/geoserver/geoserver/pull/6198 [GEOS-10624] data
   directory ne workspace


Welcome page, last glitch with "spy vs spy" geoserver.css VS wicket
developer toolbar!

   -

   display:flex assumes all children will be div and styled with flex
   -

   magic wicket:panel picks up normal div styling and breaks this idea


#capabilities .flex-display wicket:panel {

    display: flex;

    gap: 25px;

    margin: 1.5em 0;

    flex-wrap: wrap;

}

Enabling developer mode, done with system variable:
-Dwicket.configuration=development

cite as the default workspace - is empty, can we use something else?
Perhaps topp?

   -

   Was set to be default during routine cleanup ~6 years ago
   <https://github.com/geoserver/geoserver/pull/1604>


Feedback from meeting:

   -

   todo: Include serviceCapabilities even if global services are off
   -

   todo: Make the ne the default workspace
   -

   consider: Cut back roads level of detail and attributes during RC phase,
   adjust tutorial to match
   -

   consider: Show default workspace if global services are off so GeoServer
   does not appear broken
   -

   note: OGCAPI services should migrate to ServiceDescription and they can
   support per-workspace / per-layer services
   -

2.22-RC release

Looks like welcome and ne workspaces are good enough?

   -

   Anyone able to assist?
   -

   Jody have PRs merged
   -

   Branches?
   -

   Help on blog post? - andrea
   -

   Jenkins Jobs?


Anything outstanding?

GWC Security PRs

- just waiting on each other (have to be merged at the same time)

geoserver.css rewrite:

- collecting conflicts

- Michel working on extensions (required)

- Community modules (nice to have)

- Update developers guide (eventually done)

- Ask michel if he wants in for RC or after the release? Or save for 2.23
cycle …
Exposing database column description in DescribeFeatureType

Pick column remarks from databases, expose them as documentation in the XML
schema,

optionally done with a flag in the datastore.

Using PropertyType getDescription(), and enabling with a flag.

REST API and Swagger declarations

We should include the swagger API in the REST API.

How do we link to the many Swagger files though? Each controller has one,
typically the sub-service has its own API linked from it.

If we are to include swagger UI in goserver then the html pages could
incliude link to their api.

Andrea also talked about merging them all into one api, to link to from
welcome page (for admins).

Gabe worked on doing some client generation; how did that go?

Good ideas, funding required :)
pr-roundup/chit-chat

Foss4g presentation on cloud native geoserver:

   -

   faster catalog implementation, multi-threaded loader? Would love to know
   more …
   -

   going back to combined geoserver microservice; rather than geoserver wms
   / wfs / wcs microservce
   -

   microservice catalog? services are so chatty it would make things slow?
   -

   So what is split?
   -

      gui and rest api are distinct microservices
      -

      have options of distinct wms, wfs, wcs microservices
      -

   Wait for video …




Covered above?

   -

   I saw the user parameterized PR go through? Is that not risky …
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to