GRASS GIS Community Sprint Autumn 2017
GRASS people, let's meet! Because until the GRASS Community Sprint in March 2018 there's still a looong way to go and there are topics that have been on the agenda for quite some time already... but especially because it is always so nice and fun to meet :D
Purpose and Agenda
Discuss and tackle topics such as:
- Specs for GRASS GIS 8
- please edit here: https://trac.osgeo.org/grass/wiki/Grass8Planning
- What's missing for the 7.4.0 release
- Set up new website (asap) with responsive design
- Bootstrap?
- Examples: http://www.keycloak.org/
- Wordpress?
- like https://osgeo.nl/ or the new OSGeo site?
- Bootstrap?
- Development:
- Migration to git
- Include/invite more core developers
- have more grass-dev meetings
- Funding:
- define concrete goals to be funded
- discuss measures and overall system
- rewrite list of sponsors
- GSoC:
- Review and (possible) integration of GSoC 2017 work
- Outreach:
- offer more GRASS GIS courses, like on osgeo-nl
- more online material, use Sphinx
- generate tons of 1min videos
- Initiatives: one new user a day
- launch a lime survey to know who uses GRASS GIS
- convert manual to Sphinx
- Docker image with tests & benchmarks
Sponsors
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. 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. 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
Venue
- Enschede, Vero's home
Accommodation and Costs
- Enschede, Vero's home - self-funded so far (HEY, consider to donate!)
Planned participation
In person
Please add your name here:
No | Participant | Country | Arrival | Departure | Topic | T-Shirt | Notes |
1 | Veronica Andreo | Netherlands | Fri 10 | Mon 13 | Doc, testing, GCI | S | |
2 | Markus Neteler | Germany | Sat 11th | Sun 12th | See agenda :) | M | Will be travelling back from SFCon Bolzano, hence arriving on Sat |
3 | Markus Metz | Germany | Fri 10 | Mon 13 | GRASS 7.4, 8 | M | |
4 | Moritz Lennert | Belgium | Fri 10 | Sun 12 | GRASS 7.4, 8, Web site, Docs/Tutorials | M | Will have to take a train at around 18:00 on Sunday night |
5 | Nikos Alexandris | Italy | Fri 10 | Mon 13 | Allarounder, as usual + Checking old posts of mine in mailing lists and file tickets where applicable + Implementing parts of ESTIMAP as GRASS-GIS addon | M | |
6 |
Via IRC chat
(IRC is a nice archaic chat system, see IRC)
No | Participant | Country |
1 | Yann Chemin | France |
2 | Helmut Kudrnovsky | Austria |
3 |
Individual Preparation
- Bring your own computer
- Bring your power connector adapter if needed. See also http://www.power-plugs-sockets.com/
- Install subversion and the compiler tools, and come with a working GRASS development environment if possible.
Photos
Remember to take at least one group photo! :-)
Reports
See Talk:GRASS_GIS_Community_Sprint_Autumn_2017
FAQ
- 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 Veronica Andreo <veroandreo at gmail com>