GRASS Community Sprint Portland 2014

The GRASS GIS team will participate in the Portland Code Sprint 2014 at FOSS4G 2014 in US. The sprint will be held the day after the main conference (Saturday, September 13th 2014).

Purpose

This Portland FOSS4G Code Sprint 2014 is a great occasion for folks to support the development by actively contributing to the source code, manuals or likewise. This code sprint is targeting members of OSGeo software projects.

For this meeting, we welcome people committed to improving the GRASS GIS project and the interfaces to QGIS, GDAL, PostGIS, R statistics, Sextante, gvSIG, OGC Services (esp. WPS) and more. This includes developers, documenters, bug reporters, translators and others. We'll try to make a major step forward towards a stable GRASS GIS 7 release.

Sponsors

We welcome inkind as well as direct financial contributions to help reducing travelling and accommodation expenses for GRASS developers with far arrival If you are interested to sponsor the GRASS Community Sprint, please read about

sponsoring the GRASS project at http://grass.osgeo.org/donations

Note that it is also possible to buy a round of beer for the developers with a quick click using the PayPal "Buy [pizza/beer/...] Now" button

For any questions, please contact Markus Neteler <neteler at osgeo.org>. Any surplus at the end of the event will be turned over to the GRASS GIS project.

This GRASS GIS 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. 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.

The Portland event is especially interesting since important OSGeo projects come together!

Timing

When: Saturday, September 13th 2014

Duration: One day

WHEN: 08:00 until 16:00 (although the building will be open into the evening)

WHERE: The sprint will be in the Eliot Center (OSM) along side WhereCampPDX.

Venue

The sprint will be in the Eliot Center (OSM) along side WhereCampPDX.

Accommodation and Costs

Please check on the page of the sprint more information about accommodation and cost. The participation is free of charge. However, participants should plan for the following costs:

• Travel to Portland
• Accommodation
• Breakfast and dinner (partly)

Agenda - What we plan to do

Note: The program is generally open for your ideas. Please write an email to the GRASS developer list to discuss your contribution or modify this wiki.

Further details about the action items you find here and below. Topics cover non-technical, semi-technical, and technical issues.

Ideas

Please edit this wiki page!

GRASS GIS 7 release related

• http://trac.osgeo.org/grass/wiki/Grass7Planning
  • Fix the few remaining http://trac.osgeo.org/grass/wiki/Grass7Planning#Blockers
  • Decide an official sample dataset for TGRASS, see trac #2259 (comment 4)
• ...
• Last call for options keys, values and flags consolidation, use trac #2409 to coordinate

Manual improvements

• Update the remaining "empty" manual pages (<<--- power users, please contribute!)

In order to coordinate efforts (also with people working from remote places) it would be helpful if volunteers sign up in the table below, for a manual they would feel comfortable to fill. Please feel free to add other modules which need a manual update or with missing manual pages... Regarding examples for the TGRASS modules see also discussion here: http://lists.osgeo.org/pipermail/grass-dev/2014-April/068556.html And for

Module with incomplete manual	Who	Status	Link
t.rast.out.vtk		TBD	http://grass.osgeo.org/grass70/manuals/t.rast.out.vtk.html
t.rast.to.rast3		TBD	http://grass.osgeo.org/grass70/manuals/t.rast.to.rast3.html
t.rast3d.extract		TBD	http://grass.osgeo.org/grass70/manuals/t.rast3d.extract.html
t.rast3d.list		TBD	http://grass.osgeo.org/grass70/manuals/t.rast3d.list.html
t.rast3d.mapcalc		TBD	http://grass.osgeo.org/grass70/manuals/t.rast3d.mapcalc.html
t.rast3d.univar		TBD	http://grass.osgeo.org/grass70/manuals/t.rast3d.univar.html
t.remove	Stefan B.	TBD	http://grass.osgeo.org/grass70/manuals/t.remove.html
t.sample		TBD	http://grass.osgeo.org/grass70/manuals/t.sample.html
t.support		TBD	http://grass.osgeo.org/grass70/manuals/t.support.html
t.topology		TBD	http://grass.osgeo.org/grass70/manuals/t.topology.html
t.unregister	Stefan B.	TBD	http://grass.osgeo.org/grass70/manuals/t.unregister.html
t.vect.db.select		TBD	http://grass.osgeo.org/grass70/manuals/t.vect.db.select.html
t.vect.export	Eric G.	√	http://grass.osgeo.org/grass70/manuals/t.vect.export.html
t.vect.extract	Stefan B.	TBD	http://grass.osgeo.org/grass70/manuals/t.vect.extract.html
t.vect.import	Eric G.	√	http://grass.osgeo.org/grass70/manuals/t.vect.import.html
t.vect.list			http://grass.osgeo.org/grass70/manuals/t.vect.list.html
t.vect.observe.strds		TBD	http://grass.osgeo.org/grass70/manuals/t.vect.observe.strds.html
t.vect.univar		TBD	http://grass.osgeo.org/grass70/manuals/t.vect.univar.html
t.vect.what.strds		TBD	http://grass.osgeo.org/grass70/manuals/t.vect.what.strds.html
More?

