25
The Eclipse Long-Term Support Concept Jochen Krause, EclipseSource Karsten Schmidt, SAP AG Eclipse Summit Europe, Ludwigsburg November 2010

Long-Term Support for Eclipse - the next step in Enterprise Readiness

  • Upload
    sjkiwai

  • View
    935

  • Download
    0

Embed Size (px)

DESCRIPTION

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, such as SAP, are obliged to support their products, including the Open Source pieces that are used, 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 throat to choke" for all of Eclipse. Vendor neutrality and diversity bring innovation and long term viability to Eclipse, but make it difficult to provide the support Enterprises are looking for. Even companies like EclipseSource, which offer support for a number of Eclipse projects as part of their business model, can not cover the entire spectrum. The Eclipse Board of Directors has developed and approved a concept for enabling broader support for Eclipse. In the talk we will present this concept and lay out the requirements of potential support consumers like SAP and potential support providers like EclipseSource. We will describe how the Long-Term support infrastructure can become a key differentiator for Eclipse, and how it can open a new revenue streams for the Eclipse Foundation and its ecosystem.

Citation preview

Page 1: Long-Term Support for Eclipse - the next step in Enterprise Readiness

The Eclipse Long-Term Support Concept

Jochen Krause, EclipseSource

Karsten Schmidt, SAP AG

Eclipse Summit Europe, Ludwigsburg

November 2010

Page 2: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Introduction

Eclipse has always targeted commercial usage

But discrepancy between lifecycles

Early 2009: we triggeredthe discussion at Eclipse

Early 2010: Board of Directors Working Group

June 2010: Board approved proposal

Goal: have it up and running by end of 2011 Commercial approach: business

opportunities for the ecosystem

Page 3: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Eclipse is mainstream in many industries

Page 4: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Luckily we are not (yet) flying

Page 5: Long-Term Support for Eclipse - the next step in Enterprise Readiness

But even systems engineering tools have a need for looong maintenance

Page 6: Long-Term Support for Eclipse - the next step in Enterprise Readiness

We are also moving into thecomputing centers ...

Page 7: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Equinox, Riena, Virgo, Gemini, RAP, EclipseLink, ....

Page 8: Long-Term Support for Eclipse - the next step in Enterprise Readiness

On the server you care about support

Page 9: Long-Term Support for Eclipse - the next step in Enterprise Readiness

The Lifecycle Challenge

Major Eclipse release each year

– Two support releases in the following 9 months

No service releases beyond SR2

– Organizations requiring support beyond a year need to find a third party or do it themselves

Page 10: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Yawn – yet another support strategy for open source?

Page 11: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Eclipse long term support is different

Page 12: Long-Term Support for Eclipse - the next step in Enterprise Readiness

We do it the Open Source Way!

No vendor lock-in

Source code is Open Source under EPL

All fixes are visible and available foreveryone – fix each bug only once!

Page 13: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Source Control and Versioning• Source code is Open Source under EPL• Anyone can find and download the patches• Optional branching for critical fixes

Build Infrastructure• Out-of-the-box build infrastructure also for old releases

Bugzilla• The same issue tracking as for the dev codeline

IP 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

Central Infrastructure run by the Eclipse Foundation

Page 14: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Maintenance Committers

Today: Only Committers can check in source code

LTS: 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

Page 15: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Most companies have committers in only a few projects

Projects1 2 3 4 5 6 7 8 9 10

Current release

Page 16: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Most companies have committers in only a few projects

Projects1 2 3 4 5 6 7 8 9 10

Current release

Company A Company B Company C Company D Company E

Page 17: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Most projects have committers from only a few companies

Projects1 2 3 4 5 6 7 8 9 10

Current release

Company A Company B Company C Company D Company E

Page 18: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Many commercial products use many projects ...

Projects1 2 3 4 5 6 7 8 9 10

Current release

Product X Product Y

Page 19: Long-Term Support for Eclipse - the next step in Enterprise Readiness

... leading to many small support contracts

Projects1 2 3 4 5 6 7 8 9 10

Current release

Company A Company B Company C Company D Company E

Customer X Customer Y

Product X Product Y

Page 20: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Most companies offer support for only few releases back

Projects1 2 3 4 5 6 7 8 9 10

Current release

Cr -1

Cr - 2

Company A Company B Company C Company D Company E

Page 21: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Customers have support obligations for many years

Projects1 2 3 4 5 6 7 8 9 10

Current release

Cr -1

Cr - 2

Cr - 3

...

Cr - many ?

Slide fromEclipseCon 2010

Page 22: Long-Term Support for Eclipse - the next step in Enterprise Readiness

The Eclipse LTS Concept (1):System Integrators as „General Contractors“

Company A Company B Company C Company D Company E

Customer X Customer YCustomer W Customer Z

SI 1 SI 2

Page 23: Long-Term Support for Eclipse - the next step in Enterprise Readiness

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

Page 24: Long-Term Support for Eclipse - the next step in Enterprise Readiness

Outlook / Next Steps

• Eclipse Foundation has begun to 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, based on Open Source principles, could become a key

differentiator for the Eclipse ecosystem!