TSC members responsibilities regarding Code Of Conduct

[smoya]

AsyncAPI now has a team called the Code Of Conduct Committee. As per CNCF definition:

is a committee that responds to, investigates, and resolves CNCF Code of Conduct incidents.

There is an ongoing effort for creating an updated version of our Code Of Conduct (CoC) in #1013.
The new CoC suggests the involvement of the TSC as a last option for solving some incidents, specially when it comes to conflicts of interests of members of the CoC Committee.

I have put together a list of all mentions to the TSC in the CoC so you can all review and approve:

1

If the incident occurs at an event, you may report the incident in person either to a member of the AsyncAPI CoC Committee or a Technical Steering Committee (TSC) member.

Source: https://github.com/asyncapi/community/pull/1013/files#diff-1b8aa87c2a7d6d0b70db06982aa322ef9bc689dbd43638e72f797b466a435c9aR48

2

the AsyncAPI CoC Committee might need to disclose certain information about the incident to TSC in order to arrange for onsite support for a target of harassment

Source: https://github.com/asyncapi/community/pull/1013/files#diff-1b8aa87c2a7d6d0b70db06982aa322ef9bc689dbd43638e72f797b466a435c9aR184

3

If one of the CoC members listed above is unavailable or has to recuse themselves from participating in the resolution of a CoC incident due to a conflict of interest (see our Conflict of Interest policy), AsyncAPI may request assistance from the Technical Steering Committee in appointing an alternate from the TSC members to take their place for that incident.

Source: https://github.com/asyncapi/community/pull/1013/files#diff-eced177e36d3e5c6cbef6a8fe368fd2288ee933f89aeb420cfa8f88dc94fd6beR25

4

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 Committee or a Technical Steering Committee (TSC) member.

Source: https://github.com/asyncapi/community/pull/1013/files#diff-1b8aa87c2a7d6d0b70db06982aa322ef9bc689dbd43638e72f797b466a435c9aR48

5

The CoC Committee, and Technical Steering Committee (TSC) may share information with each other on an as-needed basis about reported incidents and their resolution for the limited purposes of:

Source: https://github.com/asyncapi/community/pull/1013/files#diff-1b8aa87c2a7d6d0b70db06982aa322ef9bc689dbd43638e72f797b466a435c9aR170

6

AsyncAPI may request assistance from the Technical Steering Committee in appointing an alternate from the TSC members to take their place for that incident.

Source: https://github.com/asyncapi/community/pull/1013/files#diff-eced177e36d3e5c6cbef6a8fe368fd2288ee933f89aeb420cfa8f88dc94fd6beR25

7

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.

Source: https://github.com/asyncapi/community/pull/1013/files#diff-1b8aa87c2a7d6d0b70db06982aa322ef9bc689dbd43638e72f797b466a435c9aR75

@asyncapi/tsc_members Please react to this with 👍 if you agree, 👎 if you disagree, or 👀 if you don't want to vote but want to signal that you're aware and have read this.

Feedback is also appreciated!

cc @Barbanio @Mayaleeeee @AceTheCreator @alequetzalli @thulieblack

[quetzalliwrites]

They all sound good to me! 👍🏻

[imabp]

Lgtm

[Mayaleeeee]

It makes sense to me.

[fmvilas]

Thanks for pushing this forward 💯 We're maturing as a community 👏

[smoya]

For concluding this discussions, I would suggest any TSC member or any candidate to become TSC member should have read the Code Of Conduct as a requirement.
I'm gonna open an issue for adding that requirement to https://github.com/asyncapi/community/blob/master/TSC_MEMBERSHIP.md.
Issue opened: #1097

Closing this discussion now after few weeks. Thanks folks!