Meeting on January 30th

Attendees

• Allan Day
• Rosanna Yuen
• Nuritzi Sanchez
• Marina Zhurakhinskaya

Agenda:

CoC planning topics: Reporting guidelines (longer version) Response guidelines

Notes:

Discussion of detailed reporting guidelines, such as PyCon UK has, that asks people who experienced or observed harassment, to provide the details in writing, possibly with the help of designated report takers

• Allan: it seems impersonal, makes the written report the focus, not the help someone needs

• Marina: it's possible this is suggested because it's better to have a written report written by an individual how is bringing a complaint, rather than report taker; https://frameshiftconsultingdotcom.files.wordpress.com/2016/03/conferenceincidentresponseguide.pdf has more in "Receiving harassment reports" section

• Allan: how do we want to proceed here?
• Marina: generally providing options for people to either send something in in writing or find a designated report taker and, if possible, work with them to create a written report sounds good, and providing the types of information to consider including in the report is useful
• Nuritzi read Abstractions reporting guidelines, that had a good tone; agreement that we can use it as a starting point
• Allan: summary: we want to have a section on how to provide a report, should be supportive, friendly, talk about support available and steps that will be taken by the report taker; address concers reporter might have, such as privacy (quiet place, you can stay anonymous) and being able to bring someone along for support

* Rosanna: perhaps also mention something about being able to help them to cotact the authorities * Rosanna, Marina: provide the types of information the report should contain if someone is sending it in via e-mail

Discussion of responding to reports

• Allan: break it down into different steps of the process

• Marina: we can start with PyCon UK, and see if we want to augment it with anything from GUADEC CoCs and other CoCs, and also review the incident handling guide for anything else we want to mention (it appears that PyCon UK one is already based on it)

• Nuritzi: give scenarios and handling procedures, like in GUADEC 2016

• Nuritzi: say who this page is for, like PyCon UK

• Allan: do we want to make response guidelines public? codes of conduct differ on that
• Rosanna: people can end up reading a lot of information
• Nuritzi: we can make the sections well-identified and say who they are for
• Rosanna: bullets might be intimidating
• Nuritzi: we can keep the tone friendly and empowering
• Allan: start with structure and high-level vs. each section; agreement to start with structure and high-level General

• GUADEC 2017 organizers should consider using one of prior GUADEC CoCs, with any changes that make sense to them

• Still try to have something proposed before bidding process for GUADEC 2018 opens
• Someone should start drafting sections we already discussed; discuss this more at the next meeting