Skip to content

Commit b74cee7

Browse files
RelequestualRelequestual
authored
Merge pull request #1 from Relequestual/feature/coc
Add initial Code of Conduct Includes extracts from IETF BCP 54 and a modified version of Contributor Covenant CoC. (References IETF BCP 54 as fully part of our CoC, but some extracts are helpful.)
2 parents 1c996ab + adee842 commit b74cee7

File tree

3 files changed

+192
-0
lines changed

3 files changed

+192
-0
lines changed

‎CODE_OF_CONDUCT.md

Lines changed: 185 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,185 @@
1+
# JSON Schema Organizational Code of Conduct
2+
3+
Our (The JSON Schema Organization) Code of Conduct is a combination of
4+
the "Contributor Covenant Code of Conduct" 2.1 and the IETF BCP 54 "IETF Guidelines for Conduct" (RFC7154).
5+
6+
# IETF Guidelines for Conduct
7+
8+
Note: These guidelines are not provided in full in this document.
9+
Some extracts are provided.
10+
Please see the [RFC document](https://www.rfc-editor.org/rfc/rfc7154.html) for full details.
11+
While we do not currently formally interact with the IETF beyond publication of specification documents,
12+
we have found their approach to developing specifications well informed and useful.
13+
14+
[BCP 54] provides a set of guidelines for personal interaction
15+
in the Internet Engineering Task Force. The guidelines recognize the
16+
diversity of IETF participants, emphasize the value of mutual
17+
respect, and stress the broad applicability of our work.
18+
19+
The work of the IETF relies on cooperation among a diverse range of
20+
people with different ideas and communication styles. The IETF
21+
strives, through these guidelines for conduct, to create and maintain
22+
an environment in which every person is treated with dignity,
23+
decency, and respect.
24+
25+
We dispute ideas by using reasoned argument rather than through
26+
intimidation or personal attack.
27+
28+
The IETF puts its emphasis on technical
29+
competence, rough consensus, and individual participation, and it
30+
needs to be open to competent input from any source.
31+
32+
IETF participants use their best engineering judgment to find the
33+
best solution for the whole Internet, not just the best solution
34+
for any particular network, technology, vendor, or user.
35+
36+
Some thoughts on "consensus": https://datatracker.ietf.org/doc/html/rfc7282
37+
38+
# Contributor Covenant Code of Conduct
39+
40+
## Our Pledge
41+
42+
We as members, contributors, and leaders pledge to make participation in our
43+
community a harassment-free experience for everyone, regardless of age, body
44+
size, visible or invisible disability, ethnicity, sex characteristics, gender
45+
identity and expression, level of experience, education, socio-economic status,
46+
nationality, personal appearance, race, caste, color, religion, or sexual identity
47+
and orientation.
48+
49+
We pledge to act and interact in ways that contribute to an open, welcoming,
50+
diverse, inclusive, and healthy community.
51+
52+
## Our Standards
53+
54+
Examples of behavior that contributes to a positive environment for our
55+
community include:
56+
57+
* Demonstrating empathy and kindness toward other people
58+
* Being respectful of differing opinions, viewpoints, and experiences
59+
* Giving and gracefully accepting constructive feedback
60+
* Accepting responsibility and apologizing to those affected by our mistakes,
61+
and learning from the experience
62+
* Focusing on what is best not just for us as individuals, but for the
63+
overall community
64+
65+
Examples of unacceptable behavior include:
66+
67+
* The use of sexualized language or imagery, and sexual attention or
68+
advances of any kind
69+
* Trolling, insulting or derogatory comments, and personal or political attacks
70+
* Public or private harassment
71+
* Publishing others' private information, such as a physical or email
72+
address, without their explicit permission
73+
* Other conduct which could reasonably be considered inappropriate in a
74+
professional setting
75+
76+
## Enforcement Responsibilities
77+
78+
Community leaders are responsible for clarifying and enforcing our standards of
79+
acceptable behavior and will take appropriate and fair corrective action in
80+
response to any behavior that they deem inappropriate, threatening, offensive,
81+
or harmful.
82+
83+
Community leaders have the right and responsibility to remove, edit, or reject
84+
comments, commits, code, wiki edits, issues, and other contributions that are
85+
not aligned to this Code of Conduct, and will communicate reasons for moderation
86+
decisions when appropriate.
87+
88+
## Scope
89+
90+
This Code of Conduct applies within all community spaces, and also applies when
91+
an individual is officially representing the community in public spaces.
92+
Examples of representing our community include using an official e-mail address,
93+
posting via an official social media account, or acting as an appointed
94+
representative at an online or offline event.
95+
96+
## Enforcement
97+
98+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
99+
reported to the community leaders responsible for enforcement at
100+
[email protected].
101+
All complaints will be reviewed and investigated promptly and fairly.
102+
103+
All community leaders are obligated to respect the privacy and security of the
104+
reporter of any incident.
105+
106+
In addition, JSON Schema is in the process of joining the OpenJS Foundation.
107+
The OpenJS Foundation provides an escalation path should you feel your report
108+
has not been handled appropriatly.
109+
110+
> The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to [email protected]. - https://github.com/openjs-foundation/cross-project-council/blob/main/CODE_OF_CONDUCT.md#escalation
111+
112+
## Privacy Expectations
113+
114+
As per Code of Conduct requirements set out by the OpenJS Foundation, we will maintain the confidentiality with regard to the reporter of an incident.
115+
For the purposes of tracking between Code of Conduct review members, incidents may be tracked in a private organizational GitHub Repository.
116+
In addition to any Code of Conduct review team, GitHub organizational owners will have access to view details of reports by way of having full GitHub organizational admin access.
117+
118+
## Enforcement Guidelines
119+
120+
Community leaders will follow these Community Impact Guidelines in determining
121+
the consequences for any action they deem in violation of this Code of Conduct:
122+
123+
### 1. Correction
124+
125+
**Community Impact**: Use of inappropriate language or other behavior deemed
126+
unprofessional or unwelcome in the community.
127+
128+
**Consequence**: A private, written warning from community leaders, providing
129+
clarity around the nature of the violation and an explanation of why the
130+
behavior was inappropriate. A public apology may be requested.
131+
132+
### 2. Warning
133+
134+
**Community Impact**: A violation through a single incident or series
135+
of actions.
136+
137+
**Consequence**: A warning with consequences for continued behavior. No
138+
interaction with the people involved, including unsolicited interaction with
139+
those enforcing the Code of Conduct, for a specified period of time. This
140+
includes avoiding interactions in community spaces as well as external channels
141+
like social media. Violating these terms may lead to a temporary or
142+
permanent ban.
143+
144+
### 3. Temporary Ban
145+
146+
**Community Impact**: A serious violation of community standards, including
147+
sustained inappropriate behavior.
148+
149+
**Consequence**: A temporary ban from any sort of interaction or public
150+
communication with the community for a specified period of time. No public or
151+
private interaction with the people involved, including unsolicited interaction
152+
with those enforcing the Code of Conduct, is allowed during this period.
153+
Violating these terms may lead to a permanent ban.
154+
155+
### 4. Permanent Ban
156+
157+
**Community Impact**: Demonstrating a pattern of violation of community
158+
standards, including sustained inappropriate behavior, harassment of an
159+
individual, or aggression toward or disparagement of classes of individuals.
160+
161+
**Consequence**: A permanent ban from any sort of public interaction within
162+
the community.
163+
164+
## Attribution
165+
166+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
167+
version 2.1, available at
168+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
169+
170+
Community Impact Guidelines were inspired by
171+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
172+
173+
For answers to common questions about this code of conduct, see the FAQ at
174+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
175+
at [https://www.contributor-covenant.org/translations][translations].
176+
177+
[homepage]: https://www.contributor-covenant.org
178+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
179+
[Mozilla CoC]: https://github.com/mozilla/diversity
180+
[FAQ]: https://www.contributor-covenant.org/faq
181+
[translations]: https://www.contributor-covenant.org/translations
182+
183+
# Deviations
184+
185+
To see the deviations from the Contributor Covenant Code of Conduct version 2.1, please check the git history for this file, or manually create a diff.

‎README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,4 @@
11
# .github
2+
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](code_of_conduct.md)
3+
24
A repo containing default GitHub community health files

‎docs/adr/index.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Architectural Decision Log
2+
3+
Your ADR log is in another castle (or rather, another repository).
4+
5+
Please use the ADRs found in the [Community](https://github.com/json-schema-org/community) repo for this .github repo.

0 commit comments

Comments
 (0)