Jump to: navigation, search

Difference between revisions of "LongTermSupport"

(Charter)
(43 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
=Long Term Support=
 
=Long Term Support=
 +
 +
==Working Group members==
 +
 +
===Steering Committee members===
 +
 +
IBM, SAP, CA Technologies, Innoopract
 +
 +
===Premium members===
 +
 +
OpenGeo, Atos, Ericsson, Obeo
  
 
==Initiative Goals==
 
==Initiative Goals==
 
# Enable organisations to collaborate when providing support and maintenance for Eclipse technologies
 
# Enable organisations to collaborate when providing support and maintenance for Eclipse technologies
 
# Enable support and maintenance of Eclipse technologies for Long Term (years) and Very Long Term (decades) durations.
 
# Enable support and maintenance of Eclipse technologies for Long Term (years) and Very Long Term (decades) durations.
 +
 +
  
 
==Activities==
 
==Activities==
Line 14: Line 26:
 
==Next Meeting==
 
==Next Meeting==
  
* [http://wiki.eclipse.org/LTS/March28_2012 Meeting @ EclipseCon], Wednesday March 28, 14:00 to 16:00 Eastern. This session will be in Reston Suites A, on the second floor.
+
* Steering Committee Meeting - Wednesday, October 24th from 15:30 - 16:30 in Ludwigsburg, Germany
 +
* Working group information session - Wednesday, October 24th 16:30 - 17:30 in Ludwigsburg, Germany
  
 
==Charter==
 
==Charter==
  
A draft copy of [http://wiki.eclipse.org/LTS/Charter the charter] for the LTS program is now available.
+
The [http://www.eclipse.org/org/industry-workgroups/ltsiwg_charter.php charter] for the LTS working group is now approved and available.
  
 
==LTS Ready Project Definition==
 
==LTS Ready Project Definition==
  
 
In order to be included as part of Long Term Support, a project must be compliant with the [http://wiki.eclipse.org/LTS/LTS_Ready LTS Readiness Definition]
 
In order to be included as part of Long Term Support, a project must be compliant with the [http://wiki.eclipse.org/LTS/LTS_Ready LTS Readiness Definition]
 +
 +
==LTS Ready Project tracker==
 +
 +
We have started a [http://wiki.eclipse.org/LTS/Projects list of projects either LTS ready or actively working towards becoming LTS ready].
  
 
==Value Proposition==
 
==Value Proposition==
  
LTS members can benefit from the following value:
+
Prior to the LTS program, support for Eclipse stopped at the SR2 milestone 8 months after release. Companies with products and services based on this software needed to maintain it themselves. The LTS program enables the following value:
  
 
===Stop fixing everything yourself===
 
===Stop fixing everything yourself===
* Leverage binaries built by others
+
* Share fix binaries built by others
* Leverage code with the latest & greatest fixes
+
* Share code with the latest & greatest fixes integrated
  
===Stop maintaining your own server farms==
+
===Stop maintaining your own server farms===
* Code repository
+
* Code repository, Bug tracker, Continuous integration server, Build farm
* Bug tracker
+
* Continuous integration server
+
* Build farm
+
 
* Save on cooling, real estate, power, system administration
 
* Save on cooling, real estate, power, system administration
  
 
===Hire maintenance committers===
 
===Hire maintenance committers===
* Their access is tied to employment with you
+
* Their commit access is tied to employment with you
 
* No waiting for a committer election, access is immediate
 
* No waiting for a committer election, access is immediate
 
* Flexibility to hire/contract developers in lower-cost geographies
 
* Flexibility to hire/contract developers in lower-cost geographies
  
 
===On-demand responsiveness===
 
===On-demand responsiveness===
* Add company-specific fixes 24x7 on your schedule
+
* Produce company-specific fixes 24x7 on your schedule
 
* Builds on demand
 
* Builds on demand
  
Line 55: Line 69:
  
 
There are 3 levels of participation in the LTS IWG:
 
There are 3 levels of participation in the LTS IWG:
# Steering Committee, who control the budget, resources, and direction
+
# Steering Committee, who have all Premium rights plus control the budget, resources, and direction
# Premium, who have access to a rich software production forge including build farm, code repositories, bug tracking system, and more.
+
# Premium, who have all Participant rights, plus access to a rich software production forge including build farm, code repositories, bug tracking system, and more.
# Participating, who have access to the downloads site and LTS/VLTS binaries.
+
# Participant, who have access to the downloads site and LTS/VLTS binaries.
  
 
All LTS IWG members can participate in meetings. There may be special Steering Committee only meetings.
 
All LTS IWG members can participate in meetings. There may be special Steering Committee only meetings.
Line 65: Line 79:
 
==Eclipse Foundation's role==
 
==Eclipse Foundation's role==
  
The Foundation is not a service provider. Rather it works to connect organizations seeking support for Eclipse software with those offering it in order to cultivate a vibrant ecosystem.
+
The Foundation is not a service provider. Rather it works to cultivate a vibrant ecosystem of Maintenance and support providers and consumers.
  
In order to help service providers be more efficient and effective, the Eclipse Foundation will provide the infrastructure for the code repositories, bug trackers, build farms, test farms, software signing, intellectual property management, and governance in order to manage the projects. It is the trusted vendor neutral organization doing the drudge-work so that others do not have to.
+
The Eclipse Foundation also provides the infrastructure for the code repositories, bug trackers, build farms, test farms, software signing, intellectual property management, and governance in order to manage the projects. It is the trusted vendor neutral organization doing the drudge-work so that others do not have to.
  
 
=Contact information=
 
=Contact information=
Line 101: Line 115:
 
==Meeting Minutes==
 
==Meeting Minutes==
  
LTS Workshop Walldorf, July 11, 2011: [http://dev.eclipse.org/mhonarc/lists/lts-iwg/msg00001.html]
+
* LTS Workshop Walldorf, [http://dev.eclipse.org/mhonarc/lists/lts-iwg/msg00001.html July 11, 2011]
 
+
* LTS/Polarsys relationship, [http://wiki.eclipse.org/LTS/March27_2012 March 27, 2012]
==Slide presentations==
+
* LTS Face to face @ EclipseCon, [http://wiki.eclipse.org/LTS/March28_2012 March 28, 2012]
 +
* LTS/Polarsys follow-up, [http://wiki.eclipse.org/LTS/March29_2012 March 29, 2012]
 +
* LTS Charter review, [http://wiki.eclipse.org/LTS/April18_2012 April 18, 2012]
 +
* LTS Meeting [http://wiki.eclipse.org/LTS/June29_2012 June 29th, 2012]
 +
* LTS Meeting [http://wiki.eclipse.org/LTS/July30_2012 July 30th, 2012]
 +
* LTS Meeting [http://wiki.eclipse.org/LTS/Sept_2012 September 26, 2012]
 +
* LTS Steering Committee Meeting [http://wiki.eclipse.org/LTS/Nov8_2012_SteeringCommittee Nov 8, 2012]
  
 
=Action Tracker=
 
=Action Tracker=
  
 
* Update Charter based on Feb.2012 business model - Andrew [DONE]
 
* Update Charter based on Feb.2012 business model - Andrew [DONE]
* Project plan/tracking system to tie together the many tickets and work being done - Andrew
+
* Identify chair, initiating strategic member - Andrew [DONE, thank you for chairing Pat & Jochen]
* Build LTS awareness via. videos/blogs/webcasts/meetings/etc. - Andrew + Various [Ongoing]
+
* Update Charter based on April 18, 2012 review - Andrew [DONE]
 +
* LTS IWG participation agreement - Mike/Janet [DONE]
 +
* first official meeting - Week of June 29, 2012 [DONE]
 +
* LTS Members sign-up - Andrew & members [IN PROGRESS]
 +
* LTS IWG Launch [PLANNED FOR NOVEMBER 13. 2012]
 +
 
 +
[[Category:Eclipse IWG]]

Revision as of 13:23, 2 November 2012

Long Term Support

Working Group members

Steering Committee members

IBM, SAP, CA Technologies, Innoopract

Premium members

OpenGeo, Atos, Ericsson, Obeo

Initiative Goals

  1. Enable organisations to collaborate when providing support and maintenance for Eclipse technologies
  2. Enable support and maintenance of Eclipse technologies for Long Term (years) and Very Long Term (decades) durations.


Activities

  1. Develop a business model to support the Long Term Support (LTS) Industry Working Group (IWG) at Eclipse
  2. Actively recruit member organizations to create, nurture, and grow an ecosystem of maintenance and support providing and consuming organizations.
  3. Design, implement, and operate a LTS software development forge
  4. Enable and support the directives assigned by the LTS IWG Steering Committee

Next Meeting

  • Steering Committee Meeting - Wednesday, October 24th from 15:30 - 16:30 in Ludwigsburg, Germany
  • Working group information session - Wednesday, October 24th 16:30 - 17:30 in Ludwigsburg, Germany

Charter

The charter for the LTS working group is now approved and available.

LTS Ready Project Definition

In order to be included as part of Long Term Support, a project must be compliant with the LTS Readiness Definition

LTS Ready Project tracker

We have started a list of projects either LTS ready or actively working towards becoming LTS ready.

Value Proposition

Prior to the LTS program, support for Eclipse stopped at the SR2 milestone 8 months after release. Companies with products and services based on this software needed to maintain it themselves. The LTS program enables the following value:

Stop fixing everything yourself

  • Share fix binaries built by others
  • Share code with the latest & greatest fixes integrated

Stop maintaining your own server farms

  • Code repository, Bug tracker, Continuous integration server, Build farm
  • Save on cooling, real estate, power, system administration

Hire maintenance committers

  • Their commit access is tied to employment with you
  • No waiting for a committer election, access is immediate
  • Flexibility to hire/contract developers in lower-cost geographies

On-demand responsiveness

  • Produce company-specific fixes 24x7 on your schedule
  • Builds on demand

Get a good deal

  • Our program shares the infrastruture costs across a wide ecosystem
  • We are a non-profit and operating on a cost-recovery basis

Participation Levels

There are 3 levels of participation in the LTS IWG:

  1. Steering Committee, who have all Premium rights plus control the budget, resources, and direction
  2. Premium, who have all Participant rights, plus access to a rich software production forge including build farm, code repositories, bug tracking system, and more.
  3. Participant, who have access to the downloads site and LTS/VLTS binaries.

All LTS IWG members can participate in meetings. There may be special Steering Committee only meetings.

The public are welcomed and encouraged to participate on the LTS IWG mailing list.

Eclipse Foundation's role

The Foundation is not a service provider. Rather it works to cultivate a vibrant ecosystem of Maintenance and support providers and consumers.

The Eclipse Foundation also provides the infrastructure for the code repositories, bug trackers, build farms, test farms, software signing, intellectual property management, and governance in order to manage the projects. It is the trusted vendor neutral organization doing the drudge-work so that others do not have to.

Contact information

Mailing list

Join our Discussion list

LTS Bugs in Bugzilla

See a list of Bugs

Contact person

In time, we will have a steering committee and chair. In the meantime, please contact Andrew Ross - +1 613 614 5772, Skype: rossand2002


Information archive

Mailing list Archive

Mailing list archive

Related Links

Common Build Infrastructure

There is a strong link between this program and the Common Build Infrastructure (CBI). We recognize that the LTS program must support multiple built systems. However, encourage projects to use the CBI to benefit from shared development and expertise in build technologies.

Meeting Minutes

Action Tracker

  • Update Charter based on Feb.2012 business model - Andrew [DONE]
  • Identify chair, initiating strategic member - Andrew [DONE, thank you for chairing Pat & Jochen]
  • Update Charter based on April 18, 2012 review - Andrew [DONE]
  • LTS IWG participation agreement - Mike/Janet [DONE]
  • first official meeting - Week of June 29, 2012 [DONE]
  • LTS Members sign-up - Andrew & members [IN PROGRESS]
  • LTS IWG Launch [PLANNED FOR NOVEMBER 13. 2012]