Activity Team/How to migrate from OLPC

Migrating activities from dev.laptop.org

• If you are not the author of the activity, query the author to let them know about the move.
• Create an account on http://git.sugarlabs.org and log in. Add your public SSH key to your account.
• Create a new project (http://git.sugarlabs.org, projects, new). Make your project name lowercase, e.g. pippy, turtleart, paint. Put it in category "activities".
• Clone your activity from dev.laptop.org.

git clone git://dev.laptop.org/projects/pippy-activity

• If you want to migrate a non-master branch...

git remote show origin
git checkout -b sucrose-0.82 origin/sucrose-0.82

• Push to git.sugarlabs.org with something like:

git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror

• To be able to push your changes to the new repository in the future you'll need to do a git clone on the new location into an empty directory, then change the remote origin url in .git/config within the mainline directory in that new directory to the new URL you used with your previous push:

[remote "origin"]
      url = gitorious@git.sugarlabs.org:sugar/mainline.git
      fetch = +refs/heads/*:refs/remotes/origin/*

• If you're getting a message saying fatal: The remote end hung up unexpectedly that probably means that this URL is incorrect.

• Add the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to Sayamindu to point pootle to new remote.
• Upload xo bundles and .tar.bz2 files to download.sugarlabs.org. If you don't already have one, you will need to request a shell account from the InfrastructureTeam. This is temporary. In the future, addons.sugarlabs.org will fill this role. You may also choose to leave the downloads on the laptop.org infrastructure until the new site is in place.
• Notify sugar-devel and OLPC devel about the move.
• Change sugar-jhbuild to point to the new repository if this activity was included in sugar-jhbuild (enter a ticket in http://dev.sugarlabs.org if you have no access)
• Ask an ActivityTeam Coordinator to create a Trac component for your activity.
• Transfer or resolve existing tickets related to the code in the OLPC Trac.
• Update pages on wiki.laptop.org that contain stale links to the OLPC repo and latest bundle. (e.g. Activities/All , the OBX box on the activity homepage, etc.) See olpc:Maintaining activity web information#Migrating activities to SugarLabs
• Tag the activity at ActivityTeam/ActivityStatus as migrated.