DIVERSITY STATEMENT

PyData Eindhoven welcomes and encourages participation in our community by people of all backgrounds and identities. We are committed to promoting and sustaining a culture that values mutual respect, tolerance, and learning, and we work together as a community to help each other live out these values.

We have created this diversity statement because we believe that a diverse community is stronger, more vibrant, and produces better software and better science. A diverse community where people treat each other with respect has more potential contributors, more sources for ideas, and fewer shared assumptions that might hinder development or research.

Although we have phrased the formal diversity statement generically to make it all-inclusive, we recognize that there are specific identities that are impacted by systemic discrimination and marginalization. We welcome all people to participate in the NumFOCUS community regardless of their identity or background.

INTRODUCTION & SCOPE

This code of conduct should be honored by everyone who participates in the PyData Eindhoven conference and other PyData Eindhoven events. It should be honored in any conference-related activities, by anyone claiming affiliation with PyData Eindhoven, and especially when someone is representing PyData Eindhoven in any role (including as an event volunteer or speaker).

This code of conduct applies to all spaces managed by PyData Eindhoven, including all public and private mailing lists, issue trackers, wikis, forums, and any other communication channel used by our community. The code of conduct equally applies at PyData Eindhoven events and governs standards of behavior for attendees, speakers, volunteers, booth staff, and event sponsors.

This code is not exhaustive or complete. It serves to distill our understanding of a collaborative, inclusive community culture. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the PyData Eindhoven community.

The PyData Eindhoven Code of Conduct follows below.

STANDARDS FOR BEHAVIOR

PyData Eindhoven is a worldwide community. All communication should be appropriate for a professional audience including people of many different backgrounds.

Please always be kind and courteous. There’s never a need to be mean or rude or disrespectful. Thank you for helping make this a welcoming, friendly community for all.

WE STRIVE TO:

Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.

Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.

Be careful in the words that we choose. We are careful and respectful in our communication and we take responsibility for our own speech. Be kind to others. Do not insult or put down other members of the community.

UNACCEPTABLE BEHAVIOR

We are committed to making participation in this community a harassment-free experience.

We will not accept harassment or other exclusionary behaviors, such as:

• The use of sexualized language or imagery
• Excessive profanity (please avoid curse words; people differ greatly in their sensitivity to swearing)
• Posting sexually explicit or violent material
• Violent or intimidating threats or language directed against another person
• Inappropriate physical contact and/or unwelcome sexual attention or sexual comments
• Sexist, racist, or otherwise discriminatory jokes and language
• Trolling or insulting and derogatory comments
• Written or verbal comments which have the effect of excluding people on the basis of membership in a specific group, including level of experience, gender, gender identity and expression, sexual orientation, disability, neurotype, personal appearance, body size, race, ethnicity, age, religion, or nationality
• Public or private harassment
• Sharing private content, such as emails sent privately or non-publicly, or direct message history, without the sender’s consent
• Continuing to initiate interaction (such as photography, recording, messaging, or conversation) with someone after being asked to stop
• Sustained disruption of talks, events, or communications, such as heckling of a speaker
• Publishing (or threatening to post) other people’s personally identifying information (“doxing”), such as physical or electronic addresses, without explicit permission
• Other unethical or unprofessional conduct
• Advocating for, or encouraging, any of the above behaviors

REPORTING GUIDELINES

If you believe someone is violating the code of conduct, please report this in a timely manner. Code of conduct violations reduce the value of the community for everyone. The team at PyData Eindhoven takes reports of misconduct very seriously and is committed to preserving and maintaining the welcoming nature of our community.

ALL REPORTS WILL BE KEPT CONFIDENTIAL.

In some cases we may determine that a public statement will need to be made. If that’s the case, the identities of all involved parties and reporters will remain confidential unless those individuals instruct us otherwise.

All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The PyData Eindhoven team commits to maintaining confidentiality with regard to the reporter of an incident.

