DjangoCon Europe 2020

Everybody who participates in DjangoCon Europe in one way or another is required to conform to this Code of Conduct (CoC). This includes attendees, speakers, sponsors, organizers, volunteers, and event staff.

The organizers will introduce a Code of Conduct team that will be primarily responsible for handling any incidents. The CoC applies before and throughout the event (including related activities such as social events, and social media). We have also published our response guidelines.

The team can be reached on conduct@djangocon.eu.

We would like to thank the DjangoCon Europe 2019 CoC team for the awesome CoC (which we adapted with some minor modifications) and the response guidelines (which we have adopted almost unedited from 2018).

Why do we have a Code of Conduct?

Our goals with having this Code of Conduct are:

Helping everyone feel safe and included. Attendees may have had poor experiences in other events, or may be first-timers. We want to set the expectation that harassment and other unpleasant behaviour are not acceptable. This way, people who do have an unpleasant experience know that it is neither the norm nor acceptable to us as a community.
Helping to build trust that if an incident is reported, we will not respond with victim blaming, and that we will proceed with a thorough investigation. This will be true even if the incident involves someone in a position of power, for example.
Informing everyone of the expected behaviour. We are a diverse community, and having a Code of Conduct makes the expectations over everybody's behaviour explicit and transparent.
Having a framework for report handling (see the response guidelines. The Code of Conduct is the basis for dealing with a report, assessing whether the CoC was violated, and what action should be taken.

Our Code of Conduct

We ask each attendant to keep the community in mind and do their best to foster a positive environment for everyone.

Behavior that contributes to a positive environment includes:

Being kind and considerate to others
Behaving professionally
Using welcoming and inclusive language
Being respectful of differing viewpoints and experiences
Gracefully accepting constructive criticism
Being supportive towards newcomers

We are dedicated to providing a harassment-free conference experience for everyone, regardless of race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.

We do not tolerate harassment of conference participants in any form. This includes offensive comments related to the categories above, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, violent threats or language, inappropriate physical contact, and unwelcome sexual attention. Advocating for, or encouraging, any of the above behaviour is also not acceptable.
Sexual language and imagery are not appropriate for any venue to which the CoC applies.
Some people may not wish to be filmed or photographed - respect their wishes, take extra care when publishing pictures and provide a way to request them to be taken down.
Be careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be offensive and unwelcoming to those around you. Excessive swearing and offensive jokes are not appropriate for DjangoCon Europe.
Condescending behavior towards people of different knowledge levels, and especially beginners, is unacceptable.
No one owes anyone any form of interaction or explanation for why they don't want contact. If someone asks you to leave them alone, accept and respect it without any further discussion, even if you think it is unwarranted.

Where does the Code of Conduct apply?

This Code of Conduct applies to all conference related spaces. That includes, but is not limited to:

The conference online platform
Any conference related social activities
Slack channels, tweets with the conference hashtag, and other online media
The Code of Conduct does not exclusively apply to events on the conference agenda. For example, if you join a group of attendees for unofficial virtual drinks after the talks and someone harasses you there, we would still treat that as a CoC violation.

What can happen if the CoC is violated?

In case of a Code of Conduct violation, some of the most common actions organisers may take are:

Demanding that a participant stops their behaviour.
Demanding that a participant prevents further contact with certain other participants.
Not publishing the video of a conference talk.
Cancelling a conference talk.
Removing a participant from the conference, without refund.
The action taken is at the discretion of the Code of Conduct team. Participants are expected to comply immediately, and further action may be taken in case a participant does not comply. A record will be kept of all incidents.

Where to report incidents

If a Code of Conduct incident happens to you, or you witness it happening to someone else, please contact the CoC team immediately, either in Slack or by sending an email to conduct@djangocon.eu.

Your report will be treated confidentially and will only be discussed within the CoC team.

The team members will be introduced at the conference. You can message any of them at any time to discuss an incident or concern. You can also ask any other staff to help you find them.

Our Code of Conduct team consists of: * Ana Cunha - Slack ID USFERV5QX * Joachim Jablon - Slack ID URZPLHSKB * Noah Alorwu - Slack ID URYA5P4UB * Telmo Guerra - Slack ID UKVDGJHEH

Guidelines for reporting incidents

Please do not feel like you may be a burden to us by reporting incidents. Even if you happen to report multiple incidents during the conference. We rather consider reports as an opportunity for us to act: by knowing about an incident, we can act on it, and often prevent it from going on or occuring again. But if we don't know, we can't take action.

If you're not sure if an incident was already reported by someone else, even if many people saw it, please report it. It is frequent that several people witness an incident and no one reports it, because everyone thought other people would.

If you are not sure whether the situation was a Code of Conduct violation, or whether it applied to that particular space, we encourage you to still report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.

If you think you witness something, but you're not sure what you saw, or you don't have proof, it's still very useful to us if you can report on that. You don't have to build up a case before reporting, and it's ok to report things even if you have doubts.

In your report please include, when possible:

Your contact info (so we can get in touch with you)
Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well.
When and where the incident occurred. Please be as specific as possible.
Your account of what occurred. If there is a written record (e.g. tweets or slack messages), please include screenshots and, if possible, a link.
Any extra context relevant for the incident.
If this incident is ongoing.
Any other information you would like to give us.

If you don't have some of this information, or not at this time, please still make the report anyways. You can contact us at any time after your report if you want to add, edit or take back any information you shared.

If you feel unsafe reporting in person, you may choose someone to represent you. In this case, we'd need their contact information, but we'd ask this person to make clear that they are not reporting in their own name.

When handling a report, we follow our response guidelines.