You can clone with
HTTPS or Subversion.
There is a 2-clause BSD licensed library, vcs-svn, embedded in git-core authored largely by myself and Jonathan Nieder, @jrn. It provides an interface to consume a subversion dump stream and drive a sequence of git commits. In git-core, it consumes the bi-directional interface of git fast-import. I have begun working on adapting the stand-alone upstream library that it is based on to drive the libgit2 APIs. If there is interest in baking this functionality into libgit2, I would like to do so. See https://github.com/barrbrain/svn-dump-fast-export/tree/libgit2 for my porting effort thus far.
Do you think it would make sense to create a new BSD license stand-alone project (libvcs-svn) and make Git and maybe LibGit2 consumers of this? (A bit like what vmg did with the Clar test framework in LibGit2) That way it will be nice and clear to any contributors that the libvcs-svn project that they are contributing to is a BSD licensed module and not accidentally think that they were contributing under the GPLv2 of core Git or the GPLv2+Linking Exception of LibGit2? It also means that there is one master upstream location for contributions to go to that core Git and LibGit2 are consumers of and can pull in fixes when it most make sense to those projects.
If you wanted to do this, it would be worth mailing all the people who had committed patches to vcs-svn inside core Git's directory structure and make sure they were happy with that arrangement first.
@martinwoodward, not to worry, what you describe is precisely barrbrain/svn-dump-fast-export. It originated as an independent project and care was taken to ensure the license was well documented. Of all the names that have been bestowed upon it, libvcs-svn seems to have stuck the most. The stub frontend was known as svn-fe, the core logic became git.git:vcs-svn. I do my best to keep the projects synchronised but there is still some lag from when the last Summer of Code project was merged downstream.
I have created libvcs-svn as a new home for the core library. It contains only the core code; no tests, compatibility library, or front-end.
Not much going on with this - let's close for now and reopen if anyone decides to pursue this in the future. Thanks David!