Changes between Version 24 and Version 25 of GitMigration


Ignore:
Timestamp:
04/13/19 13:38:26 (6 years ago)
Author:
neteler
Comment:

less typos

Legend:

Unmodified
Added
Removed
Modified

  • GitMigration

    v24 v25  
    66
    77SVN has served the GRASS project well as a version control system for
    8 numberous years now. The project has estabished routines and infrastructure
     8numerous years now. The project has established routines and infrastructure
    99(code repository, ticketing system, developer wiki) connected to SVN.
    1010However, with an increasing number of Open Source developers using git
    11 (and here especially the success of github), interest in moving from SVN
     11(and here especially the success of !GitHub), interest in moving from SVN
    1212to git has been expressed.
    1313
    1414Reasons to consider moving from SVN to git are to:
    15 * increase the number of contributers and thus contributions due of the popularity of git
     15* increase the number of contributors and thus contributions due of the popularity of git
    1616* make features and functionality of git available for developing GRASS and thus
    1717* make the current GRASS developers happy that prefer git (even if git can already be used against SVN: https://trac.osgeo.org/grass/wiki/HowToMaintainGrassWorkflowUsingGit)
    … …  
    3131
    3232GRASS GIS has already a git-mirror-repository for CI:
    33 * https://github.com/GRASS-GIS  (used for Travis CI, in sync, see https://travis-ci.org/GRASS-GIS/grass-ci)
     33* https://github.com/GRASS-GIS (used for Travis CI, in sync, see https://travis-ci.org/GRASS-GIS/grass-ci)
    3434In addition GRASS has a (yet unused) team within the OSGeo organisation on github.com:
    3535* https://github.com/orgs/OSGeo/teams/grass-gis
    … …  
    4242See also: https://trac.osgeo.org/grass/ticket/3722
    4343
    44 == Choosing a git plattform ==
     44== Choosing a git platform ==
    4545
    4646Moving to git involves the question which git platform to move to. So, in
    … …  
    5151Most common options / git platforms are:
    5252* github (still the most popular, yet proprietary, system with online hosting service)
    53 * gitlab (another plattform with online hosting service and increasing popularity esp. after Microsoft bought github)
    54 * bitbucket (another popular plattform with online hosting service)
    55 * gitea/gogs ("painlessly selfhosted" plattform, hosted by OSGeo SAC)
     53* gitlab (another platform with online hosting service and increasing popularity esp. after Microsoft acquired github)
     54* bitbucket (another popular platform with online hosting service)
     55* gitea/gogs ("painlessly selfhosted" platform, hosted by OSGeo SAC)
    5656
    5757Yet, there are plenty of other options:
    … …  
    6565* https://about.gitlab.com/devops-tools/github-vs-gitlab.html
    6666
    67 GitLab compared to other DevOps tools
     67!GitLab compared to other !DevOps tools
    6868* https://about.gitlab.com/devops-tools/
    6969
    … …  
    9999* Comment/close tickets via commit log
    100100* SVN->GIT sync - (Mirroring existing SVN repository) see:/ticket/1654
    101 * Integration with CI service (hosted eg. Travis CI, AppVeyor, GitLab CI), self-hosted (eg. Buildbot, ?))
    102 * ... (Please add)
     101* Integration with CI service (hosted eg. Travis-CI, !AppVeyor, !GitLab CI), self-hosted (e.g. !Buildbot, ?))
    103102
    104103