Difference between revisions of "Projects/MoveToGit/StepsToMove"

Jump to: navigation, search
m (Fix link.)
 
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.

Latest revision as of 09:12, 23 February 2012

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
  • 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, 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: Contact Allen Winter.
  • Point LXR to the new place of the module: Contact 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 KDE on Git page.


This page was last modified on 23 February 2012, at 09:12. This page has been accessed 3,348 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal