[Geoserver-devel] Meeting Minutes Feb 7th 2017

GeoServer GeoServer Developer
1

GeoTools / GeoServer Meeting 2017-02-07

Attending

Andrea Aime, Jody Garnett, Torben Barsballe, Kevin Smith

Agenda

  • Beta and 2.10.2 release February

  • Build issues

  • sprint planning / sponsorship updates

  • REST doc generation

Actions

Actions from last meeting

  • Mike to follow up sprint Doodle poll via private email as necessary (done)

  • Torben to look into why Corbertura worked for YSLD, was failing on Java 8 code (done)

  • Everyone please review Catalog Performance Improvements (GSIP-155) (PSC please vote) (done)

  • Ben to send code freeze announcement to mailing list (done)

  • Jody to remind mailing list of bug stomp on Friday (done)

February releases

Volunteeres sorted see https://github.com/geoserver/geoserver/wiki/Release-Schedule:

  • 2017-02-20 Jody Garnett & Andrea 2.11-beta

  • 2017-02-20 Torben and Kevin 2.10.2 stable

Code freeze between beta and final, Feb 18th - March 18th.

  • Jody: Plans to kill AbstractDataStore after five years? No after two years see git blame

  • Andrea: looking at GWC loading performance, coordinate on Kevin on email list (change for loop into parallel stream).

  • Kevin: Working on cached Parameter tracking in GWC. Involves API changes in BlobStore and QuotaStore Hope to have done before code freeze.

Build issues

See email “Our build tests memory filled by finalizers”:

  • andrea drive the build over the cliff

  • PDF output test → iText allocates 30 MBs fonts triggering finalizers breaking build. Building faster than we can clean up (wow!)

  • JVM design problem

  • Increase heap 512 → 768 :frowning:

  • Can we replace iText?

  • I thought new versions had license conflict… it does

  • two libraries available, we would need to make our own graphics2d implementation. So sponsorship needed

  • Can we use less objects with finalizers …

  • JVM objects we cannot avoid

  • MapContext - we could turn that off

Thanks for digging into this Andrea.

Sprint planning / sponsorship updates

Thanks to Gaia3d for gold sponsorship, we still need to gather more sponsors.

We need to book flights this week before flights go up, how can we best organize this?

  • jody: put a call out on geoserver-devel? Or contact participants directly …

Open questions about accommodation? Simone due to check and

Open questions about the train? Simone was going to check.

  • Pisa: Cars :slight_smile:

  • Florence: 30E

Cars:

  • Rent a car?

  • Car pool with GeoSolutions staff? We are looking for around 10 people

REST doc generation

Jody took the rough outline from OSGeo wiki to GeoServer wiki for details/planning.

Planning taking place here:

Doc generation seems to have the most response. Jody does not care too much …

  • Q: how to hook into build?

  • Q: will annotations be around/supported for five years?

  • Q: RAML? What is it …

  • markup for declaring api

  • tedious/verbose to write

  • markup is stable once written

  • what does it do? Nothing on its own … use:

  • community generators for web page / api docs

  • need to talk to Matt K on email list

Goals:

  • spring mvc reference/example

  • code example for Spring MVC Style endpoint

  • docs

  • code example for annotations (or yaml) for docs

  • code example for rest api tutorial

Action:

  • Jody continue with REST API Refresh

  • Reggie talk to Matt K on email list about RAML.

PR Roundup

[GEOS-7953] GSIP 155 - Core improvements for catalogs with many layers, follow up on the write side

[GEOS-7926] Fix WMTS blind re-enabling

  • kevin to merge

PDF fill optimization, candidate for backport:

https://github.com/geoserver/geoserver/pull/2094

2

On Tue, Feb 7, 2017 at 6:28 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

   -

   Andrea: looking at GWC loading performance, coordinate on Kevin on
   email list (change for loop into parallel stream).

Here is a pull request with that simple change (will use as many threads as
the available cores):
https://github.com/geoserver/geoserver/pull/2099

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------