Difference between revisions of "Activity Team/Git Migration"

Revision as of 23:58, 28 December 2010

Team Home · Join · Contacts · Resources · FAQ · Roadmap · To Do · Meetings

How to migrate activity source control from laptop.org to sugarlabs.org.

Create an account on http://git.sugarlabs.org
Log in and create a new project from the projects page (please use only lower case, e.g. sugar, turtleart, sugar-toolkit).
Clone your git module from dev.laptop.org, e.g.

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:pippy-activity/mainline.git

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.
Notify sugar-devel about the move.
Make sure that sugar-jhbuild points to the new repository (ask someone to do it for you if you have no access)

@@ Line 1: / Line 1: @@
 <noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}{{TOCright}}</noinclude>
+How to migrate activity source control from laptop.org to sugarlabs.org.
 == Import a module from dev.laptop.org ==
@@ Line 17: / Line 20: @@
 * '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] about the move.
 * '''Make sure''' that sugar-jhbuild points to the new repository (ask someone to do it for you if you have no access)
-== Clone a module from git.sugarlabs.org ==
-Instructions on how to clone a project from the git repositories of sugarlabs.org can be found at the project's repos/mainline page, for example for [http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline sugar-jhbuild]. And here is an example:
- git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
 == See also ==