feat: add FOSS Backstage talk and GNU/LInux.ch podcast
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: "Getting Real with the Supply Chain: From SBOM Data to Action"
|
||||
date: 2026-03-17
|
||||
categories:
|
||||
# Language
|
||||
- english
|
||||
# - deutsch
|
||||
- presentation
|
||||
# - podcast
|
||||
# - article
|
||||
tags:
|
||||
- OSPO
|
||||
- SupplyChain
|
||||
- DeutscheBahn
|
||||
headerimage:
|
||||
src: max-cornelius-stage.jpg
|
||||
alt: Cornelius Schumacher and Max Mehl giving the presentation at FOSS Backstage 2026. It's a total view of the auditorium from the back, with the two speakers on stage and the final slide in the background.
|
||||
# summary: Visible on the listing page, but not on the article page
|
||||
video: https://www.youtube.com/watch?v=M8wYRRCWaQU
|
||||
slides: https://up.mehl.mx/slides/2026-03-17-foss-backstage-supply-chain.pdf
|
||||
event:
|
||||
name: FOSS Backstage 2026
|
||||
href: https://26.foss-backstage.de/session/getting-real-with-the-supply-chain-from-sbom-data-to-action/
|
||||
---
|
||||
|
||||
At DB, we handle 100,000+ SBOMs per day. For our small, virtual Open Source Program Office (OSPO), the challenge is not to get lost in the data, but to cut through the jungle and identify real risks. Together with my OSPO colleague Cornelius Schumacher, I presented this challenge at the FOSS Backstage conference in Berlin. We explained how we gather data, generate insights, and take action.
|
||||
|
||||
This talk was partly inspired by my earlier FOSDEM talks ([here](/blog/2026-01-fosdem-supply-chain-strategy) and [there](/blog/2026-02-fosdem-sbom-collection)), where I focused on DB's SBOM program and its tools. In this presentation, however, we highlighted what can be learned from it for professional Open Source management.
|
||||
|
||||
One topic stood out throughout the presentation: the need for an OSPO to balance between people, value, and risk. None of these should dominate, even though governance functions often tend to focus on risk. Instead, Cornelius and I advocated for a risk-based approach to managing Open Source.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 221 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 797 KiB |
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: "Software-Lieferketten bei der Deutschen Bahn"
|
||||
date: 2026-03-25
|
||||
categories:
|
||||
- deutsch
|
||||
- podcast
|
||||
tags:
|
||||
- Community
|
||||
- DeutscheBahn
|
||||
- SupplyChain
|
||||
headerimage:
|
||||
src: ciw.jpg
|
||||
alt: The famous "Captain it's Wednesday" comic
|
||||
processes:
|
||||
- fill 1000x440 center webp
|
||||
audio: https://gnulinux.ch/podcast/CIW175.mp3
|
||||
event:
|
||||
name: Captain it's Wednesday Podcast
|
||||
href: https://gnulinux.ch/ciw175-podcast
|
||||
---
|
||||
|
||||
Ich wurde mal wieder von Ralf Hersel zum "Captain it's Wednesday" Podcast von GNU/Linux.ch eingeladen, um über Software-Lieferketten bei der Deutschen Bahn zu sprechen. Anlass waren meine jüngsten Vorträge auf der [FOSS Backstage](/blog/2026-03-foss-backstage-getting-real-supply-chain) und der [FOSDEM](/blog/2026-01-fosdem-supply-chain-strategy), in denen ich über die Herausforderungen und Chancen von Software-Lieferketten bei der DB gesprochen habe.
|
||||
|
||||
Mit Ralf habe ich mal ganz vorne angefangen: was ist eine Software-Lieferkette überhaupt, warum ist sie wichtig, und wie sieht sie bei einem großen Unternehmen wie der Deutschen Bahn aus, und was haben diese SBOMs damit zu tun? Wir haben über die enormen Mengen an Software-Komponenten gesprochen, die täglich bei der DB verarbeitet werden, und wie wir versuchen, den Überblick zu behalten und Risiken zu managen. Dabei ging es auch um die Rolle von Freier und Open Source in der Lieferkette und wie wir dabei mit der Community zusammenarbeiten.
|
||||
|
||||
Nach exakt 37 Minuten war das Gespräch auch schon wieder vorbei und natürlich konnten wir nicht in jedes Detail eintauchen. Aber ich hoffe, es war dennoch ein interessanter Einblick für die Zuhörenden.
|
||||
Reference in New Issue
Block a user