Skip to main content

Part 6: Conference Talks (PyCon 2008 Chairman's Report)

The PyCon Conference Days took place from Friday, March 14 through Sunday, March 16. More than 60 speakers gave freely of their time, and presented some great talks. On behalf of the PyCon organizers: thank you all!

We received over 140 proposals for talks, more than twice as many as we could accept, and unfortunately we had to turn down many good proposals. The PyCon Program Committee (all volunteers, led by Ivan Krstić) did a great job in the long selection process, but it's hard to balance the needs of beginners and gurus alike. It's inevitable that there were some complaints.

The only way to improve in the future is to have more participation, especially from under-represented sectors: core Python, advanced topics, PyPy, etc. There has been talk of switching to a topic-based track program (web track, advanced/technical track, introductory track, etc.). This could work, but it needs the participation of many experts. If you care about Python's North American flagship conference, join the pycon-pc (Program Committee) mailing list!

There was an issue with the printed schedule: the talk levels weren't included. Unfortunately, nobody caught this in time. We won't repeat that mistake. The levels were visible on the online schedule though.

There were some issues with talks and speakers during the conference itself. We had ideas about a speaker ready room and info packets for speakers and session chairs, but there wasn't the time or manpower to implement all the ideas we had. In future, this needs to be organized earlier and publicized better.

We had 4 tracks this year, instead of 3 in past years. How did that work out? Should PyCon remain at 4 tracks? Return to 3 tracks? Or increase to 5 or more tracks? Given the size of conference PyCon has become, we now have the freedom to choose. Also, the cost of A/V becomes more reasonable when it's spread out over more attendees, and this opens up the possibility of recording and subsequently (or simultaneously?) releasing everything.

Some people would like to see more, shorter talks. Many others believe that 30 minutes is not enough time for an in-depth talk. But if we increase to 45 or 60 minutes, we'll have far fewer talks. We can mitigate this with more parallel tracks, but then people have to make hard choices, and if any one talk is overwhelmingly popular the (inevitably smaller) room could be filled.

There is a lively discussion going on right now on the pycon-organizers mailing list. Join us!

Comments

Popular posts from this blog

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 https://us.pycon.org/2018/registration/ 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…

Python Education Summit celebrates its 6th year in 2018

Teachers, educators, and Python users: come and share your projects, experiences, and tools of the trade you use to teach coding and Python to your students. The Annual Python Education Summit is held in conjunction with PyCon 2018, taking place on Thursday May 10. Our Call for Proposals is open until January 3rd, and we want to hear from you! See https://us.pycon.org/2018/speaking/education-summit/ for more details.

What we look for in Education Summit talks are ideas, experiences, and best practices on how teachers and programmers have implemented instruction in their schools, communities, books, tutorials, and other places of learning by using Python.

Have you implemented a program that you've been dying to talk about?Have you tried something that failed but learned some great lessons that you can share?Have you been successful implementing a particular program?
We urge anyone in this space to submit a talk! We’re looking for people who want to share their knowledge and leverage…

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…