Awesome!
I'm determined to beat Flow to Github! 
I have setup a Spark repo on Github under my account, and used svn2git to convert the SVN repo into a Git repo (preserving revisions, commit messages, etc).
The repo is currently at: https://github.com/SnakeDoc/Spark
I am unable to transfer it to the igniterealtime organization until I am added. My account is: SnakeDoc
Once the repo is moved to under the igniterealtime organization, I will setup a cron on one of our servers over here to sync the SVN and Git repo's together, using the SVN as the master for now. I'll set it to run at GMT midnight since we have a pretty international community, hopefully that is convinient for everyone.
I figure we will have some transition period where we are still using both repos. Having the Git repo sync from the SVN repo for at least a few months may be good for this reason. This should give some time for people to transition to the new Git repo at their own pace.
~~~~~~~~~~
Git repo structures are usually slightly different than the normal SVN repo... such as we will probably want to move or copy the README and LICENSE docs out of the documentation directory and instead have them sit in the root directory. I'll convert the HTML docs to Markdown docs for the root directory, this way Github displays some nice info when you land on the repo's page.