Hi guys,

We had some previous discussions about version control systems and the main
conclusion was that you shouldn't tell others what to use on one hand, but
still make the whole revision history available to everybody on the other
hand. We (all) agreed that svn is a univeral, portable, interoperable
medium...

The easiest way to follow this path is this:

The SVN trunk/rtt, ocl,... branches remain the primary source for making
releases (and debian packages) and offering easy revision-history access to
everybody on every platform.

I'll switch to git using a combo of git-svn and plain git repositories on
www.github.com . My username is 'psoetens'
(warning: branches not
stable yet, see below)

Any developer who wishes to contribute can send normal patches on the
orocos-dev ML (against svn trunk or git HEAD) or notify me using a git pull
request. I'll first integrate the patches in my git repository and will then
push them to the svn server. If someone else commits on the svn server, I can
still pull them in as well.

** Technical git details: **

I cloned Sylvain's git repository on github, but I'm currently unable to take
over his origin/rtt (which is Orocos trunk/rtt) with git-svn. So we'll
probably have to look for another layout. Also, Sylvain's repository only
contains RTT, I'm unsure if we should setup a different repository for OCL (I
guess we should)?

Another project did someting similar, see this page:

I'm sure we get this resolved, but for now don't clone/fork my repository as
it will likely change or be replaced.

Peter