Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseCon Submission Guidelines"

Line 1: Line 1:
 
{{Backlink|EclipseCon 2008}}
 
{{Backlink|EclipseCon 2008}}
==Discussion==
+
==So You Want to be a Presenter?==
The EclipseCon conference committee is committed to putting on the best EclipseCon ever.  The most important feature of EclipseCon is the presentations.  Typically there are far more quality presentations than there are slotsThis section of the wiki is dedicated to establishing common guidelines that will be used by the program committee members to evaluate and select presentation proposals.
+
Thank you for taking the time to consider presenting at EclipseCon 2008.  The success of the conference is primarily based on the presentations that are put on by people like youWe would love to be able to provide a speaking slot to everyone. Unfortunately, we have a limited number of slots. 
  
==Selection Criteria==
+
In order to help you make the best submission possible, we have created this short guide on how to create the best possible submission.  Please also review the [[Selection Guidelines | EclipseCon Selection Guidelines]] since this will provide insight into how proposals are evaluated.
* '''Quality'''
+
**'''Abstract quality''': a well-articulated, well-written abstract should be indicative of the quality of the presentation
+
**'''Speaker quality''': known, expert speakers are clearly desirable
+
**'''Outline''': An outline of the presentation that is submitted with the proposal is desirable
+
  
* '''Feedback'''
+
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:
** '''Program Committee Votes''':
+
** '''Committer Votes''':
+
** '''Community Votes''':
+
** '''Community Feedback''': As represented in the EclipseZilla comments
+
** '''Presenter Response''': How does the presenter respond to feedback?
+
  
* '''Balance''':
+
'''Why would someone want to spend an hour of their time listening to this presentation?'''.
** '''Content Depth''': Introductory to Advanced Topics
+
 
** '''Track Coverage''': Wide range of subjects within the track
+
A second consideration has to be the unique-ness of your presentation.  Please take the time to search the other proposed talks to make sure that someone has not all ready proposed the same talk.    If someone has a talk that is very similar to yours, you may want to approach them about working together on the presentation.  Some of the very best presentations are done by a team of presenters.
 +
 
 +
==Submission Guidelines==
 +
 
 +
===Abstract===
 +
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?
 +
 
 +
===Audience===
 +
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?
 +
 
 +
===Outline===
 +
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.
 +
 
 +
===Slides===
 +
Optional - If you have the slides that you plan on presenting, please include them with the submission.
 +
 
 +
===Takeaways===
 +
Will your audience get anything to take away with them?  Will you provide any source code for the examples that you present? 
 +
 
 +
===Speaker Qualifications===
 +
Who are you and why are you qualified to speak on this subject? 
  
* '''Open Source'''
 
** '''Source Available''': The source or examples used in the talk should be freely available under OSS license.
 
** '''Eclipse Technology''': Presentations on Eclipse technology are preferred.
 
** '''Open Source''': Presentations on Open Source technology that interacts with Eclipse are better.
 
** '''Commerical Eclipse''': Commercial products that are Eclipse focused are less good.
 
** '''Commercial Non Eclipse''': Not appropriate for EclipseCon.
 
  
 
[[Category:EclipseCon2008]]
 
[[Category:EclipseCon2008]]

Revision as of 17:28, 1 August 2007

< To: EclipseCon 2008

So You Want to be a Presenter?

Thank you for taking the time to consider presenting at EclipseCon 2008. The success of the conference is primarily based on the presentations that are put on by people like you. We would love to be able to provide a speaking slot to everyone. Unfortunately, we have a limited number of slots.

In order to help you make the best submission possible, we have created this short guide on how to create the best possible submission. Please also review the EclipseCon Selection Guidelines since this will provide insight into how proposals are evaluated.

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 spend an hour of their time listening to this presentation?.

A second consideration has to be the unique-ness of your presentation. Please take the time to search the other proposed talks to make sure that someone has not all ready proposed the same talk. If someone has a talk that is very similar to yours, you may want to approach them about working together on the presentation. Some of the very best presentations are done by a team of presenters.

Submission Guidelines

Abstract

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?

Audience

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?

Outline

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.

Slides

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

Takeaways

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

Speaker Qualifications

Who are you and why are you qualified to speak on this subject?

Back to the top