PROCESS CHANGE: 🚨 Code of Conduct reporting mechanism for Knative is obsolete

[Ali Ok]

If somebody wants to report a code of conduct issue to Knative, they need to report it to [e-mail].

https://github.com/knative/community/blob/main/CODE-OF-CONDUCT.md:

Violations of the Code of Conduct should be reported to [e-mail]. This email address is monitored by the Knative Steering Committee. The identity of individuals who report violations of the Code of Conduct will remain confidential.

However, noone in that email alias is active in the project: https://github.com/knative/community/blob/main/groups/committee-code-of-conduct/groups.yaml

Alternatives:

1. Say that CoC issues should be reported directly to CNCF (as in the example project template: https://github.com/cncf/project-template/blob/main/CODE_OF_CONDUCT.md)
2. Change members of this committee with SC members. Steering Charter states that SC "Receive and handle reports about code of conduct violations and maintain confidentiality.".
3. Say "report to [e-mail]" instead of the other alias.

The problem with alternative (1) is that the Knative SC will not know if a CoC issue happened in Knative if the reporting is done to CNCF directly. So, the SC cannot be aware and be cautious against the bad behavior.

[Ali Ok]

cc @knative/steering-committee

[Evan Anderson]

I'm willing to perform either (1) or (2). I'm comfortable with CNCF adjudicating CoC violations, but I'm also willing to be responsible for our own community.

[Dave Protasowski]

When we update the code of conduct text can you only do it in the .github repository of each org.

I plan on deleting the extra md files from each individual repo since it's not necessary to have them with GitHub

[Norris]

I would +1 for Option (3), as I think we should be in the loop / aware of CoC violations.

[Naina Singh]

Can we do it simultaneously somehow? reported to steering AND CNCF?

[Norris]

/lgtm