[GRASS-dev] Migration to git, use addons as test case?

[Markus Neteler]

On Fri, Jan 25, 2019 at 9:15 AM Martin Landa <landa.martin at gmail.com> wrote:
>
> Hi,
>
> pá 25. 1. 2019 v 9:09 odesílatel Stefan Blumentrath
> <Stefan.Blumentrath at nina.no> napsal:
> > General structure with regards to code that need hosting (or not): trunk, addonds sandbox, website, …
> > Tickets and history

Hi Stefan,

did you already start the Wiki page (where)?

> see related ticket [1]. I wanted to setup real testing environment
> where we can test trac and git integration (I just need to do the last
> step, to restore backup of GRASS trac to sandbox). It could help us to
> decide whether to use
>
> * git + trac for issues
> * git + issue tracker together (github,. gitlab, ...) -> trac swiched
> to read only mode (probably except of wiki)
>
> Ma
>
> [1] https://trac.osgeo.org/grass/ticket/3722

For the collection, here some "further reading":

Recent opinions:
* https://www.reddit.com/r/devops/comments/8nro34/gitlab_vs_github_whats_the_right_hosting_platform/
* https://www.linuxjournal.com/content/opinion-github-vs-gitlab

GitLab compared to other DevOps tools
* https://about.gitlab.com/devops-tools/

GDAL (completed)
https://trac.osgeo.org/gdal/wiki/rfc71_github_migration (adopted)

QGIS migration (ongoing):
* https://github.com/qgis/QGIS/wiki/QGISbugtracker  (pro/con table)
* https://github.com/qgis/QGIS/wiki/QGIS-Platform-migration-plan
(outdated, stalled?)

Importantly: let's start migrating to git and not wait forever (just
my 0.042 cents).

Markus