[Rock-dev] Migration to github

On Fri, Apr 11, 2014 at 4:16 PM, Sylvain Joyeux <bir [dot] sylvain [..] ...> wrote:
> More detailed outline of the general plan (including some rationale for the
> move)
>
> http://rock.opendfki.de/wiki/WikiStart/OngoingWork/GitHubMigration

I'm proposing to leave gitorious as well for the Orocos Toolchain and
related libraries...

It would boil down to changing the installation instructions and
changing the bootstrap links to what exists on github and to reverse
the synchronisation scripts, ie, force-sync from github to gitorious.

Peter

>
> Sylvain
>
>
> On Fri, Apr 11, 2014 at 2:25 PM, Sylvain Joyeux <bir [dot] sylvain [..] ...>
> wrote:
>>
>> We've had a DFKI-private discussion a month or so ago about
>>
>> 1/ migrating to github
>> 2/ enabling commit control (i.e. give commit access to packages only to
>> the package
>> maintainers, and use merge requests / pull requests for everybody
>> else)
>>
>> The outcome was an OK in principle, especially given that it would mean
>> very little changes for non-developers (developers would only have to sign
>> in to github)
>>
>> OK ... Now ... I have some spare time, so ...
>>
>> What about I start with rock-base and rock-toolchain ?
>>
>> Sylvain
>
>
>
> _______________________________________________
> Rock-dev mailing list
> Rock-dev [..] ...
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
>

[Rock-dev] Migration to github

On Wed, Apr 23, 2014 at 3:23 PM, Sylvain Joyeux <bir [dot] sylvain [..] ...> wrote:
> On Wed, Apr 23, 2014 at 3:17 PM, Peter Soetens <peter [..] ...>
> wrote:
>>
>> I'm proposing to leave gitorious as well for the Orocos Toolchain and
>> related libraries...
>
> Yes .. I knew you would be happy about that one ;-)
>
>> It would boil down to changing the installation instructions and
>> changing the bootstrap links to what exists on github and to reverse
>> the synchronisation scripts, ie, force-sync from github to gitorious.
>
> In the Rock case, the plan was to drop gitorious completely. This is
> transparent to both developers and users as autoproj will update the git
> push/pull URLs.

Hmm. you're probably right from the user perspective. I saw an
advantage as a back-up server, github has suffered from hour-long DOS
attacks in the past.

Peter