[vc_row][vc_column][vc_empty_space height=”200″][\/vc_column][\/vc_row][vc_row opacity_bg_pattern=”0.1″ css=”.vc_custom_1611099664182{margin-bottom: 100px !important;}”][vc_column][vc_row_inner][vc_column_inner width=”1\/4″][\/vc_column_inner][vc_column_inner width=”1\/2″]
Our attendees\u2019 health and safety remain our top priority as we continue to monitor COVID-19 and look to venue, local, UK Health and Safety Agency, and WHO guidelines to make the best and most informed decisions around onsite safety and requirements. These guidelines are subject to change based upon health and safety recommendations at the time of the event.<\/p><\/div>\n <\/div>[\/vc_column_inner][vc_column_inner width=”1\/4″][\/vc_column_inner][\/vc_row_inner][vc_row_inner][vc_column_inner width=”1\/12″][\/vc_column_inner][vc_column_inner width=”10\/12″][vc_column_text]<\/p>\n
A message from the PyData London 2022 Committee<\/strong>: As the COVID-19 landscape continues to change rapidly, the PyData London Committee has implemented an up-to-date vaccination policy at PyData London 2022. Given the number of community members who will be traveling both domestically and internationally, we feel that our vaccination policy is the best and safest path forward to hosting an in-person conference. We have recently updated our Health & Safety Guidelines to require adult attendees to provide proof of up-to-date COVID-19 vaccination, as defined by the UK Health and Safety Agency<\/a>. You are considered up to date on COVID-19 vaccination if:<\/p>\n You are fully vaccinated and have received a booster shot, or<\/p>\n<\/li>\n You received the last dose of a two-dose vaccine less than 5 months ago, or<\/p>\n<\/li>\n You received a single-dose vaccine (like J&J) less than two months ago.<\/p>\n<\/li>\n<\/ul>\n We understand that some of our community members do not yet have access to the booster shot, or are ineligible to receive the booster dose at this time*. If you have questions or concerns about meeting the criteria for up-to-date vaccination, please come talk to us.<\/p>\n *Note: Due to a delay in the Health and Safety Guidelines being communicated, there is an option to take a COVID test the day before your attendance at PyData London and provide a negative test result to conference organizers.<\/p>\n Based on recent data available from the UK Health and Safety Agency<\/a><\/strong>,<\/strong><\/a> face coverings will be strongly recommended for everyone inside the conference venue at PyData London.<\/p>\n PyData London encourages the voluntary use of masks, along with other actions, as prevention against COVID-19 and other respiratory infections.<\/p>\n Wearing a well-fitting mask in indoor public spaces, regardless of your vaccination status, can help protect you and everyone close to you.<\/p>\n Some businesses may have mask preferences for their employees and customers.<\/p>\n Take the precautions below to protect yourself and others from infection and illness.<\/p>\n Individuals should not attend the event if they are COVID-positive, are exhibiting COVID symptoms (as defined by the UK Health and Safety Agency), or have been exposed, within 14 days prior to the event, to someone who was COVID-positive or showed COVID symptoms.<\/p>\n If you are feeling sick or exhibiting symptoms of COVID-19, or test positive for COVID-19, prior to the start of the conference, or on any day of the conference, please contact us and we will exchange your ticket type for an online ticket or grant you a refund.<\/p>\n We will provide a free on-site creche during conference hours. We are partnering with The Relief Group<\/a>\u00a0staffed by qualified childminders. For more information regarding childcare, please visit this page<\/a>.<\/p>\n We\u2019ve monitored COVID-related news and data since the pandemic started, and we will continue to do so moving forward. We continue to follow all UK Health and Safety Agency guidelines in addition to those of the local government and venue. International, national, regional, and local sources are closely watched and will result in a change of policy if warranted.<\/p>\n [\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/12″][\/vc_column_inner][\/vc_row_inner][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″][vc_column][vc_column_text]<\/p>\n Diversity Statement<\/a><\/p>\n Introduction & Scope<\/a><\/p>\n Standards for Behavior<\/a><\/p>\n Unacceptable Behavior<\/a><\/p>\n Reporting Guidelines<\/a><\/p>\n How to Submit a Report<\/a><\/p>\n Reporting Form<\/strong><\/a><\/p>\n Conflicts of Interest<\/a><\/p>\n What to Include in a Report<\/a><\/p>\n Enforcement: What Happens After a Report is Filed?<\/a><\/p>\n Appealing a Decision<\/a><\/p>\n Timeline Summary<\/a><\/p>\n License<\/a><\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Diversity”][vc_column][vc_column_text el_id=”diversity”]<\/p>\n PyData Global 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.<\/p>\n 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.<\/p>\n 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.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Introduction”][vc_column][vc_column_text]<\/p>\n This code of conduct should be honored by everyone who participates in the PyData Global conference and other PyData Global events. It should be honored in any conference-related activities, by anyone claiming affiliation with PyData Global, and especially when someone is representing PyData Global in any role (including as an event volunteer or speaker).<\/p>\n This code of conduct applies to all spaces managed by PyData Global, 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 Global events and governs standards of behavior for attendees, speakers, volunteers, booth staff, and event sponsors.<\/p>\n 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 Global community.<\/p>\n The PyData Global Code of Conduct follows below.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Standards”][vc_column][vc_column_text]<\/p>\n PyData Global is a worldwide community. All communication should be appropriate for a professional audience including people of many different backgrounds.<\/p>\n Please always be kind and courteous. There\u2019s never a need to be mean or rude or disrespectful.<\/strong>\u00a0Thank you for helping make this a welcoming, friendly community for all.<\/p>\n Be empathetic, welcoming, friendly, and patient.<\/strong>\u00a0We 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.<\/p>\n Be inquisitive.<\/strong>\u00a0Nobody 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.<\/p>\n Be careful in the words that we choose.<\/strong>\u00a0We 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.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Unacceptable”][vc_column][vc_column_text]<\/p>\n We are committed to making participation in this community a harassment-free experience.<\/p>\n We will not accept harassment or other exclusionary behaviors, such as:<\/strong><\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Reporting”][vc_column][vc_column_text]<\/p>\n 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 Global takes reports of misconduct very seriously and is committed to preserving and maintaining the welcoming nature of our community.<\/p>\n In some cases we may determine that a public statement will need to be made. If that\u2019s the case, the identities of all involved parties and reporters will remain confidential unless those individuals instruct us otherwise.<\/p>\n All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The PyData Global team commits to maintaining confidentiality with regard to the reporter of an incident.<\/p>\n 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 Global 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.<\/p>\n Take care of each other. Alert the PyData Global CoC response team if you notice a dangerous situation, someone in distress, or violations of this code of conduct, even if they seem inconsequential.<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Resolve”][vc_column][vc_column_text]<\/p>\n All reports of breaches of the code of conduct will be investigated and handled by the\u00a0PyData Global Code of Conduct Enforcement Team or the NumFOCUS Board of Directors<\/strong>.<\/p>\n Members of the NumFOCUS Board of Directors can be found in the\u00a0NumFOCUS website<\/a>. The members of the PyData Global Code of Conduct enforcement team include:<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Conflicts”][vc_column][vc_column_text]<\/p>\n In the event of any conflict of interest, the team member will immediately notify the Board and recuse themselves if necessary.<\/p>\n 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\u00a0reporting@numfocus.org<\/a>.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Include”][vc_column][vc_column_text]<\/p>\n 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,\u00a0our reporting form asks you to include as much of the following information as you can:<\/strong><\/p>\n The PyData Global 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.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Enforcement”][vc_column][vc_column_text]<\/p>\n PyData Global staff and\/or our event staff will attempt to ensure your safety and help with any immediate needs. PyData Global will make every effort to\u00a0acknowledge receipt within 1 hour<\/b> during conference hours, and in\u00a05 hours outside those times (and we\u2019ll aim for much more quickly than that).<\/p>\n PyData Global will make all efforts to\u00a0review the incident within 24 hours during conference days<\/strong>\u00a0and determine:<\/p>\n After PyData Global 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.<\/p>\n Once PyData Global 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.<\/p>\n Potential consequences for violating the PyData Global code of conduct include:<\/p>\n At PyData Global events<\/strong>, if a participant engages in behavior that violates this code of conduct, the conference organizers and staff may take any action they deem appropriate.<\/p>\n Potential consequences for violating the PyData Global Code of Conduct during the conference include:<\/p>\n No one espousing views or values contrary to the standards of our code of conduct will be permitted to hold any position representing PyData Global, including volunteer positions. PyData Global 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.<\/p>\n We aim to\u00a0respond within one week<\/strong>\u00a0to the original reporter with either a resolution or an explanation of why the situation is not yet resolved.<\/p>\n 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.<\/p>\n 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 Global may choose to make a public report of the incident, while maintaining the anonymity of those involved.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Appealing”][vc_column][vc_column_text]<\/p>\n To appeal a decision of PyData Global, you can contact the NumFOCUS board via\u00a0reporting@numfocus.org<\/a>.[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”Timeline”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″ el_id=”License”][vc_column][vc_column_text]<\/p>\n This code of conduct has been adapted from numerous sources, including the\u00a0NumFOCUS Code of Conduct<\/a>,\u00a0Geek Feminism wiki, created by the Ada Initiative and other volunteers, which is under a Creative Commons Zero license<\/a>, the\u00a0Contributor Covenant version 1.2.0<\/a>, the\u00a0Bokeh Code of Conduct<\/a>, the\u00a0SciPy Code of Conduct<\/a>, the\u00a0Carpentries Code of Conduct<\/a>, and the\u00a0NeurIPS Code of Conduct<\/a>.<\/p>\n PyData Global Code of Conduct is licensed under a\u00a0Creative Commons Attribution 3.0 Unported License.<\/a><\/strong>[\/vc_column_text][\/vc_column][\/vc_row][vc_row disable_element=”yes” opacity_bg_pattern=”0.1″][vc_column][vc_column_text]<\/p>\n PyData Global is an engaged and respectful community made up of people from all over the world, committed to fostering a productive, harassment-free environment for everyone. Please read the full <\/span>Code of Conduct below<\/span>.<\/span><\/p> Fundamentally, we are committed to fostering a productive, harassment-free environment for everyone. Rather than considering this code an exhaustive list of things that you can\u2019t do, take it in the spirit it is intended – a guide to make it easier to enrich all of us and the communities in which we participate.<\/span><\/p> Be friendly and patient.<\/b><\/p> Be welcoming.<\/b> We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, physical appearance, family status, technological or professional choices, academic discipline, religion, mental ability, and physical ability.<\/span><\/p> Be considerate.<\/b> Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we’re a world-wide community. You may be communicating with someone with a different primary language or cultural background.<\/span><\/p> Be respectful. <\/b>Not all of us will agree all the time, but disagreement is no excuse for poor behavior or poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It\u2019s important to remember that a community where people feel uncomfortable or threatened is not a productive one.<\/span><\/p> Be careful in the words that you choose. Be kind to others. Do not insult or put down other community members. Harassment and other exclusionary behavior are not acceptable.<\/b> This includes, but is not limited to:<\/span><\/p>\n Moderate your expectations.<\/b> Please respect that community members choose how they spend their time on the project. A thoughtful question about your expectations is preferable to demands for another person’s time.<\/span><\/p> When we disagree, try to understand why. <\/b>Disagreements, both social and technical, happen all the time and PyData is no exception. Try to understand where others are coming from, as seeing a question from their viewpoint may help find a new path forward. And don\u2019t forget that it is human to err: blaming each other doesn\u2019t get us anywhere, while we can learn from mistakes to find better solutions.<\/span><\/p>\n A simple apology can go a long way.<\/b> It can often de-escalate a situation, and telling someone that you are sorry is an act of empathy that doesn\u2019t automatically imply an admission of guilt.<\/span><\/p> 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.<\/span><\/p> You can make a personal report by:<\/span><\/p>\n By Email: Send a message to global-coc-report@pydata.org<\/a>. Organizers will respond promptly.<\/span><\/p>\n\n
MASKS<\/strong><\/h4>\n
ATTENDANCE<\/strong><\/h4>\n
CHILDCARE<\/strong><\/h4>\n
MONITORING WILL CONTINUE<\/strong><\/h4>\n
CODE OF CONDUCT TABLE OF CONTENTS<\/strong><\/h2>\n
DIVERSITY STATEMENT<\/h3>\n
INTRODUCTION & SCOPE<\/h3>\n
STANDARDS FOR BEHAVIOR<\/h3>\n
WE STRIVE TO:<\/h4>\n
UNACCEPTABLE BEHAVIOR<\/strong><\/h3>\n
\n
REPORTING GUIDELINES<\/strong><\/h3>\n
ALL REPORTS WILL BE KEPT CONFIDENTIAL.<\/strong><\/h4>\n
\nIf you feel your physical safety is in jeopardy or the situation is an emergency, we urge you to contact law enforcement before making a report to PyData Global.
\nPyData Global is committed to promptly addressing any reported issues. If you have experienced or witnessed behavior that violates the PyData Global Code of Conduct during our event, please submit a report. You can do so in three different ways:<\/div>\n\n
\n
\n
PERSON(S) RESPONSIBLE FOR RESOLVING COMPLAINTS<\/h3>\n
\n
CONFLICTS OF INTEREST<\/strong><\/h3>\n
WHAT TO INCLUDE IN A REPORT<\/strong><\/h3>\n
\n
ENFORCEMENT: WHAT HAPPENS AFTER A REPORT IS FILED?<\/strong><\/h3>\n
ACKNOWLEDGMENT AND RESPONDING TO IMMEDIATE NEEDS<\/strong><\/h4>\n
REVIEWING THE REPORT<\/strong><\/h4>\n
\n
CONTACTING THE PERSON REPORTED<\/strong><\/h4>\n
RESPONSE AND POTENTIAL CONSEQUENCES<\/strong><\/h4>\n
\n
\n
APPEALING A DECISION<\/h3>\n
TIMELINE SUMMARY<\/strong><\/h3>\n
CONFIRMING RECEIPT<\/strong><\/h4>\n
\n
REVIEWING THE REPORT<\/strong><\/h4>\n
\n
CONSEQUENCES & RESOLUTION<\/strong><\/h4>\n
\n
LICENSE<\/h3>\n
Code of Conduct<\/b><\/h3>\n
At the 2021 PyData Global Conference:<\/span><\/i><\/h5>\n
\n
Reporting<\/span><\/i><\/h5>\n