[CoC] Template for a warning following violation of the Code of Conduct

[plehegar]

It would be helpful to have a template or example for what a warning looks like in case of a violation of our Code of Conduct.

[plehegar]

Some additional considerations.

The warning has to be properly documented.

The warning must

1. indicate that this is a warning, per the guidelines
2. identify which expected behavior is not being followed, or which unexpected behavior occurred, per our code of conduct
3. encourage the individual to follow 5. If You've Done Something Improper.

[plehegar]

@TzviyaSiegman , is this something you would be willing to help drafting?

[csarven]

If there's an off chance that the Solid CoC enforcement guidelines may be of use, including its warning/strike system, please feel free to take whatever you find helpful.

[plehegar]

See also #187

[amyvdh]

We discussed this a bit in the PWE call and I wondered if we want to start the escalation scale a bit more gently (and cut off some of the thinking around the Code being used as a "weapon" with terms like "warning"). Perhaps we start with a "reminder" message and then maybe later, if needed, move to a "warning" or even a "caution".

Perhaps we could frame it like the first stage is: "Reminder: everyone must agree to W3C's Code of Conduct in order to participate in the W3C community. We have all agreed to behave in a respectful manner and when conflicts arise, to resolve them maintaining courtesy, respect, and dignity. Everyone adhering to the same high level of standards of personal behavior is what enables us to do the important work we came here to do. Thank you." (expected behavior). Then, hopefully, the reminder works and behavior goes back to what we want! (clouds part, rainbows, etc).

Then, if someone then refuses to behave respectfully, the behavior then escalates, etc, then maybe we send a "warning" - or perhaps even a more neutral term like "caution". Possibly something like: "Caution: a reminder was previously sent about the W3C Code of Conduct but the recent level of discourse in this thread (or on this list) is not in line with welcome, respectful or courteous behavior. For the cohesion of this group and the continuation of our work, this conflict can be moved to mediation by W3C Ombuds but related arguments should cease (on this list). Thank you." https://www.w3.org/policies/code-of-conduct/#immediately

I'm certainly open to other suggestions for how this might be taken by groups, better ways it might work or the different stages of escalation but it seems like maybe it goes: 1. a reminder that we operate under a code which includes behaving respectfully 2. caution that this disagreement is no longer welcome on the list (or in a meeting) and should end 3. mention a bump to mediation.

[TzviyaSiegman]

Recommendation from https://www.w3.org/2024/12/10-pwe-minutes.html

Chairs may gently remind about minor Code of Conduct violations, such as inadvertent microagressions in public (meeting, email list) using language such as, "As a reminder, Person's pronoun's are they/them." This shows support for the microagressed person and demonstrates what will and won't be tolerated without pointing a finger at an individual. All other discussions of code of conduct violation should be in private unless there is an emergency situation (such as active assault in person).

If a chair must remind/caution/warn a participant about the code of conduct:

• mention that we have a mutual agreement to operate under the Code of Conduct,
• point to the specific part of the Code that has been violated
• point to the section of the Code of Conduct that discusses what to do if you've done something improper
• Ask what support is needed to engage appropriately.

Note that the section on Safety versus comfort includes info about prioritizing a Code of Conduct complaint over a response to complaint

PWE is developing a shared understanding of accountability at W3C, an interim escalation path so that there is better documentation about when it is appropriate for chairs and others to give a time out or escalate the problem, and the ombuds program. We are also exploring shared space or community agreements

[plehegar]

@TzviyaSiegman , this looks good to me. Any chance this can be turned into a pull request ?