Decide the contribution requirements for this and the website repo

[harisood]

Decide things like:

• Who can open issues/PRs
• Who can merge
• What to protect and how
• Add people to repo and have different branches vs forks
• Automatic checks
• How many people need to approve, and who (probably co-chairs)

[Davsarper]

For some reason this was not in board, added

[Davsarper]

@rmbaxter67 I will use this issue to set how different roles and people can/should use the repo and project, if you can share here any struggles with #34 that will help me greatly
(yes I have copy pasted the comment I made in another issue, as that one was a duplicat eof this)

[manics]

Who can open issues/PRs

Anyone can open issues/PRs on a GitHub repo (unless you disable them for everyone).

Add people to repo and have different branches vs forks

I think we should encourage forks over branches in most cases, since it means everyone (members and non-members) are treated equally.

[Davsarper]

when completed add to and update #40

[harisood]

@manics to check permissions for repos and once happy close this issue, as most of this should be captured in contributing files