[GRASS-dev] New dev team on github for initial tests

Huidae Cho grass4u at gmail.com
Mon Jun 4 16:21:53 PDT 2018

Yeah, that acquisition is bad news. Why can we just not use the OSGeo one?
Just curious.


On Mon, Jun 4, 2018 at 5:00 PM, Markus Neteler <neteler at osgeo.org> wrote:

> On Mon, Jun 4, 2018 at 10:50 PM, Martin Landa <landa.martin at gmail.com>
> wrote:
> [...]
> > Migration to *git* is planned in any
> > case :-) A host platform is not decided yet.
> We simply need to decide between own hosting (incl. git repo by OSGeo)
> and effectively commercial providers (github, gitlab, bitbucket, ...).
> As long as we do not depend on highly specific features of such a
> platform, migration to another git based platform will remain "easy".
> We should carefully try to identify potential single points of failure
> like service unstable, unmaintained in the long run, pay-only traps
> and the like. But unless we use the standard features of git along
> with maybe CI we are relatively flexible in choosing the platform.
> Just my 0.02 cents,
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP
Adjunct Faculty, Kennesaw State University
Senior Geospatial Engineer, MapAnything
Open Source GIS Developer, GRASS GIS Development Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20180604/7bcdbdfe/attachment.html>

More information about the grass-dev mailing list