Talk:GRASS GIS Community Sprint Prague 2019: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
Line 1: Line 1:
= Participants and Reports =
= Participants and Reports =
== Decisions made ==
* Startup: New GUI startup procedure and roadmap for implementing it
** We spent several hours over the course of the sprint discussing different alternatives and finding a best way to implement the one we have chosen.
* GitHub migration: Keep current tickets on track open, but open new issues on GitHub.
** Keep current tickets on track open (i.e., valid and to be used), but disable opening new tickets. People involved in old tickets can continue discussing there.
** Open new issues on GitHub and direct all users there.
** We just need to clarify on mailing list that if you opened or are following an issue on Trac, you should continue there.
** No migration of issues to GitHub is needed which makes this plan simple to execute.
** Everybody is encouraged to be more "aggressive" about closing old tickets on Trac which are now invalid or no longer relevant. Opening new updated issue after that on GitHub is welcome.


== Vaclav Petras ==
== Vaclav Petras ==
Line 9: Line 20:
** Update Trac wiki Submitting/General (https://trac.osgeo.org/grass/wiki/Submitting/General?action=diff&version=17)
** Update Trac wiki Submitting/General (https://trac.osgeo.org/grass/wiki/Submitting/General?action=diff&version=17)
* PR for sync keywords of r.null & comp. (https://github.com/OSGeo/grass/pull/239)
* PR for sync keywords of r.null & comp. (https://github.com/OSGeo/grass/pull/239)
* Notes on *Decisions made* here


== Martin Landa ==
== Martin Landa ==
Line 24: Line 36:
** https://trac.osgeo.org/grass/ticket/3981
** https://trac.osgeo.org/grass/ticket/3981
* r.sim improvements - dynamic allocation
* r.sim improvements - dynamic allocation
== Ondrej Pesek ==
* https://github.com/OSGeo/grass/pull/231
* https://github.com/OSGeo/grass/pull/234
* https://github.com/OSGeo/grass/pull/241


== Markus Neteler (remote) ==
== Markus Neteler (remote) ==

Revision as of 09:41, 6 December 2019

Participants and Reports

Decisions made

  • Startup: New GUI startup procedure and roadmap for implementing it
    • We spent several hours over the course of the sprint discussing different alternatives and finding a best way to implement the one we have chosen.
  • GitHub migration: Keep current tickets on track open, but open new issues on GitHub.
    • Keep current tickets on track open (i.e., valid and to be used), but disable opening new tickets. People involved in old tickets can continue discussing there.
    • Open new issues on GitHub and direct all users there.
    • We just need to clarify on mailing list that if you opened or are following an issue on Trac, you should continue there.
    • No migration of issues to GitHub is needed which makes this plan simple to execute.
    • Everybody is encouraged to be more "aggressive" about closing old tickets on Trac which are now invalid or no longer relevant. Opening new updated issue after that on GitHub is welcome.

Vaclav Petras

Martin Landa

Anna Petrasova

Ondrej Pesek

Markus Neteler (remote)