Table of Contents
PyMCon abides by the NumFOCUS Code of Conduct.
We value the participation of each member of the PyMC 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 PyMC or not.
To make clear what is expected, all delegates, speakers, exhibitors and volunteers at any PyMCon web series event are required to conform to the NumFOCUS Code of Conduct. Organizers will enforce this code throughout the event.
We reproduce here certain portions of the NumFOCUS Code of Conduct that are specifically relevant to PyMCon. We encourage all PyMCon participants to review the complete Code of Conduct (link available below).
The Shorter Version #
Be kind to others. Do not insult or put down others. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes and language are not appropriate for PyMCon.
All communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery are not appropriate.
PyMCon is dedicated to providing a harassment-free event experience for everyone, regardless of gender, sexual orientation, gender identity, and expression, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of participants in any form.
Thank you for helping make this a welcoming, friendly community for all.
Code of Conduct Highlights Specific to PyMCon #
We reproduce here certain portions of the NumFOCUS Code of Conduct that are specifically relevant to PyMCon. We encourage all PyMCon participants to review the complete Code of Conduct.
How to 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 or anonymous report through any of the following channels:
- Online Form: The NumFocus Code of Conduct reporting form is available.
- Event specific reporting channels: Some PyMCon events might also make some extra channels available. These channels will be shared to event attendees beforehand and at the beginning of each event and optimized for a rapid response.
To file a report anonymously please use the online form.
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.). The online form supports attaching up to 5 files and email and Slack have not limit.
- 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
At PyMCon, if a participant engages in behavior that violates the Code of Conduct, the conference organizers and staff may take any action they deem appropriate.
Potential consequences for violating the NumFOCUS Code of Conduct at PyMCon 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 talk that violates the policy early
- Not publishing the video or slides of a talk 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 events (either indefinitely or for a certain time period)
- Expelling the person from the event without a refund
- Banning the person from future events (either indefinitely or for a certain time period)
- Any other response that the organizing committee deems necessary and appropriate to the situation
Person(s) Responsible for Resolving Complaints #
Reports sent via the online report form will be handled by the NumFOCUS Code of Conduct Enforcement Team.
Reports sent via the additional event specific channels will be handled by members of the PyMCon Code of Conduct Enforcement Team, consulting the NumFOCUS team if necessary.
PyMCon Code of Conduct Enforcement Team #
Members of the PyMCon Code of Code Enforcement team are:
- Oriol Abril Pla
- Ravin Kumar `rkumar@pymc_devs.com
Conflicts of Interest #
In the event of any conflict of interest, the team member will immediately notify and recuse themselves if necessary.
If you are concerned about making a report that will be read by any of the above individuals, please fill NumFOCUS report form.
Appealing a Decision #
To appeal a decision, contact Oriol Abril-Pla at
email@example.com with your appeal and the PyMCon or NumFOCUS Code of Conduct Enforcement Team will review the case.
Issue Log #
A summary of reported incidents will be provided after the event.
For sections that are present both in this page and in NumFOCUS complete Code of Conduct such as “how to report” or “Appealing a Decision”, the directives here take precedence.
This page has been adapted from numerous sources, mainly PyData Code of Conduct and JupyterCon 2020 Code of Conduct.