GeoTools / GeoServer Meeting 2015-12-29 =======================================
Attending --------- Andrea Aime Ben Caradoc-Davies Jody Garnett Ian Turton Apologies --------- Brad Hards Agenda ------ - GeoServer code sprint - Milestone release - Update Release Docs (2.7.5 Lessons learnt) - gt-geometry with 3D support - Cluster configuration discussion - Pull requests handling Actions ------- - Jody: do an updated blog post in the new year to thank GeoServer code print sponsors - Jody: talk to Justin on the mailing list about making a new milestone release - Jody: follow up with Niels on clustered notifications Actions from last meeting ------------------------- - Update PSC list to include Brad and Ian [DONE] - Jody: release milestone [BLOCKED] - Ian: release maintenance (2.7.5 et al) [DONE] http://blog.geoserver.org/2015/12/23/geoserver-2-7-5-released/ - Ben: upgrade master to Java 8 [DONE] - Andrea: merge GeoWebCache master Java 8 upgrade when GeoServer is done [DONE] GeoServer code sprint --------------------- https://wiki.osgeo.org/wiki/GeoServer_Code_Sprint_2016 https://github.com/geoserver/geoserver/wiki/Wicket-migration-code-sprint - Final flights being arranged - Jody: do an updated blog post in the new year to thank sponsors (geobeyond, transient) - Andrea sent most of the information needed to the mailing list: http://osgeo-org.1560.x6.nabble.com/Preparing-for-the-Wicket-upgrade-sprint-td5242978.html - Andrea has created a wicket7 branch with mass-migrations applied, still has compile errors, needs brain power to be applied: https://github.com/geoserver/geoserver/tree/wicket7 Milestone release ----------------- - mac: DMG failed to start the Mac App (moving the JAI jars into jetty lib folder allowed it to start). The bin release failed to start (same JAI error). - windows: bin: jukka had some trouble - seems to be old geoserver data directory. installer: not tested. - linux bin release started up just fine Confirms that change to Jetty and Spring cannot be backported. Action: Jody: talk to Justin on the email list. Update Release Docs (2.7.5 Lessons learnt) ------------------------------------------ - Jira release jobs: need to migrate from Jira SOAP to REST API - OpenGeo v Boundless URLs (e.g https://osgeo-org.atlassian.net/browse/GEOS-7355 ) - fixed during the meeting! - Changed Jira link in GeoTools blog ppost template to nicer version https://osgeo-org.atlassian.net/projects/GEOS/versions/11902 (nice - but you need to be logged in) https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=10000&version=11902 (nasty - used for cut and paste) - Ben: get an error message on nice version if unauthenticated Raise Bug report with Atlasian? gt-geometry with 3D support --------------------------- - geotools-devel mailing list: "Toward implementing gt-geometry module for supporting 3D spatial operations" http://osgeo-org.1560.x6.nabble.com/Toward-implementing-gt-geometry-module-for-supporting-3D-spatial-operations-td5242601.html This is the group we met in Korea FOSS4G following up several months later. The work was very interesting technically (Jody has discussed this with Martin). It is also very cool that they are using the ISO Geometry interfaces that we were *close* to throwing out of the codebase due to lack of use. The library they use SIGAL only does DIM-4 (not the DIM-9 that JTS does). Not quite sure what they are asking? - We would welcome their involvement - and am really glad to hear back from them! - Q: Do they need to do anything before submitting pull request? A: Code contribution agreements, think about IP etc... A: Review developers guide and be comfortable with community process - Due to native dependency this would need to be an optional plugin: * gt-geometry is an unmaintained fork of JTS 1.03 and should be killed. If they would like to take over this module great. * gt-jts-geometry still has value, but needs a maintainer to stay alive. Link to ISA server presentation: https://vimeo.com/142207448 (Indoor 3d mapping was an emergent theme for the conference) Cluster configuration discussion -------------------------------- - Jody worried about duplication introduced by clustering pull request, had questions for Andrea * Hazelcast - issues catalog changes (and drops cached resources, so node will lazy reload from JDBCConfig if needed). Probably works with filebase / in-memory catalog, but not worth since it reloads everything that would reload everything. * JMS one works with in memory catalogs. Change notification with full details (keeping filebased / in-memory catalog) Niels' proposal introduces some notification events as part of JDBCResourceStore pull request. This is done by a public class that is injected into the ResourceStore. Other sources of notification: - WPS uses distributed hashmap - GWC uses ... what? Action: Jody will follow up with Niels Pull requests handling ---------------------- - Mandatory discussion before submitting pull requests that make architectural or widespread changes - Submitter not merger remains responsible for changes - Difficult to revert abandoned widespread or entangled changes - Management problem - Submitters must provision time to fix code after merge (they have to be responsible for their contribution for some time). Link to discussion here: http://osgeo-org.1560.x6.nabble.com/Ways-to-reduce-further-the-amount-of-work-needed-to-handle-pull-requests-td5242982.html -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
