Skip to content
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.

Sign up for GitHub

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

CoC/Bylaws changes #99

Merged
merged 5 commits into from
Dec 21, 2018
Merged

CoC/Bylaws changes #99

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ebb666a
Merge pull request #9 from rcos/master
kburk1997 Dec 19, 2018
b764a17
resolve issues #98, #87, #88, #89
kburk1997 Dec 19, 2018
af3a34c
correct capitalization
kburk1997 Dec 19, 2018
87a6d37
clarification on grade penalties
kburk1997 Dec 19, 2018
87aca1b
add suggested changes from Ada and Varun
kburk1997 Dec 21, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 28 additions & 5 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, I like having the summary at the beginning.

* [Be respectful and inclusive](#be-respectful-and-inclusive).
* [Give and be welcoming to constructive feedback](#give-and-be-welcoming-to-constructive-feedback).
* [Focus on what is best for the RCOS community](#focus-on-what-is-best-for-the-rcos-community).
* Do not engage in any [unacceptable behaviors](#unacceptable-behaviors).
* At any point, you may [report CoC violations](#reporting-incidents) to our coordinators and faculty advisors.
* [Project maintainers](#project-maintainer-responsibilities) should be mindful of the Code of Conduct.
* [RPI-specific policies](#rpi-specific-policies) are outlined in our Bylaws.

## Guidelines

### 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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

* In general, avoiding any language that could be considered offensive towards marginalized groups
* **Respect people's differences.** Examples include:
* Being welcoming towards new members
Expand All @@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍


* **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
* Respecting other people's boundaries and privacy
* **Acknowledge and learn from mistakes**. This includes:
* Working to eliminate unconscious bias
* Being aware of how your actions affect others
* Correcting any harmful behavior going forward

## Unacceptable Behaviors

Examples of unacceptable behaviors include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Public or private harassment as defined [here](https://handbook.rcos.io/#/community/harassment_guidelines)
* Publishing others’ private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Reporting Incidents

At any point, you may report instances of CoC violations to RCOS faculty at <[email protected]>. You, as well as any other witnesses, have the right to remain anonymous to the rest of the RCOS community.
At any point, you may report instances of CoC violations to our [coordinators](https://rcos.github.io/rcos-handbook/#/coordinating/README) and [faculty advisors](https://handbook.rcos.io/#/coordinating/faculty) at <[email protected]>. You, as well as any other witnesses, have the right to remain anonymous to the rest of the RCOS community.

If you are uncomfortable reporting to the coordinators for any reason, you may reach out to a faculty advisor directly via our [Slack](https://rcos.slack.com/).

## Project Maintainer Responsibilities
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. In the case of contributors external to RPI and/or RCOS, temporary or permanent bans may occur. RPI-specific policies are outlined below.

## RPI-Specific Policies
RPI-specific policies, including consequences for violating the RCOS Code of Conduct in the context of RCOS at RPI, can be found under our [Bylaws](docs/community/bylaws.md). Please review these if you are a student, mentor, or coordinator at RPI, as you will also be expected to follow these bylaws.
RPI-specific policies, including consequences for violating the RCOS Code of Conduct in the context of RCOS at RPI, can be found under our [Bylaws](https://rcos.github.io/rcos-handbook/#/community/bylaws). Please review these if you are a student, mentor, or coordinator at RPI, as you will also be expected to follow these bylaws.

## License and Attribution

This Code of Conduct has been adapted with modifications from the [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) and the [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/). This Code of Conduct, like everything RCOS does, is open source and can be found in our [intro](https://github.com/rcos/intro) repository.
This Code of Conduct has been adapted with modifications from the [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) and the [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/). This Code of Conduct, like everything RCOS does, is open source and can be found in our [rcos-handbook](https://github.com/rcos/rcos-handbook) repository.
23 changes: 22 additions & 1 deletion docs/community/CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
* [Be respectful and inclusive](#be-respectful-and-inclusive).
* [Give and be welcoming to constructive feedback](#give-and-be-welcoming-to-constructive-feedback).
* [Focus on what is best for the RCOS community](#focus-on-what-is-best-for-the-rcos-community).
* Do not engage in any [unacceptable behaviors](#unacceptable-behaviors).
* At any point, you may [report CoC violations](#reporting-incidents) to our coordinators and faculty advisors.
* [Project maintainers](#project-maintainer-responsibilities) should be mindful of the Code of Conduct.
* [RPI-specific policies](#rpi-specific-policies) are outlined in our Bylaws.

## Guidelines

### 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)
* In general, avoiding any language that could be considered offensive towards marginalized groups
* **Respect people's differences.** Examples include:
* Being welcoming towards new members
Expand All @@ -19,7 +29,18 @@ 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.

### Focus on what is best for the RCOS community

* **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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or "step forward" of you are one who tends to be more quiet.

* Respecting other people's boundaries and privacy
* **Acknowledge and learn from mistakes**. This includes:
* Working to eliminate unconscious bias
* Being aware of how your actions affect others
* Correcting any harmful behavior going forward

## Unacceptable Behaviors

Expand Down
61 changes: 51 additions & 10 deletions docs/community/bylaws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

Our Bylaws are an extension of our [Code of Conduct](community/CODE_OF_CONDUCT.md). The Bylaws apply to RCOS meetings at RPI, including large group and small group meetings as well as bonus sessions, casual coding sessions, and any project meetings unless otherwise noted.

## Summary
- Do not distribute attendance codes to people not attending the session. ([Attendance Codes](#attendance-codes))
- Respect speakers by not talking or making excessive noise while they are speaking. ([Noise](#noise))
- Be mindful of your audience when choosing a topic for your talk. ([Talks/Sensitive Topics](#sensitive-topics))
- Please keep any messages you send to a live demo professional and appropriate. ([Talks/Live Demos](#live-demos))
- You may use electronics during large group talks as long as you respect the people around you. ([Large Group/Electronics](#electronics))
- Some speakers may also ask that you close all laptops unless you are following along or taking notes.
- If you are an RPI student, you are also expected to comply with the [RPI Student Handbook](https://sexualviolence.rpi.edu/sites/default/files/Rensselaer%20Handbook%20of%20Student%20Rights%20%26%20Responsibilities%2C%20November%202017.pdf).
- Appropriate [consequences](#consequences-of-code-of-conduct-violations) may follow if you violate the Code of Conduct, Bylaws, or RPI Student Handbook.

## Attendance Codes
Attendance codes are given during all RCOS small group, large group, and bonus sessions. When the attendance code is delivered, go to http://rcos.io, click "Attend", and enter the attendance code so you can be marked as present for the current session.

Expand All @@ -12,12 +22,13 @@ If you know in advance you will not be able to make an RCOS meeting, or unforese
## Noise
An important part of RCOS is being able to hear from both fellow RCOS members and guest speakers. We ask that you please refrain from talking or making excessive noise while a speaker is talking as it can be disruptive to the speaker and to your peers.

## During Large Group
During our large group sessions, we have the following policies.
## Talks

### Sensitive Topics

### 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the most recent commit


Please keep in mind that RCOS large group sessions are mandatory for all students currently in RCOS. Presentations containing detailed discussion of sensitive, upsetting, or controversial topics without warning can create an especially hostile environment when this attendance requirement is considered.
Presentations containing detailed discussion of sensitive, upsetting, or controversial topics without warning can create an especially hostile environment when this attendance requirement is considered.

Presentations should not include any content that violates our [Code of Conduct](community/CODE_OF_CONDUCT) or contains:
- Graphic violence or descriptions of violence
Expand All @@ -27,7 +38,14 @@ Presentations should not include any content that violates our [Code of Conduct]

If you're unsure about whether or not your talk conforms to the above guidelines, please reach out to a mentor or coordinator to discuss.

### 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are also thinking of having a talk review process to mitigate this

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See issues #100


## Large Group
During our large group sessions, we have the following policies.

### Electronics
RCOS likes to maintain a culture of freedom. If you choose to use your laptop or mobile device during large group presentations, you may do so as long as you are mindful of the people around you. This includes:

* Muting all audio
Expand All @@ -36,22 +54,45 @@ RCOS likes to maintain a culture of freedom. If you choose to use your laptop or
* Keeping mobile devices on "Silent" or "Vibrate"
* Using a quiet keyboard instead of a loud keyboard

In addition, some speakers may ask audience members to close all laptops and put away all mobile devices. If a speaker does so, please respect their request.
In addition, some speakers may ask audience members to put away all mobile devices and close all laptops unless they are using them to actively follow along or take notes. If a speaker does so, please respect their request.

If you absolutely must take a phone call, you can exit the lecture hall to make/take a phone call. If you need to call emergency services for any reason, you may remain in the room while you make the call.

If you use assistive technology due to a documented disability or injury, or you use a medical device that may make noise or looks similar in appearance to a mobile phone or laptop, **please touch base with a faculty member ASAP**. This will remain confidential.

## Consequences of Code of Conduct Violations
If you violate the RCOS Community Code of Conduct or Bylaws, appropriate consequences will follow at the discretion of faculty. These may include:
If you violate the RCOS Community Code of Conduct or Bylaws, appropriate consequences will follow at the discretion of faculty. In addition, if you are an RPI student, you must also comply with all policies in the RPI Student Handbook

### Short Version
Consequences may include:
- Verbal, Slack, or written warnings
- Requests to edit or delete project material
- Removal from sessions
- Grade penalties
- Early ending of a talk or session
- Removal from RCOS with a failing grade for the semester
- Loss of mentorship privileges
- Referral to Dean of Students for violations of [RPI Student Handbook](https://sexualviolence.rpi.edu/sites/default/files/Rensselaer%20Handbook%20of%20Student%20Rights%20%26%20Responsibilities%2C%20November%202017.pdf)
- Any other consequences that faculty advisors deem appropriate

See the long version below for details on what these penalties entail.

### Long Version

Consequences may include:

* A verbal or Slack warning from a mentor or coordinator
* A written warning from a faculty advisor
* A request to edit or delete any project material that violates the Code of Conduct. Project material includes, but is not limited to, status updates, blog posts, code, comments, issues, pull requests, milestones, wiki pages, static websites, graphics, social media posts, etc.
* A request to edit or delete any project material that violates the Code of Conduct
* Project material includes, but is not limited to, status updates, blog posts, code, comments, issues, pull requests, milestones, wiki pages, static websites, graphics, social media posts, etc.
* Failure to comply with this request may result in grade penalties as outlined below.
* Grade penalties on deliverables (including status updates, presentations, open source contributions, etc.) that contain inappropriate, unprofessional, or harassing content
* TODO: flesh out what grade penalties are appropriate
* For smaller deliverables such as status updates, this can result in losing half or all credit on the deliverable.
* For larger deliverables such as presentations, this grade penalty can be up to 1 full letter grade.
* If your large group talk or bonus session violates the Code of Conduct, your talk may be ended early and your slides will not be published to the #slides channel.
* If the violation occurred at an RCOS event or meeting, you may be removed from the event or meeting. This will be marked as an unexcused absence regardless of whether or not you already entered an attendance code, and you will not be able to make up this absence by attending a bonus session.
* In severe and repeated violations, you may be removed from RCOS entirely.
* If you are taking RCOS for credit, you will receive a failing grade for the semester.
* If you are currently a mentor, your mentorship position will be terminated immediately and you will be ineligible to mentor in future semesters. The same rule applies to coordinators.
* If you have violated the [RPI Student Handbook](https://sexualviolence.rpi.edu/sites/default/files/Rensselaer%20Handbook%20of%20Student%20Rights%20%26%20Responsibilities%2C%20November%202017.pdf) along with our Code of Conduct and/or Bylaws, you may also be referred to the Dean of Students.

Please note that the above list is not exhaustive and additional consequences may follow as appropriate.
22 changes: 21 additions & 1 deletion docs/community/code_of_conduct_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,20 @@ In the interest of fostering an open and welcoming environment, [your project] p

This Code of Conduct applies to all [your project]-affiliated activity online and offline.

## Summary
* [Be respectful and inclusive](#be-respectful-and-inclusive).
* [Give and be welcoming to constructive feedback](#give-and-be-welcoming-to-constructive-feedback).
* [Focus on what is best for the [Your Project] community](#focus-on-what-is-best-for-the-community).
* Do not engage in any [unacceptable behaviors](#unacceptable-behaviors).
* At any point, you may [report CoC violations](#reporting-incidents) to our coordinators and faculty advisors.
* [Project maintainers](#project-maintainer-responsibilities) should be mindful of the Code of Conduct.
* Summarize any [project-specific guidelines](#[your-project]-specific-guidelines) (if any) here.

## Guidelines
### 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)
* in general, avoiding any language that could be considered offensive towards marginalized groups
* **Respect people's differences.** Examples include:
* Being welcoming towards new members
Expand All @@ -19,7 +28,18 @@ This Code of Conduct applies to all [your project]-affiliated activity online an
* **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 project lead ASAP.

### Focus on what is best for the community

* **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
* Respecting other people's boundaries and privacy
* **Acknowledge and learn from mistakes**. This includes:
* Working to eliminate unconscious bias
* Being aware of how your actions affect others
* Correcting any harmful behavior going forward

## Unacceptable Behaviors

Expand Down
Loading