-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Document Use - Encouraging inclusive behaviors #922
base: release
Are you sure you want to change the base?
Conversation
Took a first attempt at what instructions might be around encouraged behaviors. NOTE: I included two links to resources I use/and one I have built as an example of types of content that may go there. You may have goto documents that are a better fit.
@@ -28,6 +28,12 @@ These resources may be helpful in preparing for enforcement discussions: | |||
- [jQuery Foundation Code of Conduct Enforcement Manual](https://js.foundation/community/code-of-conduct/enforcement) | |||
- [How Mozilla is Making Code of Conduct Enforcement Real - and Scaling It](https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415) | |||
|
|||
It's equally as important to consider the opportunity of this document as a driver of positive change for discussion, and action that are critical for building safe and inclusive communities. Some resources that might be helpful in leveraging this document for inclusive design: |
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.
"to consider this document…" and "for discussion and actions…"
What do you think?
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.
Yes, less wordy, more clear!
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.
OK, let me know when you've pushed the revision and I'll happily merge.
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.
Also, if you can DM me on twitter (@CoralineAda) I have something to share with you. Sorry, I know I follow you but I can't remember your handle!
@@ -28,6 +28,12 @@ These resources may be helpful in preparing for enforcement discussions: | |||
- [jQuery Foundation Code of Conduct Enforcement Manual](https://js.foundation/community/code-of-conduct/enforcement) | |||
- [How Mozilla is Making Code of Conduct Enforcement Real - and Scaling It](https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415) | |||
|
|||
It's equally as important to consider the opportunity of this document as a driver of positive change for discussion, and action that are critical for building safe and inclusive communities. Some resources that might be helpful in leveraging this document for inclusive design: | |||
|
|||
- [CHAOSS Project Inclusive Leadership Metric](https://chaoss.community/metric-inclusive-leadership/) which encourages roles of influence designed with inclusion in mind. |
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.
Love these links.
Thanks for adding this suggestion, Emma! |
Hi how can I help
…On Mon, Oct 4, 2021, 15:36 yanlinmin ***@***.***> wrote:
***@***.**** approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#922 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASCUSZ3GTU7MHQLHQFYJ5CDUFIUARANCNFSM4YDNHUOQ>
.
|
Took a first attempt at what instructions might be around encouraged behaviors as per #910
NOTE: I included two links to resources I use/and one I have built as an example of types of content that may go there. You may have goto documents that are a better fit.