chore: add documents CoC Committee and Incident Resolution Procedures #1013

Barbanio · 2024-01-10T16:05:17Z

Updating information on the Code of Conduct Committee. Adding documents 1 (CoC Committee) and 2 (Incident Resolution Procedures)of the issue #994.

@AceTheCreator @smoya @Mayaleeeee @alequetzalli @thulieblack

… added

smoya · 2024-01-10T16:15:47Z

code_of_conduct/coc-incident-resolution-procedures.md

+
+### Submit in writing
+
+To report a violation in writing, please email [[email protected]](mailto:[email protected]), which goes to all primary (not alternate) members of the AsyncAPI Code of Conduct Committee (CoC Committee). If you do not want your report to be received by all members of the CoC Committee, either because you want to submit a report anonymously or because one of the CoC Committee members has a conflict of interest, you may send your report directly to any individual member of the CoC Committee.


@derberg shall we tell Linux Foundation to add this email user?

Also we need to decide how we wanna operate as CoC Commitee regarding email watching. Shall those emails act as a redirect to all of our personal emails? Rather, shall some of us get access to that email account and check email manually from time to time? Maybe we could do some automation via Slack?

Additionally, we can set an Slack Workflow (super easy to create, just few clicks) so people can report through an Slack action. Just an example:

The data collected can be posted into a private channel where only the CoC Committee is present. This won't work for anonymous reports but for non-anonymous. However, it will IMHO add good value by letting users quickly send reports of violations, especially those that were not targeted to them, turning those "I will write an email later" into actions).

cc @Barbanio

I like the idea! Wdyt, @AceTheCreator?

I have doubts if [email protected] is the best solution that assures people feel safe to report problem.

Generic email - you have in the end no idea who has access to it.

Yeah I know other communities do it this way.... but I find it pretty strange.

Why not being transparent:

mention who people can reach out

have some kind of online form, that people can use to fill in report

This way we can 100% assure only the right people will get report.

With generic email - admins of Google Workspace (Fran, and also Me) will also have access. Not saying we will violate the trust...but still - it is not 100% safe solution

@derberg your suggestion is that the reports should be posted either via DM to a member of the CoC Committee or via form and posted automatically to the private channel the CoC Committee has?

@thulieblack any particular reason why Joanna Lee (LF legal expert) advised against it?

Its all here https://github.com/orgs/asyncapi/discussions/682#discussioncomment-6052787

ok then, so we go with generic email but also transparently mention emails of committee members in case of people want to reach out to them directly instead of generic email?

Yea, that'll be the best way in my opinion

If we go for email, we should need then @asyncapi.org (or .com) emails to give trust and to avoid mixing personal stuff IMHO. WDYT?

code_of_conduct/coc-incident-resolution-procedures.md

smoya · 2024-01-10T16:28:41Z

code_of_conduct/coc-incident-resolution-procedures.md

