Skip to main content

Tutorial proposals are due in three weeks

The PyCon 2017 call for proposals (CFP) first opened about a month ago, and the team who will be bringing the conference to Portland have been excited to watch the first wave of submissions roll in. Exciting topics from across the PyCon community have already been proposed for our talks, tutorials, and poster schedules.

But we know that many of you are brimming with ideas that you have not yet submitted, so we wanted to remind you of this year’s deadlines:

  • Talk proposals will be due on 2017 January 3.
  • Poster proposals will be due on 2017 January 3.
  • Tutorial proposals are due on 2017 November 30.

Yes, that’s right — tutorial proposals are due in three weeks!

Last year we explained the one-month difference between the talk and tutorial deadlines in a detailed blog post that we invite you to review this year if you want to understand why the Tutorial review process takes more time for its committee. Entrusted with the one PyCon schedule for which attendees pay an individual fee per course, the Tutorial Committee takes extra time to make sure that courses are going to live up to the conference’s high reputation. As the Tutorials Chair, Ruben Orduz, reminded us last year:

“It’s a very time-consuming process, but it helps in selecting the best lineup while making sure every tutorial that had potential was given a fair chance. Compressing the timeline would mean only selecting from the top well-known proposers and forgetting the rest. That would be against our philosophy of giving chances to new instructors and increasing diversity.”

So we hope those of you with dreams of offering a tutorial will find the time within the next two weeks to get your proposal written up and submitted. Just visit our “Proposing a Tutorial” page for a guide to writing up your idea and getting it submitted — before November 30, when our Tutorials CFP will close once it is midnight and the day is over in every time zone. Good luck!

Comments

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

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…