• add more examples to the manual which in turn can be used for the new Testing framework for GRASS GIS
• change TOC to collapse style with mouse-over expansion
• clone http://grasswiki.osgeo.org/wiki/Quick_wxGUI_tutorial into new one for GRASS 7 (and replace therein "random surface" with WMS etc)
• ...

New funding model to facilitate payed GRASS GIS programming

• in order to get annoying/boring issues fixed, try a crowd funding approach, eg Kickstarter
  • identify GRASS issues to be fixed for cash
  • discuss how to select the programmers
  • example: http://zim-wiki.org/contribute.html --> Bounties

Testing framework

• how to write tests and general presentation
• discuss relation to benchmarking (https://github.com/jachym/grass-performace)
• write closing Future work statement (TODO list) for related GSoC project

Module fixes related

• get g.gui.rlisetup working for circular buffers (see step-by-step example) [need some testing] trac r61866
• fix v.to.lines in Addons and move it to main GRASS GIS 7 trac r61923
• fix r.li.daemon memory leak test fixed in trac r61812 <<-- testing needed, use examples
• fix potential v.generalize memory leak (add such tests to testsuite)
• check wxGUI r.colors tool for integer maps (may show as FP maps?)
• check patch for *.colors.out trac #2399
• complete r.reclass.area improvements (LD + MN)
• TGRASS: fix numbers in aggregate: tempmean_seasonal_9 --> tempmean_seasonal_0009 | see animation tool where it is solved
• port grass64/raster/r.out.vrml/ to GRASS 7 for 3D printing (put in Addons)
• ...

Web site: related

• simplify http://grass.osgeo.org/download/software/ms-windows/
• OSGeoREL: add parsable "GRASS GIS" tag to table of OSGeoREL labs - then we could showcase them easily in the GRASS CMS
• ...

GDAL/OGR interface

• Patch for GDAL-GRASS plugin for GRASS 7: fix patch in https://trac.osgeo.org/gdal/ticket/2953

Participation

In person

Please fill the related table on the wiki page of the sprint.

Via IRC chat or hangout

IRC

#grass on Freenode

For details, see IRC

Hangout/Videobridge

There is the option to use Google+ Hangout, it is technically limited to 10 people and may require everyone to have G+ social media accounts to participate. More Information on G+ hangout.

Similarly multi-video conference calls can be done with Skype if the conference call initiator is a paid-up commercial Skype customer.

The FOSS Jitsi VoIP, IM, and video conferencing software produces a trivial to set up VideoBridge server software to the same. New: https://meet.jit.si -- zero-conf free no-accounts needed video conferencing; chat, etherpad, and prezi built in. (needs recent Opera or Chrome/Chromium with WebRTC support)

Further discussion on the pros and cons of these can be found on the Talk side of this wiki page.

Please add yourself here below (please add also your gmail account for G+ hangout):

• ...

Individual Preparation

• Bring your own computer
• Bring power connector adapter if needed (USA (Type A) (Type B))
• Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

Broadcast & Video

Perhas during the event :)

Photos

...

FAQ

• How was it last time?
  • Very nice, see GRASS Community Sprint Vienna 2014!
• 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 Markus Neteler, ... (add)

Press Release

...