move3d

h1. Instructions for developers

The new main repo for move3d is here now (at least for us). Project admins are in charge of keeping it up to date with the official move3d repos (on trac.laas.fr). We will work with a pull request system, and try to involve everyone in the reviews, to ensure the best possible quality for each part and aspect of move3d.

So, where to start? You will have to setup your workspace to use these repos instead of the trac.laas.fr ones, and use the workflow required for this project management system.

h2. Workspace set-up

h3. Change remote

Short version: in git, a remote is a server.

You will change trac.laas.fr to this repo on your local copy using git commands. So, cd to your move3d(planner/hri/studio) local copy and do the following:

<pre>

git remote set-url origin ssh://git@redmine.laas.fr/laas/users/jwaldart/move3d/[planners, hri, libmove3d, studio].git

</pre>

@origin@ is the default name usually given to remotes, esp. when using @git clone@. Yours is maybe different, use @git remote show@ to check the list of remotes and @git remote show <name>@ to see details.

You may want to add a remote instead of changing origin, use the @git remote add@ command instead:

<pre>

git remote add redmine ssh://git@redmine.laas.fr/laas/users/jwaldart/move3d/...

</pre>

h3. Add remote for pushing

You first need to create your own remote repo, where you will push your changes, and from which project maintainers will pull when you requet it. You then add it to the remotes:

<pre>

git remote add perso <url>

</pre>

You will push to it using @git push perso <branch>@ where @<branch>@ is the branch you want to push *to* (usually master).

You will pull form the main repo: @git pull origin <branch>@

*TODO*: how to set default pull/push destinations.