Projects/MoveToGit/StepsToMove - Revision history

Icwiener: Fix link.

2012-02-23T08:12:36Z

Fix link.

Mehrdad at 14:56, 23 April 2010

2010-04-23T14:56:18Z

Hein at 07:33, 4 March 2010

2010-03-04T07:33:31Z

Apaku at 19:55, 3 March 2010

2010-03-03T19:55:12Z

Apaku: Add a checklist of stuff to do when moving

2010-03-03T19:49:08Z

Add a checklist of stuff to do when moving

New page

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.
* 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
* Create a <module>-maintainers group (or invite admin users individually)
* Give the kde-developers group commit permissions so that any KDE developer can easily collaborate on the module
* The kde-sysadmins needs to be added too with admin rights, so they can help with tagging and general administration (setting up hooks etc.)
* Add the new remote repository to your local one as new remote, then push all local branches and tags to the remote repository.
* Scripty needs to be pointed to the new place of the module, '''TODO:''' how/where/what to do
* Clean up subversion, this means either leaving a single README file instead of the original content of the module, or removing the path completely
* Point EBN to the new place of the module, '''TODO:''' whom to contact (probably ebn-admin)
* Point LXR to the new place of the module, '''TODO:''' whome to contact, eean?
* Adjust the developer information on www.kde.org

Thats it. More information on the permissions and post-hook scripts (for BUG:, CCMAIL: etc) can be found on the [[Development/Tutorials/Git/KdeOnGit|KDE on Git]] page.

← Older revision		Revision as of 08:12, 23 February 2012
Line 16:		Line 16:
	* Adjust the developer information on www.kde.org		* Adjust the developer information on www.kde.org

−	Thats it. More information on the permissions and post-hook scripts (for BUG:, CCMAIL: etc) can be found on the [[Development~~/Tutorials~~/Git~~/KdeOnGit~~\|KDE on Git]] page.	+	Thats it. More information on the permissions and post-hook scripts (for BUG:, CCMAIL: etc) can be found on the [[Development/Git\|KDE on Git]] page.

@@ Line 1: / Line 1: @@
 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.
 * Execute the conversion to create a local git repository

@@ Line 12: / Line 12: @@
 * Scripty needs to be pointed to the new place of the module, you can send the kde-i18n-doc mailinglist a note and it should be taken care of.
 * Clean up subversion, this means either leaving a single README file instead of the original content of the module, or removing the path completely
-* Point EBN to the new place of the module, '''TODO:''' whom to contact (probably ebn-admin)
+* Point EBN to the new place of the module: Contact Allen Winter.
-* Point LXR to the new place of the module, '''TODO:''' whome to contact, eean?
+* Point LXR to the new place of the module: Contact [https://bugs.kde.org/enter_sysadmin_request.cgi KDE's sysadmins].
 * Adjust the developer information on www.kde.org
 Thats it. More information on the permissions and post-hook scripts (for BUG:, CCMAIL: etc) can be found on the [[Development/Tutorials/Git/KdeOnGit|KDE on Git]] page.

@@ Line 10: / Line 10: @@
 * The kde-sysadmins needs to be added too with admin rights, so they can help with tagging and general administration (setting up hooks etc.)
 * Add the new remote repository to your local one as new remote, then push all local branches and tags to the remote repository.
-* Scripty needs to be pointed to the new place of the module, '''TODO:''' how/where/what to do
+* Scripty needs to be pointed to the new place of the module, you can send the kde-i18n-doc mailinglist a note and it should be taken care of.
 * Clean up subversion, this means either leaving a single README file instead of the original content of the module, or removing the path completely
 * Point EBN to the new place of the module, '''TODO:''' whom to contact (probably ebn-admin)