Skip to main content

PyCon 2015 Call for Proposals is open!

The PyCon organizers are thrilled to announce the opening of PyCon 2015's Call for Proposals for talks, tutorials, and posters! We've seen a lot of growth in response to our CFP over the years, and our program committee is expecting a ton of proposals this time around. In 2012, you put us to work with 374 talk proposals and followed up the next year with 458. For 2014, 107 more talk submissions came in, for a jump to 565. We'll be accepting proposals through September 15 for talks and tutorials, and posters are accepted through November 1.

We want everyone to be a part of making PyCon what it is, which is why we invite everyone to submit proposals, and we invite everyone to be a part of the program committee. It's your PyCon, not mine. Whether you started with Python yesterday or you've been writing it since the 90s, everyone has different experiences, different knowledge, and a different story to tell. This is why we aim to strike a balance between beginner, intermediate, and advanced talks. We want the entire community to level up as a result of PyCon.

I often hear people say, "but I don't have anything to talk about." Well, what do you do? Why do you do it? Why did you solve the problem this way instead of that way? Why do you continue to do this? It usually only takes a couple of questions to find a good talk out of someone. Many PyCon proposals started this way, and after some refining, they've become great PyCon talks.

Over the years, we've put together proposal resources and advice to help answer some common topics surrounding our CFP. We even put together a sample proposal and reviewed it for you. If you have any questions or tips that may help others, please email them to pycon-pc@python.org.

There are likely 95 talk slots to fill, assuming we keep the usual balance of 30/45 minute slots the same, and we'll have room for 32 tutorials. This makes for some steep competition given the potential to reach over 600 talk proposals, while seeing three to four times as many tutorial proposals as available slots. While proposals will be accepted through September 15, we encourage submissions as early as possible, allowing reviewers more time to assess and provide feedback which may prove beneficial as the various rounds of review begin.

As with all past PyCons, we continue to be an "everyone pays" event, run by volunteers. Financial Aid is available thanks to the Python Software Foundation and our generous sponsors, and applications will open September 1. If Financial Aid would make your trip a possibility, we encourage you to apply once it opens.

Here are some important dates to put on your calendar:

  • September 1, 2014: Registration opens, Financial Aid opens
  • September 15, 2014: Talk and tutorial proposals due
  • November 1, 2014: Poster proposals due
  • December 1, 2014: Talk and tutorial selections announced, Financial Aid grants for speakers awarded
  • December 15, 2014: Poster selections announced, full conference schedule announced

The PyCon organizers are going to give you everything we have to create the best PyCon yet. In exchange, we need you to give us your best talk, tutorial, and poster proposals. We also need your help getting the word out there about this CFP. If there's someone you want to see speaking at PyCon - tell them! If there's a topic you want to hear about - tell us, and we'll try to get people involved.

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. 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.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
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…

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…