Activity Team/Git Migration: Difference between revisions

Line 2:

* ''Get'' 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).

* ''Log'' in and [http://git.sugarlabs.org/projects/new 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

* ''Clone'' your git module from dev.laptop.org, e.g.

git-clone git://dev.laptop.org/projects/pippy-activity

* ''See'' all the remote branches with:

git remote show origin

Line 13:

Line 14:

* ''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'' sugar-devel about the move.

* ''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 page, for example for [http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline sugar-jhbuild]. And here is an example:

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

@@ Line 2: / Line 2: @@
 * ''Get'' 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).
+* ''Log'' in and [http://git.sugarlabs.org/projects/new 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
+* ''Clone'' your git module from dev.laptop.org, e.g.
+ git-clone git://dev.laptop.org/projects/pippy-activity
 * ''See'' all the remote branches with:
   git remote show origin
@@ Line 13: / Line 14: @@
 * ''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'' sugar-devel about the move.
+* ''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 page, for example for [http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline sugar-jhbuild]. And here is an example:
+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