Submission FAQs

Sun, 2013-09-15 14:10

Thank you for taking the time to consider presenting at EclipseCon North America 2014. Your submissions are the heart of the conference, and we couldn't have an EclipseCon without you!

We look forward to reading your proposals. If you have a question that isn't answered below, please email us. The FAQs will be updated regularly, so check back occasionally for new information.

When is the submission deadline?

The last day for proposals to be submitted is November 18, 2013. If you want to be considered as an Early Bird Selection, the last day to submit is November 4.

What is an Early Bird selection?

Before the submission deadline, the program committee will pre-select a short list of their favorite talks and publish these on the conference website. You'll get early notification that your talk is accepted, and some special publicity that will generate interest in your session. If you want to be considered, submit your talk by November 4.

Are speakers compensated for speaking?

Speaking at our events gives you exposure to an audience of highly skilled developers and other software professionals from around the world. Logos from our EclipseCon Friends page will help you publicize your talk on your website or blog. For the hard cash type of compensation, each standard talk earns one free pass. Tutorials earn two free passes. Please note: the first speaker listed on a standard talk gets the discount; the first and second speakers listed on a tutorial get the discounts. For details, see the Speaker FAQs. We do not pay speaking fees or reimburse speakers for travel costs.

Who is choosing the program?

The program committee, made up of volunteers from the Eclipse community, chooses the program.

When will I know if my talk has been accepted?

Accept/decline notices are expected to go out the first week in December. The program will be published on the website shortly after that.

How do I submit a talk?

You must have an account before you can submit a talk. If you already have an account, log in using those credentials.

If you need to create a new account, follow these steps to create and activate your account:

  • Click on the "Create an account" link at the top of the conference home page. Then click on the "Create an account" tab on the Log In page, and follow the instructions to create your account
  • Look for an email with instructions on activating your account, and follow those
  • After your account is activated, use the same credentials to log in to the conference website via the "Log in" link in the main menu -- the account can't be used on the conference website until this initial login occurs!
  • Note that this account may also be used on the website (for the Forums, for Bugzilla, for the wiki, etc.)
  • If you need to reset your password, go to the account creation page and follow the instructions there
  • If you are still having trouble, email the webmasters

To complete the submission form:

  • Enter a short, descriptive, and catchy Session Title
  • Choose the Session Type: Standard (35 minutes) or Tutorial (3 hours)
  • Enter the Speaker name(s)
  • Enter Tags (your choice) to help describe the content (modeling, SOA, "success story", etc.)
  • Choose the Track (see track descriptions below)
  • Choose the Experience Level (Beginner, Intermediate, or Advanced
  • Before writing the Description, read the advice below on increasing your chances of being accepted
  • If you have your proposal in a file, use the Slides field to upload the file. You can also add a link to the file in your Description if you prefer.

Please note that the submission system does not send an auto-email to confirm that your talk was successfully submitted. To verify that your talk is in the system, use the filters on the list of submissions page to locate it. If you don't find it, please send email to

Do I need to sign a Speaker Agreement?

For previous EclipseCons, we required speakers to sign a separate Speaker Agreement and Recording Waiver. Currently, a submitter agrees to our speaker terms and conditions (including the recording waiver) when submitting a talk. Click here to read the full text of the Speaker Agreement and Recording Waiver.

What are the track descriptions?

Here are the track descriptions:

  • Eclipse RT - talks about Jetty, Equinox, OSGi, Scout, etc.
  • Eclipse RCP/Eclipse 4 - talks on migrating to Eclipse 4, best practices for Eclipse 4, building RCP applications, case studies, etc.
  • JavaScript Development - talks on Orion, frameworks like node.js, bootstrap, general JavaScript development, plus anything else of interest to JavaScript developers
  • Java Development - talks about Java 8, Java for PaaS, new Java frameworks, etc.
  • C/C++ Development - talks on embedded development, Linux development, or other talks relating to using Eclipse for C/C++ development
  • Lifecycle Tools - talks on tools are used throughout the software development process, like Hudson, Maven, Gerrit, Git, etc.
  • Modeling - talks about using Eclipse modeling technology, domain specific languages, etc.
  • Other Cool Stuff - other interesting things that you think developers need to learn, such as usability, community building, or legal issues – you decide what you think is cool!
  • Vert.x Day (for the Vert.x Theme Day; see below) - talks of interest to the Vert.x community
  • M2M Day (for the M2M Theme Day; see below) - talks about Eclipse M2M projects and other related technologies, such as Arduino, BeagleBone or Raspberry Pi
  • PolarSys Day (for the PolarSys Theme Day; see below) - talks about the PolarSys Working Group and technologies related to embedded system development

How will I know if someone comments about my submission?

The submissions system will send you an auto-email if someone comments on your submission.

What can I do to increase my chances of being accepted as a speaker?

Your submission will look better from the start if you follow this advice.

  • Choose the Session Type, Track, Experience Level, and Tags carefully – try to get it right the first time
  • If you receive an email from a program committee member, respond promptly
  • Be prepared to work with the program committee to modify your talk to fit into the program; this can mean shortening it, combining it, etc.
  • Take time to write a good Session Title – descriptive, yet short and interesting
  • The bar is higher for tutorials! For tutorials, include an outline that covers the content and the hands-on exercises you expect to have in the tutorial
  • And above all, make sure your Description is good – if your title is longer than your description, you have more work to do. All descriptions should indicate
    • What you are presenting
    • Why it is important
    • What someone can expect to take away from the presentation
    • What makes your presentation unique

What are some useful tips to know before submitting?

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, ask yourself this question: Why would someone want to use their valuable time listening to this presentation? After each conference we survey the attendees, and they have been consistent and clear about how to improve our technical talks. You will have a better chance of being selected as a speaker if you do the following:

  • Tell your story. Technical deep dives are interesting. But so is your experience! What have you been doing? How have you combined the various Eclipse technologies? Did everything work well? What have been the problems and how did you solve them?
  • Provide your presentation materials ahead of time. Either upload a file with your submission, or choose a file-sharing site for your materials and add the URL to your Description. Providing advance materials is a great advertisement for your talk and increases attendee interest in your presentation. It helps the attendees pre-select sessions, providing you with an audience that is already interested in your topic.
  • Be clear about requirements and expectations. Should attendees have software pre-installed? Should they know how to use a particular plug-in in order to get the most benefit from your session? Should they be proficient in a certain technology? For tutorials, this type of information is required.
  • Provide detail about your talk. Have you given this talk before? If so, where and when? Will your talk include a demo? Hands-on exercises? Singing and dancing?
  • Get organized before your talk. This is especially true – and required – for tutorials. Instead of spending the first thirty minutes helping attendees install software from a flash drive, use your Description to tell attendees how to prepare for the session, and provide a link to items they should download ahead of time. Then you and your audience can get to the interesting stuff right away.
  • Upload a photo and bio to your website account. Use the bio to explain why your experience, knowledge, and presentation skills will help make your talk worthwhile.

Choosing a good Session Title can be tricky. Your title should be short, descriptive, and catchy. If you want people to attend your talk, work on the title! Here's a simple test: If you are faced with choosing between the following two talks, which one would you choose?

  • Pimp My Editor or
  • Improving the Visual and Functional Attributes of the Eclipse Editor Through the Addition of Compelling Visual Communication Elements.

Back to top