CoC/Bylaws changes #99
Conversation
merge into working branch
|
Per @vakrao's feedback:
|
|
Talk review process will be moved to #100, then we can worry about removing stuff from bylaws |
| @@ -3,11 +3,21 @@ In the interest of fostering an open and welcoming environment, RCOS pledges to | |||
|
|
|||
| The RCOS Community Code of Conduct applies to all RCOS activity and activity affiliated with any RCOS project online and offline. | |||
|
|
|||
| ## Summary | |||
There was a problem hiding this comment.
Nice, I like having the summary at the beginning.
docs/community/bylaws.md
Outdated
|
|
||
| ### Presentations on Sensitive Topics | ||
| Please keep in mind that RCOS large group sessions are mandatory for all students currently in RCOS, and representatives from external companies may also be attending. In addition, students are required to attend a certain number of bonus sessions and small group presentations. |
There was a problem hiding this comment.
This is a little awkward to read. I think the sentence In addition, students are required to attend a certain number of bonus sessions and small group presentations. should be moved to a more relevant subsection.
There was a problem hiding this comment.
See the most recent commit
|
|
||
| * **Show empathy towards other community members.** Examples include: | ||
| * Actively listening to other team members | ||
| * "Stepping back" and allowing others to participate when you feel that you are dominating a conversation |
There was a problem hiding this comment.
Or "step forward" of you are one who tends to be more quiet.
| ### Laptops/Mobile Devices | ||
| ### Live Demos | ||
|
|
||
| Live demos can provide a way to make otherwise dry talks very engaging, especially in a larger setting. However, inappropriate content sent to the live demo may reflect poorly on the speaker and RCOS as a whole. Thus, we ask that the audience comply with the Code of Conduct and Bylaws in any content they send to a live demo. |
There was a problem hiding this comment.
I think we should request that live demos are well prepared and practiced. Sometimes a live demo can be a good way of putting off preparing :P
There was a problem hiding this comment.
We are also thinking of having a talk review process to mitigate this
| ### Be respectful and inclusive | ||
| * **Use inclusive language.** This includes: | ||
| * Using [gender-neutral or non-gendered language](http://geekfeminism.wikia.com/wiki/Nonsexist_language) where possible | ||
| * When referring to community members, using their preferred pronouns | ||
| * When referring to community members, using their [correct pronouns](https://www.brynmawr.edu/sites/default/files/asking-for-name-and-pronouns.pdf) |
| @@ -19,28 +29,41 @@ The RCOS Community Code of Conduct applies to all RCOS activity and activity aff | |||
| * **Be constructive and respectful** when giving others feedback. This includes: | |||
| * Only giving feedback when solicited (e.g. mock presentation, questions section of presentation, request for code review, pull request, etc.) | |||
| * Keeping all feedback constructive, objective and impersonal | |||
| * **Be accepting of constructive criticism**. If you feel that any critiques are overly harsh, excessive, or harassing, contact a coordinator ASAP. | |||
There was a problem hiding this comment.
Some suggestions from Varun:
- delete "Only giving feedback when solicited (e.g. mock presentation, questions section of presentation, request for code review, pull request, etc.)" , we want to encourage project critiques
|
|
||
| ### Focus on what is best for the RCOS community |
|
Merging with approval from Varun |
Resolves Issue: #87, #88, #89, #98
Changes in this pull request: