Call For Participation
Richard Gronback,
Borland,
EclipseCon 2007
Program Chair
There are many ways to participate in EclipseCon 2007.
The easiest way is to register
and then show up in Santa Clara,
attend sessions, converse with colleagues, and use the hallways
and lunch tables to both learn and teach about Eclipse.
If you'd like to take a little more active role in EclipseCon,
we invite you to help select the conference program. The selection
is done in an open and transparent way using the Eclipse open source
project rules. Specifically, all submission is done through
a modified Bugzilla system (hereafter known as Eclipsezilla).
Anyone in the community (including you) is welcome to review the
submissions, ask for more information, provide comments and critiques
- just as anyone in community is invited and encouraged to do for
Eclipse bugs and features.
Important Dates
- November 1st - Tutorial proposals must be in.
- November 15th - Tutorials chosen.
- December 1st - Long Talks and Panel proposals must be in.
- December 30th - Long Talks and Panels chosen.
- January 30th - Most Short Talks and Demos chosen.
- January 31st - Short Talks and Demos proposals must be in.
- February 10th - Remaining Short Talks and Demos chosen.
How To Submit A Proposal
A simple four step process:
irst, create an Eclipsezilla account
including your name, affiliation, bio, contact information, and a picture.
In good open source style, the responsibility for your bio, picture and
other information is yours - the EclipseCon website is automatically
populated from the Eclipsezilla information (i.e., nobody checks your
bio for spelling or completeness), so you'll want to make sure that it
is accurate.
If you have submitted to a previous EclipseCon, your Eclipsezilla account
is still active and there's no need to create a new one. You might want to check
your bio and perhaps update your picture.
econd, choose your presentation type.
EclipseCon has a wide variety of presentations: longer versus shorter,
overview versus hands-on, single speaker versus panels, and so on. It
behooves you to choose the right style for your topic because the
program committee will not (they'll consider your submission as is - if
it doesn't fit the type, for example if you have a hands-on short talk,
they will reject it).
- Long Tutorial - All day hands on, writing code, workshop dedicated to
learning the intricate details of the topic. These are extra cost sessions and
the attendees have high expectations. All long tutorials must include a
hands-on workshop component with a concrete take-away for
the attendees: e.g., a working piece of code they have written as learning
for the concepts and techniques. Tutorials should either be repeats of
well-received tutorials from previous conferences (because there are always
first-timers at EclipseCon) or original subjects (new to everyone).
In either case, the tutorial should include original material, examples,
or presentations because to quote a source,
"I'd hate to attend a tutorial that uses [100% of] the same content as I can
get online".
Tutorial submissions are closed.
- Short Tutorial - A two hour presentation, typically with a demo
component, but not a hands on workshop (just not enough time). These are extra
cost sessions and the attendees have high expectations. All short tutorials
must include a take-away, for instance an example project with
setup instructions to allow the attendees to experiment post-tutorial.
Tutorials should either be repeats of
well-received tutorials from previous conferences (because there are always
first-timers at EclipseCon) or original subjects (new to everyone).
In either case, the tutorial should include original material, examples,
or presentations because to quote a source,
"I'd hate to attend a tutorial that uses [100% of] the same content as I can
get online".
Tutorial submissions are closed.
- Long Talk - A one hour (or slightly less) presentation that goes
into detail on a topic. A good talk requires preparation and a good pace;
the EclipseCon audience is typically intelligent and well prepared and thus
any introductory material should be very brief (less than five minutes).
There will be four or more long talks happening simultaneously
(in separate rooms, of course).
Long talk submissions are closed.
- Short Talk - A five to ten minute presentation that covers the
highlights of a topic. The goal of a short talk is to interest the
audience in learning more, either from your website or by talking to
you later during the conference. The time limits will be strict.
Short talks are the EclipseCon version of lightning talks
(see the Perl conference's advice
on giving a lightning talk).
Short talk submissions are closed.
- Panel - A one hour session utilizing four or more panelists
talking about, or answering questions on, a general topic. This is not
a short talks session and thus the panelists do not have prepared slides.
The goal is a conversation or a controversy that is educational for the
audience. These are scheduled in parallel with other talks.
Panel submissions are closed.
- Demo - Demos are half-hour semi-lecture style demonstrations
of something interesting about Eclipse or based on Eclipse. They are
rather informal, in a smaller room, and should not involve any significant
slideware - perhaps an introductory slide with your name and thereafter
the demo.
Demo submissions are closed.
- Posters - Posters are, well, posters. During the poster
reception session, the poster authors stand by their posters and
answer questions. The rest of the time, the posters will be displayed for
attendees to browse. Posters are static; there is no table and no power
outlet for a demo.
Poster submissions are closed.
- Table Topic - During lunch, each table will have a table
topic on a sign in the middle of the table. The goal of the table
topic is that you sit at a table with other similarly-interested
individuals and thus, through conversation, you can feed your
mind as well as your body. Popular table topics will be assigned
to multiple tables in order to accommodate everyone.
Table topic submissions are closed.
- Birds of a Feather - Birds of a Feather meetings are
informal (i.e., unplanned) one-and-a-half-hour gatherings of people
who want to talk about a particular topic. BOFs are similar to
Table Topics except that BOFs happen in the evenings and are
semi-scheduled. Some BOFs are scheduled in advance but most BOFs are
scheduled on an on-demand basis at the conference itself: hosts put
up sign-up sheets, attendees sign up, and then at 5pm, the
conference organizers assign rooms and times to the most popular BOFs.
BOFs are open to everyone. There are typically a dozen simultaneous BOFs.
hird, choose your destination program committee.
EclipseCon 2007 does not have a single Program Committee to filter all the
submissions. Instead, we have sixteen (16) separate sub-committees, each
specializing on a certain aspect of the Eclipse ecosystem. In good open source
style, it is your responsibility to submit your proposal to the most appropriate
sub-committee. Please take the time to choose carefully as the sub-committees will
NOT re-assign your mis-categorized submission.
- Business - The business track is looking for long talks, short
talks and panel submissions related to doing business with Open Source. Both
practical and academic experiences are welcome. Topics can include things
such as as business models (making money with open source), legal issues and
marketing experiences.
- C/C++ Development - Topics around the Eclipse C/C++ tooling.
- Data Tooling - Topics around the Eclipse data tooling, including
databases development with Eclipse frameworks.
- Fundamentals - Topics around those more general aspects of Eclipse, such as writing
Quality APIs, User Assistance, release engineering, the Eclipse process, etc.
- Industry Vertical - The industry vertical track is looking for short
talks and panel submissions related to the use of Eclipse technology within specific
industry verticals such as Automotive, Healthcare or Finance. Topics can be either
of a technical or business nature and could cover emerging domain specific
platforms or other solutions for the vertical.
- Java Development - Topics around the Eclipse Java tooling.
- Mobile and Embedded - Topics around using Eclipse to develop
device software for mobile platforms and other embedded devices. Frameworks, tools, and user experiences.
- Modeling - Topics around the various Eclipse Modeling technologies.
Implementation, use, meta-models, graphical and textual models.
- OSGi - Topics around OSGi and the OSGi sub-system underlying Eclipse.
- Project Mashups - Topics about the interaction between Eclipse projects and/or other software products. This is an opportunity to share you ideas and experiences using the Eclipse Framework to create software solutions.
- Reporting - Topics around Reporting using Eclipse tools and
frameworks. Internals, use cases, and technology.
- Rich Client Platform - Topics around the Rich Client Platform, both
implementation and use.
- SOA Development - Topics around developing for
Service Oriented Architectures using Eclipse tools and frameworks.
- Test and Performance - Topics around the Eclipse Test and Performance
tooling: implementation, extension, and use.
- Technology and Scripting - Topics including the Eclipse Technology projects,
interesting new technologies, and scripting for the Eclipse platform.
Aperi, ALF, Buckminster, Corona, Higgins, Mylar, Parallel Tools, Rich AJAX, and more.
- Tools - Topics around the Eclipse Tools sub-projects including
PHP, Fortran, and AspectJ.
- Web Development - Topics around tools for Web and J2EE application development, including server tools and editors for web-related languages.
ourth, enter your presentation information
into Eclipsezilla.
Be sure that you enter your submission
into Eclipsezilla sufficiently before the deadline that both
the community-as-a-whole and the program sub-committe have time
to review it. Obviously, the last day is too late. If hundreds of submissions
appear on the last day, there won't be enough time for to
review them all and your submission might be one of the ones declined for
lack of reviews rather than accepted for being excellent. So why push the
envelope? Submit early and be free of worry!
The EclipseCon website is automatically generated from the
accepted Eclipsezilla entries so, as with your bio and picture, it is
your responsibility to ensure that your title and abstract are interesting
and correct. Neither the program committee nor the conference organizers
will spell check or edit your submission.
Click on the appropriate purple button
to begin your submission...
ifth, after your submission is accepted,
prepare your presentation materials (PDFs of the slide decks, or better yet,
skip the slideware and include a
well-written paper with a zip of working example code) and (optionally) upload them
to Eclipsezilla. This will automatically make the
material available on the EclipseCon 2007 website before, during, and
after the conference. We make the materials available in advance because
the reason for attending an EclipseCon presentation is to listen to you, the
expert, rather than to read the slides.
Providing the materials in advance has a number of advantages:
- It's a better advertisement for your presentation than any abstract could be.
- It allows people to follow along and make notes on their tablets.
- It allows the audience to self-select and thus you can assume the
audience is interested and knowledgable. You can skip the introductory
materials and get to "the good stuff" quickly.
It's That Easy
It's that easy - just one, two, three, four and your proposal is in
the system and being considered by the appropriate program sub-committee.
Business: BOF
