Define contributor and team permissions

[samus-aran]

This isn't a high priority but just to help with establishing the teams (which I believe still need to be decided) and thus their access/permissions on the repo.

• create teams on theopensourceway with appropriate permissions
  -- Setting permissions allows new members to correctly assign themselves to issues to thus take ownership
  -- allows members to mention teams instead of individual members to lighten individuals' workload
• establish distinction of team member or collaborators (not really a difference but some may prefer not to be associated with another organisation in order to contribute/take ownership of tasks).

Just to get over the quick win would be setting up a team as perhaps "authors" that have either write or triage permission (and thus can assign themselves issues). I suggest at the moment triage rather than write as the editorial reviewing process hasn't been defined yet.

A few articles on the setup of the repo's access/permissions for repos.

https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization

https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization#setting-base-permissions

[quaid]

OK, this has moved to be a higher priority as folks are actively working in the repo. I'm going to take assignment to figure this out in the next few days, or I'll yell for help.