Open Source Summit Europe 2026

Linux Foundation

Der Open Source Summit ist das Event für Open-Source-Entwickler:innen und -Mitwirkende. Hier kommen Maintainer:innen, Technolog:innen und Community-Leader zusammen, um Wissen zu teilen, gemeinsam an Lösungen zu arbeiten und Open-Source-Projekte voranzubringen. Es ist das Zuhause für Code, Community und die Menschen, die die Zukunft von Open Source gestalten.

Wir freuen uns sehr, dass unsere Kolleg:innen Anna-Lena Marx mit ihrem Vortrag Yocto’s Hidden Gems: Lesser-Known Tools for Daily Development und Tobias Kästner mit seinen Vorträgen Practical End to End Traceability for Zephyr’s Path to Certification und Safety BOM Is a Contract: Producing and Consuming the SPDX Functional Safety Profile vertreten sein werden.

Abstract zu Anna-Lena Marx Vortrag Yocto’s Hidden Gems: Lesser-Known Tools for Daily Development:

Yocto is a complex and huge ecosystem. Getting started may feel hard, but there are various tools to make our daily development easier right out of the box—if you know about them. Unfortunately, many developers are only used to a small subset of the available tools and their capabilities, which often leads to writing additional custom tooling for already solved problems.
In this presentation, we will dive into a selection of these existing tools and demonstrate how to take advantage of them in everyday workflows. For example, we’ll discuss how bitbake-getvar helps with debugging variables and overrides, and how to find all packages generated by a recipe with oe-pkgdata-util. We will also look into yocto-check-layer, patchtest, bitbake-config-help, and more.
The session will focus on practical use cases, showing how to leverage already available tools to save time and reduce the need for custom scripts.

Abstract zu Tobias Kästners Vortrag Practical End to End Traceability for Zephyr’s Path to Certification: 

As part of the ongoing effort to achieve IEC 61508 certification, Zephyr’s requirements capture process is underway. Yet there is still no clear picture of how these requirements trace to the tests that verify them or the code that implements them. Safety evidence is largely documented evidence, so the primary concern is generating auditable documents: requirement and test specifications, test reports, and traceability matrices.
The challenge is collecting this evidence in a community-compatible way — low-friction processes and tooling that developers and maintainers will accept.

This talk proposes a pipeline built on Zephyr’s existing documentation tools (Doxygen/Sphinx) to extract the needed information from annotated source and tests, then trace it back against requirements into an end-to-end chain.
Two demos are shown: a minimal working example against Zephyr itself, and a self-contained pipeline for a Zephyr module the authors maintain. Required process adaptations and guidelines are explained. The work is an open proposal for discussion; once agreed, it gives the community a scalable foundation to advance safety efforts, with concrete tasks contributors can pick up.

Abstract zu Tobias Kästners Vortrag Safety BOM Is a Contract: Producing and Consuming the SPDX Functional Safety Profile:

SPDX 3.1’s Functional Safety profile recently grew to model a safety case end to end: requirements and their refinement, verification, pass/fail evaluations, evidence, and assumptions of use. It standardizes how a safety case is exchanged, but not how one is produced, nor what a consumer does with one received. We demonstrate SEGkit, a prototype, open-source, project-agnostic engine that extracts a design and evidence graph from content repositories to recompute a verdict over the graph—a judgment recomputed from content, not merely recorded—and detects which evidence goes stale as code evolves; in this talk we also show how we plan to use it within Zephyr to automate safety evidence creation. This makes SEGkit interesting to projects maintaining their safety BOM as well as downstream users who want to work with one. For the latter case we argue a received BOM is best consumed as a contract—its requirements and evidence being guarantees and its assumptions the conditions the consumer must discharge against its own case. Lastly, we talk about what the profile might add for machine-checkable discharge: assumptions as checkable conditions, linked to the guarantees they constrain.
Zur Konferenzseite

inoNews

5 gute Gründe für den inovex Newsletter:

  • Exklusive Insights & Tipps unserer inovexperts
  • Infos und Updates zu IT-Trend-Themen & Angeboten
  • Trainingsrabatte & Eventeinladungen
  • Gratis Whitepapers & Infosheets
  • Austausch- & Beratungsoptionen

Zur Newsletter-Anmeldung