+
+### Submit in spoken conversation
+
+If you prefer to report the violation in a spoken conversation, you may request a virtual meeting with a CoC Committee member. If the incident occurs at an event, you may report the incident in person either to a member of the AsyncAPI CoC member or a [Technical Steering Committee](https://www.asyncapi.com/community/tsc) (TSC) member.


or a Technical Steering Committee (TSC) member.

Then this means (to me) all TSC members need to be aware of all the processes regarding the CoC. We could ping them all at some point when all of this get merged to let them know.
Wondering if dealing with CoC reports could be something some members could feel uncomfortable 🤔

Additionally, we could also recommend to, in case there are no members of the Committee to contact via email.

It makes sense. It's a very good idea. All TSC members should know the CoC, especially in case they have to act in an emergency situation.

Regarding contact by email, this is the first option given in the previous section: Submit in writing.

code_of_conduct/coc-incident-resolution-procedures.md

Co-authored-by: Sergio Moya <[email protected]>

code_of_conduct/code-of-conduct-committee.md

code_of_conduct/coc-incident-resolution-procedures.md

smoya · 2024-02-07T17:44:41Z

code_of_conduct/coc-incident-resolution-procedures.md

+
+### Communicating the Results
+
+An incident is considered “resolved” when the CoC Committee has completed its investigation and either (a) determined what remediation actions are needed to resolve an incident (including determining that the involved parties’ agreed-upon resolution is adequate) (b) or determined that the CoC was not violated and no remediation is needed. When the incident is resolved, a member of the CoC Committee will inform the person who submitted the report. The CoC Committee will determine how much information to share with the reporter regarding the committee’s findings and what remediation steps were taken, if any, taking into consideration the privacy, confidentiality, and potential impact to the individuals involved in the incident. Notification to the accused person shall follow [Notification to the Accused Person](#notification-to-the-accused-person). The CoC Committee will also determine what information, if any, is necessary to share publicly or with community and project leaders. Any communication regarding the results of the investigation will be confidential.


determined what remediation actions are needed to resolve an incident

I would expect not only know which actions to take but some kind of follow up I guess? not sure if this is out of our bandwidth tbh

Yes, maybe makes sense. How about contacting the person(s) who were affected a month or three months after resolving the conflict to see how things are going?

Makes totally sense.

code_of_conduct/coc-incident-resolution-procedures.md

smoya

Maybe some of the comments I added are related to the CNCF CoC incident resolution doc, so feel free to discard if you believe it should.

thulieblack · 2024-02-08T07:42:05Z

code_of_conduct/coc-incident-resolution-procedures.md

+
+### Confirmation of Jurisdiction
+
+After a report is submitted, the AsyncAPI CoC Committee will confirm who has jurisdiction over the incident under the Jurisdiction and Escalation Policy. If the CoC Committee does not have jurisdiction, it will escalate the incident to the TSC. Reporters will be notified if this occurs unless they reported anonymously and did not provide their contact information. If the CoC Committee does have jurisdiction and is not required to escalate it, the committee will proceed to investigate and resolve the incident.


Question: what do you mean by "Confirmation of Jurisdiction"?

This refers to the CoC committee deciding if there is a conflict of interest, who is in charge of the report, and similar things. Anyway, I believe this section refers to this supplementary document. I don't know if it makes sense to keep the section or to have a similar document.

I suggest having a similar document separately, but that's just my opinion 😉

Conflicting with my suggestion https://github.com/asyncapi/community/pull/1013/files#r1489429536 😅
I suggested to just write a small section, because the CNCF one is way bigger because, yes, CNCF is a foundation.

Hehe, I was just suggesting. Maybe we can improve the section according to our circumstances and still keep it in one document.

thulieblack · 2024-03-13T11:04:52Z

IMO I think we have resolved the major stuff @deberg, any other concerns before we go ahead?

smoya · 2024-03-13T11:19:38Z

After a month, I closed the discussion that let the @asyncapi/tsc_members know their responsibilities regarding the CoC and it's incident resolution.

Additionally, I created the following issue so we add the requirement of reading and accepting the CoC for any future new TSC member. #1097

cc @derberg

smoya · 2024-04-16T17:26:53Z

code_of_conduct/code-of-conduct-committee.md

+**Full Members**:
+
+- [Azeez Elegbede](https://github.com/acethecreator)
+- [Barbaño González](https://github.com/barbanio)


Suggested change

- [Barbaño González](https://github.com/barbanio)

Based on https://github.com/orgs/asyncapi/discussions/682#discussioncomment-7229097, @Mayaleeeee @alequetzalli @thulieblack @derberg Any of you are willing to become a full CoC Committee member?

I feel too overwhelmed to be able to say yes 😿

I'm still okay with supporting the Committee as a secondary member.

smoya · 2024-05-28T18:26:09Z

/ptal

asyncapi-bot · 2024-05-28T18:26:24Z

@derberg @alequetzalli @AceTheCreator Please take a look at this PR. Thanks! 👋

quetzalliwrites · 2024-06-04T02:00:08Z

Can we merge already? 😆

thulieblack · 2024-06-04T07:24:22Z

Looks ready to me 🚀🚀

smoya · 2024-06-05T09:28:59Z

/rtm

Barbanio added 4 commits January 10, 2024 14:59

the CoC committee document and incident resolution procedure has been…

bc4e789

… added

Update coc-incident-resolution-procedures.md

8bcf8b8

Update code-of-conduct-committee.md

decd017

Update code-of-conduct-committee.md

5a1a320

Barbanio requested review from quetzalliwrites, derberg, asyncapi-bot-eve and thulieblack as code owners January 10, 2024 16:05

Barbanio changed the title ~~chore: Add documents CoC Committe and Incident Resolution Procedures~~ chore: add documents CoC Committe and Incident Resolution Procedures Jan 10, 2024

Barbanio changed the title ~~chore: add documents CoC Committe and Incident Resolution Procedures~~ chore: add documents CoC Committee and Incident Resolution Procedures Jan 10, 2024

Barbanio mentioned this pull request Jan 10, 2024

Code Of Conduct Committee #994

Closed

10 tasks

smoya reviewed Jan 10, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Outdated Show resolved Hide resolved

smoya reviewed Jan 10, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Outdated Show resolved Hide resolved

smoya reviewed Jan 10, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Outdated Show resolved Hide resolved

Barbanio and others added 5 commits January 18, 2024 14:07

Update code_of_conduct/coc-incident-resolution-procedures.md

2761eb1

Co-authored-by: Sergio Moya <[email protected]>

Update coc-incident-resolution-procedures.md

13f28d0

Merge branch 'master' into code_of_conduct

47abfb0

Merge branch 'master' into code_of_conduct

4292f16

Merge branch 'master' into code_of_conduct

2730028

smoya reviewed Feb 7, 2024

View reviewed changes

code_of_conduct/code-of-conduct-committee.md Show resolved Hide resolved

smoya reviewed Feb 7, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Show resolved Hide resolved

smoya reviewed Feb 7, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Outdated Show resolved Hide resolved

smoya reviewed Feb 7, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Outdated Show resolved Hide resolved

smoya reviewed Feb 7, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Outdated Show resolved Hide resolved

smoya reviewed Feb 7, 2024

View reviewed changes

code_of_conduct/coc-incident-resolution-procedures.md Show resolved Hide resolved

smoya requested changes Feb 7, 2024

View reviewed changes

thulieblack reviewed Feb 8, 2024

View reviewed changes

Merge branch 'master' into code_of_conduct

94a2183

smoya mentioned this pull request Mar 13, 2024

Candidates to become TSC members should have read and accepted the Code Of Conduct #1097

Closed

thulieblack mentioned this pull request Mar 28, 2024

feat: update CoC #1132

Merged

thulieblack added 2 commits April 8, 2024 11:33

Merge branch 'master' into code_of_conduct

1cfe6d2

Merge branch 'asyncapi:master' into code_of_conduct

d3ae957

smoya reviewed Apr 16, 2024

View reviewed changes

thulieblack and others added 3 commits April 30, 2024 11:09

Merge branch 'master' into code_of_conduct

ce7731c

Merge branch 'master' into code_of_conduct

81f322e

remove Barbaño from committee

fc68dd0

smoya dismissed quetzalliwrites’s stale review via fc68dd0 May 22, 2024 06:12

smoya added 2 commits May 27, 2024 12:30

Merge branch 'master' into code_of_conduct

4c3be8a

move Maya to full member

0da913a

smoya requested review from quetzalliwrites, AceTheCreator and thulieblack May 28, 2024 18:26

smoya approved these changes May 28, 2024

View reviewed changes

quetzalliwrites approved these changes May 29, 2024

View reviewed changes

quetzalliwrites added 2 commits May 29, 2024 13:51

Merge branch 'master' into code_of_conduct

7385158

Merge branch 'master' into code_of_conduct

337e07f

thulieblack approved these changes Jun 4, 2024

View reviewed changes

asyncapi-bot added the ready-to-merge label Jun 5, 2024

asyncapi-bot merged commit 1e64010 into asyncapi:master Jun 5, 2024
8 checks passed

smoya deleted the code_of_conduct branch June 5, 2024 09:29

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: add documents CoC Committee and Incident Resolution Procedures #1013

chore: add documents CoC Committee and Incident Resolution Procedures #1013

Barbanio commented Jan 10, 2024

smoya Jan 10, 2024

smoya Feb 7, 2024 •

edited

Loading

Barbanio Feb 8, 2024

derberg Feb 21, 2024

smoya Feb 21, 2024

AceTheCreator Mar 25, 2024

thulieblack Mar 25, 2024

derberg Mar 25, 2024

AceTheCreator Mar 25, 2024 •

edited

Loading

smoya Mar 25, 2024

smoya Jan 10, 2024 •

edited

Loading

Barbanio Jan 18, 2024

smoya Feb 7, 2024 •

edited

Loading

Barbanio Feb 8, 2024

smoya Feb 19, 2024

smoya left a comment

thulieblack Feb 8, 2024

Barbanio Feb 8, 2024

thulieblack Feb 12, 2024

smoya Feb 14, 2024

thulieblack Feb 14, 2024

thulieblack commented Mar 13, 2024

smoya commented Mar 13, 2024

smoya Apr 16, 2024 •

edited

Loading

quetzalliwrites Apr 16, 2024

thulieblack Apr 17, 2024

smoya commented May 28, 2024

asyncapi-bot commented May 28, 2024

quetzalliwrites commented Jun 4, 2024

thulieblack commented Jun 4, 2024

smoya commented Jun 5, 2024


		### Submit in writing

		To report a violation in writing, please email [[email protected]](mailto:[email protected]), which goes to all primary (not alternate) members of the AsyncAPI Code of Conduct Committee (CoC Committee). If you do not want your report to be received by all members of the CoC Committee, either because you want to submit a report anonymously or because one of the CoC Committee members has a conflict of interest, you may send your report directly to any individual member of the CoC Committee.


		### Submit in spoken conversation

		If you prefer to report the violation in a spoken conversation, you may request a virtual meeting with a CoC Committee member. If the incident occurs at an event, you may report the incident in person either to a member of the AsyncAPI CoC member or a [Technical Steering Committee](https://www.asyncapi.com/community/tsc) (TSC) member.


		### Communicating the Results

		An incident is considered “resolved” when the CoC Committee has completed its investigation and either (a) determined what remediation actions are needed to resolve an incident (including determining that the involved parties’ agreed-upon resolution is adequate) (b) or determined that the CoC was not violated and no remediation is needed. When the incident is resolved, a member of the CoC Committee will inform the person who submitted the report. The CoC Committee will determine how much information to share with the reporter regarding the committee’s findings and what remediation steps were taken, if any, taking into consideration the privacy, confidentiality, and potential impact to the individuals involved in the incident. Notification to the accused person shall follow [Notification to the Accused Person](#notification-to-the-accused-person). The CoC Committee will also determine what information, if any, is necessary to share publicly or with community and project leaders. Any communication regarding the results of the investigation will be confidential.


		### Confirmation of Jurisdiction

		After a report is submitted, the AsyncAPI CoC Committee will confirm who has jurisdiction over the incident under the Jurisdiction and Escalation Policy. If the CoC Committee does not have jurisdiction, it will escalate the incident to the TSC. Reporters will be notified if this occurs unless they reported anonymously and did not provide their contact information. If the CoC Committee does have jurisdiction and is not required to escalate it, the committee will proceed to investigate and resolve the incident.

chore: add documents CoC Committee and Incident Resolution Procedures #1013

chore: add documents CoC Committee and Incident Resolution Procedures #1013

Conversation

Barbanio commented Jan 10, 2024

Choose a reason for hiding this comment

smoya Feb 7, 2024 • 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AceTheCreator Mar 25, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smoya Jan 10, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smoya Feb 7, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smoya left a 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

thulieblack commented Mar 13, 2024

smoya commented Mar 13, 2024

smoya Apr 16, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smoya commented May 28, 2024

asyncapi-bot commented May 28, 2024

quetzalliwrites commented Jun 4, 2024

thulieblack commented Jun 4, 2024

smoya commented Jun 5, 2024

smoya Feb 7, 2024 •

edited

Loading

AceTheCreator Mar 25, 2024 •

edited

Loading

smoya Jan 10, 2024 •

edited

Loading

smoya Feb 7, 2024 •

edited

Loading

smoya Apr 16, 2024 •

edited

Loading