├── Attendee Procedure for incident handling.md ├── README.md ├── Staff Procedure for incident handling.md └── code_of_conduct.md /Attendee Procedure for incident handling.md: -------------------------------------------------------------------------------- 1 | # Attendee Procedure For Reporting Code of Conduct Incidents 2 | 3 | **If you believe someone is in physical danger**, consult with a volunteer or staff member for the appropriate crisis number, non-emergency number, or police number. 4 | 5 | If you believe someone has violated the [PyCon Code of Conduct](https://us.pycon.org/2018/about/code-of-conduct/), we encourage you to report it. If you are unsure whether the incident is a violation, or whether the space where it happened is covered by this Code of Conduct, we encourage you to still report it. We are fine with receiving reports where we decide to take no action for the sake of creating a safer space. 6 | 7 | During the conference you can make a report: 8 | 9 | - To a trained incident responder, who will be wearing brightly colored shirts. 10 | - Email **** 11 | - Contact **+1 (216) 208 7987** via voice call or SMS, to reach one of the lead incident responders listed below. 12 | 13 | In the event of a conflict of interest, you may directly contact any of the lead incident responders: 14 | 15 | * Sage Sharp 16 | * PyCon US - Incident Responder 17 | * 18 | * +1 (503) 384 8831 19 | * Ewa Jodlowska 20 | * Python Software Foundation - Director of Operations 21 | * 22 | * Ernest W. Durbin III 23 | * PyCon US - Conference Chair 24 | * 25 | * +1 (216) 202 4393 26 | 27 | ## Report Data 28 | 29 | If you make a report via email or phone, please include: 30 | 31 | * Your contact info (so we can get in touch with you if we need to follow up) 32 | * Date and time of the incident 33 | * Location of incident 34 | * Whether the incident is ongoing 35 | * Description of the incident 36 | * Identifying information of the reported person: name, physical appearance, height, clothing, voice accent, identifying badge information such as company name, ribbons, or badge number 37 | * Additional circumstances surrounding the incident 38 | * Other people involved in or witnesses to the incident and their contact information or description 39 | 40 | ## Confidentiality 41 | 42 | **All reports will be kept confidential**. When we discuss incidents with people who are reported, we will anonymize details as much as we can to protect reporter privacy. 43 | 44 | However, some incidents happen in one-on-one interactions, and even if the details are anonymized, the reported person may be able to guess who made the report. If you have concerns about retaliation or your personal safety, please note those in your report. We still encourage you to report, so that we can support you while keeping our conference attendees safe. In some cases, we can compile several anonymized reports into a pattern of behavior, and take action on that pattern. 45 | 46 | In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. 47 | 48 | ## Report Handling Procedure 49 | 50 | When you make a report to an incident responder, they will gather information about the incident according to the PyCon US [Staff Procedure For Incident Response](https://us.pycon.org/2018/about/code-of-conduct/staff-procedure/). 51 | 52 | After an incident responder takes the report, they will immediately consult with the lead incident responders (Sage Sharp, Ewa Jodlowska, and Ernest W. Durbin III). 53 | 54 | If the incident is ongoing and needs to be immediately addressed, any one of the lead incident responders may take appropriate action to ensure the safety of everyone involved. 55 | 56 | If the incident is less urgent, the three incident leads will meet within 24 hours to determine an appropriate response. Examples of possible incident responses are outlined in the PyCon US [Staff Procedure For Incident Response](https://us.pycon.org/2018/about/code-of-conduct/staff-procedure/). 57 | 58 | Before the conference, staff will have a mandatory meeting where incident response procedures will be outlined. After the conference, all incident responders will attend a debriefing session with the lead responders to discuss all incidents and determine any necessary follow-up actions. 59 | 60 | ## Following Up With Reporters 61 | 62 | Within one week of an incident report, the lead responders will follow up with the person who made the report and provided their contact information. The follow up may include: 63 | 64 | * An acknowledgment that the PyCon US lead responders discussed the situation 65 | * Whether or not the report was determined to be a violation of the Code of Conduct 66 | * What actions (if any) were taken to correcting the reporter behavior 67 | 68 | In some cases, the lead responders may need to ask additional questions about the incident in order to identify the reported person. 69 | 70 | ## Conflicts of Interest 71 | 72 | If an incident responder has a conflict of interest for a report, they will recuse themselves from the discussion and handling of the incident. The incident documentation will not be available to them, and they will excuse themselves from any conversations involving handling the incident. 73 | 74 | Should two out of the three lead incident responders need to recuse themselves, Naomi Ceder (PSF's chairperson) will step in as a lead incident responder. 75 | 76 | --- 77 | 78 | This procedure has been adapted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)”, the [Django Project reporting guidelines](https://www.djangoproject.com/conduct/reporting/) (CC BY 3.0) and has been updated by [Otter Tech](https://otter.technology/). 79 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | PyCon US Code of Conduct 2 | ======================== 3 | 4 | This repository holds the canonical version of the PyCon US Code of Conduct. 5 | 6 | No changes are final until approved by the PyCon Chair / Staff and versions in place for a given year will be clearly marked, the website contents on us.pycon.org will clearly state the revision of the documents posted. 7 | -------------------------------------------------------------------------------- /Staff Procedure for incident handling.md: -------------------------------------------------------------------------------- 1 | # Staff Procedure For Incident Response 2 | 3 | Be sure to have a good understanding of our Code of Conduct, which can be found here: 4 | 5 | - https://us.pycon.org/2018/about/code-of-conduct/ 6 | 7 | Also have a good understanding of what is expected from an attendee that wants to report an incident. These guidelines can be found here: 8 | 9 | - https://us.pycon.org/2018/about/code-of-conduct/attendee-procedure/ 10 | 11 | ### When taking an incident report: 12 | 13 | 1. Ask the reporter if they want to go to a quiet space 14 | - Room 23 on May 11, Room 25C May 12-13 15 | 1. Be an active listener and don't use judgement words 16 | 1. Ensure the reporter's safety 17 | 1. Seek additional emergency resources as needed (consult the volunteer guide) 18 | 1. Take down the report and ask any clarifying questions 19 | 1. Thank the reporter for reporting the incident 20 | 1. Call or SMS +1 (216) 208 7987 to report the incident to the lead incident responders listed below. 21 | 22 | In case of a conflict of interest, you can individually contact: 23 | 24 | * Sage Sharp 25 | * PyCon US - Incident Responder 26 | * 27 | * +1 (503) 384 8831 28 | * Ewa Jodlowska 29 | * Python Software Foundation - Director of Operations 30 | * 31 | * Ernest W. Durbin III 32 | * PyCon US - Conference Chair 33 | * 34 | * +1 (216) 202 4393 35 | 36 | ### While gathering information from the reporter: 37 | 38 | 1. Do not invite them to withdraw the incident report 39 | 1. Do not ask for their advice on how to immediately respond to the incident 40 | 1. Do not offer them input into the long-term response to the incident 41 | 1. Do not promise any particular response, since it may differ from the official response decided by the lead incident responders 42 | 43 | Try to get as much of the incident in written form by the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather include the following: 44 | 45 | * Current date and time 46 | * Date and time of the incident 47 | * Location of incident 48 | * Description of the incident 49 | * Identifying information of the reported person: name, physical appearance, height, clothing, voice accent, identifying badge information such as company name, ribbons, or badge number 50 | * Additional circumstances surrounding the incident 51 | * Reporter’s name and contact information. If the reporter wants to make an anonymous report, allow them to do so. If responding to the incident would reveal who reported the incident (e.g. a microaggression in one-on-one conversation) ask the reporter if they have safety concerns about this. 52 | * Other people involved in or witnesses to the incident and their contact information or description 53 | * Do not prompt the reporter for suggestions of how to handle the incident, but record their suggested responses if they offer them 54 | 55 | Assess whether an immediate response is necessary. This initial response is very important and will set the tone for PyCon. Depending on the severity/details of the incident, please follow these guidelines: 56 | 57 | * If there is any general threat to attendees or the safety of anyone including conference staff, consult the volunteer guide for emergency and crisis resources. 58 | * If everyone is presently physically safe, involve law enforcement or security only at a reporter’s request. 59 | * After taking the report, assess whether you need a lead incident responder to immediately respond to the incident. If so, ask the reporter to stay with you and call the lead incident responders. 60 | 61 | Respond to reporter needs. You can: 62 | 63 | * Thank the reporter for making the incident report 64 | * Reassure them that the incident report will be reviewed by the lead incident responders 65 | * Gather their contact information to send a follow-up after the incident is resolved 66 | * Offer to get them water 67 | * Tell them where the Safety Room is. Offer to escort them if desired. 68 | - Room 23 on May 11, Room 25C May 12-13 69 | * Ask, "Is there a friend or trusted person who you would like to be with you?" If so, arrange for another incident responder to get this person. 70 | * Ask them, "How else can I help?" 71 | * Provide them with specific non-emergency or crisis contacts from the volunteer guide if necessary. 72 | 73 | Once something is reported, the event coordinator, the conference chair, and the lead incident responders should meet. The main objectives of this meeting is to: 74 | 75 | * Review report documentation to determine what happened 76 | * Consult documentation of past incidents for patterns of behavior 77 | * Discuss appropriate response(s) to the incident 78 | * Assign a person to make those reponse(s) 79 | * Determine the follow up actions for any impacted people and/or the reporter 80 | * Assign a person to follow up with the impacted people 81 | 82 | After the staff meeting and discussion, a staff member (preferably the conference chair or event coordinator if available) may choose to communicate with the reported person. 83 | 84 | When following up with a reported person: 85 | 86 | * Explain what happened 87 | * Focus on the impact of their behavior 88 | * Reiterate the Code of Conduct and that their behavior was not appropriate 89 | * Give them concrete examples of how they can improve their behavior 90 | * Remind them of the consequences of their behavior, or future consequences if the behavior is repeated 91 | 92 | People who are reported often get upset, defensive, or deny the report. Allow them to give any additional details about the incident. However, remember: 93 | 94 | * It does not matter if they did not intend to hurt anyone -- their behavior still impacted attendees negatively 95 | * It is not your job to reassure or forgive them 96 | * Do not allow the reported person to make an apology to the reporter or impacted person. Often an apology centers the reported person’s feelings and not the person who was impacted. You may accept their apology and offer to pass it on (but you’re not required to if you think it would negatively impact the reporter). 97 | 98 | What follows are examples of possible responses to an incident report. This list is is not inclusive, and PyCon reserves the right to take any action it deems necessary. Possible responses to an incident include: 99 | 100 | * Nothing, if the behavior was determined to not be a Code of Conduct violation 101 | * A verbal or emailed warning 102 | * Requiring that the reported person avoid any interaction with, and physical proximity to, another person for the remainder of the event 103 | * Requiring the reported person not attend evening events 104 | * Refusal of alcoholic beverage purchases at events 105 | * Ending a talk that violates the Code of Conduct early 106 | * Not publishing the video or slides of a talk that violated the Code of Conduct 107 | * Not allowing a speaker who violated the Code of Conduct to give (further) talks at the event now or in the future 108 | * Immediately ending any event volunteer responsibilities and privileges the a person holds 109 | * Requiring that a person not volunteer for future events (either indefinitely or for a certain time period) 110 | * Requiring that a person refund any travel grants and similar they received 111 | * Requiring that a person immediately leave the event and not return 112 | * Banning a person from future events (either indefinitely or for a certain time period) 113 | * Removing a person from membership of relevant organizations 114 | * Publishing an account of the incident and (optionally) calling for the resignation of a person from their responsibilities 115 | 116 | If a reported person wants to appeal the decision, notify them that they may contact the Python Software Foundation Board . Keep in mind that it is not a good idea to encourage an apology from the reported person. 117 | 118 | It is very important how we deal with the incident publicly. Our policy is to make sure that everyone aware of the initial incident is also made aware that it is not according to policy and that official action has been taken - while still respecting the privacy of individual attendees. When speaking to individuals (those who are aware of the incident, but were not involved with the incident) about the incident it is a good idea to keep the details out. 119 | 120 | Depending on the incident, the conference chair or their designate may decide to make one or more public announcements. If necessary, this will be done with a short announcement either during the plenary and/or through other channels. No one other than the conference chair or someone delegated authority from the conference chair should make any announcements. 121 | 122 | If some attendees were angered by the incident, it is best to apologize to them that the incident occurred to begin with. If there are residual hard feelings, suggest to them to write an email to the conference chair or to the event coordinator listed below. It will be dealt with accordingly. 123 | 124 | * Ewa Jodlowska 125 | * Python Software Foundation - Director of Operations 126 | * ewa@python.org 127 | * Ernest W. Durbin III 128 | * PyCon US - Conference Chair 129 | * ernest@python.org 130 | 131 | If contact cannot be made via phone or email, please proceed to the staff room. 132 | 133 | Room 11 at the Huntington Convention Center. 134 | 135 | --- 136 | 137 | This procedure has been adapted from the Ada Initiative’s guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)" and has been updated by [Otter Tech](https://otter.technology/code-of-conduct-training). 138 | -------------------------------------------------------------------------------- /code_of_conduct.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | PyCon US is a community conference intended for networking and collaboration in the developer community. 4 | 5 | We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the conference and at all conference events, whether officially sponsored by the Python Software Foundation or not. 6 | 7 | To make clear what is expected, all staff, attendees, speakers, exhibitors, organizers, and volunteers at any PyCon event are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event. 8 | 9 | ## Our Standards 10 | 11 | PyCon is dedicated to providing a positive conference experience for everyone, regardless of age, gender identity and expression, sexual orientation, disability, physical appearance, body size, ethnicity, nationality, race, or religion (or lack thereof), education, or socio-economic status. 12 | 13 | Examples of behavior that contributes to creating a positive environment include: 14 | 15 | - Being kind to others 16 | - Behaving professionally 17 | - Using welcoming and inclusive language 18 | - Being respectful of differing viewpoints and experiences 19 | - Gracefully accepting constructive criticism 20 | - Focusing on what is best for the community 21 | - Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | - Harassment of conference participants in any form 26 | - Deliberate intimidation, stalking, or following 27 | - Violent threats or language directed against another person 28 | - Sexual language and imagery in any conference venue, including talks 29 | - Insults or put downs 30 | - Sexist, racist, homophobic, transphobic, ableist, or exclusionary jokes 31 | - Excessive swearing 32 | - Unwelcome sexual attention or advances 33 | - Unwelcome physical contact 34 | - Sustained disruption of talks or other events 35 | - Other conduct that is inappropriate for a professional audience including people of many different backgrounds 36 | 37 | 38 | Participants asked to stop any inappropriate behavior are expected to comply immediately. 39 | 40 | If a participant engages in behavior that violates this code of conduct, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. 41 | 42 | Thank you for helping make this a welcoming, friendly event for all. 43 | 44 | ### Weapons Policy 45 | 46 | No weapons are allowed at conference venues, including but not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. 47 | 48 | Attendees are further expected to comply with all state and local laws on this matter. 49 | 50 | ## Scope 51 | 52 | All PyCon US attendees are subject to the Code of Conduct. This includes PyCon US staff and volunteers, as well as attendees of the tutorials, workshops, summits, poster sessions, receptions, conference, sprints, and sponsored or unofficial events. 53 | 54 | Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the Code of Conduct. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. 55 | 56 | ## Contact Information 57 | 58 | If you believe that someone is violating the code of conduct during a PyCon event, or have any other concerns, please contact a member of the event staff immediately. 59 | 60 | - **PyCon Incident Report Hotline** 61 | - Automated dialer of the individuals listed below 62 | - +1 (216) 208 7987 (Telephone or SMS) 63 | - 64 | 65 | In case of a conflict of interest, you can individually contact: 66 | 67 | * Sage Sharp 68 | * PyCon US - Incident Responder 69 | * 70 | * +1 (503) 384 8831 71 | * Ewa Jodlowska 72 | * Python Software Foundation - Director of Operations 73 | * 74 | * Ernest W. Durbin III 75 | * PyCon US - Conference Chair 76 | * 77 | * +1 (216) 202 4393 78 | 79 | Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist any attendee to feel safe for the duration of the conference. We value your attendance. 80 | 81 | ## Procedure for Handling Incidents 82 | 83 | [Attendee Procedure for incident handling](https://us.pycon.org/2018/about/code-of-conduct/attendee-procedure/) 84 | [Staff Procedure for incident handling](https://us.pycon.org/2018/about/code-of-conduct/staff-procedure/) 85 | 86 | ## License 87 | 88 | This Code of Conduct was forked from the example policy from the [Geek Feminism wiki, created by the Ada Initiative and other volunteers](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy), which is under a Creative Commons Zero license. 89 | 90 | Additional language was added by [Otter Tech](https://otter.technology/) from: 91 | 92 | - [Contributor Covenant version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct) (licensed [CC BY 4.0](https://github.com/ContributorCovenant/contributor_covenant/blob/master/LICENSE.md)) 93 | - [Django Project Code of Conduct](https://www.djangoproject.com/conduct/) (licensed [CC BY 3.0](http://creativecommons.org/licenses/by-sa/3.0/)) 94 | - [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html) 95 | - Citizen Code of Conduct (licensed [CC BY SA 3.0](http://creativecommons.org/licenses/by-sa/3.0/)) 96 | - [Affect Conf Code of Conduct](https://affectconf.com/coc/) (licensed [CC BY 3.0](http://creativecommons.org/licenses/by-sa/3.0/)). 97 | 98 | [![Creative Commons License](http://i.creativecommons.org/l/by/3.0/88x31.png)](http://creativecommons.org/licenses/by/3.0/) 99 | 100 | The PyCon Code of Conduct is licensed under a [Creative Commons Attribution 3.0 Unported License](http://creativecommons.org/licenses/by/3.0/). --------------------------------------------------------------------------------