Jachym Cepicky <[email protected]> writes: > Hi, > > (after a while) > > I agree with Rainer - and I understand the conservative point of view > - and still remember last change from cvs to svn. Meanwhile, couple of > you might have custom scripts which do enable similar magic in svn, > which are natural to git (without any need for hacking). Git really > makes it *very* easy to merge code and solve conflicts, not to mention > possibility of forking and pulling from various repos (more organised > way of accepting someone's code).
Just to clearify - forking and pull and push requests are github features - not git. Nowadays github is so sexy, that its features are often confused with being git features. > I think, it's possible to have the main repo in Git and access it with > svn client, if I'm not mistaken. But moving to git as main repo would > be wise option IMHO. > > Github certainly is great service. Custom GitLab instance on (OSGeo?) > server should certainly be considered. In the long run would a GitLab server possibly be the best option. But in the meantime a move to github would be the easiest and all features for which github is famous are there. > But what is the difference between GitHub and Intevation (for those, > who remember)? Just the scale business model IMHO, but the principal > is the same - private companies hosting infrastructure for open source > projects. This is exactly why many dislike github. But as you said, gitlab is also an option which has very nice features (also CI for testing). Cheers, Rainer > > Just my 2 cents > > J > > čt 9. 6. 2016 v 11:37 odesílatel Rainer M Krug <[email protected]> napsal: > > Markus Neteler <[email protected]> writes: > > > Hi devs, > > > > at time I am aware of two GRASS GIS related git instances: > > > > * https://github.com/GRASS-GIS (used for Travis CI, in sync) > > * https://git.osgeo.org/gogs/grass/grassgis (slighly outdated) > > > > It would be nice to go towards a bidirectional SVN <--> git(hub) > > integration in order to collect easily contributions. > > > > Any suggestions how to proceed? > > I know there are many who prefer svn to git, but the question is if the > main repo should migrate from svn to git. > > If the decision is to have a git(hub) repo, I would suggest completely > moving to git. > > I don't think one can reliably and automatically keep two repos in sync. > > As it looks now, grass-ci seems to be updated automatically. > > Cheers, > > Rainer > > > > > Markus > > _______________________________________________ > > grass-dev mailing list > > [email protected] > > http://lists.osgeo.org/mailman/listinfo/grass-dev > > -- > Rainer M. Krug > email: Rainer<at>krugs<dot>de > PGP: 0x0F52F982 > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > > > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Rainer M. Krug email: Rainer<at>krugs<dot>de PGP: 0x0F52F982
signature.asc
Description: PGP signature
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
