doc: update to reflect planned CoC#147
Conversation
Update to reflect the planned CoC process and emails. Once this in place we'll ask that projects refer to it as the master CoC that applies to their project in each of the places they refer to a CoC.
|
One thing I wondered about was whether this might be better in a separate CoC repo, but since it is governed by the CPC I left it here. |
keywordnew
left a comment
keywordnew
left a comment
There was a problem hiding this comment.
tiny nit. Otherwise, LGTM. Thank you!
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
|
@Trott thanks for catching that, fixed. |
|
|
||
| # Escalation | ||
|
|
||
| The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a cross-foundation 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@openjsf.org`. |
There was a problem hiding this comment.
cross-foundation? That suggests spanning multiple foundations (to me, at least). Do you mean cross-project (spanning multiple projects?) and/or foundation-spanning (spanning the entire foundation)?
There was a problem hiding this comment.
@Trott, how about foundation-wide ?
Yes, that's better than my suggested foundation-spanning. 👍
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
|
@Trott addressed comment |
| the section on Escalation when required. | ||
|
|
||
| ## Foundation Spaces | ||
| For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `report@openjsf.org`. The CrossProjectCouncil (CPC) is responsible for managing these reports and commits to: |
There was a problem hiding this comment.
CrossProjectCouncil reads funny to me. Should it be one word? I prefer simply Cross Project Council
There was a problem hiding this comment.
nope, not sure why it ended up that way, fixing.
brianwarner
left a comment
brianwarner
left a comment
There was a problem hiding this comment.
Minor but important change: the lists are on the "@lists.openjsf.org" subdomain. So the two key lists here are "report@lists.openjsf.org" and "coc-escalation@openjsf.org".
|
You only show lists being part of report not coc-escalation is that right? |
|
@brianwarner ^^ |
|
Argh, sorry, having a hard time computering today. Yes, both should be @lists.openjsf.org. So the correct addresses are: "report@lists.openjsf.org" and "coc-escalation@lists.openjsf.org" |
|
@brianwarner emails updated. |
|
Landed as it had enough reviews and we agreed it was ready. We should move to admin repo once it is opened and then ask projects to update to refer to it. |
Update to reflect the planned CoC process and emails. Once this in place we'll ask that projects refer to it as the master CoC that applies to their project in each of the places they refer to a CoC. * squash: minor fixups * squash: accept review suggestions Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com> * squash: accept suggestions Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com> * squash: accept suggestions Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com> * squash: address comments * squash: address comments * squash: update emails
Update to reflect the planned CoC process and emails. Once this in place we'll ask that projects refer to it as the master CoC that applies to their project in each of the places they refer to a CoC. * squash: minor fixups * squash: accept review suggestions Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com> * squash: accept suggestions Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com> * squash: accept suggestions Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com> * squash: address comments * squash: address comments * squash: update emails
9 participants
Update to reflect the planned CoC process and
emails.
Once this in place we'll ask that projects refer to it
as the master CoC that applies to their project in each of the
places they refer to a CoC.