OSCON 2012 Call for Participation
11:59pm 01/12/2012 PST.
Submit original session and tutorial ideas that share your excitement. Proposals should include as much detail about the topic and format for the presentation as possible. Vague and overly broad proposals don’t showcase your skills and knowledge, and our volunteer reviewers aren’t mind readers. The more you can tell us, the more likely the proposal will be selected.
If you are one or more of the following:
- Developer or programmer
- Systems administrator
- Hacker or geek
- Enterprise developer or manager
- IT manager, CxO or entrepreneur
- Trainer or educator
- Open source enthusiast or activist
We invite you to submit a proposal to lead conference sessions or tutorials at OSCON 2012.
Some of the topics we’re on the lookout for the 2012 conference program are:
- Best practices for building a business around open source
- Innovations in user experience such as interfaces, design, and UIs
- Cultural changes due to ubiquitous network and compute
- Cloud computing, openness in distributed services
- Geek lifestyle – hacking, quantified self, inbox zero, maker culture
- Open web, open standards, open data, open, open, open!
- Leadership in the changing Open Source culture
You’ll be asked to include the following information for your proposal:
- Proposed title
- Overview and extended descriptions of the presentation: main idea, sub topics, conclusion
- Suggested track
- Speaker(s): expertise and summary biography
- Suggested tags
Proposals will be considered for the following types of presentations:
- 3-hour tutorials
- 40-minute presentations, discussions, or panels
Limited speaking opportunities are also available through conference sponsorship. Contact Sharon Cordesse at (707) 827-7065 or firstname.lastname@example.org for more information.
Some tips for writing a good proposal for a good talk:
- Help us understand why your presentation is the right one for OSCON.
- Keep the audience in mind: they’re technical, professional, and already pretty smart. They also will smell a marketing pitch.
- Clearly identify the level of the talk and why people will want to attend: is it for beginners to the topic, or for gurus? Is this a trending topic, or an installation tutorial?
- Give it a simple and straightforward title or name: fancy and clever titles or descriptions make it harder for people (committee and attendees) to figure out what you’re really talking about
- Limit the scope of the talk: in 40 minutes, expect to pick a useful aspect of a topic; a particular technique; or walk through a simple program
- Pages of code are unreadable: mere mortals can deal with code a line at a time.
- Be authentic! Your peers need original presentation ideas that focus real-world scenarios, relevant examples, and knowledge transfer
- If you are proposing a panel, tell us who else would be on it
- Include people we don’t see often enough at tech conferences: Does your presentation have the participation of a woman, person of color, or member of another group often underrepresented at tech conferences? Diversity is one of the factors we seriously consider when reviewing proposals as we seek to broaden our speaker roster.
- Above all else, present something relevant. One of your challenges as a proposer is to demonstrate that you understand that attendees might need an extra reason to pay attention to something that they might otherwise think of as “settled”
Other resources to help write your proposals:
- Call for Participation Closes – January 12, 2012
- Program Announced and Registration Opens – March 2012
- All proposers notified – end of March 2012
Submit your proposal — Proposals are due January 12, 2012