Where do we store the CKAN repo?

[pjf]

Right now we've got sample files in the meta directory of this repo, but going forward that's probably not ideal. These files are likely to be updated often, either by mod authors or automated tools, and by having them here we clutter the commit log of changes to the code and design with changes to the data that we use.

I'm going to suggest we create a github organisation (KSP-CKAN, since CKAN is already taken), migrate this repo to there, and have another repo which is just for the meta files. This means:

• The CKAN client can dowload a single zip to get all the metainfo it needs. This is is fast, and easy, especially because we already have code that downloads and processes zipfiles.
• We can more easily implement code reviews before merge, especially of my own code, by sending pull requests to the repo. (HT to @eggrobin for the suggestion.)
• Teams are better than people. I actually want to be playing KSP, and having a org makes it easier for me to hand everything to another person when I get to do so. :)

[pjf]

@Wizarth @rafl @johndalton @techman83: Just a heads-up that I've moved the CKAN to an org. You may need to tweak the upstreams in your git configs for checked out files. Otherwise everything should work much the same. :)

[pjf]

I've now created https://github.com/KSP-CKAN/CKAN-meta , and have moved all the .ckan files across to it. There's a pending pull request that will have travis validate them all every update, which will be awesome.

While we may end up having the CKAN repo somewhere else in the future, this is an easy spot for it to exist for now, especially since we can download the whole thing as a single zip.

Marking this closed, unless there's any objections to the current approach.