Java 2017 Code Sprint

The current plan is for the Java tribe to meet in Italy the week of March 27th. This page will allow us to plan the event.

Questions:

1. Who would be interested in joining as a participating? Please add your name under "participants" below, availability is limited.

2. Who would be interested in sponsoring? ;-) Thanks to Gaia3d and OSGeo for sponsoring, and GeoSolutions for the generous In-Kind contribution of sprint venue.

Location
We will be hosted at the GeoSolutions offices in beautiful Tuscany for a week long sprint. Available seats are limited to 10 to 15!

Additional travel information is outlined in the budget details provided below.

Contacts

 * 1) GeoSolutions Office +390584962313
 * 2) Simone Giannecchini +393338128928

Sponsors
We would like to extend our thanks to the following sponsors:

Participants
Please add your name and the projects you are planning to sprint and note the likehood of your attendance.

Sponsorship
Contributions will be put towards travel costs for overseas sprinters who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.

Sponsors will receive the following benefits / honours:


 * Your logo at the top of this page
 * Mention in all of our public communication, including GeoServer 2.12 release announcement
 * Our gratitude :)

This event provides the following sponsorship levels:

This is an official OSGeo event, your contribution counts towards being recognized as an OSGeo Sponsors.

For more information on sponsorship, please contact Jody Garnett, Andrea Aime.

How to Sponsor
Sponsorship is accepted through PayPal:


 * 1) Navigate to the OSGeo website
 * 2) Click on the "Donate" button in the top right corner
 * 3) Donations are handled through PayPal, when making the donation be sure to:
 * 4) * Check the currency (USD rates are provided above)
 * 5) * Use the "Add special instructions to the seller" field on the confirmation page to mention the event (example "GeoServer code sprint sponsorship")
 * 6) * To make alternative arrangements contact OSGeo Treasurer
 * 7) The OSGeo Treasurer will contact both you and the event organizers to acknowledge your sponsorship
 * 8) * Please have a logo ready for your organization if you wish to be acknowledged publicly
 * 9) * Your event sponsorship, at your request, can contribute towards being recognized as an OSGeo Foundation sponsor

We can also ask that OSGeo provide an invoice for payment (contact Jody Garnett, Andrea Amie to make arrangements).

Sponsorship Outreach
We are reaching out to organizations to see if there is interest in sponsorship:


 * International organizations (OSGeo, GeoSolutions, Boundless);
 * Local organizations

If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).

OSGeo Funding Request
The following information is requested by OSGeo Board Code_Sprint_Guidelines:


 * Java 2017 Code Sprint (Google Docs)
 * Java 2017 Code Sprint Budget

GeoServer
The GeoServer team really benefited from geoserver code sprint 2016 and is eager to repeat the success.

GeoServer Planning
The following topics were proposed:


 * CITE Test Upfrade
 * REST API Refresh - see details below
 * Mapbox Style
 * Library Upgrade

The sprint does not have to be a single topic, if we can swarm a large beast good, but if someone wants to join and work on a side topic to leverage the presence of others, that’s good too.

REST API
The REST API Refresh focuses on migrating the module from Restlet to the more popular Spring MVC, fixing as many issues as we can, and documenting the result.

The REST API for GeoServer is popular, but not well maintained, collecting a large number of outstanding bugs. Many of these complain about functionality and lack of documentation. The large number of bugs (API called correctly but produced an error) may be producing more requests for documentation (developer assumed they called it incorrectly, and asks for improved documentation with an example that works).

Internally the REST API is written using an early java library called "restlet" (http://restlet.com/). There is a desire to migrate to spring rest api which is annotation driven and better supported. The risk in performing a migration to Spring MVC is introducing more bugs than are fixed. This is somewhat offset by having a larger pool of developers familiar with the codebase and the technologies used.

/**    * API endpoint to get details on a specific layer * @param wsName The workspace name * @param name The layer name * @param req The HTTP request * @return The layer, encoded as a JSON object */   @RequestMapping(value="/{wsName}/{name:.+}", method = RequestMethod.GET) public @ResponseBody JSONObj get(@PathVariable String wsName, @PathVariable String name, HttpServletRequest req) {

Rough plan:


 * Create a rest-ng module (alongside existing rest, restconfig, importer-rest, ....)
 * Module based on Spring MVC - see simple PrjController.java example and complex LayerController.java example.
 * Set up converters/encoders for resources
 * Migrate restconfig functionality
 * Migrate importer-rest functionality
 * resource-rest-api
 * rest-upload
 * Audit functionality against GUI
 * shortlist missing functionality for proposal and implementation (examples recalculate feature type columns, rest layer bounds from SRS boudns, ...)
 * Test cases should remain unchanged
 * Documentation
 * Set up documentation team operating concurrently, capturing each resource as it is completed
 * Go for a resource description, json and xml example, example of each kind of request (GET, PUT, POST, DELETE) as appropriate. See mapbox example and boundless example.
 * Consider auto generating example output from test case (see spring-restdocs)

This activity will require quite a bit of people (all hands on deck).

Reference:


 * Searching for REST
 * Searching for Module (not always properly assigned)

Library upgrades
Last year's sprint was devoted to updating a key library and required all hands on deck to help make the transition a smooth one. Ideally we would like to stay on top of library upgrades; however often a change to one has a cascade effect as we need to update (and test) each library in turn.

Note:


 * We may wish to migrate from guava to java 8 and commons collections; as guava often produces conflicts for downstream projects

GeoTools Plans
The GeoTools codebase has a number of smaller of ideas that may of be of interest to volunteers:


 * JDK 9 + maybe JDK 8 updates in the code base (like stream ready support for feature collection, where we can use lambda for profit)
 * JDK 9 replacement for plugin system (service registry) is required

The above ideas may also be suitable to anyone attending remotely who like the focus and support of a dedicated code sprint block on the calendar.