Der Open Source Summit ist das Event f\u00fcr Open-Source-Entwickler:innen und -Mitwirkende. Hier kommen Maintainer:innen, Technolog:innen und Community-Leader zusammen, um Wissen zu teilen, gemeinsam an L\u00f6sungen zu arbeiten und Open-Source-Projekte voranzubringen. Es ist das Zuhause f\u00fcr Code, Community und die Menschen, die die Zukunft von Open Source gestalten.<\/p>\n
Wir freuen uns sehr, dass unsere Kolleg:innen Anna-Lena Marx mit ihrem Vortrag Yocto\u2019s Hidden Gems: Lesser-Known Tools for Daily Development<\/strong><\/a> und Tobias K\u00e4stner mit seinen Vortr\u00e4gen Practical End to End Traceability for Zephyr’s Path to Certification<\/strong><\/a> und Safety BOM Is a Contract: Producing and Consuming the SPDX Functional Safety Profile<\/a> <\/strong>vertreten sein werden.<\/p>\n Abstract<\/strong> zu Anna-Lena Marx Vortrag Yocto\u2019s Hidden Gems: Lesser-Known Tools for Daily Development: <\/strong><\/p>\n 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\u2014if 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. Abstract<\/strong> zu Tobias K\u00e4stners Vortrag Practical End to End Traceability for Zephyr’s Path to Certification:\u00a0<\/strong><\/p>\n 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. 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. Abstract<\/strong> zu Tobias K\u00e4stners Vortrag Safety BOM Is a Contract: Producing and Consuming the SPDX Functional Safety Profile:<\/strong><\/p>\n Wir freuen uns sehr, dass unsere Kolleg:innen Anna-Lena Marx mit ihrem Vortrag \u201eYocto\u2019s Hidden Gems: Lesser-Known Tools for Daily Development\u201c und Tobias K\u00e4stner mit seinen Vortr\u00e4gen \u201ePractical End to End Traceability for Zephyr’s Path to Certification\u201c und \u201eSafety BOM Is a Contract: Producing and Consuming the SPDX Functional Safety Profile\u201c vertreten sein werden.<\/p>\n","protected":false},"featured_media":69935,"parent":0,"template":"","events_types":[85],"service":[505],"class_list":["post-69929","events","type-events","status-publish","has-post-thumbnail","hentry","events_types-konferenz","service-embedded-systems"],"acf":{"start_date":"20261007","finish_date":"20261009","time":null,"finish_time":null,"location":"Prague, Czechia","organizer":"Linux Foundation","file":null,"hubspot_signups":false,"hubspot_signups_text":"","add_speakers":false,"speakers_headline":"Speaker:innen","speakers":null,"contact":null,"contact_heading":"","contact_text":""},"yoast_head":"\n
\nIn 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\u2019ll 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.
\nThe session will focus on practical use cases, showing how to leverage already available tools to save time and reduce the need for custom scripts.<\/p>\n
\nThe challenge is collecting this evidence in a community-compatible way \u2014 low-friction processes and tooling that developers and maintainers will accept.<\/p>\n
\nTwo 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.<\/p>\n