Skip to main content

Writing a Good Proposal


As you may know, the call for proposals for PyCon 2012 is open, and we're waiting for you to submit your best talk, tutorial, and poster ideas at http://us.pycon.org/2012/speaker/. If you haven't submitted yet, don't worry, you have 42 days and we'll give you some tips along the way. If you already submitted, take a chance to fine tune your proposal with some tips on each section of the proposal form.


Title


The first and sometimes last thing your prospective audience will see is the title. With PyCon being a multi-track conference, no matter what kind of proposal you're writing, you're going to be up against others when it comes time for the big show. Tutorials usually run two at a time, talks run five at a time, and posters run all at once. If you want to attract attendees, you'll need to hook them with a solid title.



Kind

With this year's call for proposals being a unified format, we're using a unified proposal page for all types. Each type occurs in a different setting and has different attributes, so be sure to submit the right kind of proposal.

  • Tutorial

    Tutorials open up the conference on Wednesday March 7, 2012 with a two day series of classroom-style education. Presenters have three hours to teach 20-60 students on their topic, and receive compensation for their work. Most tutorials include interactive examples, relevant source code, and printed course materials.

  • Talk

    Talks are the main feature of PyCon and start on Friday March 9, 2012 and run through Sunday. In 2011, we had 95 talks spread over the three days, with five talks running at the same time. Durations run either 30 or 45 minutes, and we've brought back the "extreme" track.

  • Panel

    Panels are multi-speaker talks on a certain topic. In the past we've had panels on IDEs, Python implementations, educational use, and many more. If you're planning a panel, make sure you have other speakers on board, as you'll want to add their speaker profile at the end.

  • Poster

    Posters are a great way to show your latest project, organization, or anything you want to display to the community. You get a 4'x4' space to show your work, and many past presentations have also included interactive demos. It's a great event to be a part of, and allows for a more intimate experience with attendees over a traditional talk.



Category

The category drop down helps the organizers group submissions by topic both for evaluation and scheduling, so be sure to identify your proposal as accurately as possible. We think the selections represent the typical range of submissions we've seen in the past, but we know we haven't caught everything. If you must, use the "other" selection.

As you can see, you only get one choice, so choose wisely. If your talk is about A web framework with B database using C distributed framework to talk to D cloud provider, you've got some thinking to do. Pick the slot which you feel your proposal fits in the best -- it'll help your chances as a submitter, and it'll help your audience should you be selected.



Audience

Like the past PyCon schedules we've put together, 2012 is likely to provide quite the exercise in scheduling on the attendee side. Five options at any given time on five topics by five speakers. It's a lot to choose from, and our usual range of first timers to 20 year vets want a peek into what level you'll be speaking at.

You don't want a beginner expecting a beginner talk and leaving your experienced talk without understanding a thing, do you? For every-one's sake, try to be as accurate as possible in your assessment of the target audience. The organizers will likely use it to ensure the proposed talk matches the level. The attendees will use it to figure out if they want to attend or not.



Extreme

Want to skip the appetizer and dig right into the main course? Extreme talks skip the introductory parts of a presentation and get right to the topic at hand. If you're looking to pack a punch with your talk, going the extreme route might be for you. For more details, see http://us.pycon.org/2012/speaker/extreme/.



Duration

At PyCon 2011 we had room for 95 talks, 20 of which were of the 45 minute variety, leaving the remaining 75 talks to be 30 minutes in length. We try to be accommodating to duration requests, but keep in mind that we only have a limited amount of extended time slots. If you can fill a 45 minute slot, by all means, request it and we'll see what we can do.



Description

The description is your chance to reel in a prospective attendee that your talk is for them. Keep it short and sweet -- you only get 400 words and they'll be printed in the conference program, featured on the website, and likely used for video uploads.

A good description leads the reader right into their seat without asking for it. Introduce your topic, share a few important pieces of information, and sell your conclusion. A good title paired with a good description leaves no doubt in an attendee's mind that your talk is the one they want to see.



Abstract

The abstract is your way to show us what exactly you're working with. There's no limit on the content here, and you're able to use Markdown to jazz it up. Add as much or as little detail as you feel you need in order for the program committee to judge your talk on. Pro tip: we're judging your talk exactly as you have submitted it. We can't assume you will cover anything you haven't submitted. In fact, we try to make as few assumptions as possible, so try to be thorough.

We've seen several abstract formats, with one of the more popular being an outline-style. Previous submitters have broken down into two or three level deep outlines, sometimes including time estimates on how long each section will take. The more conversational paragraph-style has also been popular, summarizing the submitter's story similar to a blog post.

No matter how you write your abstract, know that it's your canvas to show us that you have a topic that PyCon attendees and the worldwide online audience want to see. We want to put together the best conference available, so please join in helping us to do that.


--


For more details, check out the call for proposals and the speaker pages on our site. Proposals are due in 42 days, so get to work. We're looking forward to receiving your submissions and working with you to tweak them and create the best conference ever.



Comments

Just to be certain, in the proposal form the abstract is said to be limited to 400 characters, and this post says 400 words. So which one is right? It makes a small difference ;).
Brian Curtin said…
@Félix-Antoine -- thanks for bringing that up! It was a mental lapse on my part: 400 characters is correct, I'll update the post.
Eric Snow said…
Just to be clear, the character limit applies to the Description section and not the Abstract section. The abstract can be as long as you want, if I understood correctly.

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…