1 of 3

Call-to-action and goal�“Automotive Grade Open Source”

Proposal: Establish a Special Interest Group “Automotive Grade Open Source” under the auspices of Eclipse SDV �based on the input from the VDA Sherpa Governance Group

We are looking for a

  • Collaborative approach involving many companies and associations
  • “Code first” leveraging existing and ongoing work
  • “Done is better than perfct” start with pragmatic solution and then expand

1

July 1, 2024

Secure & Stable Open Source with Automotive Grade (taken from VDA input to SDVoF (FEDERATE, HAL4SDV))To enable automotive grade within the framework of an open source ecosystem, process requirements must be defined and a qualification process established, e.g. via project labels. �This includes the complete development processes, e.g. according to the VDA scope. �As a prioritization and deep dive, secure programming languages within the scope of SWE.4 and an integration test strategy within the scope of SWE.5 are to be considered in this project.

As presented in AOSS May 14th

Public

2 of 3

Special Interest Group “Automotive Grade Open Source”�Starting point for work and food for thought

2

July 1, 2024

ASPICE

    • VDA Scope: SWE.4, Integration test strategies within SWE.5
    • Eclipse SDV:�SDV Process 1.0 (Definition of Badges and Flavors): Requirements, Testing, Documentation, Code Guidelines, Release Process

Functional Safety

    • Eclipse SDV: ThreadX SIG
    • Align with NDS zserio
    • Align with ELISA

IP and Legal

    • How to mix open and closed source. Open sourcing of interfaces
    • Align with �“SDV Alliance”:�Compatibility of license terms between associations (Eclipse SDV, SOAFEE, COVESA, AUTOSAR, a.o.)

Maintenance

    • Long-term maintenance concepts �e.g. for Linux �(see commercial offerings)

As presented in AOSS May 14th

Public

3 of 3

Next steps�“SIG Automotive Grade Open Source”

Meeting schedule

  • Kick-off meeting still in July possible, e.g. July 22th or 29th?
  • Meeting schedule? Monthly

Working mode

Results

  • We want to create results (documents such as guidelines, best practices, process descriptions etc)
  • This SIG is not meant to be an information sharing meeting “what is happening in other bodies”
  • Do we also want to contribute to other organizations or associations like ISO26262?

Structure

  • Sub-structure / Working groups?

Participation

  • Great feedback so far: approx. 20 companies showed interest to contribute
  • What about non-Eclipse SDV members?
    • Associations contributing to Automotive-Grade standards like ISO26262 such as VDA, ELISA etc.
    • Non-member companies being interested to contribute?

3

June 30, 2024

Public