Skip to content

20 Mar 2024

Jump to bottom
Philipp Ahmann edited this page Mar 20, 2024 · 5 revisions

Roll call

* indicates TSC voting members

Host

  • *Philipp Ahmann

Attended this meeting

  • *Steve VanderLeest
  • *Alessandro Carminati
  • *Paul Albertella
  • *Sudip Mukherjee
  • *Kate Stewart
  • Olivier Charrier
  • *Gabriele Paoloni
  • *Christopher Temple
  • *Matt Kelly
  • Pete Brink
  • *Lukas Bulwahn

Regrets

Attended recently in the past

  • Vipul Gupta

Topics & Notes

Check past action items

  • AI: TSC follow up: How to prepare for the the core parts of the kernel session to make it productive in the workshop?
    • may be on agenda next time.
  • AI: Topics for plumbers to be evaluated in the next TSC
  • Action items are migrated to github issues.

Plumbers mini-conf

  • Plumbers micro-conf deadline is April 4th.
    • CfP: https://lpc.events/event/18/abstracts/
    • Plumbers is in Austria (Vienna) this year 18-20th September
    • Plumbers are best for problems and how to engage with the kernel community to get them sorted out and what is feasible from their point of view.
    • Series of problems...
      • Lack of documentation. How to get community engaged in improving Kernel documentation.
        • show example in how to improve documentation?
        • need to get buy-in.
        • what is a acceptable level of details?
        • (Also topic for F2F workshop)
      • Requirements is also an aspect of documentation
        • traceability, how to identify changes
      • How to link up test coverage and increase coverage
        • Boeing recently started a study with university Illinois to work on various kind of coverage like MC/DC
          • Should respond to CfP at Plumbers to put a talk in (maybe for testing track)
          • Connect also to Collin King to measure coverage with stress-ng.
          • Make it a seminar. Let it be hosted by the Tools WG.
        • MC/DC is relevant for DAL-A and also for ASIL-D
      • what helps people proving safe usage of Linux kernel?
        • workload tracing (already upstream by Shefali and Shuah)
        • ks-nav work
          • submit ks-nav talk also to OSS EU in safety-critical track
        • RTVM Runtime Verification Monitoring by Daniel Bristot
      • Codethink, Red Hat, Linutronix, and Wind River may be good candidates to be there.
        • If someone has names who be there, please share with Kate & Philipp
    • Testing and Dependability may be an own mini-conf at plumbers

June workshop registration and further planning

  • Registration is here: https://forms.gle/HV9ciQTcbkSwLZ1BA
  • June 4-5 in Lund (Sweden)
  • More information in last TSC meeting minutes.
  • Topic proposals from last TSC
    • Start day 1: Ask me Anything session (like last workshop)
    • ELISA in world of Software Defined Vehicles (vehicles does not mean "cars" alone)
    • Day 2: What does SOTIF mean for ELISA?
    • Day 2: What are technical roadmap topics important for members to be worked on during the next year?
    • Continue to work/discuss on the core parts of the kernel
  • Topics based on registration sheet
    • Later during 1st day: State of Linux Feature working group due to restart (LFSCS WG)
    • Tools WG KS-NAV state.
    • Improving Kernel Documentation and involving the experts (Arch WG)
    • STPA-like vs Expert Driven FMEA (Arch WG)
    • (OSEP will discuss topics for WS in tomorrows OSEP meeting.)
  • Further topics
    • Nix may propose something about reproducible, dependable systems, SBOMs
    • Coordination between different WGs especially LFSCS, OSEP, and ARCH
    • SPDX Safety profile. (Kate & Nicole)
    • SBOM generation from yocto by Joshua Watt (Kate)
    • reserve spot for Volvo maybe about "digital safety belt"
    • Evening time: Testing the Kernel,
      • forming requirements (and guidelines on requirements for requirements)
      • creating traceability
    • Path and content for a coding day.
  • Next TSC meeting create a formal agenda out of workshop topic proposals.

WG Coordination [started]

  • Input for discussion: Recently, in the safety arch WG the current asset and coordination between WGs has been quickly discussed. As of now the expectations have been to have the domain specific WGs to define safety requirements for Linux following specific use cases analyses and then having the horizontal WGs (especially Arch, LFSCS and OSEP) to elaborate on specific safety analyses, methodology and technical investigation for Linux to support the allocated safety requirements. However recently the OSEP WGs has been elaborating safety requirements and architectural assumptions that can be used as a baseline for the Arch WG and the LFSCS WG to work on. So in addition to the top-down flow (from domain WGs to Horizontal WGs) we could also discuss a bottom up flow; i.e. domain specific WGs can review such safety requirements/claims in the context of their specific use cases.
  • Have discussion on the devel mailing list and continue during TSC meeting

Coding day ideas for timing and content [skipped]

  • depending on content we may need to have different co-location (e.g. more safety or more kernel or integrator)
  • Next possible chance to co-locate with Eclipse SDV would be towards end of the year (due to schedule conflicts)

First half year topics for webinar series

  • Past webinars on website: https://elisa.tech/seminar-series/
  • Lukas presented his work from exida symposium - March 12th (~170 registrations and +70 attending)
  • ASIL-D certified Rust compiler is targeted for - May 8th (will be announced after Lukas' webinar)
  • stress-ng update -> Kate wants to follow up with Collin King
  • Later during the year:
    • Have something about SOTIF, depending on discussions during June workshop.
    • RT webinar once PREEMPT_RT is fully mainline.
    • ELISA user story by a company.
    • Seminar on Coverage by university Illinois and Boeing (Steve)
      • already good presentation material available
      • can something be presented in first week of April before OSS NA to establish connections.

AoB

Announcements

Upcoming events

Clone this wiki locally