Updates per CoC Working Group Meetings #749

jorydotcom · 2021-04-27T17:32:31Z

Related to #726 & Others -

REVISIONS:

Removes references to coc-escalation@ & separate process for coc-escalation - everything handled via ‘reports@’
Clarifies that reports go to a CoC Panel, not the entire CPC
Designates Staff responsibility for first contact to reporter/ensuring contact persons are identified
Reinforces use of the /moderation repo
Creates Contact persons team to handle report processing by an available subset of CoC Panel members
Creates escalation to full CoC Panel if contact persons are not in agreement OR the resolution is not satisfactory to the reporter/target

COMMENTS (ported from the doc):

general, non-line specific comment

The one thing that I'm not sure if it will be a deterrent for people is.

I send a report to report@openjsf.org

I'm unhappy with the result and want to escalate

hmm, I need to send the escalation to the same people who already decided in a way that I did not agree with. Will this result in -> why bother its the same group so how is that an escalation?
It was one of the reasons for escalation to be separate from the regular flow in the earlier version.
Not a blocking comment, but seems to me that it might deter escalations.

Additional comments ported to specific lines

jorydotcom · 2021-04-27T17:33:17Z

HANDLING_CODE_OF_CONDUCT_REPORTS.md

@@ -4,69 +4,40 @@ This document describes the proposed process for handling reports and escalation
 This process covers two types of reports based on the [Foundation's Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md):

 * Reports for spaces managed by the Cross Project Council (CPC) which come in through `report@opensjsf.org`


In this bullet point, reports@openjsf.org is called out specifically. What about the second bullet point? It seems that address would work as well. In fact, I think the most recent incident used that address and fell into this second bullet point bucket.

jorydotcom · 2021-04-27T17:33:58Z

HANDLING_CODE_OF_CONDUCT_REPORTS.md

@@ -4,69 +4,40 @@ This document describes the proposed process for handling reports and escalation
 This process covers two types of reports based on the [Foundation's Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md):

 * Reports for spaces managed by the Cross Project Council (CPC) which come in through `report@opensjsf.org`
-* Escalations which come in through `coc-escalation@openjsf.org`.   
+* Reports or escalations that have been brought to specific OpenJS Foundation projects and delegated to the CPC by that project’s leadership.   


Does this item include:

escalations when the reporter is not satisfied with the project's resolution

escalations when the reporter wants to reach out to the foundation directly because it involves one of the project leads or members of their CoC Panel

I might be misunderstanding, but I'm not sure this description covers completely those scenarios or are those going to be handled in a different way?

The reason why I ask thins is that in FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md I see the following:

"In exceptional cases where a reporter wishes to challenge the response from the CPC or project, or does not feel comfortable reporting through the standard processes, an escalation report can be made to coc-escalation@openjsf.org."

Which I don't think is fully captured here.

Thanks!

jorydotcom · 2021-04-27T17:35:40Z

HANDLING_CODE_OF_CONDUCT_REPORTS.md

-
-If a report to coc-esclation does not include one of those, the reporter will be asked to to provide one of those three as the 
-reason for reporting to coc-escalation.
+All members of the [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel)


need to update the panel list

jorydotcom · 2021-04-27T17:36:08Z

HANDLING_CODE_OF_CONDUCT_REPORTS.md


 ## Code of Conduct

-The OpenJS Foundation and its member projects use the Contributor Covenant v2.0 as its Code of Conduct. Refer to the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) for the full text of the CoC and the reporting and esclation procedures.
+The OpenJS Foundation and its member projects use the Contributor Covenant v2.0 as its Code of Conduct. Refer to the [Code of Conduct](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md) for the full text of the CoC and the reporting and escalation procedures.

 ## Confidentiality and record-keeping
 Personal information is confidential. All reports should be recorded, together with the discussion of it. The following private repos will be used to record and discuss reports.

 * report@openjsf.org -> github.com/openjs-foundation/moderation


need to create this private repo

jorydotcom · 2021-04-27T17:36:58Z

HANDLING_CODE_OF_CONDUCT_REPORTS.md

-
+When a report is received to `report@openjsf.org` the following actions will be taken:
+   * An OpenJS Foundation staff representative will respond within 24 hours to the reporter or target confirming that the report has been received. 
+   * The staff representative will seek to determine whether the report is emergent and requires immediate attention (e.g. for an ongoing issue) or the report is a reactive response to an incident with no immediate danger. 


we talked about different timelines during the meeting in case something needs immediate attention or not.

HANDLING_CODE_OF_CONDUCT_REPORTS.md

mcollina · 2021-04-27T20:25:36Z

HANDLING_CODE_OF_CONDUCT_REPORTS.md

+     1. Information gathering: The contact persons will collect information in the private moderation repository..
+     1. Discussing the report: The contact persons will discuss the facts of the report in context of opinions via meeting, email, or discussion via private issue.
+     1. Acting on the report: The contact persons will attempt to reach consensus on the action to be taken.
+     1. Sharing the resolution: If the contact persons are in agreement, the resolution is shared with the reporter or target by the contact persons and recorded in the moderation repository. If the contact persons are not in agreement or if the reporter or target expresses concern or dissatisfaction with the resolution,  then the contact persons will bring the report to the CoC Panel  for further discussion. This cycle can continue until the panel reaches consensus that the reporter or target's concerns have been adequately addressed. If the panel cannot reach consensus within 7 days, the matter will be taken to a vote of the panelists. If no feedback is received within 7 days the resolution is considered as accepted. 


This should really be split into two points: sharing the resolution and appeal.

I would recommend have 15 days to reach consensus - it's an appeal procedure anyway and there is no urgency anymore.

mhdawson · 2021-04-30T16:53:57Z

I think this is missing corresponding changes in: https://github.com/openjs-foundation/cross-project-council/blob/main/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

They go hand and hand and need to be updated together.

bnb · 2022-04-08T21:16:42Z

any plans on merging this or should it be updated or closed?

mhdawson · 2022-04-12T18:27:04Z

@bnb I think it needs updates and/or questions in the issue addressed so dependson wether those happen from my perspective.

jorydotcom · 2022-05-17T16:52:57Z

In today's working CPC meeting about the CoC we discussed this PR. We feel it is still directionally the right way to go and will be updating the PR to reflect @mcollina and @mhdawson 's feedback and comments.

joesepi

We discussed in today's meeting and per that discussion and include Jory's most recent comment on this issue, I approve.

bnb · 2023-04-11T16:27:37Z

It has now been two years without merging this. Is it still needed? If so, can it be merged? 😅

Co-authored-by: Matteo Collina <hello@matteocollina.com>

eemeli · 2023-07-19T09:53:04Z

conduct/HANDLING_CODE_OF_CONDUCT_REPORTS.md

+When a report is received to `report@openjsf.org` the following actions will be taken:
+   * An OpenJS Foundation staff representative will respond within 24 hours to the reporter or target confirming that the report has been received. 
+   * The staff representative will seek to determine whether the report is emergent and requires immediate attention (e.g. for an ongoing issue) or the report is a reactive response to an incident with no immediate danger. 
+


Suggested change

eemeli · 2023-07-19T09:53:26Z

conduct/HANDLING_CODE_OF_CONDUCT_REPORTS.md

+   * The Staff Representative will identify two contact persons from its CoC Panel to examine and act on the report. The contact persons will be chosen on the basis of schedule and availability.
+   * The contact persons will then execute the following procedures:
+     1. Acknowledging the report: The contact persons will respond to let the reporter or target know that the report is being discussed.
+     1. Information gathering: The contact persons will collect information in the private moderation repository..


Suggested change

1. Information gathering: The contact persons will collect information in the private moderation repository..

1. Information gathering: The contact persons will collect information in a private moderation repository.

eemeli · 2023-07-19T10:04:39Z

conduct/HANDLING_CODE_OF_CONDUCT_REPORTS.md

+     1. Discussing the report: The contact persons will discuss the facts of the report in context of opinions via meeting, email, or discussion via private issue.
+     1. Acting on the report: The contact persons will attempt to reach consensus on the action to be taken.
+     1. Sharing the resolution: If the contact persons are in agreement, the resolution is shared with the reporter or target by the contact persons and recorded in the moderation repository. If the contact persons are not in agreement or if the reporter or target expresses concern or dissatisfaction with the resolution,  then the contact persons will bring the report to the CoC Panel  for further discussion. This cycle can continue until the panel reaches consensus that the reporter or target's concerns have been adequately addressed. If the panel cannot reach consensus within 7 days, the matter will be taken to a vote of the panelists. If no feedback is received within 7 days the resolution is considered as accepted. 
+     1. Final resolution: the resolution is implemented and the outcome reported to the reporter or target, and/or other involved parties.


Do I understand right that this is the first point at which a person accused of a CoC violation might hear about it? Or is communication with such a person implicit in the "Information gathering" phase?

I find it a little concerning that this process does not appear to allow for anyone to defend their actions before final resolution.

tobie · 2023-07-19T12:32:40Z

This is an old pull request that has just been updated because of #1116. It’s probably not going to land anyway. For the main issue for all CoC related work, check #1122.

tobie · 2024-02-24T21:33:25Z

Obsoleted by #1135.

jorydotcom commented Apr 27, 2021

View reviewed changes

jorydotcom requested review from joesepi, mcollina and molant April 27, 2021 17:52

mcollina reviewed Apr 27, 2021

View reviewed changes

joesepi approved these changes May 17, 2022

View reviewed changes

tobie added the TOPIC-code-of-conduct All issues related to the CoC update and process label Jun 28, 2023

jorydotcom and others added 2 commits July 18, 2023 12:52

updates per CoC Working Group Meetings

db01e34

Fix typo

9b3333e

Co-authored-by: Matteo Collina <hello@matteocollina.com>

ljharb force-pushed the coc-handling-updates branch from 47e12bc to 9b3333e Compare July 18, 2023 19:52

ljharb requested a review from a team as a code owner July 18, 2023 19:52

eemeli reviewed Jul 19, 2023

View reviewed changes

tobie mentioned this pull request Jul 20, 2023

Code of Conduct Plan of Action #1122

Open

15 tasks

tobie closed this Feb 24, 2024

ljharb deleted the coc-handling-updates branch February 24, 2024 23:20

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Updates per CoC Working Group Meetings #749

Updates per CoC Working Group Meetings #749

jorydotcom commented Apr 27, 2021

jorydotcom Apr 27, 2021

jorydotcom Apr 27, 2021 •

edited

Loading

jorydotcom Apr 27, 2021

jorydotcom Apr 27, 2021

jorydotcom Apr 27, 2021

mcollina Apr 27, 2021

mhdawson commented Apr 30, 2021

bnb commented Apr 8, 2022

mhdawson commented Apr 12, 2022

jorydotcom commented May 17, 2022

joesepi left a comment

bnb commented Apr 11, 2023

eemeli Jul 19, 2023

eemeli Jul 19, 2023

eemeli Jul 19, 2023

tobie commented Jul 19, 2023

tobie commented Feb 24, 2024

		@@ -4,69 +4,40 @@ This document describes the proposed process for handling reports and escalation
		This process covers two types of reports based on the [Foundation's Code of Conduct Requirements](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md):

		* Reports for spaces managed by the Cross Project Council (CPC) which come in through `report@opensjsf.org`

	1. Information gathering: The contact persons will collect information in the private moderation repository..
	1. Information gathering: The contact persons will collect information in a private moderation repository.

Updates per CoC Working Group Meetings #749

Updates per CoC Working Group Meetings #749

Conversation

jorydotcom commented Apr 27, 2021

Choose a reason for hiding this comment

jorydotcom Apr 27, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mhdawson commented Apr 30, 2021

bnb commented Apr 8, 2022

mhdawson commented Apr 12, 2022

jorydotcom commented May 17, 2022

joesepi left a comment

Choose a reason for hiding this comment

bnb commented Apr 11, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tobie commented Jul 19, 2023

tobie commented Feb 24, 2024

jorydotcom Apr 27, 2021 •

edited

Loading