GeoTools / GeoServer Meeting 2016-08-09 =======================================
Attending --------- Ben Caradoc-Davies Ian Turton Kevin Smith Torben Barsballe Jody Garnett Devon Tucker Jukka Rahkonen Agenda ------ - Time to replace Skype? - Releases - GSIP pull request handling - FOSS4G Prep - Pull Requests Actions ------- - Ben: 2.8.5 release - Skype vs Hangout, technical hardships (try Hangouts next time) - Devon: mailing list announcement for 2.9.1 Actions from last meeting ------------------------- - Devon/Jody: 2.9.1 release [DONE] - Ben: 2.8.x release [PENDING] - Ben: Write copyright header blog post for use by wider community [DONE] - Jody: set up a FOSS4G pre-sprint meeting to get organized here on QGIS SLD export (handled via email) - Alessio: send email to geoserver-devel on backup-restore? (done) Time to replace Skype? ---------------------- - Skype vs Hangout, technical hardships - 25 minutes trying to start the meeting with Skype (incompatible version, web not working for all) - Somewhat successful with Hangouts - Try Hangouts next time - Jukka: voice quality not as good as with Skype, though (in Finland, 8 mbps ASDL connection) Releases -------- 2.9.1 - mailing list announcements pending - some discussion on how to handle security vulnerabilities. Move to standard boilerplate in release announcement, and just link the the fixed issues for details. 2.8.5 Release - Ben is release manager; ready to go, waiting on CITE tests - Kevin has backported GWC security fixes GeoServer 2.10-M0 / GeoTools 16-M0 / GWC 1.10-M0 - Torben on point, release "this week" - A bit of a communication scramble to get ready :( - Kevin and Torben working on QA for GeoServer - Devon, Jody, Torben, IanT working on QA for GeoTools GSIP pull request handling -------------------------- - Email from Andrea https://sourceforge.net/p/geoserver/mailman/message/35270220/ Andrea's Proposal: In the GeoServer history something deemed worthy of a GSIP has been going though the following steps: * Open discussion against a written proposal and vote * Actual code development (could start earlier, but at the risk of the one proposing the GSIP) * Pull request and review (because accepting a plan does not equate accepting its implementation) The first step has some wait time to allow the PSC to review the proposal, it's now set to 1 week. The last one, never had a max time to be performed, but people knew and respected the key developers in the area and allowed a bit of time for changes to be reviewed (the longer, the bigger the pull request was, with some consideration about avoiding too large pull requests at all costs, given review is not paid). - Proposes one week before merging, extra week on request - We are behind on pull requests review applies to all pull requests; not specifically an issue to GSIP - GSIP and pull requests orthogonal - The proposal from Andrea is similar to how GeoTools functions, ie a timebox so proposals are not held up due to lack of volunteers. - We have some kind of trouble here, not sure what to do about it - Suggestion: Include interested parties in the tasks section who wish to review. As per geotools proposal process "tasks" section. - GSIP acceptance criteria? Ben clarified ... from developers guide - So GSIP-149 was "accepted" three weeks ago - Suggestion: Add an "accepted" tickbox to the GSIP template :) FOSS4G Prep ----------- - geotools intro workshop - Jody, Devon meeting this afternoon - geotools datastore workshop - meeting with Ian, Jody, Torben tomorrow - geoserver style workshop - Kevin, Torben meeting this afternoon. Milestone when complete, see above - state of geoserver presentation - in google docs, content with Jody, Andrea, share with rest of PSC for review/content - pre-sprint: Some sld/qgis discussion, lack of resources. Also consider stream discussion - post-sprint: Java 9 upgrade Pull Requests ------------- Focus on milestone https://github.com/geoserver/geoserver/pull/1643 GDAL Binding - waiting on review from module maintainer - Do not package outdated gdal-bindings jar https://github.com/geoserver/geoserver/pull/1624 vector tiles - Dave volunteered as module maintainer, should be able to review https://github.com/geoserver/geoserver/pull/1689 Add REST entry point to GeoFence - [GEOS-7647] waiting module maintainer to review? - waiting 20 days https://github.com/geoserver/geoserver/pull/1701 OL3 Preview wraps tiled layers https://github.com/geoserver/geoserver/pull/1702 OL3 Preview wraps tiled layers, using OL3 internal srs - Two solutions for [GEOS-7272] which one would you like to use? - Who would like to make the decision? Torben likes 1702 better, relies on OL3 projection support, so a bit of caution warranted in case OL3 does not support a projection that we are using. - Other approach marks layer global - both have been reviewed we just need a decision - action: talk to Andreas from OL3 project for clarification https://github.com/geoserver/geoserver/pull/1724 Wfs-ng backwards compatibility test - blocked on wfs-ng fixes on geotools? https://github.com/geoserver/geoserver/pull/1757 Remove unnecessary directory creation (legacy code from before resour… - makes sense, not sure how to do a pull request for this GeoTools - wfs-ng pull requests - geopackage fix from Ian - image mosaic refactor is still in progress - https://github.com/geotools/geotools/pull/1254 URL encoder filter function; a bit surprised this cannot be done already? - https://github.com/geotools/geotools/pull/1240 imagemosaic-jdbc bugfixes; not sure we have an active maintainer here? -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
