Talk:GRASS GIS Community Sprint Berlin 2019

Sponsors & Supporters

The GRASS Community sprint was kindly sponsored by FOSSGIS e.V. and coorganized by DIW Berlin, which provided the venue.

Participants and Reports

Summarizing press release: TODO

GRASS GIS community sprinters at DIW Berlin, 2019

Peter Loewe

Community-Sprint 2019 Zenodo high level view

• Discussion about Zenodo / GitHub integration
• Set up of Wikipage about the Zenodo-GitHuB integration with all known facts and necessary steps tp dp this.
• Investigating v.surf.mass for social sciences and economic research.
• Preparation of OSGeo as a software commons for upcoming FOSS4G in Bucarest.
• Provision of Sprint infrastructure (coffee machine, vittle, display of holy GRASS relics, etc.)

Markus Neteler

• creation of all new Github repos
  • GRASS GIS core: https://github.com/OSGeo/grass (GRASS GIS >= 7.x)
  • GRASS GIS legacy: https://github.com/OSGeo/grass-legacy (GRASS GIS 3.x, 4.x, 5.x, 6.x - 1987 - 2016)
  • GRASS GIS addons: https://github.com/OSGeo/grass-addons
  • GRASS GIS promotional material: https://github.com/OSGeo/grass-promo
  • Upcoming new web site: https://github.com/OSGeo/grass-website
• Testing of new Github repo at: https://github.com/OSGeo/grass/
• Github teams created - different roles for read/write/admin access
  • grass-committers: GRASS GIS developers team (read/write)
  • grass-admin: GRASS GIS GitHub admin team (all)
  • grass-docker-homebrew-users: users for automated dockerhub and homebrew builds (read-only)
• New Github users added upon email communication
• Draft version of https://trac.osgeo.org/grass/wiki/HowToGit
• (briefly) discussed image collections in GRASS GIS (needed for H2020 openEO.org)
• First PR :-) GH-PR #8
• aftermath cleanup: tracked in https://trac.osgeo.org/grass/wiki/GitMigration#Aftermathcleanup

Nicolas Bozon

• Presentation via video call of a first glance at the upcoming new GRASS GIS web site based on Hugo

Upcoming new GRASS GIS web site

Martin Landa

• Working on GitHub migration
  • finalize source code migration to GitHub (trac #3722)
    • Targets:
      • https://github.com/OSGeo/grass
      • https://github.com/OSGeo/grass-addons,
      • https://github.com/OSGeo/grass-promo,
      • https://github.com/OSGeo/grass-legacy
    • svn2git migration dump and logs: https://grass.osgeo.org/svn2git_archive/
• Update/Fix WinGRASS build procedure to work with Git
• GH-PR #9
• Discussed GRASS support for image collection with Soeren

Ondřej Pešek

• g.gui.gmodeler: Working on PyWPS export (see github commits overview)
• Research and discussions about ANN-fueled semantic segmentation modules for GRASS GIS
• Watching Sören's screenings of Mandelbrot's fractals

Anna Petrasova and Vaclav Petras

• video call from sprint to sprint: Minneapolis OSGeo sprint <--> Berlin GRASS GIS community sprint
  • discussing GitHub migration and HowToGit document

Veronica Andreo

• video call from Argentina
  • learning and testing with HowToGit document
  • discussion about progress of the new website

Anne Ghisla aka aghisla

• Discuss with Peter about archiving of source code in Zenodo (one DOI per GRASS release, connection with git)
• Follow closely the svn2git migration and the design of the new commit/push workflow
• Start working on the HTML man pages, so that they refer to git for source code and last edit timestamp (GH-PR #11, work in progress)
• Investigate a clean way of dropping Python 2.x support, to be done before 2020 (official EOL of Python 2.x)
• Check with MarkusM how to update g.extension to use git - maybe the Debian Python Team's way can be of inspiration https://salsa.debian.org/python-team/tools/python-modules

Markus Metz

• Help with git migration and documentation https://trac.osgeo.org/grass/wiki/HowToGit
• Fix basic GIS functionality: r.contour (#3846), GH-PR #6
• Help on polishing github profile
• discussions with the other participants on best practice and future plans (git, python3, proj6)