FOSS4G 2015 Code Sprint
Code Sprint - what's that?
A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise.
With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great :)
All participants are welcome and you don't need to register or attend FOSS4G to attend the Code Sprint (registering here on the wiki is appreciated for planning purposes like coffee and food). Some projects will prefer attendees who have previously engaged with the project and already have a working development environment on their computer (i.e. not all project will welcome helping you set up your development environment).
Where & When
WHEN: The day after the main conference (Saturday, September 19th 2015) has been set aside for the Code Sprint, approximately 09:00 until 18:00
What to Bring
How to get there
- 5 minutes by walk from Exit 11 of Gangnam Station, Subway Line #2
- 5 minutes by walk from Exit 4 of Sinnonhyeon Station, Subway Line #9
- ask on the foss4g2015 mailing list, foss4g2015(at)lists.osgeo.org (subscribe)
Additional Interested People
The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.
- Jeffrey Johnson
- Matt Hanson
- Work on Abstract Map Client Framework
- Develop prototypes of the kDijkstra family functions for the pgRouting 2.2 version.
Ecere / GNOSIS SDK
- Kickstart the development of our new open-source graphics engine which will power both the new version of the cross-platform UI toolkit (featuring auto-layout and cascading style sheets) as well as the new capabilities of our GNOSIS geo-spatial SDK, such as curved text labels and smart label placement, and improved vector graphics support. The first back-end implementation for the new engine will likely be based on OpenGL ES 2.0 in order to support both a wide variety of mobile and desktop devices as well as WebGL deployment.
See http://ecere.org/ideas/graphics/ for more info and a detailed development plan.
- CITE tests upgrades (actually fix failing tests, or work your way against a new test, or work on the "single data dir for all CITE tests")
- Bug fixing
- Modify latest CMake for GDAL to use CMake ExternalProject feature, some restructure of sources tree, etc.
- Check if CTest can be used for GDAL testing.
To participate, copy a project skeleton and start a section below for your project.
- your goals