GitHub: migrate away from Subversion repository

[sl4mmy]

Migrate away from Subversion repository. Remove temporary
.idea/.gitkeep file. This file was only necessary when manually
importing the last few commits from Subversion. Update IntelliJ
configuration to recognize local working copy as Git instead of
Subversion. Add initial .gitignore to keep build droppings out
of the Git repository. Fix the SVN source control test to no longer
rely on the fact that CruiseControl itself uses Subversion.

Signed-off-by: Kent R. Spillner kspillner@acm.org

[sl4mmy]

After this gets merged we should consider ways of disabling the existing Subversion repository at SourceForge. Here are a few possibilities, in no particular order, that I thought of (I'm not sure they're all actually doable):

• Disable the Subversion repository entirely from the SourceForge project page
• Make the Subversion repository read-only
• Tag & branch the current trunk in order to preserve history, then delete everything under trunk and replace with a README that points people to the code on GitHub
• Don't bother preserving history since it's already in the Git history, just delete everything and replace with a README that points people to the code on GitHub
• Do nothing with the Subversion repository, just make an announcement on the users and devel mailing lists

[sl4mmy]

Regardless of how we choose to disable the Subversion repository, there are a few additional things we should do:

• Update the "source repository" link on the website to point at GitHub
• Comb through the documentation looking for others links to the Subversion repository and replace them with links to GitHub

[sl4mmy]

And a few optional things we might consider doing as well:

• Migrate the website to GitHub pages
• Close, or migrate, remaining issues in JIRA to GitHub issues
• Refactor the repository and promote some directories (e.g. contrib/) to separate repositories under the CruiseControl organization on GitHub

[hackmann]

• Tag & branch the current trunk in order to preserve history, then delete everything under trunk and replace with a README that points people to the code on GitHub

I like this option, there are probably a lot of references to our subversion repository on external sites that we cannot change.

• Make the Subversion repository read-only
• Do nothing with the Subversion repository, just make an announcement on the users and devel mailing lists

I don't like these as it's possible for someone to find the old subversion repository without reading the notice that we are using github now.