Skip to main content

What's up with the program committee?

"What's up with my PyCon proposal?"

That's the question I've gotten pretty much since the day the call for proposals closed for PyCon 2012. Since the program committee does most of its work in private, it can try anyone's patience waiting to find out how their proposal fared. Well, starting with this post I'll do my best to keep you informed of where we are.

As Jesse announced last month, we had record-breaking levels of talk submissions this year -- about 380 talk proposals. And it's not just quantity: the quality has been breathtaking. Sadly, we have just over 100 spots on the schedule. Selecting the best proposals is quite a challenge.

Let me tell you a bit about how our review process works:

First, the committee reads through proposals and scores them (using a system based on the Identify the Champion system). The goal here is to identify "champions" -- a committee member who feels strongly that the proposals should be placed on the schedule.

Next, we meet in real time (on IRC) to discuss each proposals. Champions advocate, we debate, and ultimately vote. At this point, we're considering each proposals in isolation, judging it strictly on its merits. Typically we vote to accept about 75% of proposals at this point.

Of course, this leaves us with far too many talks for the schedule. So the final step is to make the hard decisions and cull this list of (excellent) proposals down to the final schedule. We do this by grouping overlapping or similar proposals and looking at the balance of talks at the conference as a whole. We gather for a final round of meetings, debating and voting on which talks are the strongest in each area.

So where are we now?

Well, we've completed the first part -- each talk's been reviewed by a number of reviewers (at least three, at usually five or more) -- and we've started holding our first round of IRC meetings. We've discussed about a third of the talks so far. Extrapolating from our current rate tells me we should have the first round finished shortly after Thanksgiving. Based on our timeline last year, this means we should likely have the final selection of talks done by Christmas.

Ultimately, this means that if you've proposed a talk you should hear back from us right around the new year. I know it's a long time to wait, but I know it means we'll have an incredible program this year.


Popular posts from this blog

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…

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

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…