PR code review guidelines

[rborn]

We should mention in the guidelines that anyone can review the PRs (to free some load from the maintainers) but int he same time the release and merge procedures are restricted so we can keep the builds in a working state.

[kelset]

@orta posted an RFC to add Peril to the org here, maybe it's something that we can use to enforce said rules? (once we define them?)

[rborn]

@kelset @orta didn't know about peril, I'll have a deeper look but it looks good at a first glance 🤗

[orta]

I think most of the these discussion issues could be verified with a daily task in Peril

[kelset]

For context, here's Peril's repo https://github.com/danger/peril#i-want-to-use-peril

Btw @orta in that section it says that basically we'd need to self-host. Any suggestions on that?

Should we follow this? https://github.com/danger/peril/blob/master/docs/setup_for_org.md

[orta]

Nah, don't self-host - run on Peril staging. I can hook that up 👍

[orta]

@kelset can you make a repo called peril-settings for this org? Then I can do the rest I think