[GRASS-dev] Migration to git, use addons as test case?
Nikos Alexandris
nik at nikosalexandris.net
Thu Jan 31 15:04:37 PST 2019
A bit late, my "outsider" view, even if some points are known/repeatedly
discussed:
- I prefer gitlab
- Pragmatically, however, github is still "bigger"
- Allow me (to reiterate) please: it is important to "open-up" to as many
contributors, any kind of, as possible--thus, a decentralised
repository is the way to go. Perhaps I am not that attached to SVN to
know it well, but I shouldn't be worried or need to check
multiple times each time I decide to commit something (in my case, the
Add-ons repository). I can break local GRASS GIS repositories as
many times without worries core developers will accept if and when they
judge some request is ready for merging in.
- If the PSC decides for an in-house solution (i.e. OSGeo's
infrastructure or else), consider perhaps some additional workload,
to implement/integrate authorisation and login mechanisms, or similar,
stuff that all "big" players have seamlessly working.
On/Off-topic:
- Add-ons should be only accepted along with some basic unit test
- Please consider also using new ways of interacting: slack or similar?
Cheers, Nikos
* Stefan Blumentrath <Stefan.Blumentrath at nina.no> [2019-01-27 10:37:02
* +0000]:
>Hi again,
>
>
>Having browsed some of the historical discussion and arguments made,
>moving to gitlab.com seems like a natural choice to me personally
>nowadays (with github beeing bought by Microsoft). If we (and equally
>important also OSGeo) see a significant advantage of hosting it in
>OSGeo infrastructure it seems to be doable to import/export projects
>that way.
>
>If competetive copy-left solutions (like e.g. sr.ht or gitea) emerge
>and there pop up push factors to leave gitlab.com pluss hosting on
>OSGeo infrastructure is considered robust enough I would expect
>migration tools will be developed / provided (like import / export
>functions in gitlab).
>
>
>So, I would be happy with a PSC decision on git hosting to speed up the
>process (as I in fact don have strong opinions here), but if you want
>to collect user and developer perspectives in advance, the drafted
>google-forms-survey could be launched as soon as on Monday (tomorrow),
>if of interest.
>
>
>Cheers
>
>Stefan
More information about the grass-dev
mailing list