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.
Ganymede Provisioning Workshop
Eclipse has long had Update Manager as its provisioning mechanism. Now over five years old, Update Manager comes from the era that predates OSGi, where Eclipse was a static tooling platform, Eclipse as a Rich Client Platform had not evolved, and where we could get away with assuming considerable computer skills in our users.
This workshop brings together committers from interested parties to evaluate current provisioning initiatives, project shared ongoing needs, and sketch an efficient and practical roadmap that leads to quality enabling solutions to provisioning problems.
Contents
Dates
The workshop will meet for two full days, April 10th and 11th, 2007.
All participants are expected to say overnight the night of the 10th. We expect some travelers will want to say the night of the 9th and/or the 11th.
Location
The event will be held about an hour's drive outside of Ottawa, at the Fairmont Le Château Montebello Hotel. We've chosen this venue for the relaxed and somewhat isolated environment where attendees can focus their full attention on workshop business.
You are responsible for your own room registration using a code we provide. See Registration below.
Goals
Overall this workshop seeks alignment and coordination between existing projects, committers and member companies with an eye to addressing the provisioning needs of Eclipse developers and users. More precisely we set out to:
- Develop a shared problem understanding and lexicon to foster future collaboration
- Define and set out the requirements for basic provisioning support
- Explore the requirements for more advanced provisioning support
- Identify key problems in the current Update Manager (and other systems) that must not be repeated
- Identify key features in the current Update Manager (and other systems) that must be retained
- Identify relevant standards and protocols and establish focal points for those technologies
- Coalesce the community around a vision for the next generation of provisioning support in Eclipse
The workshop investigation and output should be both broad and deep while still having an significant impact in the Ganymede (post Europa) timeframe. Note, however, all work products will be considered advisory to the greater Eclipse community where all final decision making will take place.
Attendance
This is not a meeting for managers or observers, it's a workshop for do-ers - people who have code or real-world experience to contribute or can provide other substantial information that furthers the goals of the workshop.
In an effort to ensure maximum communication opportunities, the overall number of attendees will be tightly managed. For example, we may choose to have at most one person from any given project attend. Teams are encouraged to coordinate and self-select delegates to participate.
The meeting will be conducted in English.
How to register
You will need to register in two places, once with the Eclipse Foundation, and then with the hotel.
- Email Anne Jacko to register with the foundation. Please tell her your full name, email and phone numbers, and which projects you will be representing.
- We do not yet have the registration code for the conference. Once we do, you will find hotel registration information here. Please let Anne know when you have registered for the hotel.
If you have an interest in attending, whether you have registered or not, you are welcome to list yourself and the nature of your interest below.
- your name and contact info here
Things to be discussed
We will use this space to list tools, technologies, methods, protocols and conventions that should be of interest to the participants.
Agenda
The workshop will alternate between plenary and breakout sessions. Attendees will collectively select breakout topics in the plenary sessions, tangibly contribute in self-assigned breakouts, and then reconvene to summarize results for the whole.
Breakout groups will be expected to quickly identify issues, review likely solutions, and recommend actions. Each group will draft written conclusions in this wiki that will be the basis of their report in the following plenary.
This is the agenda we used for the build workshop. We will adjust this to meet the needs of this workshop as they surface.
Day One
- (30 min) Introduction to the workshop, its roots in Europa, and a vision for its most valuable contribution to Ganymede. -- Ward Cunningham and Jeff McAffer
- (90 min) Lightning retrospectives presenting current systems, best practices, pain points and wish lists. We recommend these be presented from notes prepared in this wiki and following our Lightning Retrospective Guide as appropriate. -- All Attendees
- (15 min) Snack and email break
- (90 min) Lighting retrospectives continued.
- (60 min) Lunch and email break
- (30 min) Topic brainstorm and first cut prioritization. We will use some variation of "cast each of five votes on most important topics". Although topics will probably not be surprising, attendees will begin choosing how to apply their efforts the remainder of the day.
- (60 min) First breakout meeting
- (15 min) Snack, email and wiki writing break
- (30 min) First summary reports and discussion; see Europa Build Workshop Breakout Results
- (60 min) Second breakout meeting
- (15 min) Snack, email and wiki writing break
- (30 min) Second summary reports and discussion
At this point we will break before assembling for dinner. We expect attendees to enjoy the site facilities before and after dinner. However, we hope that the issues of the day and the opportunities for tomorrow will be frequent topics of conversation.
Evening
We invite attendees to participate in an experimental design technique which we will call Pod Programming. We will take one or two problems from the day's sessions and talk through programming them using CRC-Card techniques. We will pay particular attention to fitting into the design style and coding patterns employed in Eclipse. This will be recorded, indexed, and released under the EPL license. The resulting podcasts will serve as both concrete implementation hints and more abstract insight into the thought processes of our best authors.
- (45 min) Pod Programming session I
- (15 min) Break
- (45 min) Pod Programming session II
Day Two
- (30 min) Reconvene, overnight reflection. We may have an invited speaker in which case we will enlarge this spot. -- Ward Cunningham
- (60 min) Third breakout meeting
- (15 min) Snack, email and wiki writing break
- (30 min) Third summary reports and discussion
- (60 min) Fourth breakout meeting
- (15 min) Snack, email and wiki writing break
- (30 min) Fourth summary reports and discussion
- (60 min) Lunch and email break
- (60 min) Fifth breakout meeting
- (15 min) Snack, email and wiki writing break
- (30 min) Fifth summary reports and discussion
- (90 min) Consolidation, assessment and call to action -- Bjorn Freeman-Benson, et. al.
At this point the formal workshop will be over. We expect eastbound attendees to stay over for early morning flights.