Skip to main content

How & why cities and dates are selected for Pycon

Foreword from the Chair:

The PyCon staff, volunteers, tutorial presenters, speakers, poster presenters, and community members have been hard at work preparing for PyCon 2018 in Cleveland, Ohio. Along the way, we’ve gotten a chance to have some solid discussions about what makes PyCon good as well as where it can improve.

In February one of those discussions was around the dates when PyCon 2018 will be occurring, specifically the conflict with Mother’s Day 2018. The outcome of that discussion was a commitment by the PyCon staff to better communicate what decisions and compromises were made along the way and how they were considered.


PyCon is run by the Python Software Foundation, which is a grant giving non-profit. Many misunderstand or are unaware of this relationship, but the Python Software Foundation relies on maintaining a strict budget for the operation of PyCon in order to continue its grants programs and other financial responsibilities.

The PyCon staff and Python Software Foundation Board of Directors strive to improve year over year. After realizing that PyCon 2014 and 2015 conflicted with the observance of Passover, PyCon’s scheduling has explicitly avoided major religious observances and US holidays.

The end result is a schedule which varies year to year and a myriad of compromises small and large that are made along the way. This year one of those compromises was to schedule the conference in conflict with the following holidays and religious observances:

  • May 10 - (Second day of Tutorials) Ascension Day
  • May 13 - (Third day of Talks) Mother’s Day
  • May 16 - (Third day of Sprints) Start of Ramadan


Conflicts were known and understood in advance of booking. For conflicts that staff did not have personal experience with, members of the community were asked to help fill in the blind spots. In spite of this we failed to properly and openly communicate the known conflicts, which allowed for speculation that they simply hadn’t been considered. This is a fair assumption, but it is not the case. In addition, our lack of transparency lead to the conflict being a surprise for many as they registered for PyCon or began booking their travel and accommodations.

With the help of our community, we’ve made adjustments and are planning specific events and spaces to better support mothers at PyCon this year. Moving forward, we will be more transparent about the known conflicts with PyCon’s dates and the ways that we work to accommodate groups which are impacted by those conflicts.

To better fill in the specifics of how it occurs, the team that works year-round to manage the logistics and planning for PyCon worked to develop a summary of that process, and we’d like to share it with you today.


Ernest W. Durbin III
Chair - PyCon US 2018



PyCon: How are the cities and dates selected?

Recently, community members requested a deeper look into the process of selecting a city and dates for PyCon US. Below is an overview of the steps* taken: Selecting a city and dates for PyCon a is process that usually takes about 6 months and involves many layers. First, we start with a list of cities that the Event Coordinators come up with along with any cities suggested by the community. We contact the local convention visitor bureaus and share with them our needs and expectations through a request for proposal (RFP). Our RFP includes the space we need, historical hotel costs, room night pickups, and types of services we need. Additional requirements included in the RFP are:
  • Low-cost to no-cost space rental
  • Avoiding religious holidays
  • Reasonably priced internet and food
The cities that do fulfill our requirements, respond back with a proposal, which usually includes one to three date options depending on their availability. From there we work with all available cities on space -- that is usually the most work. Each city sends us the space they think will work. Our Event Coordinators go through every line to make sure it matches our needs. If a city has the space we need, we look at hotels. We consider the distance of the hotels from the convention center and their price. If hotel expectations are met, our Event Coordinators plan site visits to those cities.

* Steps can change from time to time as we constantly try to refine our process.

A Case Study

We’ll run through a sample scenario of how the above mapped out to the selection of 2020 and 2021, which was recently finalized. We started with seventeen cities. We ended up only doing site visits to four cities. The large drop in cities is mainly because several cities turned us down for various reasons such as already being booked or not having enough space. PyCon requires 11 days of meeting space for setup, tutorials, the main conference, and sprints. Because we have such a lengthy span it is not always easy to find locations that can accommodate us. City A was a large city and the dates we were looking at were in February. Since we were looking at February dates, the hotel rates were more in line with our expectations. However, once we saw the space we realized it would not work. City B had great space and good hotel rates so we were hopeful. It also had lots of places to stay near the convention center. City C had good space and hotels, but we did not feel safe walking around in it at night. It was also the second most expensive of the three. City D was having most of the convention center rebuilt but it looked promising and the hotels matched our expectations. One thing we noted is that the area around the convention center lacked places that PyCon attendees would enjoy and would have to take buses to other neighborhoods. The expenses involved with City D were also the highest so we did not select it. In the end, we recommended to the Board of Directors that we move forward with City B for 2020. We plan to announce the city soon - possibly at PyCon 2018.

Known conflicts for PyCon 2019-2021


  • 2019: May 1 to May 9
    • May 1 (First day of Tutorials) - Yom HaShoah
    • May 6 (First day of Sprints) - Start of Ramadan
    • May 9 (Last day of Sprints) - Yom Ha'atzmaut
  • 2020: April 15 to April 23
    • April 16 (Second day of Tutorials) - Last Day of Passover
    • April 17 (First day of Talks) - Orthodox Good Friday
    • April 18 (Second day of Talks) - Orthodox Holy Saturday
    • April 19 (Third day of Talks) - Orthodox Easter
    • April 21 (Second day of Sprints) - Yom HaShoah
    • April 23 (Last day of Sprints) - Take our Daughters and Sons to Work Day
  • 2021: May 12 to May 20
    • May 13 (Second day of Tutorials) - Ascension Day
    • May 13 (Second day of Tutorials) - Eid al-Fitr (End of Ramadan)
    • May 15 (Second day of Talks) - Armed Forces Day
    • May 17 (First day of Sprints) - Shavuot
If you are aware of any conflicts we've missed, please reach out to pycon-local at python dot org. We will update this list and notify the community.
If you’d like to recommend a city for us to check out in the future, feel free to email us anytime: pycon-local at python dot org

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
Who should write a proposal? Everyone! If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…