1 of 16

Our Mission
Our Goals
Program Objectives
Strategies and Tactics
Member Participation

Agenda

2 of 16

Our Mission

Build a community to promote and endorse organizations from the Automotive industry which are members of this SIG to discuss and create open guidelines and practices for open source projects to understand and meet industry requirements based on their vehicle safety and security processes.

�

3 of 16

Our Goal

Create, deploy and raise awareness on functional safety process and material for Eclipse SDV projects to follow willingly with the goal of improving adoption. Contribute to existing Eclipse safety process definition(s).

�

4 of 16

Our Mission
Program Objectives
Strategies and Tactics
Member Participation

Agenda

5 of 16

Program Objectives 2025

Project Support

Thought Leadership

Community

Innovation

Program objectives are high level pillars of the plan. Specific strategies and tactics will be grouped under these 4 pillars

Create and deploy functional safety process support materials that can help the usage of such processes by other SDV projects in applying these to better understand safety requirements.

Work with standardization external organizations and its working groups that are responsible for functional safety specifications for better open-source synergy.

Create community content and guideline documents for open-source projects regarding functional safety and security requirements

Provide an open floor for industry organizations, which should be members of this SIG, to contribute to the group’s documents and discussions. Provide training for committers and adopters

�

6 of 16

Our Mission
Program Objectives
Strategies and Tactics
Member Participation

Agenda

7 of 16

Strategies and tactics

Objectives: Project Support

Literature research on what is there in the field of open source and CI/CD centric processes;
Check which standards are currently in draft which focus on modern software development beyond traditional requirements first approach;
Leverage the experience gained from the Eclipse ThreadX certification process definition
Document open source good practices;
Document which work products are needed by standards;
Show how open source projects create the work products demanded by the standards.

Analyse safety requirements from relevant Standards

Filter what makes sense for Eclipse SDV Projects
Document and categorize requirements and make it publicly available

Prepare projects for certification

Onboard and introduce commiters to the topic
Knowledge sharing with Eclipse SDV projects
Contribute to projects if possible

8 of 16

Strategies and tactics

Objectives: Innovation

Involve safety certification authorities and those creating the standards. Eg Exida, and TÜV
Start with ISO26262, SOTIF, ISO21434 (Security) and UNECE WP.29

Reduce the gap between safety certifications and open-source

It’s also about bringing those specs (safety certification standards) closer to open-source
As open as we can get it to be

9 of 16

Strategies and tactics

Objectives: Thought Leadership

White paper recommendations

Fact based

Work with the Marketing Committee to raise awareness on the SIG activities

Community blog posts (Eclipse blog platform)

Knowledge sharing between groups members

Demos, lessons learnt, presentations, etc
FAQs and recommendations, e.g. as shown here: Automotive Processes for Open Source SW SIG — Eclipse Automotive Processes for Open Source SW SIG documentation

Talks and presentations in events such as Embedded World, OCX and other conferences

Open guideline documents

Add content to the community guideline documentation

Blog posts

Write blog posts to spread the word about the group’s work
Share your experience on being a group member and contributor

10 of 16

Strategies and tactics

Objectives: Community

Work with other projects that have Functional Safety in mind like ThreadX, Xen, Zephyr, ELISA, SPDX and so on;
Eclipse SDV Blueprints

Create new blueprints
Contribute to existing ones

Eclipse SDV Badges

So projects can target earning badges around functional safety requirements

Promote open-discussions

Promote and endorse open discussions between group members
Actively involve contributors and committers

Invite experts

Invite experts of the industry when needed

11 of 16

Member Participation

12 of 16

How You Can Contribute

Engage in our bi-weekly meetings

Join our open floor discussions
Bring experts to share their knowledge with the group

Contribute to our Guideline Documentation

Propose and contribute to our guideline documentation

Engage with external safety specification groups

Help us engage with external specification groups, such as ISO 26262, ASPICE, etc

Generate community content

Write Eclipse SDV blog posts to spread the word about the group and its work
Share your experience as a group member

Eclipse SDV Projects Engagement

Requirement badges
Blueprint creation and contribution

�

13 of 16

Proposed Member Goals

Program	All Members
Define Group Goals	1/year
Open Discussions	2/month
Blog Posts	4/year

�

14 of 16

Thank you!

�

15 of 16

Our Mission

Software used within vehicles has to meet special automotive requirements to be safe and secure. These requirements are defined and checked through processes described in standards and norms such as Automotive SPICE (ASPICE), Functional Safety (ISO26262, SOTIF) and long-term maintenance (compliant with UNECE regulations R.155 and R.156), Security (ISO21434 and EU Cyber Security Resilience Act) to systems and software.

Our mission is to create recommendation, best practices, and guidelines how to meet automotive processes for open-source development within the scope of Eclipse SDV.

Initial focus areas of the Automotive Grade Open Source Special Interest Group could be:

Foster open-source software development in compliance with Automotive grade maturity models
How can Safety qualification (according to ISO26262) be achieved with open-source
Impact of long-term maintenance (e.g. as defined by UN ECE R156) on open-source
IP and legal questions when combining open source and closed source as well as related to documentation, if needed

�

16 of 16

Our Tasks and Objectives

The tasks and objectives for the SIG should include:

analyze requirements from key automotive standards (ASPICE, ISO26262, UNECE R.155/156, ISO21434) and their relevance to open-source within the scope of Eclipse SDV
look at ongoing activities within the Eclipse SDV WG (SDV Process, Eclipse ThreadX), and align with SIGs (Threadx SIG, Rust SIG),
align with initiatives outside Eclipse (such as ELISA, NDS zserio) and SDV Alliance
create a comprehensive concept on how to achieve automotive grade open source for safety qualification
include recommendations which group or project within or outside the Eclipse Foundation might take care of elements of this concept
drive and influence standardization activities in the ISO or IEC context.

