The document discusses the significance of open source software in mastering future industry challenges, highlighting its historical development and principles. It emphasizes the collaborative nature of open source within diverse ecosystems, illustrated by case studies like Airbus, and the importance of governance and IP management for maximizing innovation benefits. Furthermore, it outlines initiatives like the Eclipse OpenMDM working group aimed at creating industry standards.

1. Industry
Collabora/on
in
Open
Source
-­‐
an
impera/ve
to
master
the
challenges
of
the
future
Ralph
Müller
Managing
Director
Eclipse
Founda/on
Europe
GmbH
@ralph_mueller
January
2015
1

2. Hardware
Age
2

3. Game
Changer
3

4. Wikipedia: Hauptburg Burghausen
The
Age
of
the
SoNware
Products

5. innovation mostly driven by software
large scale software systems
cross-company
cross-discipline
operational safety and security
longevity
Industry
Challenges
5

6. 6
Interlude
Open Source Software
• Free Software Movement
• Open Source Software

7. 7
Free Software Movement
• launched 1983
• GNU project, FSF
• Copyleft - GNU Public License
(GPL)
• ethics based
• protect the 4 rights of the end-
user (use, investigate, modify,
distribute)
Richard Stallman, Wikipedia

8. 8
Open Source Software
• 1997 - Cathedral and Bazaar
• 1998 - Netscape code
becomes Mozilla
• 1998 - Open Source Initiative
• pragmatic approach to
solving software problems
• Free as in free beer
Eric S. Raymond, Wikipedia

9. 9
The 10 Commandments
• Free redistribution
• Include source code
• Modifications and derived works
• Integrity of author’s source code
• No discrimination against person and groups
• No discrimination against fields of endeavor
• Distribution of license
• License not specific to a product
• License not restricting other software
• License technology neutral
OSS Freedoms*
Freedom 0
to run the program,
for any purpose
Freedom 1
to study how the program works,
and change it to
make it do what you wish
Freedom 2
to redistribute copies
Freedom 3
to distribute copies of your
modified versions to others
http://opensource.org/

10. 10
Change of Tides
Heise Developer, 2014

11. The
Open
World
11

12. 12

14. Predictability
14

15. Diversity

16. Eclipse
• Millions
of
users
• Thousands
of
products
• Thousand+
commiSers
• Hundreds
of
companies
and
projects
• twenty
employees
• zero
product
managers
16

17. 17

18. ©AIRBUSFRANCES.A.S.Tousdroitsréservés.Documentconfidentiel.
Our constraints
One example : AIRBUS A300
•Program began in 1972 and
will stop in 2007
2007-1972 = 35 years...
•Support will last until 2050
2050-1972 = 78 years !!!
On board software development for very long lifecycle
products

19. Case
Study:
Airbus

20. Case
Study:
Airbus

21. 21

22. * main provider:
change of business
TopCased
TTM
22

23. Ecosystem
Maturity
User
Benefits
OSS
OSS
+
Community
Apache, FSF
OSS
+
Community
+
Business
Ecosystem
Eclipse,
OW2
OSS
+
Community
+
User Centric
Ecosystem
Eclipse WGs
Linux Foundation
User-­‐Driven
Open
Source
Collabora/on
23

24. Dürfen wir uns zivile Sicherheitssysteme mit
Closed Source Software überhaupt noch leisten?
Denkansätze am Beispiel der ETCS-Migration bei
der Eisenbahnsignaltechnik
Deutsche Bahn AG
Klaus-Rüdiger Hase
Technik, Systemverbund und Dienstleistungen
Braunschweig, 03.12.2009
24

25. 25

26. Quelle: http://www.osbf.eu/blog/konsortiale-open-source-softwareentwicklung/im-energiesektor/#.U4G05JR_t2J 26

28. Eclipse
Working
Groups
28

30. Create
Terrabytes
of
Data
30

31. Towards
a
Industry
Standard
Implementa/on
31

32. State
of
openMDM
June
2013
32

33. Transforma/on:
The
Eclipse
openMDM
WG
founded
33

34. openMDM
Classifica/on
• ver/cal
industry
ini/a/ve
• related
to
industry
standard
• consumer-­‐lead
• membership:
– OEMs
(Daimler,
BMW,
Audi,
Tata)
– domain
engineering
companies
• goal:
open
implementa/on
sets
industry
standard
34

35. Opera/onal
Model
of
openMDM
35
Steering Committee
Quality Committee
Architecture Committee
Working Group
• charter
• requirements
• funding
• processes
• overall quality goals
• tools and methods
• architecture oversight
• platform decisions
• future plans

36. The
Secret
Sauce
• Licensing
model
for
sharing
co-­‐developed
innova/on
• Clear
goals,
focused
funding,
result
control
• Rely
on
OSS
development
processes
• Governance
model
to
ensure
level
playing
field
for
all
par/cipants
• IP
management
to
maximize
commercializa/on
opportuni/es
36

39. 39

41. Thank you!