Skip to main content
Jump to: navigation, search

EclipseCon 2009 Submission Guidelines

Revision as of 18:11, 17 October 2008 by (Talk | contribs) (Difficulty)

< To: EclipseCon 2009

These pages are referenced from the main website. [1]

So You Want to be a Presenter?

Thank you for taking the time to consider presenting at EclipseCon 2009. Your submissions make up the heart and soul of our conference. We would love to be able to provide a speaking opportunity to everybody. Unfortunately, we have a limited number of slots, so we need to pick those talks that we think will provide the best conference possible.

This short guide has been created to help you create the best presentation submission possible. Submissions are evaluated and selected by the EclipseCon 2009 Program Committee (PC). The PC is divided into categories that are loosely based on the Eclipse project structure. Our goal is to provide a balanced program that represents all of the Eclipse projects and communities. Please review the EclipseCon 2009 Category Descriptions to insure that your talk is submitted to the appropriate category.

The category representatives with finding the best talks for their category. Each representative will use their own evaluation criteria based on the goals of their category, but we all share the EclipseCon 2009 Selection Guidelines.

I have also created a blog post which provides additional thoughts and references.

Submission Guidelines

Quality presentations are a lot of work! If you are not prepared to spend the time putting together a quality proposal, it is unlikely that you will find the time to prepare for the presentation. Take the time to think clearly about what you want to say, and more importantly:

Why would someone want to use their valuable time listening to this presentation?.

Category Check

Please take the time to search the other submissions within your chosen category. If someone has a talk that is very similar to yours, you may want to approach them through the comments section to suggest working together on a presentation. Some of the very best presentations are done by a team of presenters.

Speaker Qualifications

Anyone can submit a talk, but the PC is looking for the very best presentations. Great presentations require a good topic, but the key is the presenter. Your experience, knowledge, and presentation skills all make a difference. Please fill out your bio in the EclipseCon system.

If you have done this presentation at a different venue, please add a comment to your submission that details when and where. If this is your first time presenting at a national conference, please consider a short talk (10 minute or 30 minute).

The Submission is Only a Starting Point

Please be prepared to work with the category reps to modify your talk so that it can fit into the program. This may mean combining your talk, shortening your talk, or changing the subject matter.

The Submission Form

The Eclipse submission system has been designed to be very easy to use. All you need is a Title, Abstract, Type, Category, Difficulty, and a list of the authors. That said there are things that you can do to distinguish your submission from the others.


Short, Descriptive and Catchy. We all hate sales, but that doesn't mean we can live without. Your title is your sales pitch. If you want people to select your talk or attend your talk work on the title. A simple test if you are faced with two talks:

  • Pimp My Editor
  • Improving the Visual and Functional Attributes of the Eclipse Editor

Which one would you choose?


The abstract is the most inportant component of your submission. Take the time to demonstrate that you are an articulate communicator that has something valuable to share with the community. At a minimum your abstract should address these four questions:

  • What are you presenting?
  • Why is it important?
  • What can someone expect to take away from the presentation?
  • What makes your presentation unique?


EclipseCon has three basic types of talks.

  • Short Talks are 10 to 30 minutes long and are designed to get people excited and engaged on a particular subject. If you do a great job on a Short Talk the audience won't know how you have done something, but they will be really excited to take the time and learn it on their own.
  • Long Talks are one hour in length and are designed to provide a thorough road map of a particular technology.
  • Tutorials are four hour hands on presentations where it is expected the attendees learn how to work with a technology. All of the EclipseCon tutorials will require that the instructor to let the attendees get their hands dirty. Tutorial presenters should expect to have their presentation reviewed by the PC representatives in the month prior to the conference start.


Please refer to the EclipseCon 2009 Category Descriptions for a full discussion of the categories.


The program committee is attempting to provide something for everyone. That means we need talks that range in difficulty from the novice to the expert. We have adopted the ski run standard to identify the difficulty of a talk.

  • Green circle.png Green Circle - Easiest
  • Blue square.png Blue Square - Intermediate
  • Black diamond.png Black Diamond - Difficult
  • Double black diamond.png Double Black Diamond - Expert

When gauging the difficulty, consider how difficult would it be for a typical person that is a member of the categories community. If your talk is based on having two years experience developing SWT widgets, you have a dreaded Double Black Diamond. If you feel your talk can be attended by anyone that is attending the conference, you have a Green talk.


Additional Information

Once you have submitted your abstract, you should return to your submission and add a comment (or two or three or four) with additional information for program committee. It is important to use a comment so that this information is not displayed on the website as the abstract.


It is very helpful when evaluating presentations if the presenter states who they think their audience is.

  • What types of experience should your audience have?
  • How technical should your audience be?
  • Will your audience participate in any way? If yes, how?
  • What does someone that doesn't fit the above two objectives get out of your presentation?


Typically, presenters do not know exactly what they will present since the conference lead times are relatively long. A high level outline provides insight into your presentation and typically augments the Abstract nicely.


Optional - If you have the slides that you plan on presenting, please include them with the submission.


Will your audience get anything to take away with them? Will you provide any source code for the examples that you present?

Back to the top