[Geoserver-devel] GeoTools / GeoServer Meeting 2017-08-08

GeoServer GeoServer Developer
,
1

Attending

Ben Caradoc-Davies

Torben Barsballe

Jody Garnett

Jukka Rahkonen

Kevin Smith

Apologies

Brad Hards

Agenda1. Access to the new build server for geogig / geofence teams

  1. foss4g prep

  2. code-freeze updates

  3. build.geoserver.org

  4. repo.boundlessgeo.org

  5. Travis CI builds failing

Actions- Erik Merkle: Request build.geoserver.org access on email list to manage geogig community builds

  • Torben: can take look at doing an FOSS4G information sheet, no promises

  • Jody, Kevin and Andrea: working on FOSS4G feature frenzy talk

  • Torben: geoserver team to OSGeo Booth wiki page

  • Jody: to help start the FOSS4G GWC talk, will share with geowebcache-devel list

  • Jody: to add GeoServer BOF to wiki page

  • Jody: will add slide to AGM for GeoServer and GeoTools

  • Torben: will have to contact Nick about Boundless repo backups.

Previous Meeting actions- Jody: Catch up with Nick and SAC. about Windows build cert from OSGeo (done)

  • Jody: 2.12-beta release - check if greater than 1 week delay is worth discussing, will report to a new email thread. (1 week delay is fine)

  • PMC: Kevin starting working, please vote on GSIP 169 (done)

  • Mike: Review new REST-API Docs and take look for gaps during August bug stomp.

  • Andrea: Make an email thread for Marlin renderer at JavaOne, work with Simone (or Jody) to request $500 USD for our GeoServer PSC Budget. (done)

  • Andrea: Merge Marlin PR https://github.com/geoserver/geoserver/pull/2105 (done), and ask email list to test a nightly, will need to test installers during 2.12-beta.

  • Dave Blasby: gs-vectortiles needs a maintainer or goes back to community (email had come in over weekend, dave resolved discussion)

Access to the new build server for geogig / geofence teams

GeoGig and GeoFence teams would like access, this server is run by GeoServer PSC.

Note: GeoGig relies on ares to build “non clean ip” stuff like OSM integration, that due to license is not welcome on eclipse infrastructure.

How do we want to manage server permissions? Normal motion, just like adding a committer.

Action: Erik Merkle: Request build.geoserver.org access on email list to manage geogig community builds

Foss4g prep

List:

  • Information sheet - do we want one? It will be printed for next week. See example A4 information sheets here https://github.com/OSGeo/osgeo/tree/master/marketing/print

  • Action: Torben can take look at doing an information sheet, no promises

  • beta website - here is a link http://osgeo.getinteractive.nl/projects/geoserver/ (feedback welcome, layout and content still being sorted)

  • State of GeoServer talk

  • this is done!

  • Feature frenzy talk

  • jody asked on user list, no replies, looking for cool or unique geoserver features

  • previously we had a list of “best” features (oracle, wfs-t, etc…)

  • multilayer sld

  • netCDF and deep WCS functionality, hard to show (see animations)

  • Action: Jody, Kevin and Andrea working on this

  • State of GeoWebCache

  • Kevin is focused on code freeze, may need help?

  • Action: Jody to help start the talk, will share with geowebcache-devel list

  • Establish osgeo office hours for geoserver team - specific time to sign up?

  • Noon on friday? Not good for torben who has a talk at 1:30

  • How about thursday? Noon.

  • Action: Torben to geoserver team to OSGeo Booth wiki page: https://wiki.osgeo.org/wiki/FOSS4G_2017_Booth

  • BOF

  • How about thursday? After booth session.

  • Action: Jody to add GeoServer BOF to wiki page: https://wiki.osgeo.org/wiki/FOSS4G_2017_BirdsOfAFeather

  • AGM Report

  • GeoServer: This is Simone’s responsibility, board is trying to be “tough” this year as some projects have slacked off

  • We can add a slide to the AGM, take the project status page from state of geoserver talk

  • GeoTools - this is Jody’s responsibility

  • Action: Jody will add slide to AGM for GeoServer and GeoTools

  • Twitter

  • This is unfortunate https://twitter.com/geoserver

  • Want to try for geoserver_gis, geoserver_osgeo, getgeoserver, etc…

  • GeoTools workshops

  • Ian is reviewing, anyone else want to help?

  • Torben has volunteered to help - thanks!

  • Code Sprint

  • Please sign up

code-freeze updates

We are delaying a week to give ourselves more time due to foss4g.

  • Kevin is working on GSIP-159

  • running into issues with WMS-C special cases

  • WMTS GetFeatureInfo

  • Everything else is just tiles

  • Should have no trouble making the code freeze

  • HSV Rotate

  • Simone responded with the contrast enhancement recommended, rather than the rendering transform recommended by andrea (no api change)

  • Still working on the geometry transform since that will not be affected by the code freeze

  • MapBox Style community → extension?

  • Not qualified yet, needs to be deployed in anger, consider for 2.12.1

  • GWC REST API Migration

  • This is critical path, seems to be close to finishing on time

  • REST API Documentation to Swagger

  • Not required for code freeze, but we need to finish these docs for release

  • css community → extension?

  • Happening on email list, did we get enough votes?

  • Efficient filtering of small polygons, and avoiding labeling issues with large ones

  • Not sure if this requires an API change, seems like a great idea (would love to see the visual result)

build.geoserver.org

When can we shut off Ares?

Repo.boundlessgeo.com discussion

Has been failing builds, not sure why:

  • Configuration issue?

Ares builds are failing, because timeouts contact repo:

  • Artifactory backups are slow

  • JFrog recommend using third-party backup (filesystem plus database dump) for large repos

  • Saturdays during backup may produce a timeout.

  • Switch to third party backup solutions

  • Action: Torben will have to contact Nick.

Travis CI builds failing- Travis CI builds often fail with timeouts (50 minutes elapsed) and mysteriously killed builds (memory limit?)

  • GeoTools passed

  • GeoServer failed, ran for 9 mins and got killed, so perhaps a memory limit

  • One thread, get killed by time limit

  • Too many threads get killed by memory limit

  • Can we lower heap, and increase number of threads