Status of the project

[spotlesscoder]

I assume this project is not actively maintained anymore as some forks are quite a bit ahead of this repo and there are 32 open PRs.

Would be nice if we could get some life into this project again.

[FranklinYu]

I would highly appreciate if the user can accept some collaborators to review PRs. At least this way we can move forward!

Or just transfer the gem to any active fork.

[astier]

I would also like to know the current status. Would be nice if @nirvdrum could give a quick response.

[th0ger]

Hey @nirvdrum, I understand this is build for free with your costly time, and thanks for that. In all respect, could take a decision on whether you want to continue this project or pass the torch to another (co-)maintainer.

[nirvdrum]

I'm sorry for the delayed response.

There are a few reasons for the current state of the project. For the most part, I find it to be feature-complete and development has been limited by what git-svn can provide. I'll admit I haven't kept up with git-svn, but mostly because it hadn't been touched for years with no real indication of continued development. If that's changed, I'm happy to re-evaluate.

I've been approached by others about co-maintaining the project, but there hasn't been a good fit. Most of the PRs I receive address one person's pet feature and don't seem all that generally useful. Likewise, I put a lot of effort into ensuring wide compatibility for svn2git, including supporting every active Ubuntu LTS release (going back five years). Many PRs I've received break that compatibility guarantee and historically only end up working well on macOS, since compiling the latest from source (via Homebrew) is a common installation mechanism there. (That's shifted a bit because it's easy to update git on Windows these days. But, Linux distros for the most part are going to use whatever was current at the time of release.) Moreover, most PRs I review haven't been tested on any other platform than the author's primary one, so all of that testing gets delegated to me. Finally, svn2git is the sort of project that people contribute to to solve their immediate migration problem and then frequently move on. I'm not terribly interested in having a co-maintainer that's going to leave in a few months.

I should get better about closing out issues and PRs. I did get burnt out on it as the vast majority of submissions either didn't work on all target platforms or were wish list items that svn2git couldn't deliver due to limitations in git-svn. I suppose with GitHub Actions and Docker images for multiple distros and multiple versions, an adequate testing system could ensure compatibility across the board.

If all of that sounds like something you're interested in working on, I'm happy to chat with you more about co-maintaining. It usually ends up discouraging people, I'm afraid.

[spotlesscoder]

Thanks for the info :)
Unfortunately I don't have to co-maintain the project

[Rikj000]

@nirvdrum I've created a new Rikj000/Ruby-SVN2Git-Docker repository,
which adds support to use Nirvdrum/SVN2Git under docker! 🎉

It installs old Git (v1.8.3.1) from source, to ensure successful branch + tag conversion.
And also applies patches from the open PRs to resolve bugs (e.g. with latest Ruby).

Users can use this docker container until maintenance of this project gets picked up again.

Also feel free to utilize my work for an official docker container! 🙂