[Geoserver-devel] GeoTools / GeoServer PMC meeting - 2023-08-01

GeoServer GeoServer Developer
1

Attending- Torben Barsballe

  • Kevin Smith

  • Jody Garnett

  • Andrea Aime

Actions from prior meetings:- [DONE] Ian/Jody - GS 2.23.2 Release troubleshooting

Agenda- GeoServer Release

  • Bolsena coming up - geotools refactor

  • Sponsorships

  • Resource API

  • Large catalogs speedup PRs

Actions- Jody: Resource API needs a path forward (see discussion). Propose a breakout meeting with Gabe and Niels

  • [DONE] Andrea: For Large Catalog loading, suggest use a of a SoftCache at CRS.decode(wkt) method to Gabe via PR

GeoServer Release

Some challenges, but mostly went fine

Security vulnerabilities remain an ongoing challenge - some manual intervention is always necessary to review whether or not a vuln. is important enough to merit a warning in the release notes.

Bolsena coming up - geotools refactor

Funding is secured, but we need to decide how to allocate funds for the code sprint. Otherwise things are going forward.

MapFish Print communication is slow, camptocamp is committed to gradle:

  1. ideal camptocamp will update gradle build

  2. pom.xml from geosolutions fork is backup lan

  3. removing printing extension is fallback

GeoFence can also be handled more directly updating the pom.xml

Sponsorships and Communication

See communication page:

Check out the home page: https://geoserver.org/

  • sponsors are highlighted, …

  • core contributors also

Check out new sponsorship page:

  • Listing out 2023 sponsors by logo

  • Prior sponsors text link only

Wiki: https://github.com/geoserver/geoserver/wiki/Sponsor

  • lists things seeking funding

  • think about how to fund backlog of security vulnerabilities for example

Feedback

  • block quote style is to big for email examples

  • maybe we can use a “note” ?

  • update css?

  • Looks like it is coming direct from bootstrap

blockquote p {

font-size:17.5px;

font-weight:300;

line-height:1.25

}

blockquote p {

font-size:14px;

font-weight:300;

line-height:20px

}

  • This change has now been made

Resource API- Gabe and Niels are having trouble with the API changes made earlier this year

  • The definition of path was inconsistent for windows absolute paths

  • Early resource store work was not strict about use of paths, and when to use Resource and when to use File

  • The email conversation is going in circles because something has to break

  • We have to accept that something that break

Jody proposes to be strict:

  • Make ResourceStore produce a warning on absolute paths, or throw an exception

  • There should already be one utility method that can look at a path and decide if is absolute (and use File) or decide it is a data directory resource (and use Resource to get a File)

  • Do the QA to find all the places where ResourceStore was used for absolute paths and fix them to use Files API correctly

  • GeoServerFileChooser may require some work to be careful

  • Remove the test case that was expecting ResourceStore to handle absolute paths
    (as this is indeed in appropriate)

Is a small code-sprint needed to start off this work?

action: Jody propose a breakout workparty to start this activity on the email list

Large catalogs speedup PRs

Set of PRs to speed up loading large data dir. 100k workspaces and 600k layers. Interesting stuff.

Interesting challenges with CRS.decode(wkt) being a bottleneck

  • Gabe is making a cache in loader code

  • Can we provide a cache at GeoTools level?

  • Lots of caches in at factory level

  • Use a SoftCache at CRS.decode(wkt) method

action: Andrea: suggest CRS.decode cache to Gabe via PR

Cheers,

Torben