-
Notifications
You must be signed in to change notification settings - Fork 81
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
docs: Add Code of Conduct #455
Conversation
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.
🎉
CODE_OF_CONDUCT.md
Outdated
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported to the community leaders responsible for enforcement at | ||
[INSERT CONTACT METHOD]. |
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.
This needs to get updated with a contact method. As part of the TDR-0073 approval I'll be setting up an email alias to receive these. However, if you have a contact address for the React USWDS project, feel free to use that.
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.
Thanks for tagging me, @haworku!
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.
@brainsik for sure! yep I had already filled in oss-coc@truss.works in
6aa4485. Can you ping in the oss slack channel when that is set up? We don't have an email address for the project so gonna let this PR sit open until that alias is created.
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.
Sorry I missed that. Will do!
Confirmed that oss-coc@truss.works is up |
The email address is setup, but we agreed to create docs about how to do the enforcement before publishing. That work is being tracked as InfraSec #174849673. |
Summary
Related Issues or PRs
closes #454
[This PR may have to hold until email alias is created and/or TDR is approved]