Difference between revisions of "GRASS Community Sprint Bonn 2016"
m (stefan to do)
|Line 169:||Line 169:|
| August 26
| August 26
| August 28
| August 28
Revision as of 21:09, 17 August 2016
- CodeSprint I: Sun 21.08.2016 12:00 - Tue 23.08.2016 (open end) (see also here)
- FOSS4G 2016 Schedule
- CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m (see also here)
Get together of GRASS GIS project members to take decisions and tackle small and larger problems.
For this meeting, we welcome people committed to improving the GRASS GIS project. This includes developers, documenters, bug reporters, translators, and users!
If you are interested to sponsor the GRASS Community Sprint, please read about
sponsoring the GRASS project at http://grass.osgeo.org/donations/
and, if needed, contact Markus Neteler <neteler at osgeo.org>. Any surplus at the end of the event will be turned over to the GRASS GIS project.
The GRASS Community Sprint is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet in Bonn. The community sprint is an important opportunity for the GRASS developers to discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. Please see below for the more detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community sprint will be directly contributed back into the GRASS project to the benefit of everyone who uses it.
Thanks to our sponsors
Accommodation and Costs
- to be defined
Agenda - What we plan to do
Note: The program is generally open for your ideas. Please edit this wiki page!
More core developers with SVN write access
- Develop a strategy to refresh the group with core SVN write access
- Migrate the good old CMSMS to Wordpress
- Finalize the new GRASS GIS flyer prepared by Vincent Bain
- needed: catchy time series screenshot
- Release GRASS GIS 6.4.6:
- Coordination is done here: http://trac.osgeo.org/grass/wiki/Grass6Planning
- Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
- Release GRASS GIS 7.0.5:
- Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.0.5tobebackported
- Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.0.5-News
- Release GRASS GIS 7.2.0:
- Coordination is done here: https://trac.osgeo.org/grass/wiki/Grass7Planning#a7.2.0
- Changes are tracked at: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News
Documentation and translation
- Add examples to manual pages
- Translation of messages
- Translation of Wiki pages
Source code Quality Assessment
- integrate "coverity scan" with Travis, https://scan.coverity.com/travis_ci
- check "coverity scan": copy-paste errors, https://scan.coverity.com/projects/1038
- Open bugs concerning GRASS 7: https://trac.osgeo.org/grass/report/19
- : Add link to source code in the documentation pages (almost done, let's finish it!)
- improve r.modis addons
- integrate Google Summer of Code projects (where adequate)
- continue working on OBIA toolchain:
- Testing of mean shift in i.segment
- Finalization of r.object.geometry and its integration into i.segment.uspo
- add R-batch files to OSGeo4W-winGRASS7 see osgeo4w/ticket 413
- Implement an optional session "kickstart" in GRASS with LatLong predefined, then open import wizard | switch projection inside (like most other GIS do!)
Better integration of git into development
- since github/gitlab/bitbucket etc are a valuable and recognized source of new source code, we should be able to receive such contributions easily
- OSGeo currently deploys a self-hosted "gitlab" repo: https://lists.osgeo.org/pipermail/sac/2016-August/007345.html
... YOUR IDEA HERE ...
For organizational reasons, please additionally register at: https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint
Please add your name here or contact Luca Delucchi <lucadeluge at gmail com>:
|1||Luca Delucchi||Italy||August 21||August 28||L|
|2||Martin Landa||Czech Republic||August 21||August 28||L|
|3||Markus Neteler||Italy||August 21||August 28||Releases, project coordination, bug hunting, getting more ppl involved||M|
|4||Nikos Alexandris||Switzerland||August 21||August 28||S or M|
|5||Veronica Andreo||Argentina||August 26||August 28||S|
|6||Moritz Lennert||Belgium||August 21||August 27||M|
|7||Stefan Blumentrath||Norway||August 26||August 28||Port some Addons to python? (or whatever you put me up to)||L|
|8||Milena Nowotarska||Poland||August 21||August 28||M|
|9||Anna Zanchetta||Italy - Israel||August 22||August 27||Implementing and improving some imagery modules, inshallah||S|
Via IRC chat
(IRC is a nice archaic chat system, see IRC)
- Bring your own computer
- Bring your power connector adapter if needed (photo: Germany). See also http://www.power-plugs-sockets.com/
- Install subversion and the compiler tools, and come with a working GRASS development environment if possible.
We have to remember to take at least one group photo! :-)
- Is the GRASS Community Sprint just a coding event?
- It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project.
- On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software
- Is the GRASS Community Sprint for developers only?
- No: anybody can help, with testing, checking out bugs and fixes, documentation and more.
- Where can I get help and more information about the community sprint?
- Contact Luca Delucchi <lucadeluge at gmail com>