The CNCF Code of Conduct Committee (“CoC Committee”) is a committee that responds to, investigates, and resolves CNCF Code of Conduct incidents.
Our Jurisdiction and Escalation Policy describes the CoC Committee’s relationship to the Linux Foundation (LF) events staff, who enforce the Linux Foundation Events Code of Conduct, and project-level Code of Conduct responders (e.g., the Kubernetes Code of Conduct Committee).
The CoC Committee consists of 3 community members and 2 CNCF staff members. The members of the interim committee are listed below:
Community Members (elected by the Technical Oversight Committee):
- Bill Mulligan
- Josh Berkus
- Tim Pepper
Alternate Community Members:
- Carla Gaggini
- Jeremy Rickard
- Chris Aniszczyk, CNCF CTO
- Amye Scavarda Perrin, CNCF Director of Developer Programs
If one of the CNCF staff members listed above is unavailable or has to recuse themselves from participating in resolution of a CoC incident due to a conflict of interest (see our Conflict of Interest policy), CNCF may appoint an alternate CNCF staff member to take their place for that incident.
In order to ensure that multiple Community Members are involved in resolution of each incident, alternates participate when one or more of the primary Community Members listed above are unavailable (e.g., due to illness) or recuse themselves due to a conflict of interest. Similarly, LF and CNCF may appoint an alternate for a particular incident if one of their representatives listed above is unavailable or has a conflict of interest.
How Decisions Are Made
Decisions of the CoC Committee shall be made by consensus whenever possible. In the event consensus cannot be reached, decisions shall be made by majority vote of non-conflicted members of the CoC Committee. A decision to take temporary interim action in the event of an emergency may be taken by any individual CoC Committee member acting in good faith, and the CoC Committee shall review such action and decide whether to confirm or reverse such action. Any permanent action shall require approval of a majority of non-conflicted members of the CoC Committee. The CoC Committee may take action without a meeting if a majority of non-conflicted members express agreement in writing (e.g., email or slack) and none of the non-conflicted CoC Committee members either object to the proposed action or request a meeting to discuss the proposed action within 24 hours after the action is first proposed to the CoC Committee. In the absence of such agreement in writing, the CoC Committee may only take action during or after a meeting takes place at which the proposed action is discussed and agreed to by consensus or voted upon by a quorum of the non-conflicted members. A majority of non-conflicted members shall be deemed a quorum for purposes of a meeting. See the “Conflict of Interest” section of the Incident Resolution Procedures for more information.
External Support Resources
The CoC Committee may, in its discretion, engage external mediators, investigators, advisors, and consultants as needed to assist with resolution of CoC Incidents. Any such external resources shall not have a vote, and shall be required to maintain confidentiality in accordance with our Confidentiality Policy.
Incident Resolution Procedures
Please see our Jurisdiction and Escalation Policy and our Incident Resolution Procedures, which address:
- How to submit a report
- What information to share in your report
- What happens after a report is submitted
- Information sharing
- Confidentiality Policy
- No retaliation
- Conflicts of interest
This document is licensed under the Creative Commons Attribution 4.0 International License.