Jump to: navigation, search

Difference between revisions of "LTS"

(Value Proposition)
(Participating people/organizations)
Line 63: Line 63:
 
In time, we will have a steering committee and chair. In the meantime, please contact [mailto:andrew.ross@eclipse.org?Subject=Eclipse%20LTS%20Program Andrew Ross] - +1 613 614 5772, Skype: rossand2002
 
In time, we will have a steering committee and chair. In the meantime, please contact [mailto:andrew.ross@eclipse.org?Subject=Eclipse%20LTS%20Program Andrew Ross] - +1 613 614 5772, Skype: rossand2002
  
==Participating people/organizations==
 
  
* Mike Milinkovich, Eclipse Foundation
 
* Ralph Mueller, Eclipse Foundation
 
* Andrew Ross, Eclipse Foundation
 
* Denis Roy, Eclipse Foundation
 
(Add yourself too if you are interested)
 
  
 
=Information archive=
 
=Information archive=

Revision as of 10:02, 15 March 2012

Long Term Support

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

  • Meeting @ EclipseCon, Wednesday March 28, 14:00 to 16:00 Eastern. This session will be in Reston Suites A, on the second floor.

Charter

A draft copy of the charter for the LTS program is now 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

Value Proposition

The LTS program was created in recognition of the fact the value potential for Eclipse software doesn't stop with two maintenance builds (e.g. SR1 and SR2) in the first year post-release (aka. SR0). The LTS program provides the infrastructure and governance to allow Eclipse software to be supported as long as it is needed.

Most organizations reading this are going to be interested in reducing expenses and/or increasing revenue.

The development model, methods, and software license used for Eclipse software enabled sharing costs, risks, and benefits across the ecosystem. This can provide significant cost-benefit and innovation advantages compared to a sole firm bearing these costs and working alone. Membership gives you access to the facilities and software that others have jointly invested in, further reducing costs and risks. Marketing is expensive. If you are an organization offering maintenance and support services, the LTS program will help you find a market for your firms skills and technology. If you are an organization looking to consume services from a support and maintenance offering firm, the LTS program will help you connect with trusted organizations. These are a couple of obvious ways LTS IWG membership can add value to your organization.

Participation Levels

There are 3 levels of participation in the LTS IWG:

  1. Steering Committee, who control the budget, resources, and direction
  2. Premium, who have access to a rich software production forge including build farm, code repositories, bug tracking system, and more.
  3. Participating, 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 connect organizations seeking support for Eclipse software with those offering it in order to cultivate a vibrant ecosystem.

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.

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

LTS Workshop Walldorf, July 11, 2011: [1]

Slide presentations

Action Tracker

  • 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
  • Build LTS awareness via. videos/blogs/webcasts/meetings/etc. - Andrew + Various [Ongoing]