You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to adopt the Contributor Covenant CoC.
In addition, we want to mention we also subscribe to the principals found in IETF BCP 54 / RFC 7154.
Violations should be reported to me at a specific email, initially. We will look to form a review comittee later. (Also note, if/when we joing the OpenJS Foundation, there is an escalation process.)
We want to communicate our CoC clearly.
It should be in our .github repo community health file, which then appears on the side for new users and under text areas for existing users. We may also want to create a default Issue and PR template. We should also communicate our CoC on our website and on the slack server (announcement and greetbot).
We should consider a template to report potential violations, making sure we gather the minimal information.
Actions:
Create a .github repo
Add a PR to the .github repo that includes the Contributor Covenant CoC. (Should mention BCP 54 and highlight specifics.) (Add initial Code of Conduct .github#1)
Make sure CoC document includes note about how if we join the OpenJS Foundation, there is a clear path to escalation
Please let me know if there's anything, including actions, that I've missed, and I'll update this post accordingly.
- [ ] Create an Issue and PR template that includes key points and points to CoC
This is not required, as it will be highlighted in a box on the right automatically first time, and always under the text area.
The text was updated successfully, but these errors were encountered:
Relating to #2
We want to adopt the Contributor Covenant CoC.
In addition, we want to mention we also subscribe to the principals found in IETF BCP 54 / RFC 7154.
Violations should be reported to me at a specific email, initially. We will look to form a review comittee later. (Also note, if/when we joing the OpenJS Foundation, there is an escalation process.)
We want to communicate our CoC clearly.
It should be in our .github repo community health file, which then appears on the side for new users and under text areas for existing users. We may also want to create a default Issue and PR template. We should also communicate our CoC on our website and on the slack server (announcement and greetbot).
We should consider a template to report potential violations, making sure we gather the minimal information.
Actions:
Please let me know if there's anything, including actions, that I've missed, and I'll update this post accordingly.
- [ ] Create an Issue and PR template that includes key points and points to CoCThis is not required, as it will be highlighted in a box on the right automatically first time, and always under the text area.
The text was updated successfully, but these errors were encountered: