Hi, Two minor non-PSC comment on RFC 6, which generally looks very good to me:
1) One thing I probably would word a bit differently, is the comment on the addon repository, that currently says: " repository grass-addons repository for addons (this will become less relevant as people tend to keep their addons in own repositories)" Here I would say that esp because people are keeping addons in private repositories, it is even more important to simplify contribution to AddOns (and I hope the move to git would help). Because I consider it as highly valuable to have available addons gathered in one place (see amongst others: https://trac.osgeo.org/grass/ticket/3583). 2) Even being among those who voted for gitlab, I have to admit (as hinted earlier) that I would nevertheless come to the same conclusion that github sould be the destination/target (simply for pragmatical reasons). Also, many participants asked for OSGeo projects sticking together. And most of them are on github. That said, it would be nice if we could try to avoid making a later move away from github too painful (no lock in). In other words, lets try (as far as possible) to stay away from github-specific features[1] that will be hard to move. Just to acknowledge that, a) the decision for github as a target is mainly a pragmatical one (as it is not Free and Open) and following the current majority vote b) even OSGeo projects that currently are on GitHub, like QGIS, have an eye on Gitlab [2] based on a feature analysis [see 1] c) with 43 participants voting for GitHub, 24 voting for gitlab (pluss 5 voting for gitlab in OSGeo infrastructure) there is still (already?) a significant number of people with different preferences But again, lets move to git(hub) and try to stay as flexible as possible... Cheers Stefan 1: https://about.gitlab.com/devops-tools/github-vs-gitlab.html 2: https://github.com/qgis/QGIS/wiki/QGIS-Platform-migration-plan -----Original Message----- From: grass-psc <[email protected]> On Behalf Of Markus Neteler Sent: tirsdag 5. mars 2019 22:49 To: Martin Landa <[email protected]> Cc: GRASS PSC list <[email protected]> Subject: Re: [GRASS-PSC] git migration On Tue, Mar 5, 2019 at 8:24 PM Martin Landa <[email protected]> wrote: > Hi, > > as you probably know there some attempts to move GRASS source code to > git, see also related survey > https://docs.google.com/forms/d/1BoTFyZRNebqVX98A3rh5GpUS2gKFfmuim78gbradDjc/viewanalytics. > > From my POV, GRASS PSC should decide which platform to use. Result of > the survey noted above is quite clear, GitHub platform won. I come to the same conclusions. Importantly, once migrated we can run a mirror in Gitlab. > I would suggest to create a new RFC document for GitHub (source code, > issues, wiki?) migration and than to vote about it. > > See also https://trac.osgeo.org/grass/ticket/3722#comment:20 I have drafted a document: https://trac.osgeo.org/grass/wiki/PSC/RFC/6_MigrationGitHub Please review and comment. Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog _______________________________________________ grass-psc mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-psc _______________________________________________ grass-psc mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-psc
