Difference between revisions of "Activity Team/How to migrate from OLPC"

Revision as of 17:29, 27 February 2009

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

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

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.

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 download.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 sugar-devel and OLPC devel about the move.
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.

@@ Line 17: / Line 17: @@
 * '''Add''' the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to [[User:SayaminduDasgupta|Sayamindu]] to point pootle to new remote.
 * '''Upload a xo bundle''' to [http://addons.sugarlabs.org/ 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 [http://downloads.sugarlabs.org/ downloads.sugarlabs.org].  Request a shell account from the [[InfrastructureTeam]] if you don't have one already.
+* If your activity is part of Fructose, '''upload a .tar.bz2''' to [http://download.sugarlabs.org/ download.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 [http://wiki.laptop.org/go/Template:Migrated_to_sl.o 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).