ChibiOS Free Embedded RTOS

In my opinion, Option 2 is a must:
a) personally, I am fed up with sourceforge, it ruined my last weekend trying to get a build script working with dependencies on projects hosted there.
b) A read only repo hidden behind ssh keys is not good enough if you want people to find this excellent project and contribute to it. GitHub offers the most visibility of any open source project nowadays.
c) As an earlier comment also said, I to have come through learning SVN, then Hg, and now only remember git commands. The younger generation have only known git.
d) A reliable git mirror is a must and would stop lots of unofficial forks (or at least be able to keep an eye on them)...
e) GitHub has features beyond just source control (which I guess you will not use other then a mirror), there issues system and ability to integrate with third party build systems (travis CI etc) is great and could benefit…

Giovanni wrote:That would be perfect but it does not work for large repositories (read the blog post), would be possible to create a script that does exactly that? I could host it on the same SVN server. Apparently it is just matter of calling the appropriate git commands.

Giovanni

I beg to differ!
We (at nanoFramework) have been using svn2git for a long time now and have setup mirror repos for the last 2 branches and it's all there running smoothily.

Check the mirrors here:
https://github.com/svn2github/ChibiOS-17-6-x
https://github.com/svn2github/ChibiOS-18-2-x

Anyone can fork those.

A git mirror is definitely a must have!

How's the SVN situation settled? Is it stable and not going to change again next week? What's the new URL?

It is stable now: https://svn.code.sf.net/p/chibios/svn2

There is also an automatic off=site mirror now, just in case.

Giovanni

Ok, I will update the github mirror script tonight!

I'm finding that a lot of what are presumably external repositories are coming up as 'not found'. Most, if not all, appear to relate to the SPC5. Is this right?

Here's an extract from the log (there's lots more!):

I need to update those externals or remove the branches entirely, the SPC5 stuff is now handled elsewhere.

Giovanni

Done, https://github.com/ChibiOS/ChibiOS is now mirroring the new SVN repo.

One other thing that would be really nice to have on the git mirror is tags for the released versions.

Right now we just have the release branches, which get continuously updated between official releases in the series.
This makes it difficult to specifically target a 17.6.4 (or any other specific release in the 17.6.x series) without going back searching for the corresponding commit that was tagged in svn.

It looks like on SVN this is being handled by creating a branch under a specific "path" (HEAD/tree/tags).
Is it possible to convert these branches to tags automatically when syncing to the git mirror?
If not, is this something that could be done manually whenever a release is tagged in svn?