Python weekend is an event organized by Kiwi.com, intended for learning, collaborating and networking. We value the participation of each member and we 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 event.
To make clear what is expected, all staff, attendees, mentors, organizers, and volunteers at any Kiwi.com event are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event.
The Python weekend is dedicated to providing a positive event 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.
Examples of behavior that contributes to creating a positive environment include:
Examples of unacceptable behavior by participants include:
Participants asked to stop any inappropriate behavior are expected to comply immediately.
If a participant engages in behavior that violates this code of conduct, the event organizers may take any action they deem appropriate, including warning the offender or expulsion from the event with no refund.
Thank you for helping make this a welcoming, friendly event for all.
No weapons are allowed at event 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.
Attendees are further expected to comply with all state and local laws on this matter.
All Python weekend attendees are subject to the Code of Conduct. This includes staff and volunteers and mentors.
If you believe that someone is violating the code of conduct during the event, or have any other concerns, please contact a member of the event staff immediately.
Event staff will be happy to help participants venue security or local law enforcement, or assist any attendee to feel safe for the duration of the event. We value your attendance.
Procedure for Handling Incidents
If you believe someone is in physical danger, consult with a volunteer or staff member for the appropriate crisis number, non-emergency number, or policy number.
If you believe someone has violated the Code of Conduct (link), 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.
During the event you can make a report:
If you make a report via email or phone, please include:
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.
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 event attendees safe. In some cases, we can compile several anonymized reports into a pattern of behavior, and take action on that pattern.
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.
When you make a report to an incident responder, they will gather information about the incident according to the Staff Procedure For Incident Response.
After an incident responder takes the report, they will immediately consult with the lead incident responders (Jona Azizaj).
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.
After the event, all incident responders will attend a debriefing session with the lead responders to discuss all incidents and determine any necessary follow-up actions.
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:
In some cases, the lead responders may need to ask additional questions about the incident in order to identify the reported person.
Conflicts of Interest
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.
Be sure to have a good understanding of our Code of Conduct.
Also have a good understanding of what is expected from an attendee that wants to report an incident.
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:
Assess whether an immediate response is necessary. This initial response is very important and will set the tone for the event. Depending on the severity/details of the incident, please follow these guidelines:
Respond to reporter needs. You can:
Once something is reported, the event coordinator, and the lead incident responders should meet. The main objectives of this meeting is to:
After the staff meeting and discussion, a staff member (preferably the event coordinator if available) may choose to communicate with the reported person.
When following up with a reported person:
People who are reported often get upset, defensive, or deny the report. Allow them to give any additional details about the incident. However, remember:
What follows are examples of possible responses to an incident report. This list is not inclusive, and Kiwi.com reserves the right to take any action it deems necessary. Possible responses to an incident include:
If a reported person wants to appeal the decision, notify them that they may contact the Community Team at firstname.lastname@example.org. Keep in mind that it is not a good idea to encourage an apology from the reported person.
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.
Depending on the incident, the event organizers 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 event and/or through the Slack channel. No one other than the event organizers or someone delegated authority from the event organizers should make any announcements.
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 listed above. It will be dealt with accordingly.
This Code of Conduct was forked from the example policy from the PyCon Code of Conduct, which is licensed under a Creative Commons Attribution 3.0 Unported License.
The procedure has been adapted from the PyCon Code of Conduct (CC BY 3.0) and has been updated by Kiwi.com Community Team.