*GeoServer / GeoTools Meeting 26 July 2016*
Attending: Alessio, Jody, Torben, Andrea, Simone, Ian, Simone
Agenda:
1. Bug Stomp Sprint Results
2. Release Train and Blockers
3. Getting a head(er) with OSGeo Legal
4. FOSS4G Prep / Code Sprint
5. Backup/restore pull requests
6. Pull request review
Previous meeting actions:
- (done) chris: repo being restarted with more capacity
- andrea/kevin: Security vulnerability fix as per email discussion
- torben/jody: community module YSLD, need documentation ...
- (done) Ian: see if MapServer want to sprint with us on SLD
- (done) Ben: Security vulnerability fix as per discussion
*Bug Stomp Sprint Results*
results:
https://osgeo-org.atlassian.net/secure/ConfigureReport.jspa?projectOrFilterId=filter-11000&statistictype=issuetype&selectedProjectId=10000&reportKey=com.atlassian.jira.plugin.system.reports%3Apie-report&Next=Next
For the prep we had 160 "new bugs", we reviewed half of them (many were
sent back for more details, and the ones that were ready added into the mix
for the bug stomp sprint).
Majority of closed tickets is for old-new-features that were requested
(often by community members where the budget did not come through). A new
feature request from 2006 has not been popular enough to catch budget by
now can ow be closed.
Actual bugs, 35 closed, 6 won't fix, 3 cannot reproduce, 1 not a bug, 25
actually fixed:
https://osgeo-org.atlassian.net/issues/?jql=project%20in%20(GEOS%2C%20GEOT)%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-07-22%20AND%20resolved%20%3C%3D%202016-07-24%20AND%20issuetype%20%3D%20Bug%20ORDER%20BY%20resolution%20ASC
Next sprint?
- Do it in conjuction with "foss4g post-sprint" on sat/sun
Action:
- (draft) simone write blog post
- (done) andrea/jody write some words about the foss4g post-sprint
activities
*Release Train and Blockers*
Kevin has a patch in testing; we should be good to go later today.
Pull requests about it? Incoming?
Update from Kevin: OK, so I've run through a bunch of ad hoc tests with
patched geoserver poking at things that use jsonlib and bean utils. Nothing
seems broken.
Q: Did Kevin figure out what was breaking his local build? A: No!
Q: Did you get Kevin good tea? A: "yes"
Actions:
- Devon/Jody expect to go ahead with the 2.9.x release today
- Ben is up for the 2.8.x release
- 2.7.x users are advised to udpate (we will word blog post appropriately
"potential" rather than "actual").
*Getting a head(er) with OSGeo Legal*
Ben and I met with OSGeo legal council last week, waiting on Ben to send
email summary/write blog post.
TLDR: We are good with respect to headers, small advantage
- headers not required for (c)
- small advantage to headers is opportunity to document license
Actions:
- (done) Brad: Change geoserver dev guide? Is this done/merged ...
https://github.com/geoserver/geoserver/wiki/Proposals/GSIP-147
- Ben: Write up blog post for use by wider community (ie incubation, other
osgeo projects)
*FOSS4G Prep*
pre-sprint:
- Andrea to organize with QGIS sprint, engaged with qgis community,
response is "interested" from the user community, and from some boundless
developers
- Andrea has a patch, need to learn python to write test
- Need access to actual C++ developer, symbology that uses functions and
property names does not have any mapping to SLD expressions current!
- What kind of SLD export? Need a graduated approach:
1.0 SLD
1.1 SE / SLD
GeoServer approach with vendorOptions
- Lots of issues, non standard marks, random extension
Filter where expression should be
Units expressed in on screen mm
Extra attributes where they should not be
- QML vs SLD with respect to completness
- Should we consider making our own XSD that includes vendorOptions? Not
going to happen...
- Or should we poke OGC to offically add vendorOptions? Timesink...
post-sprint:
- bug stomp activity for near and far
- Java 9 compatible (roll out a service registery replacement and test it
to death)
- Existing patches look to be license encumbered
Action:
- Jody: set up a pre-sprint meeting to get organized here on QGIS SLD export
*Workshop Prep*
GeoTools workshops are both going ahead!
- double check Java 8 use
- datastore api change for streams (nice to have)
GeoServer Style Workshop
- GSIP 149 Updated Style Page - in progress going well, expect to complete
this week
- migrate YSLD Reference to user manual
- migrate YSLD Cookbook to user manual (can have one cookbook with tabbed
examples). Would that approach still work for PDF? Not sure ... and not
sure if this is used. Although it has been requeted - assume examples would
show up one after another in the PDF similar to note blocks. Worth an
experiment...
Performance / Enterprise Setup Workshop
- So popular it is being run twice!
- Running on maintenance branch 2.8 so no prep needed
Multidimensional Workshop
- Working as usual, against 2.8
Basic intro
- Working as usual, against 2.8
State of GeoServer Presentation
- copying previous format, will need all new functionality
*Backup/restore pull requests*
GSIP-145 Voting needs to happen on the email list
Q: Discussion of "/rest/activity" api endpoint so we can share background
tasks management?
Pros:
- Advantage is single point to see what oint to see what server is doing
Cons:
- Goes against rest goal of grouping by resource.
PR Parametic Catalog
- expand connection parameters with variable
- https://github.com/geoserver/geoserver/pull/1705 PR: (GEOS-7614)
Allowing GeoServer to store property placeholders as templates into the
catalog
PR reload config:
- https://github.com/geoserver/geoserver/pull/1664 PR: (GEOS-7616) Allowing
plugins to be discovered through appContext and reload/store conifguration
via Interface #1664
- allow plugins to reload after restore
PR Community module: self contained, does not need review
- https://github.com/geoserver/geoserver/pull/1668
Action:
- Alessio - send email to geoserver-devel
*Pull request review*
Out of time - take this up next meeting
------------------------------------------------------------------------------
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
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
