Skip to main content

The new, simpler Tutorial proposal form closes tomorrow!

This is the time of year when the upcoming PyCon really starts to feel closer, with the close of our earliest CFP (Call for Proposals) tomorrow on November 30. This is the first of several milestones for the conference that start arriving more and more frequently through the late autumn and winter. Each milestone ratchets PyCon one step closer to its arrival.

Our earliest CFP is for our Tutorials, which closes tomorrow — at the end of the day on November 30 anywhere on Earth. So if it is still November 30 in your time zone, then the CFP will not yet be closed!

IMG_0794.jpg

What are the main features of Tutorials?

  • Tutorials are 3-hour-long courses that pack the first two days of the PyCon conference schedule.
  • Students register ahead of time and pay separately for each 3-hour tutorial they attend.
  • We end the Tutorials CFP a full month earlier than for Talks and Posters, so the tutorials committee has extra time to fully vet each proposal and to generate a solid line-up of valuable topics that will repay the students’ investment to attend them.
  • In return for providing this value to the conference, we compensate each instructor. The amount can vary each year depending on the conference budget, but in 2016 we were able to reward them each with $1,500 for the instruction they provided our attendees.
  • You can learn more at our Proposing a Tutorial page, which includes links to long lists of topics in case you need inspiration!

If you proposed a tutorial last year, you will be happy to learn that we have streamlined the form to only four fields beyond the title itself:

  1. The Description is the public advertisement for your Tutorial and will be visible on the PyCon web site — replacing what used to be separate Description and Abstract fields. The other fields below are private and shared only with the committee.
  2. The Audience field lets you write a free-form description of who you think will be interested in and benefit from your tutorial. It replaces the old Audience, Category, and Perceived Value fields.
  3. The most detailed information, as before, belongs in the Outline that you write up for the committee.
  4. Finally, the Additional notes let you describe your previous experience as an instructor and mention any special setup or materials that your tutorial will require. It replaces the old fields Additional Notes, Additional Requirements, More Info, and Handout.

Hopefully the new form means that you spend less time puzzling over what the difference between a Description and an Abstract is, and more time focusing on your ideas about your course!

Does teaching at PyCon interest you? There is only one day left to submit your proposal! Head on over to the Proposing a Tutorial page and get your idea submitted before the end of the day on November 30 anywhere on Earth.

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…

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…

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…