Eclipse	Ecosystem	Working	Groups	
Hacking	the	so7ware	value	chain	
		Gaël	Blondelle	
Director	of	European	Ecosystem	Development	
Eclipse	Founda@on	Europe	
@gblondelle	
	
Nov	2016	–	POSS	Community	Summit
2010	–	Eclipse	becomes	more	than	an	IDE	
•  Before:	Eclispe	projects	are:	
– Developed	in	Java	
– Bundled	in	OSGi		
– Run	on	the	Eclipse	plaQorm	
•  A7er:	Eclipse	projects	must	conform	with	the	
Eclipse	process	and	legal	framework	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 2
A	business	friendly	ecosystem	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 3
Eclipse	Public	License	
•  Default	license	for	all	Eclipse	projects	
•  OSI	cer@fied	as	an	open	source	license	
•  The	most	commercially	friendly	weak	copyle7	license	
–  Allows	commercial	re-licensing	of	binaries	
–  Modern	patent	license,	with	reasonable	termina@on	clause	in	event	of	
li@ga@on	
•  With	the	approval	of	the	Board,	Eclipse	projects	can	be	
licensed	under	different	terms	than	the	EPL	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 4
Eclipse	Development	Process	
•  Proven	process	for	crea@ng	
successful	open	source	projects	and	
communi@es	
•  Open,	Transparent,	Meritocra@c	
•  Vendor-neutral	
•  Supported	by	professional	staff	with	
years	of	experience	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 5
Eclipse	Working	Groups	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 6	
OpenPAAS
The	PolarSys	Working	Group	
•  PolarSys	is	an	Eclipse	Industry	Working	Group	
created	by	large	industry	players	and	by	tools	
providers	to	collaborate	on	the	crea@on	and	
support	of	Open	Source	tools	for	the	development	
of	embedded	systems.	
•  Domains	such	as	aerospace,	defense	and	security,	
energy,	health	care,	telecommunicaAons,	
transportaAon	must	meet	several	requirements.	
•  Main	projects:	
–  Capella,	CDT,	Papyrus,	Titan,	Trace	Compass	
Participating Member
Guest Academic Member
Steering Committee Member
Long	Life	Cycle:	The	case	for	Open	Source	
AIRBUS Aircraft Life Cycle
Up to 80 years !!
Open	Source	offers	a	new	op@on		
by	combining	the	best	of	“Make”	and	“Buy”	
User	may	influence	
further	development	
OpAon:	Use		
Open	Source	soTware	
Significantly	reduced	
project	risks	and	costs	
Is	a	de-facto	standard	
+	
+	
+	
SoTware	tailored	
to	the	user	needs	
OpAon:	Make		
bespoke	soTware	
Reduces	project	risks	in	
soTware	development	
OpAon:	Buy	
commercial	soTware	
+	 +	
Very	high	total	cost	and	
project	risks	in	soTware	
development	
User	with	very	limited	
influence	in	the	
development	
–	
–	
VS.	 VS.	
Total	cost	sAll	high	–	
Becomes	legacy	in	the	
future	
–	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 9
Typically	less	than	20%	of	Requests	For	
Enhancement	(RFE)	get	into	the	tool	
Proprietary	Tool	Vendor	Ecosystem	
100	%	of	RFE	are	able	to	get	into	the	tool	
e.g.	80%	generic,	20%	as	user	extensions		
	
PolarSys	Open	Source	Ecosystem	
Tool
Vendor
End User
Requests
End User
Requests
End User
Requests
End User
Requests
End User
Requests
10
An	ambi@ous	objec@ve	
Change	the	tools	ecosystem	
	 No lock-in!
You or many third party can add features
A theoretic basis about the management 

of common property resources	
•  Elinor	Ostrom	(August	7,	1933	–	June	12,	2012)	was	an	American	poli@cal	economist.	
•  2009:	Nobel	Memorial	Prize	with	Oliver	E.	Williamson,	for	"her	analysis	of	economic	
governance,	especially	the	commons".		
•  Ostrom	iden@fied	8	"design	principles"	of	stable	local	Common	Pool	Resource	
management:	
1.  Clearly defined boundaries;
2.  Rules adapted to local
conditions;
3.  Open decision-making
process;
4.  Effective monitoring;
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 11	
5.  A scale of graduated sanctions;
6.  Cheap and easy conflict
resolution;
7.  Self-determination of the
community;
8.  Multiple nested layers for
scalability.
Focus	on	OpenPASS	
Evaluation and assessment of active safety systems. openPASS Toolset | Olaf Jung, BMW AG
2
2 3 4 5
Need for new
methods of
assessment.
Assessment of
active safety.
Toolset: openPASS. Harmonization

and chances for

new ratings.
1
Traffic, accidents

and traffic safety.
OPENPASS.
OVERVIEW.
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 12
OpenPASS	–	ctd.	
Evaluation and assessment of active safety systems. openPASS Toolset | Olaf Jung, BMW AG
UNDERSTANDING TRAFFIC AND ACCIDENTS.

4
− Accident is a result of
multiple interacting
factors in traffic.
− The safety
performance of
Assistance Systems
must be evaluated by
taking these complex
interactions into
account.
TRAFFIC CONFLICT ACCIDENT
REDUCTION

of conflicts.
ACCIDENT AVOIDANCE

or mitigation.
Accident as a process of interacting factors.
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 13
Auto	OEM	collabora@on	in	OSS	
ENPASS.

TUAL STATUS.
openPASS
Framework
Graphic User
Interface
Crash Re-
Simulation Core
Virtual Experiments
Simulation Core
Additional Topics &
Features
?
it Daimler tauschen nach
über die Anbindung von
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 14
Thanks!	
Gaël	Blondelle	
Director	of	European	Ecosystem	Development	
gael.blondelle@eclipse.org	
@gblondelle	
+33	673	392	185	
Nov-2016	 Copyright	(c)	2016,	Eclipse	FoundaAon,	Inc.	Made	available	under	the	Eclipse	Public	License	1.0	 15

Eclipse Ecosystem Working Groups Hacking the software value chain