We are looking forward to another great event in 2017 with current ideas, more talks, and lots of social networking. We need you to make this happen! Please submit a talk if you have a great story to tell on any of the topics below.
The Call for Papers is now closed. Thanks to everyone who submitted.
We encourage new speakers to submit. To help with that, check out Writing a Great Abstract for a Tech Conference. (Thanks to program committee member Marcel Bruch for the tips.)
Send us email.
- Eclipse Technologies and Community Submit in this track if you want to showcase popular or upcoming Eclipse frameworks, technologies and projects, such as RCP, e4, language tools, or collaboration tools. You can also use this track to share new technology and ideas for the Eclipse community (simultaneous release, automated error reporting, Eclipse.org infrastructure, and so on).
- Modeling Technologies & Applications Eclipse is the longstanding home to a variety of mature and exciting modeling technologies designed to master the development of complex software and systems, as well as to build domain-specific modeling tools on top. This track covers all aspects of Eclipse modeling technologies, such as graphical modeling, model-based user interfaces, model transformation, validation, storage, collaboration on models, and much more. This includes EMF, Sirius, Papyrus, Capella, and more. We also welcome talks on applications of those Eclipse modeling technologies from the different industries and domains including PolarSys solutions.
- Xtext Summit This track will feature any Xtext-related talks. If you have interesting case studies to share or want to present about some advanced technical topics in Xtext, this track is for you. Best practices for language design as well as integrating Xtext languages with other modern technologies would also be of interest. Xtext Summit talks will be scheduled on Wednesday, 21 June. See the Xtext Summit page for more information.
- IoT This track is all about things and how to engage with them. 2016 has been a great year for the IoT technologies and for Eclipse IoT in particular, and there is no doubt 2017 will be even bigger. Are you developing applications that run on Devices? On Gateways? Are you focusing on Industry 4.0? Are you more on the backend side? Facing security concerns? Dealing with massive scale or tiny footprint? If you are eager to share how you use Eclipse technologies to help you build your things or have new project ideas, then this track is for you.
- Data Analytics & Data Science This track is all about technology for turning data into actionable knowledge. This includes topics such as data analysis, machine learning, simulation and modeling, big data, smart data, open data, visualizations, or high performance computing. We also welcome case studies from specific industries as well as talks from the domain specific working groups such as Science and LocationTech.
- Cloud and DevOps This track is all about cloud, containers and the infrastructure and tools that keep it all running efficiently. Doing DevOps with home-made infrastructure or whatever-as-a-service? Working with Eclipse cloud frameworks such as Orion, Che, Flux, or Dirigible? Using Docker, Vagrant, or Kubernetes? Tell us all about it in this track.
- Open Source Best Practices Open Source development requires tools and practices to foster collaboration and productivity. It includes technical best practices (distributed scm, code reviews, etc.), intellectual property and license management, people and programs that make it work, exchange with the community (activity dashboard, how to contribute, how to open bugs, etc.) or even gamification. In addition, more and more organizations try to take advantage of those successful OSS development best practices for inner development, by deploying "inner source." This track is about sharing return of experiences, evangelism, how-to's or advanced open source practices and inner source.
- Other Cool Stuff Did we miss a nice topic you want to talk about in the list above? Don't worry, there's still room for proposing it here! We are looking for talks about user experience, software quality, gamification, and so on. Any interesting topic is welcome!
Note to researchers: We also solicit researchers from academia and industry (either junior or senior researchers) to submit talks related to innovative technical solutions. To stimulate and galvanize the discussion with the Eclipse community, we strongly suggest that you include an initial implementation or demonstration to help illustrate your ideas.
Not sure of the right track? If you aren't sure which category is the best fit for your submission, just take a guess and the program committee may change it later. There's no "wrong" type of submission and we want the conference to be appealing to a large audience. If you think your topic is interesting, there's a good chance the program committee will too!
The talk types are
- Standard (35 minutes) Standard talks are the basic conference sessions, starting at 9:00 on both Wednesday, 21 June and Thursday, 22 June.
- Ignite (5 minutes) Ignite Talks are on Wednesday, 21 June at the end of the day in a special session with all conference attendees. Ignite Talks have a specific format; each talk is a maximum of five minutes long with nor more than twenty slides. (Please note that Ignite Talk speakers do not receive a free pass.)
- Showtime Demo Showtime happens during lunch on Wednesday, 21 June. For more information see the Showtime page. (Please note that Showtime presenters do not receive a free pass.)
Wondering about hands-on workshops? For 2017, workshops will be organized by community members, and held on Tuesday, 20 June, at the Unconference. For more information, see the Unconference page.
- January 18, 2017: submissions open
- March 15, 2017: early-bird submission deadline
- March 29, 2017, 23:59 CET: submissions close
Send us email.
Important Information for Speakers
We have designed EclipseCon France to maximize the opportunity to meet other attendees, visit the sponsors, and get updated on what the community is doing. The program organization is simple. Standard talks are 35 minutes long, scheduled into 45-minute time slots. Please note that the conference language is English.
We strongly encourage the actual speaker to submit the proposal. Sometimes a third party will submit on a speaker’s behalf. Typically such proposals are not accepted. We want speakers who are engaged and really want to speak at the conference. The program committee will review all proposals, but proposals submitted by third parties will be given lower priority.
Not all speakers receive discounts. Co-speakers are welcome, but for standard talks, only the first speaker on the talk gets a pass. We are not able to give passes to Ignite Talk speakers or Showtime Demo presenters.
The sessions and keynotes at EclipseCon are chosen by an independent program committee made up of volunteers from the Eclipse community. To learn more, see the Program Committee page.
Writing a Great Abstract for a Tech Conference
Note: The following guidelines were initially published here and slightly modified.
The following questions can help guide you when writing your abstract, but you may not have to answer each one of them explicitly.
- What is your talk about? It is important to be specific and to focus; you are not going for comprehensiveness in talks. Especially not in short talks.
- Who is the talk targeted at? Beginners? Experts? What knowledge is required to understand the talk? It may not be necessary to mention the answer in the abstract. But, even then, figuring it out helps you write the abstract.
- What does one get out of your talk? Attendees will scan your abstract to decide whether they will attend - or not. Make it clear what they will learn in your talk to attract the right (interested) people.
- How is your talk unique; what makes it better than other talks? You may have addressed this if your abstract already answers the former question. But sometimes people submit talks on the same or very close topics. Being precise what you will talk about (and maybe not talk about) helps the program committee to select talks with little or no overlap.
A few general tips on writing a good abstract:
- Don’t rush it. Write the abstract, leave it alone for a day or two, go over it again and then submit it.
- Stay positive and interesting.The abstract is more like a sales pitch. Be sure that you pique the interest of your readers. But stay concrete enough so that everyone gets a clear vision of what they will hear and learn in your presentation.
- Avoid language and spelling mistakes. If your abstract already contains lots of spelling mistakes, how good and well prepared will your presentation be? Obviously, non-native speakers deserve more leniency, but using a spell checker is an absolute minimum.
- Optimize for quick reading. Be concise with language. Bullet lists can help, too.
- Pick an interesting talk title. The title should contain the information what your talk is about. Don’t shy away from buzz words like Agile, Scala Testing, etc. Don't leave people totally in the dark just to sound cool (like “Houston, we have a problem”).
- Direct the abstract at the conference attendees, not at the program committee. The abstract will be used in the program, which is why the attendees are your real audience.
Tips for writing a speaker bio:
- Be concise but make sure readers know you are an expert in the domain you submit your talk in. Otherwise attendees and program committee members might give preference to others although they may have less experience in that domain than you have.
- If you’ve already have spoken at one or more conferences tell this fact to the program committee. There is often a field you can fill out like “message to the committee.” If not, consider adding it to your bio. Sounds lame? Maybe, but then the committee knows that you’re able to do a presentation and other conferences have already accepted you in the past.
- If there are slides or videos of your talks, send the links! This helps the program committee do an even better job of judging the content of your submitted talk.
Send us email.