GeoServer/GeoTools meeting Nov 11 2014
---------------------------------------------------------
Attending
---------
Andrea Aime
Jody Garnett
Jukka Rahkonen
Topics
---------
0) Catalog scalability
1) 1.6.1 release
2) Getting feedback on ml got harder
3) wfs pull request
4) OGC Compliant badges
Action items
----------------
- JG: Will check if I can push out 2.6.1 [FAILED]
- JG: Review #777 importer for ians [DONE]
- JG: To look up code sprint / march details and send to geoserver-devel.
Looking to get three people for three days to attack UI on new dev branch.
[DONE - inconclusive]
- AA: setup JDK 8 Travis build [DONE]
- JG: Added GeoServer to the OGC implementation list under OSGeo :)
0) Catalog scalability
----------------------------
Jody reports a fix was made by 2.6.x. The fix was for GetFeature, see
GEOS-6597
1) 1.6.1 release
---------------------
In 7 days now, still missing a release manager, please show up :-)
No volunteer available, have to look at tag teaming: GeoTools -> GWC ->
GeoServer.
Q: How long? A: 4-6 hours (most of that is writing blog post anouncement).
Idea: Email coordination of rolling release, Jody start GeoTools today, ask
Kevin to kick GWC before the weekend, Andrea to try GeoServer on the
weekend. Blog post with Jukka on Monday?
Q: How to find what is new?
- proposals :)
- Jira change log, asking developers for details (and docs if they did not
write them)
- Commits in documentation section <-- that is a good idea (
https://github.com/geoserver/geoserver/commits/2.6.x/doc)
- blog posts to link to
Outline for anouncement:
- copy from previous anouncement
- date, version, links to downloads
- link to change log (jira)
- a couple bullet points based on Jira fixes
- about release section (link to articles, proposals, etc..)
2) Getting feedback on ml got harder
-------------------------------------------------
GeoSolutions needs feedback on new/incoming features.
Jody vanished (working on wfs feedback on the pull request about 50% done
geotools one).
Examples:
* Nicola's GWC in memory caching (Kevin was looking at this - may be ?)
* Scalability against large catalog
* GSIPs lately are getting less votes (can look at retiring PSC members
that have not voted ... in a year?)
Probably everybody is just _very_ busy
3) wfs pull request
------------------------
Jody is working though them.
- GeoTools 50% done
- GeoServer -- will this break when GeoTools request accepted on to master?
4) OGC Compliant badges
-----------------------------------
We list a few in http://geoserver.org/ but I could not find the same ones
from http://www.opengeospatial.org/resource/products
We need to first upgrade the cite tests, right now we don't pass the
official tests.
But we can get "implementing" state without it.
Action: Jody get us added to the list under OSGeo :)
5) Meeting time
15 mins past the hour is better, Jody will send invite next time.
5) WPS incoming stuff
---------------------
- Cancel
- Input limits (size, ranges)
Once we have those, we could push WPS to core. Jody wants to review the
process API before doing that, and push geotools process modules to
supported land too.
6) WCS in INSPIRE
-----------------
Interesting link from Jukka:
https://ies-svn.jrc.ec.europa.eu/projects/download-services-tg/wiki/MIG_workshop_on_WCS-based_INSPIRE_download_services
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
