Create guidelines on handling CoC violations

[achrinza]

This is a 2-part issue:

1. Handling CoC violations in general
2. Handling CoC violation enforcement requests from the OpenJS Foundation

Handling CoC violations in general

The Contributor Covenant v2.0 (CCv2.0) provides terse enforcement guidelines which may be difficult to augment into each violation report that the TSC looks into. This can lead to disagreements on how to triage, document and evaluate the impact and severity of the CoC violation.

The CCv2.0 enforcement guidelines were influenced by Mozilla's code of conduct enforcement ladder, and we can take influence from Mozilla's other processes as well:

1. Triage system
   Help document the context of the report, such as the background of who is being reported.
2. Investigation templates
   Assist in formally documenting the complaint investigation process, and clearly stating who in the TSC is accountable for pushing the complaint through the process. Aids in providing accountability.
3. Notification & follow-up communication templates
   Standardises how we communicate with the affected parties.

Handling CoC violation enforcement requests from the OpenJS Foundation

Although the OpenJS Foundation as the right to request the hosted projects to take action, they have stated that forcing projects to adopt OpenJSF's resolutions are left vague and that historically, CoC violation enforcement were scoped within the project's specific community. See the OpenJSF CPC Meeting 2022-04-12 meeting minutes "Update Contributor Covenant Code of Conduct to v2.1".

Hence, this becomes a more involved process for projects who want to exercise independent evaluation of the report:

1. How much of the report is shown to the hosted projects' CoC contacts?
2. How does the LoopBack TSC evaluate and take action on these reports?
   a. Do we also need to perform our own notification and follow-up communications (as above) in addition to what the OpenJSF would do?

The OpenJSF CPC does not currently provide resources for hosted projects to adopt as part of their CoC process.

Other References

• https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415
• OpenJS Foundation CoC issue: Clarify requirements around CoC violation openjs-foundation/cross-project-council#786 (comment)
• OpenJSF Foundation CoC requiremens: https://github.com/openjs-foundation/cross-project-council/blob/4e801af388d03edaf370e734fb9e6e6a633ade7e/conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

[achrinza]

Further CoC adjustments are being made in openjs-foundation/cross-project-council#984 and openjs-foundation/cross-project-council#983.

[achrinza]

As part of the amendments to the CoC, a note was added to the CoC Preamble:

openjs-foundation/cross-project-council#991

We should consider updating our documentation to include this notice. In addition, we'll need to continue monitoring the modified CoC that would be adopted.

Currently, the patch code hasn't been merged:

openjs-foundation/cross-project-council#972

Hence there currently isn't a stable, canonical CoC that the OpenJSF is planning to adopt.