Set up repository for remote work

[leesharma]

Now that we're out of the hackathon weekend, we should set up the repository for a remote, part-time team. We're not going to be able to talk across the table, so we should make expectations explicit and make communication easy.

The goal is to make it easy to visit the repo and see what's going on/jump in (even for new contributors) without weight down our development process.

To me, this means:

• Add basic meta information (LICENSE, CODE_OF_CONDUCT, tags, description)
• Add README + other developer documentation
• Decide on our git flow/practices (ex. no merging without code review, contributor branches, CI setup, styleguide/linting, CONTRIBUTING, etc.)
• Decide on project management practices (ex. are we using GH projects? What issue tags are we using?)

Anything I'm missing? Anything sound too overbearing/overkill?

[leesharma]

Also, I'm assuming we're using the built-in GitHub tools (issues, milestones, maybe projects) to keep track of things. Are you all on board with that? Anyone have another preference?

I like GH because it's easier for new contributors: everything's in one place–the same place it is for other GH projects.

[leesharma]

Thoughts on the MIT license? aedb4ff

I like it–I think it's in the spirit of open data, but it does mean we don't have any say on the derivatives (someone commercializing it, using it in a way we don't approve of, etc.)

Other licenses can be found here: https://choosealicense.com/