Adopt a Code of Conduct for community health files

[stevepiercy]

References:

• Choosing a Code of Conduct #852
• https://github.com/collective/icalendar/community
• https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project

Todos:

• Use https://www.contributor-covenant.org/
• Determine who would receive, investigate, and respond to reports
• Add public contact method that uses GitHub comments
• Add private and secure contact method (TBD)

I have no interest in drafting this, but I support copy-pasting something that works for us, starting with whatever is already established by https://github.com/collective/.github/community (there is none).

[SashankBhamidi]

This should cross-off the checklist

[niccokunzmann]

See also: #852

[stevepiercy]

@niccokunzmann thanks for the reminder.

I added a checklist and edited the description.

The hard part is determining who will handle private reports. By default, it would be active maintainers, I guess. I could ask the Plone Foundation for either an email account with delegates or a Google Group, both of which would be icalendar@plone.org, to handle requests.

[niccokunzmann]

If CoC violations happen by a maintainer, it is good to have a third party mediate. Having an email address is nice! If you do that, we need to document that

• in the CoC
• in the maintenance section for a clear onboarding process for maintainers