|Type:||(one of) talk, hands-on tutorial, panel, ...|
|Presenter:||presenter name <email@example.com>|
|Python level:||beginner, intermediate, advanced, any, ...|
|Moderator:||moderator name <firstname.lastname@example.org> (panels only)|
|Panelists:||panelist 1, panelist 2, panelist 3 (panels only)|
Here, give a description of your event's topic, suitable for printing in the PyOhio event booklet. Aim for 150 words or less. It should help attendees decide whether the event is right for them.
Here, give more details to help the program committee evaluate your proposal. This will not be published in the program guide. Include anything that will help the committee understand your proposal.
If you are requesting a slot different from the standard 40 + 10 minutes, explain what you require and why.
Outline the overall structure for your talk. This portion will not be included in the program guide, but will be used by the program committee; a good outline shows that you have begun well-organized preparation. Panel proposals don't need outlines, since they are fundamentally unpredictable.
- Small carnivores
- Tripping hazard
- Bite toes
A brief biography of you and/or the panelists, for publication in the program guide: anything about you that you'd like attendees to know. 100 words or less, or 200 for panels with multiple panelists.
I will sign the recording release agreement (text at http://wiki.python.org/moin/PyOhio/RecordingRelease).
Attached FilesTo refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.
You are not allowed to attach a file to this page.