Skip to main content
Jump to: navigation, search


NOTE: This site does not yet have definite information. Currently everything on this page is speculative and for planning purposes by the organizers. When dates and locations become fixed, we will make the announcements and remove this banner.


The focus of the event is to gather companies with commercial products based on Eclipse or packages that install into Eclipse. Attendees will integrate their products and test whether they work together in harmony. The outcomes of the event, in addition to the testing, will be

  1. To create requirements for the Eclipse platform to make the task of integrating different products easier
  2. Create guidelines and best practices for future commercial adopters to follow
  3. Build a network of contacts to allow for better integration in the future, outside the boundaries of PluginFest events


  • Eric Cloninger (Motorola) ericc@
  • Ian Skerrett (Eclipse Foundation) ian@

Date and Time

We are planning 2-3 days in the middle of the week during February. The final date will depend on the responses of the attendees and the availability of meeting space.

  • Feb 1-3
  • Feb 8-10
  • Feb 15-17
  • Feb 22-24


This event will probably occur somewhere in the SF Bay area. We are looking for offered space from one of the organizers/attendees or using meeting space at a hotel. We are considering several locations outside SF Bay.

  • Sunnyvale/Mountain View area
    • Staybridge Suites (101 & 237 on Mathilda) - Approximate cost: $800 (small facility, flexible terms - 25 people max)
    • Country Inns and Suites (237 & Lawrence) - Approximate cost: $5500 (large facility, they handle everything)
    • Motorola offices
    • Google campus (probably available)
  • Burlingame/SFO airport area
    • Crowne Plaza (101 & Broadway)
  • Outside SF Bay area
    • Belize
    • Austin, TX (Nokia or MOT)
    • Chicago (Motorola offices downtown or WIND/Downers Grove)
    • Ottawa

Because this meeting will involve lots of people working in pairs, we expect people to come and go as necessary and probably work late into the evening of the first night. We will try to find a location that will accommodate this need.


Attendees should be developers who understand how their products are built, configured, and used. Ideally, at least one developer and the person responsible for the vision of the product (e.g. Product Manager), although this could easily be the same person. The developer should be capable of making code and resource changes, rebuilding the product and any installation or distribution media. At least one representative from the company should be prepared to handle key generation requests in "near" real-time.

Add an entry to the table below if you are interested in attending and your choice of dates.

Name Company Role Product(s) tested Meal Planning Choice of date
Eric Cloninger Motorola Product Manager MOTODEV Studio Omnivore Any
TBD Motorola Engineer MOTODEV Studio / Sequoyah Omnivore Any
Doug Schaefer Wind River Engineer
Xavier Ducrohet Google Engineer Android
Google Engineer App Engine
Google Engineer GWT
Google Engineer Instantiations

On-site requirements

  • Reliable internet
    • Wired
    • Wireless
    • Switches + network cables
  • A/V equipment (rented or loaned)
    • Projector + Screen (preferably capable of greater than 1024x768)
    • LED monitors (22" or greater)
    • Pristine test machines


  • Meeting space (whether on-location or off-site)
  • A/V equipment
  • Catered Breakfast & Lunch
    • Continental breakfast
    • Sandwiches, salads, and cold cuts for lunch
  • Pizza delivery for Dinner + drinks (beer + soda) on Night 1
  • Possible group event at conclusion of Night 2

Testing Procedures

  • Pristine test environment vs. real-world
  • VMWare images
    • WinXP
      • Classic Theme
      • Standard Theme
    • Win7
    • Ubuntu 10.10
    • Fedora 14
    • MacOS?


Day 1

  • 8:30 Registration, setup, socializing
  • 9:00 Opening remarks (15-30 minutes)
    • Purpose and outcomes of the event
    • Methods of testing
    • Recording results for event report
    • Conflict resolution
  • Lecture (60-75 min) - The purpose of this prior to the testing is to perform level-setting up front about what is and is not a common property, so that when problems are found, that the people in the room can make corrections on the fly and possibly test again.
    • Common properties in Eclipse
    • Proper ways to extend/manipulate common properties
    • Installation workflows
      • Monolithic install
      • Merged install
      • Products vs. plugins
      • P2 vs. Mylyn vs. ???
  • Break
  • Decide pairings for Day 1, based on likely user scenarios
  • Work through the remainder of the day on testing products
  • 12:00 Lunch (catered onsite)
  • 17:00 Recap
  • Work as late as individual teams want. Have pizza and beer delivered at 18:00.

Day 2

  • 8:30 Breakfast, socializing
  • 9:00 Post-mortem
    • What worked, what didn't in Day 1
    • New discoveries
  • Decide pairings for Day 2, based on individual preference, chosen by lottery
  • 11:30 Lunch (offsite, catered onsite, or individual choice)
  • 16:00 Reconvene to discuss how to help future developers avoid the pitfalls identified in this event
    • Best practices documentation
      • already available
      • created by this group (volunteer)
  • 18:00 Evening entertainment

Back to the top