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.

Comments

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…