This document defines how the OpenJS Foundation implements its code of conduct.
If you want to report an incident, go to code-of-conduct.openjsf.org.
The Cross Project Council (CPC) delegates enforcement of the Code of Conduct to the Code of Conduct Team (CoC Team) through this Code of Conduct Team Charter. This charter defines the composition and roles of the CoC Team, along with CoC team responsibilities and operations.
The CoC Team's responsibilities are to:
- Handle code of conduct incident reports.
- Handle code of conduct escalation requests.
- Handle code of conduct appeals.
- Keep the CPC up to date on cases requiring the CPC's attention.
- Provide regular transparency reports to the CPC.
- Uphold this charter, the code of conduct, and the code of conduct policy.
The CoC Team is composed of five (5) primary members and a variable number of alternate community members.
Primary members are CoC Team members responsible for handling cases.
The five primary members are:
- The OpenJS Foundation Executive Director
- The OpenJS Foundation Communications Manager
- Three (3) community members
The name and email address of the primary members are documented in the code of conduct.
Alternate community members are CoC Team Members who are available as backup when there aren't enough primary community members available to handle a case.
The Cross Project Council (CPC) will hold an annual selection process in order to select primary and alternate community members.
The CPC is responsible for ensuring that the CoC Team is as representative and diverse as possible. To do so, the CPC commits to reach out proactively to individuals from underrepresented groups.
Candidates can self-nominate to be selected as an alternate community member, a primary member, or both.
Candidates must meet the eligibility requirements.
Primary and alternate community members of the CoC Team must:
- Commit to uphold the Foundation's Code of Conduct
- Commit to uphold the Foundation's Code of Conduct Policy
- Commit to uphold this charter
- Be willing to treat every accused individual in the same way regardless of the impact of their contributions to open source
No two primary community members can work for the same employer nor hold leadership positions in the same OpenJSF project.
Members of the CoC Team serve a one-year term. There are no limits on the number of terms a CoC Team member may serve.
Each appeal, escalation request, and incident report must be handled by a minimum of three (3) and a maximum of five (5) members.
At least two (2) of the members involved in handling a case must be community members and at least one (1) must be an OpenJS Foundation staff member.
If not enough primary community members are available to meet those requirements, primary members should involve one or more alternate community members. Similarly, if no OpenJSF staff primary member is available, another OpenJSF staff representative, chosen by the staff, should be involved instead.
Appeals to responses provided by the CoC Team itself should be handled by a different set of members than those responsible for the initial response.
The CoC Team uses the Cross Project Council's Decision Making Process.