This industry working group charter is governed by the Eclipse Foundation Industry Working Group Process document.
- 1 Problem statement
- 2 Goals and Vision
- 3 Core services and activities
- 4 Connections with other Eclipse Working Groups
- 5 Membership
- 6 Governance
Adoption of Eclipse tools and runtimes has reached an all time high, and today Eclipse software is embedded into many commercial software products. Enterprise software vendors are required to support their products, including the Eclipse components, for many years. Thus they are looking for support offerings that cover a variety of Eclipse projects and a large number of releases. The issue becomes more urgent the more Eclipse technology reaches into the runtime stack.
Due to the diversity of projects and committers at Eclipse, which come from a variety of companies and individuals, it is currently impossible to get a 'one-stop-support-contract' for all of Eclipse technologies needed. Vendor neutrality and diversity bring innovation and long term viability to Eclipse, but make it difficult to provide the support enterprises are looking for. It is very difficult for any one company in the Eclipse ecosystem to offer support and maintenance that covers the entire spectrum of Eclipse technologies.
Goals and Vision
The goal of the Long Term Support (LTS) Industry Working Group (IWG) is to enable the Eclipse ecosystem to consume and provide maintenance and support for the full breadth of Eclipse technologies.
To implement this vision, the IWG will:
- Enable an ecosystem-based solution for long term support and maintenance.
- Define and implement the policies, procedures and infrastructure required for long term support and maintenance, including software repositories, software builds, software distribution, and test facilities.
- Define a roadmap for LTS deliverables.
- If agreed to by the Steering Committee, create and define the content to be contained in LTS releases, including:
- defining an LTS release branch based on an Eclipse release train, and
- the content of LTS service releases.
There are 4 roles in this ecosystem:
- Consumers are organizations that acquire maintenance and support services.
- Maintenance Service Providers(MSPs) leverage the IWG systems to provide commercial support and maintenance services to Consumers.
- Self Service Maintenance Providers(SSMPs) are Consumers that leverage the IWG systems to provide internal support and maintenance services.
- Project Support Providers(PSPs) are organizations or individuals that leverage the IWG systems to provide support and maintenance services for one or more Eclipse projects.
It is expected that MSPs and SSMPs will aggregate the services of PSPs to provide service to Consumers.
Core services and activities
- LTS provides a forge that enables building Eclipse software in the future for maintenance and support. The forge will include:
- Code repositories
- Bug tracking
- Knowledge management
- Software distribution and code signing
- Access to this forge will be available to employees and contractors of IWG participating organizations. This access enables creation of the following:
- Software updates
- Maintenance releases
- A listing service that lists Member organizations capable of providing support and maintenance for Eclipse technologies.
Connections with other Eclipse Working Groups
The LTS IWG may have connections with other IWGs such as Polarsys, Automotive, and others.
In particular, there will be a strong link between LTS and Polarsys. Specifically, Steering Committee Members of the Polarsys IWG will automatically be Participating Members of the LTS IWG.
An entity must be at least Solutions Members of the Eclipse Foundation, have executed the LTS IWG Participation Agreement, and conform to this Charter to participate in the LTS IWG.
There are two membership levels: Steering committee and Participating. Steering committee members have governance influence over the direction of the IWG. Both levels have access to the LTS forge.
LTS IWG Steering Committee Member Fees
|Turnover||Eclipse Solution Membership||Steering Committee Membership||Total|
|>$100 million <= $250 million||$15.000||$30.000||$45.000|
|>$50 million <= $100 million||$10.000||$30.000||$40.000|
|>$10 million <= $50 million||$7.500||$20.000||$27.500|
LTS IWG Participating Member Fees
|Turnover||Eclipse Solution Membership||LTS PSP Membership||Total|
|>$100 million <= $250 million||$15.000||$10.000||$25.000|
|>$50 million <= $100 million||$10.000||$10.000||$20.000|
|>$10 million <= $50 million||$7.500||$7.500||$15.000|
|<$1 million & < 10 employees||$1.500||$1.500||$3.000|
|Privilege||SC Member||Participating Member|
|Member of the Steering Committee||X||-|
|Member of the Change Control Board||X||-|
|Host custom build on LTS infrastructure||X||X|
|Host custom branch on LTS infrastructure||X||X|
|Access to the LTS build and signing infrastructure||X||X|
|Access to binary releases||X||X|
This Long Term Support IWG is designed as:
- a user driven organization,
- a means to foster a vibrant and sustainable ecosystem of components and service providers,
- a means to organize the community of each project or component so that users and developers can define and provide maintenance content collaboratively.
In order to implement these principles, the following governance bodies have been defined:
- The Steering Committee
- Change Control Boards
Steering committee members are required to:
- define the strategy of the IWG,
- define an annual program plan and budget, including the setting of annual LTS IWG dues,
- define support durations for LTS and VLTS,
- define additional membership levels for the IWG,
- define the global roadmap,
- discuss and update the charter,
- manage the creation, operation, and termination of Change Control Boards,
- define and implement marketing and communication activities,
- elect a chairman each year, and
- meet a minimum of twice per year.
Change Control Boards
Each service release defined by the roadmap is led by a Change Control Board.
Change Control Boards members are required to:
- create and maintain a plan, to be approved by the Steering Committee,
- prioritize and approve all software changes to be included in each service release, and
- report regularly to the Steering Committee on status.
The Change Control Board elects a chairman who represents the projects.
Each Change Control Board will be disbanded once the service release under its control has been released.