Meeting on October 10

Attendees: Benjamin, Nuritzi, Meg, Rosanna, Marina, Ben

Notes

  • A lot of research already done by GF

  • We particularly want to focus on how different CoCs use specific examples and enforcement policies

  • The criteria on GF wiki are about community CoCs, but they apply to event ones and people found them helpful in evaluation

  • Useful for each team member to have an overview of existing CoCs - not captured by reading one or two each

  • We should create a framework for identifying which CoCs we like, as well as which parts of them we like. That way we can possibly either adopt someone else's wholesale, or cherrypick to construct our own

  • Maybe we can identify CoCs that we have read and liked and share those with the group

  • The existing list of CoCs in our spreadsheet is short and misses a lot of examples - will need to be elaborated if we want to identify ones to base ours on

  • Note that event codes of conduct on the GF wiki are called anti-harassment policies and are listed at http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Adoption , while community codes of conduct are evaluated at http://geekfeminism.wikia.com/wiki/Code_of_conduct_evaluations

  • What aspects of a CoC are we interested in/think are important
  • What nuance do we like about codes of conduct? What codes of conduct feel welcoming and present a community as a positive place, as well as provide specifics on inappriate behavior and enforcement? How easy is the code of conduct to understand?

Goals for our CoC

  • Tone: we want to establish GNOME as being welcoming and also say that we won't tolerate bad behavior
  • Make sure it's written in a way that's easy to understand
  • Be understandable for all the different cultures and non-native speakers
  • Making sure that we have an enforcement policy and make sure people know how to handle even small offenses

What are we protecting members from?

  • A lot of CoCs are protecting against "harrassment" def: aggressive pressure or intimidation. Should we include a different term to protect attendees more broadly?

  • "Bad behavior" - ??? Is that the term that we want to use? "Unacceptable behavior"? When you call it harassment, it seems that there is intention in it. However, harassing behavior might not be directed at anyone individually, it might be a joke/image that is harassing to some people by making them feel excluded/uncomfortable.

  • CoCs perform many different roles and have different audiences. Need to have a thorough account of these if we are going to have a discussion of roles.

QUESTION

  • Photo policy - is this a part of the event CoC? What are the laws in different countries that might affect it? Some people might appreciate having an area to sit in, where they will not be in photos.

NEXT STEPS

  • find CoCs that have aspects we like and note those, include specific examples and write your name next to your additions.

  • create collection of resources - for each aspect a list of excerpts on the wiki (e.g. wording, tone, examples, etc).

  • each person in the CoC working group should identify their favorite CoCs

  • add research to: https://wiki.gnome.org/Diversity/CoCWorkingGroup/Resources/CoCs/Review

  • each person finds and reviews at least 3 codes of conduct and presents findings at next session

Updated Timeline

  • Present the issue, process proposal, and solicit initial input from the Board - August 16th
  • Presenting the issue and soliciting initial input (hopes and thoughts) from the community (send an email to the Foundation List). Invite people to become core and support members. - DONE September 12 (initially planned September 6)
  • Research code of conduct resources and other codes of conduct by other groups, understand legal implications - (initially planned by October 10)
  • Draft a standard event code of conduct and share with the community for feedback - by October 28
  • Revise the standard event code and summarize feedback from the community, share with the Board - by November 15
  • Feedback from Board - by December 12
  • Revision of draft presented to the board - by January 16
  • Voted on by the Board - (hard deadline by March 15th)

Diversity/CoCWorkingGroup/Minutes/20161010 (last edited 2016-10-24 05:11:23 by Nuritzi Sanchez)