Increasing the Odds of Speaking at EclipseCon

DZone 's Guide to

Increasing the Odds of Speaking at EclipseCon

· Java Zone ·
Free Resource

Each year people are mad/shocked/angry/disappointed/sad their talk did not get selected for EclipseCon.   Unfortunately, each year we have a limited numbers of speaking spots and typically 3-4 times the number of proposals.  The Program Committee (PC) does their best to select talks they feel will be of most interest to the attendees.   Each year I think they have always done a great job selecting a great program.

The question though is how can you increase your odds of getting your proposal accepted?

Step 1 Make sure you write a really good proposal, see our guidelines for the best practices.

Step 2  Get your proposal in early.  The PC will be reviewing hundreds of proposals and they do so over a period of time.  Don’t wait until the day before the deadline of November 30.

Step 3 Submit your proposal before November 17.  The PC will be selecting the top 5 early picks from those submitted by this date.   Instead of competing with hundreds of submissions you will be competing with likely less than 100.

Step 4 Apply to participate in the EclipseCon Audition Sessions.  If you are convinced you have a great topic but afraid the PC won’t get it, why not present a summary of the topic to the PC.  We have setup the audition sessions to allow potential speakers to make their pitch to the PC.   You can see who has already signed up for an audition.  This is your opportunity to sell your idea but you need to register by November 15 and be ready to present on November 18.


There you have it.  If you are really serious about speaking at EclipseCon, make sure you follow all these steps.  For those that submit their proposal on November 29 and 30, I wish you good luck.  For those that submit earlier, you are only increasing your odds.


From http://ianskerrett.wordpress.com/2010/11/12/increasing-the-odds-of-speaking-at-eclipsecon/


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}