Migrate wiki repository from Google Code to another service

[GoogleCodeExporter]

Need to investigate if GitHub suits our needs for hosting the BRATA project.

With Google's announcement about shutting down Google Code, we need to 
investigate migrating the following to other services:

 - Each repository
 - The wiki, which is just another repository (This issue)
 - The issues database
 - List of users

Is there anything else that needs to be migrated?

According to Google, all existing projects will remain functional through July, 
2015, before the project data become read-only. Early next year, the site will 
shut down but project data will be available for download in an archive format.

Google suggests that the Google Code Exporter tool will be the simplest option 
to export projects directly to GitHub, and they have documentation on how to 
migrate to GitHub, Bitbucket, and SourceForge manually.

Original issue reported on code.google.com by @jawaad-ahmad on 14 Mar 2015 at 7:28

[jawaad-ahmad]

The export/import placed the wiki pages on a new wiki branch of the brata repository. There were a couple more steps needed using a third-party tool referenced on the Google pages to export the Google Code wiki pages to Markdown files for the GitHub wiki.

I remember needing to run the command to run the third-party tool, which cloned both the brata repo and the brata.wiki repo, made changes, and finished. Studying the output, I saw an error message I think with a sed command that made me think something went wrong, but it turns out everything was fine.

During the conversion between the page formats, I think sed was trying to do a substitution and there were no occurrences of the text on a couple of the pages, so the error message was misleading.

The wiki is now in the brata.wiki repository again, so there is no more need for the wiki branch in the brata repository and can go away at some point.

I think this issue can stay in-work till we decide what to do with the wiki branch. Either we leave as-is forever as suggested in another issue, or we could delete all pages and then merge the wiki branch to master, and then delete the wiki branch. This is effectively a no-op for the branch, but going through the history we'd be able to get back to the files if ever needed.

For those unfamiliar with Git, I learned yesterday that deleting a merged branch is not a destructive operation; it is recommended practice to essentially close-out the branch and stop further changes from occurring on the branch. In the ClearCase world, this would be similar to obsoleting the branch type.

[jawaad-ahmad]

I had some scripts in a subfolder of the Google Code wiki repository. I don't think they got copied over to GitHub. Need to go back and get them. One of them was used to take the master GUB and split it into individual documents.

[jawaad-ahmad]

If we haven't used them, we can live without them. Nothing more to do here.