-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update our Code of Conduct to reflect OpenJS Foundation Code of Conduct #5
Merged
benjagm
merged 4 commits into
json-schema-org:main
from
Relequestual:coc-openjsf-escalation
Aug 30, 2023
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
166e727
Update our Code of Conduct to reflect OpenJS Foundation Code of Conduct
Relequestual 7c202fa
Update CODE_OF_CONDUCT.md
Relequestual 3810e72
Update CODE_OF_CONDUCT.md
Relequestual 14f868c
Make it clearer that the JSON Schema project is not part of the IETF
Relequestual File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -1,7 +1,21 @@ | ||||||
# JSON Schema Organizational Code of Conduct | ||||||
|
||||||
Our (The JSON Schema Organization) Code of Conduct is a combination of | ||||||
the "Contributor Covenant Code of Conduct" 2.1 and the IETF BCP 54 "IETF Guidelines for Conduct" (RFC7154). | ||||||
- The IETF BCP 54 "IETF Guidelines for Conduct" (RFC7154) | ||||||
- The "Contributor Covenant Code of Conduct" 2.1 | ||||||
- The OpenJS Foundation Code of Conduct | ||||||
|
||||||
## Applicable sections | ||||||
|
||||||
We take the whole of the Contributor Covenant Code of Conduct 2.1 as is. | ||||||
|
||||||
We reference the IETF BCP 54 "IETF Guidelines for Conduct" (RFC7154) as a guideline. | ||||||
We do not subscribe to its defined Reporting Transgressions of the Guidelines (Appendix A), | ||||||
as JSON Schema is not part of any IETF working group. | ||||||
|
||||||
We subscribe to the OpenJS Foundation Code of Conduct in full. The OpenJS Foundation Code of Conduct | ||||||
consists of the Contributor Covenant Code of Conduct, commitments relating to reports, | ||||||
and an escalation process. | ||||||
|
||||||
# IETF Guidelines for Conduct | ||||||
|
||||||
|
@@ -103,18 +117,6 @@ All complaints will be reviewed and investigated promptly and fairly. | |||||
All community leaders are obligated to respect the privacy and security of the | ||||||
reporter of any incident. | ||||||
|
||||||
In addition, JSON Schema is in the process of joining the OpenJS Foundation. | ||||||
The OpenJS Foundation provides an escalation path should you feel your report | ||||||
has not been handled appropriatly. | ||||||
|
||||||
> 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 coc-escalation@lists.openjsf.org. - https://github.com/openjs-foundation/cross-project-council/blob/main/CODE_OF_CONDUCT.md#escalation | ||||||
|
||||||
## Privacy Expectations | ||||||
|
||||||
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. | ||||||
For the purposes of tracking between Code of Conduct review members, incidents may be tracked in a private organizational GitHub Repository. | ||||||
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. | ||||||
|
||||||
## Enforcement Guidelines | ||||||
|
||||||
Community leaders will follow these Community Impact Guidelines in determining | ||||||
|
@@ -180,6 +182,19 @@ at [https://www.contributor-covenant.org/translations][translations]. | |||||
[FAQ]: https://www.contributor-covenant.org/faq | ||||||
[translations]: https://www.contributor-covenant.org/translations | ||||||
|
||||||
# Deviations | ||||||
# The OpenJS Foundation Code of Conduct | ||||||
|
||||||
The OpenJS Foundation Code of Conduct is mostly formed from the Contributor Covenant Code of Conduct. | ||||||
Significantly, we copy here the defined issue escalation process. | ||||||
|
||||||
## Privacy Expectations | ||||||
|
||||||
As per Code of Conduct requirements set out by the OpenJS Foundation, recipients of reports will maintain the confidentiality with regard to the reporter of an incident. | ||||||
For the purposes of tracking between Code of Conduct review members, incidents may be tracked in a private organizational GitHub Repository. | ||||||
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. | ||||||
|
||||||
## Escalate an issue | ||||||
|
||||||
The OpenJS Foundation provides an [escalation path](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md#escalate-an-issue) should you feel your report has not been handled appropriatly. Recipients of reports commit to participate in the defined path of escalation when required, as required by the OpenJS Foundation Code of Conduct. | ||||||
|
||||||
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. | ||||||
> The OpenJS Foundation maintains a [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel). 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 coc-escalation@lists.openjsf.org. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This CoCP link looks like a 404 to me. Not sure what the right one is, that repo doesn't have that file, is it on a branch? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest to remove entirely this section: "IETF Guidelines for Conduct"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We agreed not to remove it, but to modify it, on our previous call: json-schema-org/community#429 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Please let me know if this is now clearer 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly speaking I still find very confusing dedicating a full opening section of our CoC to the IETF ways of working when we are no longer members of the IETF. It appears to me like we are reluctant to move forward with our CoC evolution as part of the OpenJS Foundation. I think 99% our Community don't know what is the IETF BCP 54 or RFC7154 because there were not part of the spec editing discussions.
I suggest to move this whole section at the bottom of the CoC after "The OpenJS Foundation Code of Conduct"
This is the same thinking I shared in the OCWM but It seems I am the only one with this thinking, therefore I am approving the PR to move forward.