Difference between revisions of "FOSS4G 2013 Code Sprint"
|Line 147:||Line 147:|
|Line 158:||Line 159:|
Revision as of 06:38, 30 August 2013
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 :)
Where & When
The day after the main conference (Sunday 22nd September) has been set aside for the Code Sprint. There is also a plan to provide facilities throughout the event in the main venue.
We also have a hackathon running on 17th & 18th September which is also free to attend. See the geohack pages for details.
What to Bring
How to get there
- ask on the foss4g2013 mailing list (subscribe)
Additional Interested People
The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.
To participate, copy a project skeleton and start a section below for your project.
- your goals
Please note: the OpenLayers 3 sprint is taking place on Wednesday 18th in room: Humanities A3
- Tim Schaub
- Bart van den Eijnden
- Julien-Samuel Lacroix
- Jachym Cepicky
- The OpenLayers 3 sprint will begin with a presentation and background
- Ian Turton
- Dependency audit / cleanup
- Look at replacing JDOM with DOM as it is only used internally
- Replace vecmath to avoid Java 3D dependency
- Consider replacing Apache Commons Collections with Guava (if Gabriel still is interested)
- Replace or inline JSR-275 unit classes
- separate i18n as standalone *_nl* jars to keep translations separated from core code base
- add new developer docs how to synch translations to/from Transifex
The uDIG (user-fiedly Desktop Internet GIS) is moving from Refractions to LocationTech.org (an Eclipse Industry Working Group for location aware software). The initial IP review of the uDig codebase is complete and we are in position for our initial code contribution.
- Initial Code contribution
- Refactor from net.refractions.udig to org.locationtech.udig
- Update headers
- Update about.html files
- Clean up after IP review
- Migrate to GeoTools 9.0-M1 (a new milestone with several IP issues resolved)
- Temporarily disable features from the product (for example that depend on antlr 2.7.7)
- Make it look pretty
- Update target platform to Eclipse Kepler for a new look and feel
- Update branding for splash screen and about dialog