Table of Contents

Migrating GRASS code repository from SVN to git

Background and aims

SVN has served the GRASS project well as a version control system for
numberous years now. The project has estabished routines and infrastructure
(code repository, ticketing system, developer wiki) connected to SVN.
However, with an increasing number of Open Source developers using git
(and here especially the success of github), interest in moving from SVN
to git has been expressed.

Reasons to consider moving from SVN to git are to:

increase the number of contributers and thus contributions due of the popularity of git

make features and functionality of git available for developing GRASS and thus

Requirements and criteria

Anyway, a first step in order to chose from the available options is to define a
list of criteria (here requirements and features) of the git platform to
move to. For OSGeo a list of requirements has been compiled:
​https://wiki.osgeo.org/wiki/GitServiceRequirement
Yet, that list does not necessarily reflect all or the most important
requirements of the GRASS project and the motivation for moving to git...