Activity Team/How to migrate from OLPC

< Activity Team
Revision as of 16:02, 23 February 2009 by Wade (talk | contribs) (Divide into sections, clarify some steps, improve primary verb highlighting.)

Migrate the code

  • 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
  • Clone the project from the new repository in order to be able to push your changes. You'll need to do a git clone into an empty directory, using the same URL you used with your previous push:
git clone gitorious@git.sugarlabs.org:sugar/mainline.git sugar

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

Set up SugarLabs services

  • 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 a xo bundle to addons.sugarlabs.org. Be sure to include a couple of screenshots of your activity in action.
  • If your activity is part of Fructose, upload a .tar.bz2 to downloads.sugarlabs.org. Request a shell account from the InfrastructureTeam if you don't have one already.
  • Update the OLPC wiki page for the Activity, noting the migration. Use the Migrated to sl.o template.
  • 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.

Notify the community