Activity Team/How to migrate from OLPC

From Sugar Labs
< Activity Team
Revision as of 16:38, 23 February 2009 by Wade (talk | contribs)
Jump to navigation Jump to search

Migrating activities 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 to addons.sugarlabs.org. Be sure to include a couple of screenshots of your activity in action.
  • Leave a message on the OLPC wiki page for the Activity noting the migration. Use the Migrated to sl.o template.
  • 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.