Code of Conduct
This document contains text adapted from the DISE safe space statement, Philip SS Howard’s EDER 619 course guidelines, and the NordicJS COC, and the TorontoJS code of conduct.
We are committed to nurturing a space where students, post-docs, lecturers, professors and members of the community can all engage in the exchange of ideas and dialogue, without fear of being made to feel unwelcome or unsafe on account of biological sex, sexual orientation, gender identity or expression, race/ethnicity, religion, linguistic and cultural background, age, disability, or any other aspect integral to one's personhood. We therefore recognize our responsibility, both individual and collective, to strive to establish and maintain an environment wherein all interactions are based on empathy and mutual respect for the person, acknowledging differences of perspectives, free from judgment, censure, and/or stigma.
The Social Studies of Computing group is a space for teaching and learning. We are committed to creating authentic opportunities for learning. Our view of learning is conceived as a social process that is co-constructed between/amongst faculty and students. In order to foster a positive environment for learning, we are expected to demonstrate awareness and respect of others. We are expected to be accountable to ourselves and others and to be engaged, collegial and accessible. By doing so, we are more fully able to share together in the types of critical dialogue, creative thinking and reflective practice that help us grow as scholars and as people.
0. Land Expectations
Our lab activities take place on Dish With One Spoon territory, which sets forth three basic rules for inhabiting this land:
- Take only what you need
- Leave some for everybody else
- Keep it clean
We expect settler participants and lab members to behave in accordance with the Indigenous law of this land. The principles of the The Dish With One Spoon covenant can be applied on mulitple levels to our lab activities, from a very literal interpretation to interpretations which are more high level:
- How to share the physical space in which lab activities take place (e.g. keep the lab clean, don’t take up more space than you need, share generously)
- How to share the resources within the lab (e.g. budget for travel)
- To value sustainability in one’s research agenda (e.g. doing research on how to mitigate computer science’s environmental impacts, reducing the environmental effects of conference travel by favouring train travel over air travel, incorporating Indigenous scholarship)
- How to behave as a settler on colonized land: to appreciate the need to share (return) resources to Indigenous groups in order to foster good relations.
1. Discussion Guidelines
This is a space where discussions about sexism, ableism, racism, colonialism, homophobia, cisnormativity, and other forms of oppression are regularly discussed and learnt about. To ensure a learning community where critical discussions about oppression can be safely and meaningfully discussed, we ask participants to:
Speak authentically
Appreciate that no question is ridiculous
Intend no harm
Honour each other’s words and truths
Honour silence
Honour all emotions – including anger
Remember that anti-oppression requires a long-term growth mindset
Embrace discomfort
Gracefully accepting constructive criticism
2. Accessibility
We strive to be an accessible space and to provide accessible events. All our events and spaces are wheelchair accessible and scent-free environments.
Accessibility is a collective effort and we expect:
Participants to respect the scent-free environment: refrain from wearing perfume, cologne, body spray, and heavily scented hygiene products
Participants to avoid unwelcoming behaviour, such as:
- Blatant -isms: saying things which are explicitly sexist, racist, ableist, ageist, homophobic, transphobic, intersexist, ethnocentric, islamophobic, antisemitic, and so on.
Avoiding casual bigotry. For example: avoiding ableist terms such as “crazy”, “dumb”, “insane” or “lame”. A primer on inclusive language surrounding disability is here.
- Misgendering trans, non-binary, and intersex individuals, or implying their genders are inferior (e.g. trans women are “female-identifying” rather than female)
- Discriminatory jokes
- Sexualizing groups of people
- Berating or demeaning people for a lack of knowledge
Participants to make a good-faith effort to use inclusive language, such as:
- Favouring gender-neutral language where suitable (e.g. “people” rather than “men and women”; “they” rather than “he/she”)
- When referring to an individual or group of people, if they have explicitly stated a preference for how they would like to be referred, to respect this (e.g. identity-first vs people-first disability language, Latine/Latin@/Latino/Latinx/Hispanic/Chicano/etc, black vs Black, pansexual vs bisexual)
- If somebody admits to you that they are new or unfamiliar with a concept, to frame this as an opportunity for learning rather than a deficiency
Participants to make a good-faith effort to provide image descriptions, audio transcripts, and video captions, as appropriate
Participants to refrain from using light strobing effects; if sharing videos which contain light strobing effects, to provide a warning
Participants to make a good-faith effort to provide content warnings as judged appropriate; e.g. if the concerning content is not clear from the material’s title
Participants to make a good-faith effort to keep learning about accessibility, inclusive language, and intersecting forms of oppression. No list of accessibility requirements can ever be complete; a commitment to learning and growing is what is more important.
If somebody fails to meet these expectations, see “When Something Happens”.
3. Harassment
We are dedicated in providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, or religion.
We do not tolerate harassment. Harassment includes, but is not limited to:
Deliberate intimidation, stalking, or following
Harassing photography or recording
Sustained disruption of talks or other events
Inappropriate physical contact
Unwelcome sexual attention
Deliberate misgendering of trans, queer, nonbinary & intersex partipants
Advocating for, or encouraging, any of the above behaviour
4. When Something Happens
If you see a Code of Conduct violation, follow these steps:
Let the person know that what they did is not appropriate, explain constructively to the person why it was inappropriate, and ask them to stop. For tips on how to do this, see the next section.
If you do not feel safe doing so, proceed to step 3.
That person should immediately stop the behavior and correct the issue. If that person is you, see the section “If You Screwed Up”.
If this does not happen, or if you are uncomfortable speaking up, contact the group’s manager (Prof Elizabeth Patitsas), or another professor connected with the lab, as soon as possible
A professor will immediately address the issue and take further action.
You can contact Prof Patitsas via keybase (@patitsas), email (elizabeth.patitsas@mcgill.ca), twitter DM (@patitsel), or SMS/Signal (if you have her number).
If for whatever reason you'd prefer to contact a different professor, you can contact Prof McMahan via email (peter.mcmahan@mcgill.ca) or keybase (@mcmahan).
4.1 Turning An Inappropriate Situation Into a Teachable Moment
So you’re in a situation where you’re witnessing a Code of Conduct violation.
First off, consider your own safety. If talking to the individual(s) would put your safety at risk, focus on your safety. Extract yourself from the situation, and proceed to step 3.
If you are safe, next remember the bystander effect. If you’re not the only witness, it could be everybody is waiting for somebody else to speak up. Assume it’s up to you to speak up.
Next you could be stuck on what to say. If it’s a situation you’ve never encountered before you could be at a loss for something situation specific. Here are some general-purpose responses that you can default to:
“Why did you say that?”
“Just so you know when you said <thing>, I felt <feeling> because <reason>. In the future could you instead <do/say alternate thing>?”
More examples of general-purpose reactions: http://www.racialequityvtnea.org/wp-content/uploads/2018/09/Interrupting-Bias_-Calling-Out-vs.-Calling-In-REVISED-Aug-2018-1.pdf
An unfortunate reality is that marginalized people have to do a disproportionate amount of teaching others about their marginalization. After the situation happened, it is recommended that you tell somebody you trust about it so you can debrief and process your emotions.If you tried to respond appropriately, but felt you failed to do so, proceed to step 3.
4.2 If You Screwed Up
Francesca Ramsey has an excellent video on how productively react and how to apologize: https://www.youtube.com/watch?v=C8xJXKYL8pU
Summary:
Remember to listen --- your intent was presumably good, but here what matters is impact, not intent, and that means listening to what the impact was.
An effective apology requires two parts:
Take responsibility for what you’ve done
Make a commitment to change the behaviour
And she recommends two additional steps:
Say thank you to the person who brought your mistake to your attention
“Don’t just say it, do it” - change your behaviour
5. Professional Norms in Lab Meetings
Further details on professional norms for lab meetings ("standup") are provided in the lab handbook.
6. Attribution
As noted upfront, this document is a combination of multiple sources. Some sources have been copied verbatim. In-text citations were not provided to ensure flow of content, so here we would like to explicitly credit which parts came from where:
- The first two paragraphs originated by copying directly from the DISE Safe Space. The first paragraph remains a copy; the second paragraph was modified for this context.
- The section on Discussion Guidelines originated by directly copying Philip SS Howard’s discussion guidelines for EDER 617. The opening text was modified slightly, the list was added to (growth mindset & accepting criticism), and the Maya Angelou quote & discussion of it were added at the end. The point on gracefully accepting criticism came from the TorontoJS code of conduct (COC).
- The section on Harassment and When Something Happens originated by copying those sections from the NordicJS code of conduct, with minor modifications for the university setting. The NordicJS COC was based on the Code of Conducts of JSConf AU which is based on The Geek Feminism wiki, the work of Valerie Aurora and Conference Code of Conduct.
- Language on unwelcoming behaviour was adapted from the TorontoJS COC.