Difference between revisions of "LongTermSupport"
|Line 14:||Line 14:|
Conference call [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120730T09&p1=188&ah=1
Conference call [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120730T09&p1=188&ah=1 EDT on July 30th, 2012] see [http://wiki.eclipse.org/LTS/July30_2012 the Agenda]
Revision as of 12:31, 10 July 2012
- 1 Long Term Support
- 1.1 Initiative Goals
- 1.2 Activities
- 1.3 Next Meeting
- 1.4 Charter
- 1.5 LTS Ready Project Definition
- 1.6 Value Proposition
- 1.7 Participation Levels
- 1.8 Eclipse Foundation's role
- 2 Contact information
- 3 Information archive
- 4 Action Tracker
Long Term Support
- 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.
- Develop a business model to support the Long Term Support (LTS) Industry Working Group (IWG) at Eclipse
- Actively recruit member organizations to create, nurture, and grow an ecosystem of maintenance and support providing and consuming organizations.
- Design, implement, and operate a LTS software development forge
- Enable and support the directives assigned by the LTS IWG Steering Committee
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
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
- 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
There are 3 levels of participation in the LTS IWG:
- Steering Committee, who have all Premium rights plus control the budget, resources, and direction
- Premium, who have all Participant rights, plus access to a rich software production forge including build farm, code repositories, bug tracking system, and more.
- 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.
Join our Discussion list
LTS Bugs in Bugzilla
See a list of Bugs
In time, we will have a steering committee and chair. In the meantime, please contact Andrew Ross - +1 613 614 5772, Skype: rossand2002
Mailing list Archive
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.
- LTS Workshop Walldorf, July 11, 2011
- LTS/Polarsys relationship, March 27, 2012
- LTS Face to face @ EclipseCon, March 28, 2012
- LTS/Polarsys follow-up, March 29, 2012
- LTS Charter review, April 18, 2012
- LTS Meeting June 29th, 2012
- 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]
- LTS Members sign-up - Andrew & members [IN PROGRESS]
- LTS IWG Launch & first official meeting - Week of June 29, 2012