You're right, though: GitHub is horrible for large blobs of data like this. At the time I didn't know how big the data releases would end up being.
Tom and I have plans to talk more about future data releases and how they might be made with a more appropriate tool.
The best tool would offer
* Transparancy (who, specifically, is behind it)
* Time stamping
* Linkability, with über-stable URIs
* Public issue tracking.
* Documentation, including the possible crowd-sourcing thereof.
Edit: In this case we have identifiable and passionate individuals behind the initiative. This is far from faceless and cursory, as most data-dumps are. What's not to love here?
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.
When I was searching for suggestions I didn't see any way for people to submit changes to the released data back to the organization releasing the data. Getting community feedback is what they cared about the most so I suggested GitHub.