Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Ganymede Provisioning Workshop"
(→How to register) |
|||
| Line 1: | Line 1: | ||
| − | Eclipse has long had | + | 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. | ||
==Dates== | ==Dates== | ||
| − | The workshop will meet for two to three days with consideration for long distance travelers. The exact dates and duration will be firmed up around | + | The workshop will meet for two to three days with consideration for long distance travelers. The exact dates and duration will be firmed up around EclipseCon this year. |
==Location== | ==Location== | ||
| − | The event will be held near either Ottawa, Ontario or Portland, Oregon. We prefer a relaxed and somewhat isolated environment where | + | The event will be held near either Ottawa, Ontario or Portland, Oregon. We prefer a relaxed and somewhat isolated environment where attendees can focus their full attention on workshop business. |
http://www.barbados-paradise.com/mediac/400_0/media/DIR_109/palme.jpg | http://www.barbados-paradise.com/mediac/400_0/media/DIR_109/palme.jpg | ||
| Line 16: | Line 15: | ||
==Fun== | ==Fun== | ||
| − | Taking a lesson from the [[Europa Build Workshop]], we feel at least one relaxing group activity should be included. Perhaps | + | Taking a lesson from the [[Europa Build Workshop]], we feel at least one relaxing group activity should be included. Perhaps sword swallowing or fire walking? |
==Goals== | ==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. | |
| − | == | + | ==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. | ||
==How to register== | ==How to register== | ||
| Line 38: | Line 42: | ||
==Things to be discussed== | ==Things to be discussed== | ||
| − | We will use this space to | + | We will use this space to list tools, technologies, methods, protocols and conventions that should be of interest to the participants. |
| − | + | ||
| − | + | ||
== Agenda == | == Agenda == | ||
| − | The workshop will | + | 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 | + | 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. | This is the agenda we used for the build workshop. We will adjust this to meet the needs of this workshop as they surface. | ||
| Line 72: | Line 74: | ||
* (30 min) Second summary reports and discussion | * (30 min) Second summary reports and discussion | ||
| − | At this point we will break before assembling for dinner. We expect attendees to enjoy | + | 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. |
'''Day Two''' | '''Day Two''' | ||
Revision as of 00:54, 16 February 2007
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 to three days with consideration for long distance travelers. The exact dates and duration will be firmed up around EclipseCon this year.
Location
The event will be held near either Ottawa, Ontario or Portland, Oregon. We prefer a relaxed and somewhat isolated environment where attendees can focus their full attention on workshop business.
http://www.barbados-paradise.com/mediac/400_0/media/DIR_109/palme.jpg
Fun
Taking a lesson from the Europa Build Workshop, we feel at least one relaxing group activity should be included. Perhaps sword swallowing or fire walking?
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.
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.
How to register
We are not yet taking reservations for this event. However, if you want to be on the "be sure to include me" list, write your name here.
- 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.
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.