ESUG is a global community of developers who share information, discuss ideas, and work together. Everybody who participates in our community in one way or another is required to conform to this Code of Conduct (CoC). This includes online communications, meetup and conference attendees, speakers, sponsors, founders, moderators, organisers, and volunteers.
Our goals with having this Code of Conduct are:
The Code of Conduct isn’t an exhaustive list of things that you must do, or can’t do. Rather, take it in the spirit in which it’s intended. It’s a guide to make it easier to enrich all of us and the communities in which we participate, and which we represent.
If you believe someone is violating the Code of Conduct, please report it. Contact details are listed at the end of this page. When handling a report, we follow our Code of Conduct Response Guide.
Some events may provide alcoholic drinks. However, participants are expected to drink responsibly. Alcohol use or other intoxication are never accepted as an excuse for CoC violations.
This Code of Conduct applies to all spaces managed by ESUG. This includes:
Any other forums created or used by the community for communication.
The Code of Conduct does not exclusively apply to events on an official agenda. For example, if after a scheduled social event you go to a bar with a group of fellow participants, and someone harasses you there, we would still treat that as a CoC violation. Similarly, harassment in chat platform direct messages related to ESUG can still be covered under this Code of Conduct.
In addition, violations of this code outside our spaces may affect a person’s ability to participate in them.
When you sponsor ESUG or related event, we welcome you as a member of our community, and we expect you to be respectful to the community you operate within.
All 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) must not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
In addition, sponsors and affiliates of conferences, meetups, and online activities should not employ aggressive recruiting techniques, invasive marketing behavior, or similar actions towards community members. In case of violations, sponsors might be sanctioned and expelled from the event or activity with no return of the sponsorship contribution.
In case of a Code of Conduct violation, some of the most common actions organisers may take are:
The action taken is at the discretion of the Code of Conduct committee. 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.
If a Code of Conduct incident happens that affects you, or if you witness it affecting someone else, please contact ESUG board immediately at board@esug.org.
Please do not feel like you may be a burden to us by reporting incidents. Even if you happen to report multiple incidents. We rather consider reports an opportunity for us to act: by knowing about an incident, we can act on it, and often prevent it from continuing or repeating. But if we don’t know, we can’t take action.
If you are not sure whether the situation was a Code of Conduct violation, or whether the CoC applied to that particular space, we encourage you to still report it. We would much rather have additional 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.
In your report please include, when possible:
If you don’t communicate all of this information at the time, please still make the report and include as much information as you have.
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 you to make clear that this person represents you.
When handling a report, we follow our Code of Conduct Response Guide.
All reports will be kept confidential. In some cases, a public statement might be required (for example in a CoC transparency report following conferences), but these reports are anonymized and do not include any personally identifying information.
If your report concerns a member of the Code of Conduct committee, you can report the issue to any other response team member or any other organiser.
If your report concerns a member of the Core Operations, which receives emails to conduct@writethedocs.org, you can report the issue individually to any of the other organisers.
This Code of Conduct was originally based on the one of Write the Docs. It was originally based on the DjangoCon Europe 2018 Code of Conduct and the Django Project Code of Conduct, which in turn credits the original text of the Speak Up! project, inspired in its turn by the Fedora Project, as well as the Python Mentorship Project and many others. Some inspiration was also taken from the FreeBSD Code of Conduct