GeoTools / GeoServer Meeting 2015-04-14
Attending
---------
Ben Caradoc-Davies
Jody Garnett
Torben Barsballe
Jukka Rahkonen
Andrea Aime
Niels Charlier
Agenda
------
- Database builds
- Jira migration update
- Windows builds
- Release volunteer
- GeoFence integration status
- Nabble mailing list complaints
Actions
-------
- JG: ask about jira migration on SAC email list
- JG/AA: release!
- JG: put a reminder for nabble users on the communication page
Actions from last meeting
-------------------------
- AA: Communicate to devel list that new issues can be created
- HH: upload what issue we have now, do a second pass with
component/versions
- BCD: proposal to change PSC / PMC grace period to 6 months and make
removal automatic [PENDING]
- JG: ask for nightly build test for checkboxes on firefox, etc...
Database Builds
---------------
Oracle database working!
MySql and SqlServer working too
Postgis online, but not working fully (see email discussion).
Ben: happy with Andrea's proposed change.
Ben: available for app schema online tests
Q: Are we done?
A: What about app-schema?
What is needed? Suitable database in postgis AND suitable database in oracle (for 3d tests need spatial companion oracle component).
Q: Run against same database?
A: Practice has been separate but may not be required.
See: http://docs.geoserver.org/latest/en/developer/programming-guide/app-schema/index.html
CodeHaus migration update
-------------------------
It looks like Jira versions and components are all created:
1. (done) placemarks created
2. (done) comments ported
3. (done) attachments? not sure - at least some
4. title?
5. description?
6. links?
7. status/resolution?
Priority: titles/descriptions
Astrodog is the point of contact, contractor hired by OSGeo.
Starting to feel the friction, none of the Jira instances is fully usable at the moment.
Ben: Need ability to update old tickets to reference new, so creation of new tickets is insufficient.
Andrea: Users wanting to attach new sample data, sending Andrea private emails.
What would you like to do? Complain louder...
Where:
- SAC: email list?
- TRAC: http://trac.osgeo.org/osgeo/ticket/1478
What are we getting for feedback?
- Astrodog indicates it is almost done each time we ask.
GeoTools:
- wiki migrated
- module matrix --> README.md
- removed all references to codehaus from docs (new signup up instructions)
GeoServer:
- TODO: need to remove all references to codehaus from the docs
Windows builds
--------------
Andrea has been struggling with this one.
Improvement: One build out of six failing (previously 1 out of 10 working)
On virtual machine the EPSG database responsible for current failing CRS.decode("EPSG:4326") - but no indication that the database could not be setup.
Huh: race condition? failure to create database ...
Only fails on VM, not on real hardware.
Q: where is it failing? VM GeoSolutions has set up ESXi/ESXI server (think VMWare with hypervisor).
Q: Is it VMWare specific? Perhaps try VMWare locally ...
Q: Can we give it a larger slice to see if it is resource starved? Nope not in position to.
Q: Try using HSQL in memory (rather than expose test to disk access). Perhaps too much work - since all it would is verify this as a disk use.
Q: Could we remove temp epsg database before each run? Problem is we have multiple concurrent builds on this machine - should not be problem as file as readme.
Q: seperate temp java.io dirs? Not yet ...
Generally comments:
* Several tests leaving temporary files in global temp directory
Release volunteer
-----------------
Release scheduled, may be blocked by CodeHaus migration.
Q: May not be enough changes?
A: There might be some changes going though, for example validation ones on SLD
Volunteers: Jody and Andrea
GeoFence integration status
---------------------------
* https://github.com/geoserver/geoserver/pull/1005
- Pull request that creates the GeoFence server community module, can run GeoFence integrated in GeoServer, the client will talk to the inner server
- On top of that GUI web page, wicket based, add/rules/modify rules, not everything supported. Rules with restrictions not supported yet, review and testing needed. AA -> ask Emanuele to test/review
- Work ongoing supporting the REST api for rules, tests integrating CXF, work moving to wire the restlets with Spring rest.
- Spring rest api quite similar to cxf, easy to move
(The Oracle/Java official way would be https://jersey.java.net/, mixed experiences with it)
Nabble mailing list complaints
------------------------------
- People sending email to nabble - and not getting a response (since nabble does not send to us).
- Phil Scadden uses nabble and occasionally replies 
http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
http://osgeo-org.1560.x6.nabble.com/GeoServer-f3786387.html
Q: Can we block nabble or auto-reply to it?
A: Nabble (without a subscription) is already blocked, but users ignore the "could not deliver" response.
Q: Can we white-list nabble?
A: Does not have a stable email address (tries to use nabble user's email list).
Actions:
Ideas:
- Update communication page to say do not post via nabble.
Q: Remove links to nabble archive from our docs (use gmane, sourceforge)?
Ben: nabble much easier to user for searching and thread viewing
Q: Andrea: move list to google groups?
Jody: Just like google code ...
Clarification:
* Nabble is warning people they need to subscribe, and provides a button to do so.
* So this is a case where people are not following the instructions.
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz>
New Zealand