You Can Speak at Pycon, by Anna Martelli Ravenscroft

Have you ever considered submitting a proposal to speak at PyCon but weren't sure how to even get started? This session will walk you through the steps to get there, so that you'll be ready to propose a talk for next year!

Transcript

1. YOU Can Speak at PyCon! Anna Martelli Ravenscroft http://goo.gl/XZYI7 1 Thursday, March 14, 2013
2. The Conference Cycle CFP Opens Prepare slides PyCon! Write & Submit Proposal Think of Topic Reviewing Notification CFP Closes 2 Thursday, March 14, 2013
3. PyCON CFP timeline • Call For Proposals Opens in July • CFP Closes in September • Reviewing: September - November • Notifications sent in early December https://us.pycon.org/2013/speaking/cfp/ 3 Thursday, March 14, 2013
4. Review process • Initial reviews • vote on proposals • feedback for presenter • Kittendome • Is it a good proposal for PyCon? • Thunderdome • Two proposals enter, one leaves https://us.pycon.org/2013/pc/guide/ +1 4 Thursday, March 14, 2013
5. Criteria • Would I go see this talk? • Would a lot of attendees go see it? • Is proposal well thought out? • Does author know enough about topic? • Is it too ambitious (or too narrow)? 5 Thursday, March 14, 2013
6. Improve YOUR chances • DON’T wait until the CFP! • Start now! 6 Thursday, March 14, 2013
7. Find a topic • What are you working on? How do you apply Python? • What packages/modules do you use? • a new feature/module/package or a different way of using it? • What projects do you contribute to? • What interests you? Some of the best talks are “related” or “fringe” topics 7 Thursday, March 14, 2013
8. Don’t self-select out • Newbies welcome! • *You* are the expert on how *you* use Python • Push the envelope • Some of the best talks are REALLY OUT THERE! 8 Thursday, March 14, 2013
9. Start talking! • Blog • Lightning talks • Unconferences • Open Space 9 Thursday, March 14, 2013
10. Give the talk! • User Groups: • BayPiggies, PhillyPUG, ... • PyLadies, ... • Other conferences: • local, regional: PyOhio, ... • international: EuroPython, ... • related: DjangoCon, SciPy, ... • unrelated: ACCU, ... 10 Thursday, March 14, 2013
11. Improve the talk • Ask audience: “What didn’t work? What was confusing?” Use Q&A • Resources to improve presentations: • books, blogs, youtube,... • Think beyond the slides • Body language and speaking • Add stories, anecdotes • Add audience participation • Video is your friend 11 Thursday, March 14, 2013
12. Submit early and often • Submit early to get more feedback • Submit multiple talks • different angles • different audiences • Submit to multiple venues 12 Thursday, March 14, 2013
13. Reviewer Feedback • While CFP is open - reviewers have more time/energy for giving feedback • Make sure we have a good eddress • Respond promptly • Modify proposal 13 Thursday, March 14, 2013
14. “Ideal” Conference Cycle CFP Opens Refine slides Write & Submit Proposal Think of Topic Revise Proposal Reviewing Notification CFP Closes Blog Lightning Talks Write & present Reviewer Feedback Practice PyCon! 14 Thursday, March 14, 2013
15. Proposal Submission • Title • Audience Level • Category • Description (50 words) • Abstract (500 words) • Notes to reviewers • Bio 15 Thursday, March 14, 2013
16. Title • Short, catchy • Descriptive • Interest not obfuscation • Guidebook 16 Thursday, March 14, 2013
17. Description • Summary for attendees • What’s the talk about? • Who is the intended audience? • WIIFM? 17 Thursday, March 14, 2013
18. Abstract • The “meat” of the proposal. Will be printed for attendees. • What’s it about? • How is it related to Python?(!) • Why is it important/interesting? • Who should attend and what will they get out of it? • Timing (too narrow/too broad?) 18 Thursday, March 14, 2013
19. Outline • Rough outline of your talk! • Topic headers with approximate timing: • intro of topic 5 mins • main points 15 mins • conclusion 2 mins 19 Thursday, March 14, 2013
20. Bio • Not just for the program book! • Who are you and why are YOU the right person to give this talk? • Don’t assume all reviewers know you 20 Thursday, March 14, 2013
21. Notes to Reviewers • anything you want us to know but don’t want printed • E.g., you’re submitting a tutorial and a talk and want to only do one or the other... • If you’ll be afk during review process • If you’re addressing/comparing multiple packages/modules, etc, -- LIST some • Don’t surprise us or leave us guessing! 21 Thursday, March 14, 2013
22. Avoid! • Sales pitch • Typing instead of slides • Internet-required • have backup plan (DESCRIBE backup plan in notes to reviewers) • CoC Violations 22 Thursday, March 14, 2013
23. Tread lightly • Case studies • What will audience learn? • In-house/proprietary products • How audience can apply info? • 45-minute talks • much higher bar for acceptance • Live demos 23 Thursday, March 14, 2013
24. If your talk’s not accepted • Remember that PyCon gets 100s of proposals each year • Consider a Poster or Lightning Talk • Try again next year! 24 Thursday, March 14, 2013
25. WE WANT To speak at PyCon! YOU http://goo.gl/XZYI7 25 Thursday, March 14, 2013