update README

CONTRIBUTING.md

@@ -40,8 +40,10 @@ Make sure you do the following before making a PR:
 * Makesure your fork is up to date, it can be tricky trying to make a PR, and then rebase it to master. It's easier to do before you PR.
 * If you made a visual change, provide screenshots in the PR description.
 * If your PR contains anything you think might be hard to grok, explain it with diff comments in github. (After you submit your PR)
+* Keep PRs single purpose focused. Make multiple PRs if you have multiple purposes.
 
 ## Code Conventions
+The linter should pick up most of these:
 * No semicolons
 * Commas dangle `,`
 * 2 spaces for indentation (no tabs)

README.md

@@ -131,6 +131,13 @@ exports.index = "src/index.html"
 exports.live = true
 ```
 
+## Issues
+In the spirit of making enclave more accessible to developers who are new to open source, we decided that we would turn off the issue feature on GitHub. In place of issues, we are inviting anyone with a bug / feature idea / api change or whatever else to create a pull request that exposes the bug or shows how you might add a feature.
+
+Honestly, we'd rather see a poorly written PR than an issue. Take a shot in the dark if you must! Features, bugs and api changes are easier to discuss around a pull request than an issue.
+
+Ridding ourselves of issues also tightens our community. No more side-line issue makers and small team of PR doers. For more information about making a PR see the [contributing](./CONTRIBUTING.md) guide.
+
 ## Contributing
 
 [See the Contributing Guide](./CONTRIBUTING.md)