Difference between revisions of "FOSS4G 2013 Code Sprint"
(three little LAStools projects with rapidlasso) |
m |
||
| Line 166: | Line 166: | ||
*[[User:yjacolin|Yves Jacolin]] : documentation translation | *[[User:yjacolin|Yves Jacolin]] : documentation translation | ||
*[[User:warmerda|Frank Warmerdam]] | *[[User:warmerda|Frank Warmerdam]] | ||
| + | |||
| + | == GRASS GIS == | ||
| + | |||
| + | '''Attending:''' | ||
| + | |||
| + | * ... | ||
| + | |||
| + | '''Goals:''' | ||
| + | |||
| + | * [http://trac.osgeo.org/grass/wiki/Grass7/Tech-Preview GRASS GIS 7 tech preview release preparation] | ||
| + | * ... | ||
| + | |||
| + | == Iris == | ||
| + | |||
| + | Find [http://live.osgeo.org/en/overview/iris_overview.html Iris on OSGeo Live] or via [http://www.scitools.org.uk scitools.org.uk] | ||
| + | |||
| + | '''Attending:''' | ||
| + | |||
| + | * [[User:ian|Ian Edwards]] | ||
| + | |||
| + | '''Goals:''' | ||
| + | |||
| + | * Possible tasks for an Iris code sprint are being discussed in the [http://2013.foss4g.org/conf/programme/workshops/4/ Iris big data workshop] and throughout the conference, one option is to begin a QGIS plugin by building on our existing basic [https://github.com/SciTools/cartopy/pull/345 interface]. | ||
| + | |||
| + | '''When''' | ||
| + | |||
| + | * Timing will depend on availability of people who are interested. Look out for details on the Met Office stall, or contact [[User:ian|Ian]] | ||
== LASvalidator == | == LASvalidator == | ||
| Line 196: | Line 223: | ||
** complete options for existing tools | ** complete options for existing tools | ||
** consider full Linux support through 'wine' | ** consider full Linux support through 'wine' | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:FOSS4G2013]] [[Category:FOSS4G]] [[Category:Code_Sprints]] | [[Category:FOSS4G2013]] [[Category:FOSS4G]] [[Category:Code_Sprints]] | ||
Revision as of 22:27, 14 September 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
East Midlands Conference Centre, Nottingham, UK.
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
TBD
Sponsor
Questions/Comments/Ideas
- 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.
- Volker Mische: no specific project
- Anne Ghisla: mainly GRASS GIS but also interested in other projects
- Your name: project(s)
Workgroups
To participate, copy a project skeleton and start a section below for your project.
Project-name
Attending:
- user
- user
Goals:
- your goals
OpenLayers 3
Please note: the OpenLayers 3 sprint is taking place on Wednesday 18th in room: Humanities A3
Attending:
- Tim Schaub
- Bart van den Eijnden
- Julien-Samuel Lacroix
- Jachym Cepicky
- Volker Mische
- Milan Antonovic
Goals:
- The OpenLayers 3 sprint will begin with a presentation and background
GeoTools
Attending:
- Ian Turton
- user
Goals:
- 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
GeoServer
Attending:
Goals:
- TBD
Tracker:
https://jira.codehaus.org/browse/GEOS
Repository:
TBD
Goals: TBD
Possibles:
- 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
uDIG
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.
Attending:
Goals:
- 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
Tracker: https://locationtech.org/bugs/
Repository:
TBD
MapServer
Attending:
- Daniel Morissette
- Michael Smith: Also PDAL
- Jeff McKenna : documentation
- Tamas Szekeres
- Yves Jacolin : documentation/translation
Goals:
- TBD
GDAL/OGR
Attending:
- Even Rouault
- Tamas Szekeres
- Yves Jacolin : documentation translation
- Frank Warmerdam
GRASS GIS
Attending:
- ...
Goals:
Iris
Find Iris on OSGeo Live or via scitools.org.uk
Attending:
Goals:
- Possible tasks for an Iris code sprint are being discussed in the Iris big data workshop and throughout the conference, one option is to begin a QGIS plugin by building on our existing basic interface.
When
- Timing will depend on availability of people who are interested. Look out for details on the Met Office stall, or contact Ian
LASvalidator
Attending:
Goals:
- completing CRS check for http://github.com/LASvalidator
- support for more/all GeoTIFF tags
- support for OGC WKT strings
- how? borrow needed code from GDAL / GeoTIFF libs
- slightly related side-project:
- add full proj4 reprojection capabilities to las2las of LAStools
LAStools in QGIS
Attending:
Goals:
- improve LAStools's Sextante toolbox
- modularize Victor Olaya's existing code (started)
- add more recent tools
- complete options for existing tools
- consider full Linux support through 'wine'