Attending
Jody Garnett
Kevin Smith
Jukka Rahkonen
Torben Barsballe
Actions from Last Meeting
-
Jody: Letter for JTS Topology Suite Release (permission to distribute
Oracle classes as BSD):
https://github.com/geotools/geotools/wiki/JTS-ORA-Contribution
Agenda
-
Automated CITE Tests
-
Java 9
-
OSGeo CITE Application
-
OSGeo Budget request
-
Sprint Planning
-
Google Code In Tasks (Education outreach)
-
Pull Request Roundup
Actions
-
Jody/Torben: Schedule CITE debugging session
-
Jody: Remind GeoTools PMC to vote on Java 9 Proposal
-
Jody: Forward OSGeo CITE Application email and determine how much time
is left for this renewal application. Probably not much because automatic
mail from OGC says “are due to be renewed by *October 31st, 2017*.
-
Jody: Need a spreadsheet comparing sprint location costs to justify
budget request (short list from email discussion, compare flights and
accommodation for January/February?)
-
Kevin: Bounce GWC planning of gwc email list for discussion review
-
Jody: Revise http://osgeo.getinteractive.nl/projects/geotools/ with
features list from OSGeo-Live
Automated CITE Tests
All except wfs 1.1 working on apollo.
For upgrading to new CITE tests; waiting on this activity to complete (and
sufficient resources).
Actions:
-
Looks like we need debugging session to see where test case is stuck (so
JDB session on build.geoserver.org).
-
Or list the open files and ports for the test case (how to determine
process ID for the test?)
Java 9
Pull request in review, proposal could be reviewed and approved, awaiting
javadocs.
Actions:
-
Jody: Remind GeoTools PMC to vote
OSGeo CITE Application
OSGeo has a reminder from OGC to renew stuff; see email on bo...@osgeo.org
list. Jody will forward.
If we manually run the tests and see what we pass we can get certification
for this year free-of-charge due to partnership between OSGeo and OGC.
Can we ask for a volunteer to stand up a server and run the tests, whatever
we pass we can submit, whatever we do not pass we could make a bug report.
It is not automated but it would be something …
Not sure if we can do this, email seems to indicate Oct 31st.
Action:
-
Jody: Forward email and determine how much time is left for this renewal
application. Probably not much because automatic mail from OGC says “are
due to be renewed by
*October 31st, 2017*. BTW GeoServers can be found from
http://www.opengeospatial.org/resource/products/compliant under Product
Provider: Boundless. Latest version on the list is 2.9.1.
OSGeo Budget request
A reminder to think about this was sent out by Anita, to have on hand for
November Budget.
Budget ideas GeoServer
-
sprint planning, see below, was $3000 last year
-
consider hiring student to run cite tests (see above) it would be a good
way to promote standards and interoperability for all our projects :D
Budget ideas for GWC
-
via incubation committee, but budget still available?
-
asked for ideas on mailing list, anything suitable there? See below...
-
license cleanup, distributed contributors, idea?
Budget idea for GeoTools
-
RPE JAI Wrapper sprint, use $3000 above as a guide? Or look at more
extensive fundraising
Discussion on use of students
-
Intern to run CITE tests is not a bad idea
Sprint Planning
Kevin seems to be the most organized getting GWC refresh underway.
GWC Sprint outline:
1.
code cleanup in 2017 to get the codebase ready
2.
add new features during sprint:
1.
based on competitive analysis with other products
2.
review of geoserver integration
Idea: Importer cleanup
1.
Clean up codebase, use of switch statements
2.
Goal: Import geopkg with styling and publish as GeoServer workspace
(unpacking styles etc... as needed)
JAI Replacement:
1.
Targeted for OSGeo sprint in Bonn
Action:
-
Need a spreadsheet comparing location costs to justify budget request
(short list from email discussion, compare flights and accommodation for
January/February?)
-
Kevin: Bounce GWC planning of gwc email list for discussion review
Google Code In Tasks (Education outreach)
This is for highschool, similar goals as GSOC, but instead focused on
getting students to *use* open source.
There was email on discuss (ha ha) Jody has put in a couple geotools tasks
that amount to compiling and running the quickstart to display a shapefile.
GeoServer tasks suggestions welcome.
Contact vickie for access to shared google doc of tasks (this is private
because students are in a competition to complete tasks).
Pull Request Roundup
- GeoTools: https://github.com/geotools/geotools/pull/
https://github.com/geotools/geotools/pull/1721
-
failing, kevin?
https://github.com/geotools/geotools/pull/1722
-
Reviewed, awaiting response from submitter
https://osgeo-org.atlassian.net/browse/GEOT-5018
-
Got an email wondering why this was not merged, thing it is missing a
test case still
https://github.com/geotools/geotools/pull/1719
-
work in progress, not merged yet
https://github.com/geotools/geotools/pull/1717
-
reviewed by aaime, feedback addressed, questions answered
-
If discussion is settled this can be merged?
-
Jody notes an API change, asks if proposal required
https://github.com/geotools/geotools/pull/1712
-
feedback addressed, torben is merging
-
Q: backport? WIll ask on PR.
https://github.com/geotools/geotools/pull/1711
-
open feedback awaiting changes;
https://github.com/geotools/geotools/pull/1698
-
backport merged
https://github.com/geotools/geotools/pull/1693
-
PR looks sensible
-
1st time contributor, Torben is asking for for CLA
-
Jody, Some formatting problems, provided link to developers guide
https://github.com/geotools/geotools/pull/1692
-
Andrea already asked for a testcase, currently waiting
https://github.com/geotools/geotools/pull/1670
-
Java 9
-
Discussion indicates this is waiting on javadocs for new factory methods
-
Compatibility with ImageIO Registrable Service
-
Downstream testing with GeoServer, GWC, others, …
https://github.com/geotools/geotools/pull/1657
-
Waiting on test case and CLA
-
No feedback for 3-4 months
-
Subject of previous review roundup
-
Jody has sent a request out to both bug ticket and PR, providing links
between the two so the PR can be closed if we do not get a response.
https://github.com/geotools/geotools/pull/1649
-
Fix may be wrong, not quite certain
-
Additional logic seems “okay” but ignores converter design
-
Tests rewritten and avoid color literals, reduced test coverage would
open us up to breaking existing working functionality
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
