Migration to Git/Github

Wonderful, thanks! Don't hesitate to ping me if you have any other questions on our experiences in the scientific python community. 

I'm very strongly committed to open source in support of open science/education, but I also think it's important to know pick which battles to spend limited resources on, and to be strategic about it. If we want to change the world towards more open science/education, using a closed service like github (that actively supports the efforts of the open source/science community) is a perfectly rational choice as far as I'm concerned, in as much as:

* it makes us more effective in our actual goals towards more open science/education

* it's *possible* to switch away from it in the future, were there a need to be so for some reason.  In the case of GH, that switch might not be the easiest (migrating bug history would take some work), but it's not impossible either.

Given the two considerations above, I would rather be effective *today* on GH, than kneecap myself in today's battles out of a hypothetical concern of possible problems with GH at some unspecified future. If those problems with GH ever materialize, we'll deal with them then and there. But in the meantime, we have real work to do, and doing it on GH is the most fluid and effective way to achieve our actual goals. And who knows, those problems might never actually materialize, so why pay the price of dealing with them up front for no good reason?