Review the GitHub Community settings.

[edthedev]

Tasks:

• Under 'Insights' -> 'Community' in the GitHub menu, review the community best practices, and complete any we can.

See the Community tab on SecOps-PowerShell-CISDSC for an example completed within our team.

Tasks:

• [x] Ensure README.md exists.
• [ ] Add a Code of Conduct .md file - I suspect that this one will work for us without any changes, as our security inbox is already in the contact fields.
• [ ] Add a contribution guide. This one had to be heavily customized for the project, but we might be able to start with a cut-down simplified version of it.
• [x] Include a LICENCE file.
• [ ] set up an issue template (the defaults are probably fine)
• [ ] set up a pull request template (the defaults are probably fine)
• [ ] check the box to say we will accept content reports (this means that if someone reports our repository to GitHub, our team admins will be copied on the notification).

[edthedev]

Also there's an interesting resource here (which GitHub also links to). https://opensource.guide/