Initial 'ground rules' document

[mburns]

(since the rules repo is currently empty, it's tricky to make a PR against it. At a minimum, an empty document placeholder would be useful, so that we could iterate on it through Pull Requests)

We should have a document (presumably, README.md) that lays out the basic rules (and links to more detailed markdown documents, when needed) of how RedGuide maintains cookbooks.

This document should probably cover:

• how to add cookbooks to the RedGuide org / request inclusion

  • maintainer or licensing (?) minimum requirements to deal with Bus Factor issues

• preferred way to handle PRs and merging to master.

  "With great power comes great responsibility" - Uncle Ben

  • Don't push into master (unless trivial and very simple hotfix)
  • Use develop branch wherever it exists
  • Ask for 1~2 👍 before merge
  • Use the force & appeal to common sense

• optional how to propose new rules

• optional minimum expectations of cookbooks (CI, style, versioning, minimal supported platforms) or opinionated defaults.

[mburns]

related: redguide/redguide.github.io#2