[Geoserver-devel] GeoServer PSC Meeting Minuets November 17th 2015

GeoServer Meeting 2015-11-17

Attending

Ben Caradoc-Davies
Ian Turton
Jody Garnett
Torben Barsballe
Jukka Rahkonen
Andrea Aime
Kevin Smith
Brad Hards
Frank Gasdorf

Agenda

  • Releases: 2.8.1 (etc), 2.7.4 (etc)
  • CITE tests and build infrastructure
  • Simplify Jira workflow
  • Sprint Planning
  • JAI Replacement Update
  • Pull request/issue discussion

Actions

  • Jody: merge GeoTools PR #1030 and backport to 14.x for 14.1/2.8.1
  • Jody: merge GeoTools PR #1048 for 14.x for 14.1 release
  • Ben: release 14.1/2.8.1
  • Alessio: release 2.7.4
  • Ben: simplify Jira workflow for GeoTools and GeoServer
  • Jody: call for nominations for PSC on mailing list
  • Jody: nominate Kevin Smith for PSC on mailing list
  • Kevin: GeoTools / GeoServer - change from snapshot to main (to prevent HTTP 409). Kevin will prepare pull request

Actions from last meeting

  • Andrea whitelist winbuild instead of subscribing [DONE]
  • Jody: check CITE test problem with boundless IT [DONE, but not yet fixed]
  • Ben: call for volunteers to migrate master to Java 8 [DONE]
  • Jody: for Victoria code sprint, reach out to BC government, vivid
    solutions, etc…
  • Ben: make a wiki page for the Victoria code sprint [DONE]
  • Andrea : fill wiki page for code sprint

Releases

See release note:

CITE tests and build infrastructure

  • priority: May have a fix, see mailing list
  • If possible use Jenkins instead of manual testing
  • Future: Hook up new TE-2015 CITE tests from Andrea

Simplify Jira workflow

  • Ben to fix workflow (make new workflow and cut out extra states)
  • Jody just granted full administrator rights to Ben
  • Make a backup first

Sprint Planning

Victoria code sprint:

Paris Code Sprint:

JAI Replacement Update

  • Technical debt page: https://github.com/geotools/geotools/wiki/Replace-JAI (please help update this)
  • LocationTech Steeting Committee: will worth with LocationTech to fundraise for development.
  • OSGeo Board has responded positively: Will work with OSGeo to update downstream GeoTools / GeoServer and related project
  • EclipseCon Europe - had a good discussion the “science working group”, and the GeoTrellis lead Rob Emanuele
  • The replacement should be a joint LocationTech/OSGeo project.
  • Still need a good name for this project (TileProcessingEngine, OpenJI, OpenTI (for tile imaging, OpenTIP)?

GeoServer Steering Committee

http://docs.geoserver.org/latest/en/developer/policies/psc.html

Jody: Nominate Kevin Smith as a member of the PSC.
Ben: +1 second

Take this to the mailing list.

Pull request/issue discussion

Already covered:

  • GeoTools PR #1030 - check contributor agreement and issue report
  • GeoTools PR #1044 (GEOT-5298)
  • GeoTools PR #1048 (GEOT-5302) - jody - merge and pick for master
  • GEOT-5306 (daniele romagnoli required to review). Torben to take discussion to email
  • GEOS-7270 nodata sections either from reprojection or in image may be filled in white in WMS. Behaviour varies between GeoTiff and other formats, and between JAI and JAI-EXT. (Looks like this QA issue in the JAI-EXT codebase on difference between background color and NO_DATA)

General Discussion:

  • Q: Has warning “no a support forum” helped with useless bug reports for Geoserver? A: Yes it has helped.
  • Q: Should we do the same for GeoTools? A: Not needed as the audience is developers
  • Kevin: GeoTools / GeoServer - change from snapshot to main (to prevent HTTP 409). Action: Kevin will prepare pull request.
  • Rate of pull requests has increased Andrea is unable to keep up. Jody and Ian have volunteer to help review.
  • Discussion of error reporting (strip out frameworks from stack trace? Perhaps a bad idea).

On Tue, 17 Nov 2015 02:45:40 PM Jody Garnett wrote:

GeoServer Meeting 2015-11-17

.....

General Discussion:

.....
Team recognised Andrea's efforts on JIRA ticket cleanup and grooming.

Brad

On Wed, Nov 18, 2015 at 5:54 AM, Brad Hards <bradh@anonymised.com> wrote:

Team recognised Andrea's efforts on JIRA ticket cleanup and grooming.

Here is a report showing the cleanup effect, the two weekends spent cleaning
up already fixed, stale, or non reproducible issues are rather visible,
followed
by one in which I've started to look at some tickets I've earmarked as
possibly
easy to fix (still have some 140 in list to verify and if actually easy,
fix):

https://osgeo-org.atlassian.net/secure/ConfigureReport.jspa?projectOrFilterId=project-10000&periodName=daily&daysprevious=120&cumulative=true&versionLabels=none&selectedProjectId=10000&reportKey=com.atlassian.jira.plugin.system.reports%3Acreatedvsresolved-report&Next=Next

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 Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
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.

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