Important Dates

• Call for Proposals opens: October 15, 2007
• Proposal submission deadline: November 19, 2007
• Proposal acceptance: November 30, 2007
• Cancellation date: February 10, 2008 (for inadequate attendance)
• Handout PDF deadline: March 1, 2008

Submission Format

Proposals should be 800 to 1500 words long (i.e., three to six pages in manuscript format). Multiple tutorial sessions may be requested, but a separate proposal must be submitted for each session (separate outlines, etc.). Do not combine two sessions into one proposal. Proposals must include the following information:

• Tutorial title.
• Presenter name(s) & contact information (email, telephone).
• Tutorial format description (lecture, interactive lecture, Q&A session [master class], hands-on, etc.). Be specific.
• Recording: indicate if you are amenable to your tutorial being recorded. "I give permission to record and publish my PyCon tutorial for free distribution."
• Intended audience (difficulty level, experience required): non-programmers, beginning programmers, advanced users, CPython developers, etc.
• Prerequisites: What experience must attendees have in order to fully benefit from this tutorial? If one tutorial is a prerequisite for another, this must be clearly noted in both proposals.
• Attendee Requirements: A list of software and hardware attendees will need for the tutorial. (Laptop required or recommended? Python installed? Which version? 3rd-party packages required? Provide links & versions.)
• Presenter Requirements: Any special requirements you may have. Standard equipment is a 1024x768 projector; you supply the laptop.
• Notes for reviewers.
• Promotional summary (max. 100 words).
• Detailed tutorial outline, for review (include timing).
• Tutorial outline for website publication, if different from the above.
• Presenter bio (one paragraph), written in the third person ("Presenter Name is..."). Include where you live, your job, your projects, books you've written, volunteer activities, family, etc.
• Previous experience: references of presentation/teaching engagements (sessions taught at OSCON, EuroPython, local user groups, at work, etc.). Extra consideration will be given to presenters with prior experience.

Be specific and detailed. Tutorial levels not matching some attendee expectations was a significant complaint in 2007.

Plaintext (ASCII or reST) is preferred, with HTML as a secondary alternative. Send your proposal (and any questions) to <pycon-tutorials@python.org>.

See the example tutorial proposal.

Preparation

PyCon attendees will pay extra to register for your tutorial, and you are being paid to present it. You are expected to prepare professional slides & handouts, and to practise and polish your delivery. Check your code for typos & syntax errors (i.e., run all of your code).

Presenters must supply PDFs for handouts (notes, workbook, etc.), maximum 50 pages. At minimum, handouts must contain a copy of the presentation (slides), but you are encouraged to include more details. PyCon will reproduce sufficient copies for everyone enrolled.

If you're having trouble meeting the deadlines, please let us know as soon as possible.

Presenters are encouraged to promote their tutorials. You may submit an article for publication on the PyCon blog (the earlier the better).

Honoraria

Tutorial presenters will receive $1000 per tutorial, plus free conference registration.

We reserve the right to cancel tutorials with fewer than 10 people enrolled as of the cancellation date. Presenters will not be paid for cancelled tutorials.