EstablishingLong Term Supportfor EclipseEclipseCon 2011Santa Clara, CA, March 2011Jochen Krause, EclipseSourceKarsten Schmidt, SAP AG
Introduction Eclipse has always targeted commercial usage But discrepancy between lifecyclesEarly 2009: we triggeredthe discussion at EclipseEarly 2010: Board ofDirectors Working GroupJune 2010: Boardapproved proposalGoal: have it up andrunning by end of 2011 Commercial approach: business opportunities for the ecosystem
The Lifecycle ChallengeMajor Eclipse release each year – Two support releases in the following 9 monthsNo service releases beyond SR2 – Organizations requiring support beyond a year need to find a third party or do it themselves
Yawn – yet another support strategy for open source?
We do it the Open Source Way!No vendor lock-inSource code is Open Source under EPLAll fixes are visible and available foreveryone – fix each bug only once!
Central Infrastructure run by the Eclipse FoundationSource Control and Versioning• Source code is Open Source under EPL• Anyone can find and download the patches• Optional branching for critical fixesBuild Infrastructure• Out-of-the-box build infrastructure also for old releasesBugzilla• The same issue tracking as for the dev codelineIP process, signing of archives• Generate the trust associated with the Eclipse brand by running the IP process and by signing the archives• Binaries will only be available to participating companies
Maintenance CommittersToday: Only Committers can check in source codeLTS: Concept of „Maintenance Committers“• ... are nominated by companies• ... do not have to be committers (but all committers are maintenance committers)• ... may check in code into maintenance codelines, not into dev codeline• But: each patch must be offered to the committers to be included in the dev codeline
Most companies have committers in only a few projects Projects 1 2 3 4 5 6 7 8 9 10 Current release
Most companies have committers in only a few projectsCompany A Company B Company C Company D Company E Projects 1 2 3 4 5 6 7 8 9 10 Current release
Most projects have committers from only a few companiesCompany A Company B Company C Company D Company E Projects 1 2 3 4 5 6 7 8 9 10 Current release
Many commercial products use many projects ... Projects 1 2 3 4 5 6 7 8 9 10 Current release Product X Product Y
... leading to many small support contracts Customer X Customer YCompany A Company B Company C Company D Company E Projects 1 2 3 4 5 6 7 8 9 10 Current release Product X Product Y
Most companies offer support for only few releases backCompany A Company B Company C Company D Company E Projects 1 2 3 4 5 6 7 8 9 10 Current release Cr -1 Cr - 2
Customers have support obligations for many years Slide from EclipseCon 2010 Projects 1 2 3 4 5 6 7 8 9 10 Current release Cr -1 Cr - 2 Cr - 3 ... Cr - many ?
The Eclipse LTS Concept: System Integrators as „General Contractors“ Customer X Customer W Customer Z Customer Y SI 1 SI 2Company A Company B Company C Company D Company E
The Business Model• Customer benefits – One contract partner, all customers share the costs – No vendor lock-in• SIs benefits – Access to Open Source support infrastructure and Know-How – Bundling of the otherwise fragmented OSS support market• Support companies: Get a shop-in-shop effect – Can get into business with their Know-How (committership) – Significantly lower infrastructure investments• Eclipse Foundation – Additional revenue through fees for central infrastructure – Key differentiator compared to other OSS organizations
Outlook / Next Steps• Prepare the technical infrastructure (e.g. by moving the platform build to Eclipse)• Collect input from potential customers, „General Contractors“, Companies offering project support• Concept to be refined, based on the feedback• All input from YOU is highly appreciated• Plan: have the infrastructure up and running by end of 2011 A well-structured Long-Term Support infrastructure, basedon Open Source principles, could become a key differentiator for the Eclipse ecosystem!