Skip to main content

PyCon US 2013: How many talk tracks are there?

You're probably wondering where the program is for PyCon 2013 coming in March. The short version is that, well - the program committee is having meetings almost every day trying to go through 459 individual talk proposals. 

Yes. Four Hundred and Fifty-Nine.

That's astounding. Literally unprecedented in the history of the conference. You can ask the team - I was fretting and hand wringing and pacing all over worrying about not having enough proposals and then the tidal wave hit. 459. Amazing. To top that? 129 tutorial proposals.

This is amazing.

It also presents the staff, volunteers and program committee a conundrum. With the 5 tracks PyCon's main conference has room for maybe 90 talks. That's if we squeeze and push. With 459 proposals, the majority of which are exceedingly high quality, incredibly interesting and completely community driven, the program committee is under immense stress and an astounding workload.

So, to relieve some of it - and to be able to share even more with the community at the conference, I am pleased to announce we are adding a 6th track to PyCon 2013. 

70631 o

 

That's right. Instead of 5 tracks, we're adding a 6th. I know - this puts pressure on you, as attendees when we announce the schedule to have to pick between 6 simultaneously potentially interesting talks. That's why we're also recording all talks - the hallway track and down time is still important to us. But just as important to us is the ability to expose the community to amazing speakers, awesome topics and to spread knowledge as far and as wide as we can.

Yes - this means more hard choices when attending talks, but it also means more choice, and more variety. Luckily, with the success of PyCon 2012 and the ongoing strength of PyCon 2013 projections, and the amazing, continued support of our sponsors (and trust me, we still need more!) this means we can expand 2013 to sustain this.

Keep in mind though, this will probably be the only year we do this - we have the convention center space, we have you - our amazing and supportive community and sponsors. 2013 is the year we pull out all the stops - we have even more announcements coming.

Thank you - feedback (and sponsorship), as always, is welcome.

Jesse Noller - Chair, PyCon 2013.

Comments

Anonymous said…
A friendly suggestion: this year I went to OSCON by O'Reilly, which had a large number of parallel tracks, and in general was an enormous event. I think one mistake that was made was the estimate of the distribution among the tracks. It seemed as though it was assumed that people would spread out evenly, and so some of the rooms were too small to hold the excited crowd. This was very disappointing because it meant that if you didn't run to your next chosen talk, you could be left outside and miss out.

I don't know what the convention center you're using is like, so perhaps this isn't an issue, but please be mindful of the fact that some talks will simply be more popular than others, and so larger rooms may be needed.

Looking forward to the event.
Lennart Regebro said…
PloneConf this year let people say what talks they wanted to see, so it was possible to arrange them for maximum availability.

Popular posts from this blog

PyCon 2018 Call for Proposals is Open!

It’s here! PyCon 2018’s Call for Proposals has officially opened for talks, tutorials, posters, and education summit presentations. 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.

Before we dive in, the deadlines:
Tutorial proposals are due November 24, 2017.Talk, Poster, and Education Summit proposals are due January 3, 2018.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 need beginner, intermediate, and advanced proposals on all sorts of topics. We also need b…

PyCon 2018 Launches New Site, Sponsorship Search

After two great years in Portland, PyCon is shipping off to Cleveland for the 2018 and 2019 renditions of the Python community's largest gathering. PyCon 2018 will take place May 9 through 17 with two days of tutorials, three days of talks, and four days of development sprints.

For more information, check out our newly refreshed website at https://us.pycon.org/2018/ and follow us here on the blog and at @pycon on Twitter.

New Website

The new site features a design centered on the historic landmark Terminal Tower, a 52 story skyscraper that overlooks downtown Cleveland. When it opened in 1930, the tower was the fourth tallest building in the world and the tallest building outside of New York City. Though its height no longer tops the charts, the tower and surrounding Tower City area remain highly important to the city. What once was a beacon to guide ship captains to Cleveland's port and airplane pilots to its airport, the tower now includes 508 LEDs that light up for the holida…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…