Update our Code of Conduct to reflect OpenJS Foundation Code of Conduct #5
Conversation
Fix escalation anchor link for OpenJSF CoC
CODE_OF_CONDUCT.md
Outdated
| > 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.
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.
| > 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. | |
| > The OpenJS Foundation maintains a [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/conduct/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. |
Fix broken link to OpenJSF CoC requirements doc
|
We probably need to update a bunch of badges to reflect this kind of thing, right? Right now all the repos just mention Contributor Covenant. |
|
Well, we subscribe to the CoC proper in full, but define a few extras. What do you think we need to do? (genuine question) |
|
It's I guess not the worst thing in the world to leave as-is. Today yeah there's no practical difference though maybe someone who sees the badge and is familiar with the contributor covenant will at some point be surprised we in fact expect them to comply with more than that. Perhaps an alternative is just a more generic badge, e.g.: But I don't feel strongly if we're lazy and leave it. |
|
I'd be fine with that and maybe suggest in addition "(CC 2.1+)". Although I don't know if that has the connotation I'd want it to. |
|
|
||
| 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 |
There was a problem hiding this comment.
I'd suggest to remove entirely this section: "IETF Guidelines for Conduct"
There was a problem hiding this comment.
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.
Updated. Please let me know if this is now clearer 🙏
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 dont 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.
Fixes json-schema-org/community#163
Moved modifications to the Contributor Covenant Code of Conduct to their own sections.
Added details about the OpenJS Foundation Code of Conduct.
Specified that the IETF BCP 54 are taken a guide only.