The preliminary plan:

• Wait until the github exporter works again and give it a try

• From a manual hg to git conversion the following issues need to be considered:

  • The git repo is 100 MB vs hg 35 MB. Figure out why?
  • Try to convert the "issue 42" in commit messages to "issue #42" or something github recognizes.
  • tags didn't get transfered, reapply them if needed
  • while we are at it maybe change the naming of release tags from quodlibet-X.Y.Z to something like release-X.Y.Z so there is no confusion with branches. (branches get used on readthedocs, so changing them would break links in older QL releases)
  • Delete merged branches?

github org: https://github.com/quod-libet git repo test: https://github.com/quod-libet/test

The google exporter will only work with projects having < 1000 bug reports, so we have to do it manually.

Also, a note for people, like myself, with hg queues: probably best to export them as patches locally, and import them as new local branches on a new fork of the soon-to-be official repo (or could figure out git stash with Github, but doesn't seem worth it).

Small update:

• git gc --aggressive solved the size issue, now at 20MB
• it also supports exporting tags, so also solved
• if we at the end create a fresh github repo and import issues, issue numbers should match up (nick: you might want to unfollow that, since the import might generate tons of emails?)

For fixing references to issues/revisions the following things could be handled:

1) References to other revisions in commit messages. 2) References to issues in commit messages 3) References to other issues in issues 4) References to revisions in issues

2-4 are fixable with a bit of python. 1 not with the current export script as the export is split in two stages and only after the second stage git hashes are available; might be a nice challenge :)

Because Google Code is going away [0] we've moved this bug tracker to GitHub.

This issue is now available at

https://github.com/quod-libet/quodlibet/issues/1557

In case you are still interested in this issue and have a GitHub account, you can subscribe to the new issue using the "Subscribe" button on the right hand side of the page.

[0] http://google-opensource.blogspot.co.at/2015/03/farewell-to-google-code.html