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

From Sugar Labs
Jump to navigation Jump to search
(Divide into sections, clarify some steps, improve primary verb highlighting.)
Line 1: Line 1:
−
== Migrating activities from dev.laptop.org ==
+
== Migrate the code ==
−
 
 
 
* If you are not the author of the activity, '''query''' the author to let them know about the move.
 
* 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 [http://git.sugarlabs.org/account your account].
 
* '''Create''' an account on http://git.sugarlabs.org and '''log in'''. Add your public SSH key to [http://git.sugarlabs.org/account your account].
−
* '''[http://git.sugarlabs.org/projects/new 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"'''.
+
* '''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 [http://dev.laptop.org/git dev.laptop.org].
 
* '''Clone''' your activity from [http://dev.laptop.org/git dev.laptop.org].
 
  git clone git://dev.laptop.org/projects/pippy-activity
 
  git clone git://dev.laptop.org/projects/pippy-activity
Line 10: Line 9:
 
  git checkout -b sucrose-0.82 origin/sucrose-0.82
 
  git checkout -b sucrose-0.82 origin/sucrose-0.82
 
* '''Push''' to git.sugarlabs.org with something like:
 
* '''Push''' to git.sugarlabs.org with something like:
−
 
 
  git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror
 
  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.
  
−
* 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:
+
== Set up SugarLabs services ==
−
 
+
* '''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.
−
  [remote "origin"]
+
* '''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.
−
      url = gitorious@git.sugarlabs.org:sugar/mainline.git
+
* 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.
−
      fetch = +refs/heads/*:refs/remotes/origin/*
+
* '''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).
−
* If you're getting a message saying '''fatal: The remote end hung up unexpectedly''' that probably means that this URL is incorrect.
+
* Ask an [[ActivityTeam/Contacts|ActivityTeam Coordinator]] to create a '''Trac component''' for your activity.
  
−
* '''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.
+
== Notify the community ==
−
* '''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 [http://wiki.laptop.org/go/Template:Migrated_to_sl.o Migrated to sl.o] template.
 
 
* '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] and [http://lists.laptop.org/listinfo/devel OLPC devel] about the move.
 
* '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] and [http://lists.laptop.org/listinfo/devel 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/Contacts|ActivityTeam Coordinator]] to create a '''Trac component''' for your activity.
 
 
* Transfer or resolve '''existing tickets''' related to the code in the [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=acoustic-measure-activity&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=milestone OLPC Trac].   
 
* Transfer or resolve '''existing tickets''' related to the code in the [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=acoustic-measure-activity&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=milestone 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]]
 
* 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]]

Revision as of 17:02, 23 February 2009

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

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Activity_Team/How_to_migrate_from_OLPC&oldid=20011"