Skip to main content

Talk, Poster, Education Summit proposals due January 3rd — but feel free to submit them now!

With the holidays nearly here, this is the moment to ask yourself: are you really — when you return groggily to work on Tuesday January 3rd following the “New Year’s (Observed)” holiday on Monday — going to remember to write and submit your Talk, Poster, and Education Summit proposals for PyCon 2017?

Waiting until the last minute is very tempting. After all, the whole reason that we worked with the Talk and Poster committees to move the deadline as close to PyCon as we dared was to let you submit as current and as up-to-date a proposal as possible.

But — are you sure that you want to risk starting your first work day of the New Year (if your schedule even puts you back at work by the 3rd!) with a conference deadline looming only hours later?

I myself am adopting a safer approach this year: I will be going ahead and submitting all of my proposals this week, ahead of the holidays. Then, if I do remember the deadline, I can always log into the PyCon web site on January 3rd and use the “Edit” button to make all of the last-minute revisions that I want. But if I forget? Then at least an early version of each proposal will be in the system and can be considered by the Program Committee!

As was true last year, our schedule is designed to allow Financial Assistance submissions to include any Talk, Tutorial, Poster, or Education Summit proposals that you get accepted:

  • January 3 — Talk, Poster, and Education Summit proposals due, as long as it is January 3rd Anywhere on Earth (AoE).
  • February 1–12 — Talks, Tutorials, Posters, and Education Summit schedules announced.
  • February 15 — Financial Assistance applications due.
  • March 3 — Financial Assistance grants awarded.
  • March 30 — Your deadline to respond to offer of Financial Assistance.

One final note: more than 90% of our Early Bird tickets are now gone, with only a few dozen remaining. If you have hoped to purchase your Student, Individual, or Corporate ticket at our discounted rate, then your time is almost up — register as soon as you can, and we look forward to seeing you in Portland in May 2017!

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…

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…

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…