[ckan-dev] git move

[David Read]

Despite a pretty successful move of the main CKAN repo to Github, in
recent months we've all had to suffer several haphazard moves of CKAN
extensions:
* a new person does it every time, wasting time them learning how to
do the transition
* no-one gets told it has happened
* the old repo doesn't get marked as deprecated
* relevant documentation and wiki links don't get updated
* the buildbot breaks, requiring login to fix it every time

Can I suggest that no-one moves any more CKAN repos until it can be
done efficiently and with prior agreement?

David Raznick spent many hours getting the script right for the
history to be retained correctly. David, perhaps can we schedule a day
when you can migrate the repos, and some of the rest of us work
through a ticket to ensure this checklist of things get done in one
batch?

David