Moving from Subversion to Git

Sometimes it's good to have someone basically forcing you to make time to improve a lingering situation. Subversion was a long time a bottleneck (literally in I/O, and figuratively in collaboration) in RPMforge. I also had been using our public Subversion infrastructure for some unrelated Open Source projects.

So thanks to Yury V. Zaytsev (!) we are finally undertaking the migration to Github infrastructure. This will also mark the beginning of the project's name translation from RPMforge to RepoForge.

Names for subversion repositories

When I have to set up a subversion repository I like to give them special names. Especially when multiple subversion repositories are deployed inside organizations, it make sense to remove any confusion to name them something other than "subversion" or "svn".

I often prefer the name "shelf" for the repository that holds most of the technical information for a sysadmin team. This repository typically would hold directories like: docs/ rpms/ scripts/ tools/ per operating system or technology domain.