This page documents the steps to follow for moving a module from KDE's subversion repository to gitorious.org.

This page documents the steps to follow for moving a module from KDE's subversion repository to gitorious.org.

−

* Write a ruleset for the module and make sure the git repository has all necessary history in it. See the [[Projects/MovetoGit/UsingSvn2Git|Using Svn2Git]] page for more information about this step.

+

* Write a ruleset for the module and make sure the git repository has all necessary history in it. See the [[Projects/MoveToGit/UsingSvn2Git|Using Svn2Git]] page for more information about this step.

* Find a sysadmin who can shut down write access to all places in svn that belong to the module. This is needed so that a final rsync will contain all current history for the module and you don't miss any commit.

* Find a sysadmin who can shut down write access to all places in svn that belong to the module. This is needed so that a final rsync will contain all current history for the module and you don't miss any commit.

* Execute the conversion to create a local git repository

* Execute the conversion to create a local git repository

Revision as of 14:56, 23 April 2010

This page documents the steps to follow for moving a module from KDE's subversion repository to gitorious.org.

Write a ruleset for the module and make sure the git repository has all necessary history in it. See the Using Svn2Git page for more information about this step.

Find a sysadmin who can shut down write access to all places in svn that belong to the module. This is needed so that a final rsync will contain all current history for the module and you don't miss any commit.

Execute the conversion to create a local git repository

Create a project (if there's no existing one that fits yet) and a git repository on gitorious.org via its webinterface.

Create a <module>-reviewers group with the review permission set for the git repository