For possibly unintentional breaches of the code of conduct, you may want to respond to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please report the issue to the PyData Eindhoven CoC response team directly, or fill out this form (https://forms.gle/UydhxLYdtBw2XJir9) with your report if you prefer to do this on your own.

Take care of each other. Alert the PyData Eindhoven CoC response team if you notice a dangerous situation, someone in distress, or violations of this code of conduct, even if they seem inconsequential.

HOW TO SUBMIT A REPORT

If you believe someone is violating the code of conduct, please report this in a timely manner. Code of conduct violations reduce the value of the community for everyone and we take them seriously.
You can make a personal report by:
By Email: Send a message to conduct@numfocus.org. Organizers will respond promptly.
Online Form: NumFOCUS Code of Conduct Report (your name and contact information are not required).

CONFLICTS OF INTEREST

In the event of any conflict of interest, the team member will immediately notify the Board and recuse themselves if necessary.

If you are concerned about making a report that will be read by any of the above individuals, you can submit your report directly to the NumFOCUS board through reporting@numfocus.org.

WHAT TO INCLUDE IN A REPORT

Our ability to address any code of conduct breaches in a timely and effective manner is impacted by the amount of information you can provide, so, our reporting form asks you to include as much of the following information as you can:

• Your contact info (so we can get in touch with you if we need to follow up). This will be kept confidential. If you wish to remain anonymous, your information will not be shared beyond the person receiving the initial report.
• The approximate time and location of the incident (please be as specific as possible)
• Identifying information (e.g. name, nickname, screen name, physical description) of the individual whose behavior is being reported
• Description of the behavior (if reporting harassing language, please be specific about the words used), your account of what happened, and any available supporting records (e.g. email, GitHub issue, screenshots, etc.)
• Description of the circumstances/context surrounding the incident
• Let us know if the incident is ongoing, and/or if this is part of an ongoing pattern of behavior
• Names and contact info, if possible, of anyone else who witnessed or was involved in this incident. (Did anyone else observe the incident?)
• Any other relevant information you believe we should have

The PyData Eindhoven CoC response team will attempt to gather and write down the above information from anyone making a verbal report in-person at an event. Recording the details in writing is exceedingly important in order for us to effectively respond to reports. If event staff/meetup organizers write down a report taken verbally, then the person making the report will be asked to review the written report for accuracy.

ENFORCEMENT: WHAT HAPPENS AFTER A REPORT IS FILED?

ACKNOWLEDGMENT AND RESPONDING TO IMMEDIATE NEEDS

PyData Eindhoven staff and/or our event staff will attempt to ensure your safety and help with any immediate needs. PyData Eindhoven will make every effort to acknowledge receipt within 1 hour between 8:00 and 22:30 UTC, and in 5 hours outside those times (and we’ll aim for much more quickly than that).

REVIEWING THE REPORT

PyData Eindhoven will make all efforts to review the incident within 24 hours during conference days and determine:

• Whether this is an ongoing situation, or if there is a threat to anyone’s physical safety
• What happened
• Whether this event constitutes a code of conduct violation
• Who the bad actor was, if any

CONTACTING THE PERSON REPORTED

After PyData Eindhoven has had time to review and discuss the report, someone will attempt to contact the person who is the subject of the report to inform them of what has been reported about them. We will then ask that person for their account of what happened.

RESPONSE AND POTENTIAL CONSEQUENCES

Once PyData Eindhoven has completed our investigation of the report, we will make a decision as to how to respond. The person making a report will not normally be consulted as to the proposed resolution of the issue, except insofar as we need to understand how to help them feel safe.

Potential consequences for violating the PyData Eindhoven code of conduct include:

• Nothing (if we determine that no violation occurred)
• Private feedback or reprimand from PyData Eindhoven to the individual(s) involved
• Warning the person to cease their behavior and that any further reports will result in sanctions
• A public announcement that an incident occurred
• Mediation (only if both reporter and reportee agree)
• A permanent or temporary ban from some or all PyData Eindhoven spaces (mailing lists, GitHub repos, in-person events, etc.)
• Assistance to the complainant with a report to other bodies, for example, institutional offices or appropriate law enforcement agencies
• Removing a person from future PyData Eindhoven events and any formal affiliation to the PyData Eindhoven community
• Publishing an account of the harassment and calling for the resignation of the alleged harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the person is the event leader, or refuses to stand aside from the conflict of interest, or similar)
• Any other response that PyData Eindhoven deems necessary and appropriate to the situation

At PyData Eindhoven events, if a participant engages in behavior that violates this code of conduct, the conference organizers and staff may take any action they deem appropriate.

Potential consequences for violating the PyData Eindhoven Code of Conduct during the conference include:

• Warning the person to cease their behavior and that any further reports will result in sanctions
• Requiring that the person avoid any interaction with the person they are harassing for the remainder of the event
• Ending a session that violates the policy early
• Not publishing or removing a recording of a talk or session that violated the policy
• Not publishing or removing slides of a talk or session that violated the policy
• Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future
• Immediately ending any event volunteer responsibilities and privileges the reported person holds
• Requiring that the person not volunteer for future PyData Eindhoven runs (either indefinitely or for a certain time period)
• Requiring a person to immediately leave the event and not return without receiving a refund
• Banning the person from future events (either indefinitely or for a certain time period)
• Any other response that PyData Eindhoven deems necessary and appropriate to the situation

No one espousing views or values contrary to the standards of our code of conduct will be permitted to hold any position representing PyData Eindhoven, including volunteer positions. PyData Eindhoven has the right and responsibility to remove, edit, or reject comments, Mattermost messages, commits, code, wiki edits, issues, and other contributions that are not aligned with this code of conduct.

We aim to respond within one week to the original reporter with either a resolution or an explanation of why the situation is not yet resolved.

We will contact the person who is the subject of the report to let them know what actions will be taken as a result of the report, if any.

Our policy is to make sure that everyone aware of the initial incident is also made aware that official action has been taken, while still respecting the privacy of individuals. PyData Eindhoven may choose to make a public report of the incident, while maintaining the anonymity of those involved.

APPEALING A DECISION

To appeal a decision of PyData Eindhoven, you can contact the NumFOCUS board via reporting@numfocus.org.

TIMELINE SUMMARY

CONFIRMING RECEIPT

• PyData Eindhoven will make every effort to acknowledge receipt of a report within 1 hour between 8:00 and 22:30 UTC, and in 5 hours outside those times (and we’ll aim for much more quickly than that).

REVIEWING THE REPORT

• PyData Eindhoven will make all efforts to review the incident within 24 hours during conference days.

CONSEQUENCES & RESOLUTION

• We aim to respond within one week to the original reporter with either a resolution or an explanation of why the situation is not yet resolved.

LICENSE

This code of conduct has been adapted from numerous sources, including the NumFOCUS Code of Conduct, Geek Feminism wiki, created by the Ada Initiative and other volunteers, which is under a Creative Commons Zero license, the Contributor Covenant version 1.2.0, the Bokeh Code of Conduct, the SciPy Code of Conduct, the Carpentries Code of Conduct, and the NeurIPS Code of Conduct.

PyData Eindhoven Code of Conduct is licensed under a Creative Commons Attribution 3.0 Unported License.