Explain escalation pathways and connection to parent organization #2

Open
opened 2026-08-03 14:58:13 +00:00 by jwheel · 0 comments

Per a discussion which took place in PR #1, this issue is opened to track a longer-term discussion of better explaining the escalation pathways available to the Code of Conduct Committee, and how that connects to the parent organization (i.e., SFC).

At project start, it is logical to defer this topic since we need more project engagement and interaction before we can better explain something which presently has no absolute explanation. However, later when more organizations and key participants are on-boarded, we should provide better clarity into how this connects, what authority the CoC Committee has, and who the CoC Committee "reports" to for either recommending or enforcing CoC Committee decisions.

[Per a discussion](https://git.copyleft.org/copyleft-next/code-of-conduct/pulls/1#issuecomment-10) which took place in PR #1, this issue is opened to track a longer-term discussion of better explaining the escalation pathways available to the Code of Conduct Committee, and how that connects to the parent organization (i.e., SFC). At project start, it is logical to defer this topic since we need more project engagement and interaction before we can better explain something which presently has no absolute explanation. However, later when more organizations and key participants are on-boarded, we should provide better clarity into how this connects, what authority the CoC Committee has, and who the CoC Committee "reports" to for either recommending or enforcing CoC Committee decisions.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
copyleft-next/code-of-conduct#2
No description provided.