Generalise & emphasise (consistent) Code of Conduct on website

[sadielbartholomew]

We have a 'Contributor Code of Conduct' document which was added to back in mid-2020 to the cf-conventions repository, possibly because it is quite standard to have such a file at that point and indeed GitHub now provides templates and auto-referencing to such a document, where present in a certain form.

But such a file is only attached to that one repository, and applicable to contributors, but really we would like to make it more general, namely to apply to all relevant repositories (notably discuss and this repo also) and for example to also apply to:

• CF-related events especially Workshops and Training events, both for participants that are online and in-person;
• discussions e.g. simply commenting in these repositories, which is absolutely a contribution form but for which the code of conduct is not highlighted by GitHub (unlike for someone opening a first-time Issue where they get prompted to consult such a file).

In particular, we should mention it prominently on the CF website both to highlight the rules encapsulated themselves and to emphasise they apply to the larger scope covered above.

---

As suggested by @japamment at the 2022 CF Workshop hackathon session today, as paraphrased (with some details fleshed out from a brain dump of my own thoughts) by myself. @erget gave an important point: that a motivation for such a document / set of rules is not just to enforce them, but to indicate to all and potential future contributors that we are welcoming and inclusive as a community.

[sadielbartholomew]

I've just realised that CONTRIBUTING.md documents can be somewhat similar in nature to Code of Conduct type documents, so we should also check that we reference the latter in the former consistently across all the repositories including this one where people might contribute directly or indirectly to CF.

[ethanrd]

Hi @sadielbartholomew - GitHub supports defining default community health files. We could set that up for CF and the same files would apply to all CF repos unless we override them in a particular repo. Along with CONTRIBUTING.md and CODE_OF_CONDUCT.md, this can also include SUPPORT.md, issue and PR templates, and a few other files.

[sadielbartholomew]

We could set that up for CF and the same files would apply to all CF repos unless we override them in a particular repo. Along with CONTRIBUTING.md and CODE_OF_CONDUCT.md, this can also include SUPPORT.md, issue and PR templates, and a few other files.

Thanks @ethanrd, that's a great idea to keep all of the files consistent in this respect! I remember creating a .github repository in this way for another project, ES-DOC, which demonstrates it working in practice. Maybe, if nobody disagrees, we can create a new Issue to document this related but larger task of consolidating all of the health files into one dedicated repo, to keep them consistent and help with maintainability?