Skip to main content

Part 2: Attendance & Registration (PyCon 2008 Chairman's Report)

From 2006 to 2007 we saw an increase of about 43% in attendance, from 410 to 586 attendees. I was expecting 800-900 people for 2008, but I feared we would see more... and my fears were realized with over 1000 attendees, an increase of 77% over PyCon 2007. We had over 420 people registered for tutorials on the Thursday before the talks (March 13), more than the total conference attendance in 2006 (the first year with a PyCon tutorial day). Attendance at the development sprint was at an all-time high: at least 250, possibly many more.

Registration started late this year, as did early-bird registration. Early-bird registrations accounted for about 75% of the total, and about half of the early-bird registrations were done in the last week (300 over 4 days; over 100 in a single day!). Next year we must open registration earlier and close early-bird registration much earlier, so we have some real numbers to work with early enough to be useful (e.g. for swag orders & catering plans).

The registration system itself had some rough edges, which we've noted and will be working on. It's quite something that there were only rough edges though, since PyCon-Tech was mostly written by one person in his (not-so) spare time. Doug Napoleone could sure use some help on the PyCon-Tech project!

In a classic snafu the credit card processing service used by PyCon & the PSF up and quit the day before the end of early-bird registration. It wasn't our fault or specific to us (many other online businesses were affected), but that didn't stop complaints. Andrew Kuchling and Doug Napoleone did a great job behind the scenes solving problems and soothing people's anxieties.

In addition to the pycon-organizers mailing list, there's also a pycon-tech mailing list. All are welcome!

The phenomenal increase in attendance caused us some growing pains. We had to revise the seating plan in the ballrooms to fit more people (we'd planned to have more tables, but we couldn't do that and fit over 1000 people). The catering plan had to be reworked. The wireless network was affected. I'll address these issues in parts 3 & 4.

Comments

illume said…
Hello,

just a note about credit card processing companies...

All CC processors have problems, so you *need* a backup provider - or two.


cheers,

Popular posts from this blog

Keep an eye out for the Open Space events at PyCon this year!

These meetup-like events are a great way to learn something new or connect with others who share similar interests. Due to their self-organized nature and the breadth of topics, there is bound to be an Open Space event that can enrich your conference experience. In the past, Open Spaces have included a wide range of topics such as natural language processing, web frameworks, yoga, and playing board games. Any topic that two or more attendees are interested in could be a good candidate for an Open Space.

Open Spaces are held during the three main conference days in meeting rooms reserved for these events. Any attendee can create an Open Space event and reserve a room by adding a card to the Open Spaces boards found near the registration desk. Checking these boards regularly during the conference, subscribing to the hashtag #PyConOpenSpace, and following @openspacesbot on Twitter are ways to keep informed about upcoming Open Spaces.

Promoting your Open Space 
If you decide to host your …

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 Foundat…

Code of Conduct Updates for PyCon 2018

With PyCon 2018 approaching, I’m excited to share some work that the PyCon staff, volunteers, and Python Software Foundation have undertaken in preparation! The Python community and thus the PyCon community is always evolving and growing. In light of this it is crucial that we periodically reconsider and adjust the way that we interact within these communities. In 2012 PyCon adopted a Code of Conduct to foster a more welcoming environment at the conference and provide policies and procedures for addressing violations. Each year since, changes have been adopted to work towards our goal of an enjoyable and fulfilling conference for all attendees. For 2018, we took a larger step and worked with a third party expert fromOtter Techto reevaluate and improve our Code of Conduct, reporting procedures, and staff response procedures. Sage fromOtter Techcame with a resounding recommendation fromNorth Bay Pythonorganizers. In this post, I’d like to summarize the changes we’re bringing this year. If y…