Difference between revisions of "Talk:GRASS GIS Community Sprint Berlin 2019"

From GRASS-Wiki
Jump to: navigation, search
m (Martin Landa)
m (+ link to https://data.neteler.org/tmp/grassgis_2019_berlin_sprint_group_anim.gif)
 
(18 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
= 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 =
 
= Participants and Reports =
  
 
Summarizing '''press release''': TODO
 
Summarizing '''press release''': TODO
  
 +
<center>
 
[[File:grassgis 2019 berlin sprint group photo.jpg|400px|center|GRASS GIS community sprinters at DIW Berlin, 2019]]
 
[[File:grassgis 2019 berlin sprint group photo.jpg|400px|center|GRASS GIS community sprinters at DIW Berlin, 2019]]
 +
GRASS GIS community sprinters at DIW Berlin, 2019 ([https://data.neteler.org/tmp/grassgis_2019_berlin_sprint_group_anim.gif animated GIF])
 +
</center>
  
 
== Peter Loewe ==
 
== Peter Loewe ==
Line 10: Line 17:
  
 
* Discussion about Zenodo / GitHub integration
 
* Discussion about Zenodo / GitHub integration
* Working on Wikipage about the [https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage Zenodo-GitHuB integration]
+
* Set up of Wikipage about the [https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage Zenodo-GitHuB integration] with all known facts and necessary steps tp dp this.
 
* Investigating [https://grass.osgeo.org/grass7/manuals/addons/v.surf.mass.html v.surf.mass] for social sciences and economic research.
 
* Investigating [https://grass.osgeo.org/grass7/manuals/addons/v.surf.mass.html 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, vittles, display of holy GRASS relics, etc.)
  
 
== Markus Neteler ==
 
== Markus Neteler ==
Line 17: Line 26:
 
* creation of all new Github repos
 
* creation of all new Github repos
 
** GRASS GIS core: https://github.com/OSGeo/grass (GRASS GIS >= 7.x)
 
** 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 - 1999)
+
** 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 addons: https://github.com/OSGeo/grass-addons
 
** GRASS GIS promotional material: https://github.com/OSGeo/grass-promo
 
** GRASS GIS promotional material: https://github.com/OSGeo/grass-promo
Line 42: Line 51:
 
* Working on GitHub migration
 
* Working on GitHub migration
 
** finalize source code migration to GitHub ({{trac|3722}})
 
** 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
+
*** 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
 
* Update/Fix WinGRASS build procedure to work with Git
 
* {{github_pr|9}}
 
* {{github_pr|9}}
Line 63: Line 77:
 
** learning and testing with HowToGit document
 
** learning and testing with HowToGit document
 
** discussion about progress of the new website
 
** 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 ({{github_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 ({{trac|3846}}, {{github_pr|6}})
 +
* Help on polishing github profile
 +
* discussions with the other participants on best practice and future plans (git, python3, proj6)

Latest revision as of 22:34, 4 August 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

GRASS GIS community sprinters at DIW Berlin, 2019 (animated GIF)

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, vittles, display of holy GRASS relics, etc.)

Markus Neteler

Nicolas Bozon

Upcoming new GRASS GIS web site

Martin Landa

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