[Geoserver-devel] GeoTools / GeoServer Meeting 2016-06-14

GeoServer GeoServer Developer
1

GeoTools / GeoServer Meeting 2016-06-14

Attending
---------

Ben Caradoc-Davies
Jody Garnett
Torben Barsballe

Apologies
---------

Ian Turton

Agenda
------

- GeoServer OSGeo Project Officer
- Release schedule
- OSGeo update
- Upgrade to NetCDF-Java 4.6.6
- ImageMosaic refactoring part 1
- Pull requests

Actions
-------

- Jody: encourage updates to docs/jira to record Simone as GeoServer project officer
- Alessandro and Andrea: release 14.4 / 2.8.4

Actions from last meeting
-------------------------

- Ben to email list to ask for more PMC votes on OSGeo copyright header legal advice [DONE]
- Jody: Contact Justin to declare GeoTools copyright header policy change done, merge in change to developers guide [DONE]

GeoServer OSGeo Project Officer
-------------------------------

Simone Giannecchini has volunteered:
- OSGeo board updated
- website: http://www.osgeo.org/content/foundation/board_and_officers.html (done)
- wiki: https://wiki.osgeo.org/wiki/Contacts (done)
- jira: https://osgeo-org.atlassian.net/projects/GEOS (not yet)

Release schedule
----------------

Updated the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

We are looking at a short release cycle due to release delays of 2.9.

- Alessandro and Andrea have (been) volunteered to release 14.4 / 2.8.4

Release priorities/ideas/mad plans for GeoServer 2.10 release timeframe:
- Jody and Devon are taking a run at GeoTools codebase prior to foss4g workshop in August. Intend to update library for Java 8 syntax.
- Status endpoint is collecting more and more sanity checks (expect GUI during 2.10.x timeframe?) https://osgeo-org.atlassian.net/browse/GEOS-4585
https://osgeo-org.atlassian.net/browse/GEOS-7567
- ImageMosaic api refactor ongoing
- VectorTiles documentation

OSGeo update
------------

Board has been informed of new GeoServer project officer.

Board approved asking for legal advice on GeoTools header policy. Ben/Jody are working with Michael Smith on this one....

OSGeo Marketing committee has asked how they can help:
- GeoTools: Encourage committers, always encourage committers
- GeoServer: Encourage participation, testing, updated handouts?

General discussion on where we get new developers? From companies/organizations, submitting a few pull requests, ...

How can we be more sticky as a community? Our "community" modules is one attempt on this front, not so useful now with github.

Our pull reviews can be ... harsh "no discussion, no jira, no party" (but more directed at longstanding developers cutting corners). We do a better job meeting new developers half way, but time is limited. Can be intimidating to find a good test case example to copy from; perhaps we can make a short list.

Predictable release tick/tock between stable/maintenance helps attract contributions (if not volunteers). As does our open process.

Larger proposals get stuck in review, try many small proposals.

Upgrade to NetCDF-Java 4.6.6
----------------------------

Targeting 2.9.x backport for July 2.9.1 release.

[GEOT-5434] Upgrade to NetCDF-Java 4.6.6
https://osgeo-org.atlassian.net/browse/GEOT-5434

ImageMosaic refactoring part 1
------------------------------

https://github.com/geotools/geotools/wiki/Refactor-ImageMosaic-Index-and-Catalog-management-for-improved-extensibility

Should add Ben's summary to the docs: proposal provides why, pull request provides what.

Notes:
- This is a smaller proposal easier to follow
- The last section has gone beyond strict API interface change and has a fair bit of discussion (is this needed?)
- Needs links to Jira and mailing list discussions

Pull requests Roundup
---------------------

- Many pull requests were reviewed, and some merged

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

2

On Tue, Jun 14, 2016 at 10:48 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Release schedule
----------------

Updated the release schedule:
https://github.com/geoserver/geoserver/wiki/Release-Schedule

We are looking at a short release cycle due to release delays of 2.9.

I remember discussing a few options for the release cycle of 2.10.x when
discussing the delay in 2.9.x, but I don't recall a decision being made.
The proposal for the delay indeed does not state what to do for 2.10.x
in the option we chose:
https://github.com/geoserver/geoserver/wiki/GSIP-142

The decision to make a shorter cycle should be discussed and voted, without
it the usual 6 months cycle should be applied instead (e.g., defaulting on
normal rules, which demand for a 6 months cycle).
If we go for a short cycle it should also be well advertised to allow every
contributor
to plan accordingly (getting it out now is late, but better than not saying
anything
at all).

Release priorities/ideas/mad plans for GeoServer 2.10 release timeframe:
- Jody and Devon are taking a run at GeoTools codebase prior to foss4g
workshop in August. Intend to update library for Java 8 syntax.

Interesting and welcomed. Do you have anything specific in mind?

Our pull reviews can be ... harsh "no discussion, no jira, no party"

(but more directed at longstanding developers cutting corners). We do a
better job meeting new developers half way, but time is limited. Can be
intimidating to find a good test case example to copy from; perhaps we
can make a short list.

Remember, when a test seems hard to put together,
there's always the option of asking on the list for suggestions.

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.

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

3

Updated the release schedule:

https://github.com/geoserver/geoserver/wiki/Release-Schedule

We are looking at a short release cycle due to release delays of 2.9.

I remember discussing a few options for the release cycle of 2.10.x when
discussing the delay in 2.9.x, but I don't recall a decision being made.

If I remember the discussion there was concern about developer availability
unless we stick to the September / Feb release cycle. Sticking to the
September/Feb implies that we have less time for RnD (due to 2.9 being
delayed).

- Jody and Devon are taking a run at GeoTools codebase prior to foss4g

workshop in August. Intend to update library for Java 8 syntax.

Interesting and welcomed. Do you have anything specific in mind?

Going to dust off the conversations we had with Kevin during the Java 8
migration. Focus will be on Features given the ContentDataStore workshop.