05 Mar 2025 - elisa-tech/tsc GitHub Wiki

Roll call

** indicates TSC voting members*

Host

  • *Philipp Ahmann

Attended this meeting

  • *Kate Stewart
  • *Alessandro Carminati
  • Henrik Brandle
  • *Igor Stoppa
  • *Olivier Charrier
  • *Nicole Pappler
  • *Sudip Mukherjee
  • Stephen Oresanya
  • *Gabriele Paoloni
  • Peter Brink
  • Christopher Temple

Regrets

  • Pierre Brangier

Attended recently in the past

  • Julien Spanneut
  • Sebastian Hetze
  • Pierre Brangier
  • *Alessandro Carminati
  • *Gabriele Paoloni
  • Henrik Brandle
  • *Kate Stewart
  • *Matt Kelly
  • *Matthew Weber
  • *Nicole Pappler
  • Patrick Uven
  • Sebastian Hetze
  • *Christopher Temple
  • *Olivier Charrier
  • Panos Kalorog
  • *Igor Stoppa
  • Pete Brink
  • *Paul Albertella
  • *Igor Stoppa
  • Michael Mahoney
  • Jaylin
  • Naresh Ravuri
  • Elana Copperman
  • *Sudip Mukherjee
  • *Lukas Bulwahn
  • Steve VanderLeest
  • Youssef Hajjioui
  • JE[A]Y
  • Vipul Gupta
  • Qasim

Topics & Notes

Check past action items

  • Action items in github issues
  • https://github.com/elisa-tech/tsc/issues
  • AI-Paul: Discuss in OSEP WG meeting where to put the "good practices for Open Source" document
    • Discussed, but not a proposal yet
  • AI: EMQ SDV WG ideas to be added to one of next TSC meeting agenda
    • Follow up between Philipp and Jaylin during March.

ELISA Annual Virtual WG Updates [info]

  • Blog goes out today. Thanks to Gab and Mae for their preparations.

Railways Working Group Discussion [info]

  • Meeting to discuss it will happen on Thursday 16:00 UTC.
  • Invitation via devel mailing list.

Requirements within the Kernel [cont.]

  • https://docs.google.com/document/d/1c7S7YAledHP2EEQ2nh26Ibegij-XPNuUFkrFLtJPlzs
  • Script demo as PR is merged: https://github.com/elisa-tech/linux/pull/2
    • Live demo. image
    • Script searches for missing Req-Ids.
    • Script has two verbs "check" and "generate".
    • Check looks for missing Ids
    • Generate creates the missing Ids.
    • Check also can show in case something has changed.
    • Req-Id is unique and not changed. In case just some comment and minor corrections this will affect the hash.
    • Proposal: Rather than "The id at 749 is OK but changes are made" it could imply that the change is OK.
      • Req hash key is identical with the requirement initially, but once changes are made the hash key has to be updated.
      • After some time it will be most likely saying "The id at xyz is OK but changes are made" for most parts. This function is not really a meaningful. After time the information may be "hash key has changed".
      • Req-Id and Hash key is calculated the same way, but changes are made is not meaningful as the actual thing to be checked is on hash key
      • Currently it is just to show that the logic that a change can be detected is implemented.
  • Everyone welcome to make proposals on how to write requirements and make the proposals in the pull requests.
  • When mature, need to get Steve into the meeting to get his feedback as being the maintainer for the subsystem.
  • Idea: Build the kernel in ELISA CI and execute scripts like to check requirements for proper Id to showcase and having a blue print for own use.

Minimal Application Feature Requirement Update from LFSCS

  • topic for beginning of next TSC meeting.
  • ...

Next ELISA WS thoughts and considerations

  • Option: May 7-9 at Volvo in Lund Sweden (like last year)
  • Ideas:
    • Being more intentional to include more time for discussions
    • Closer to unconference sessions (e.g. 10 minute topic introduction, 30 min discussion, 10 min wrap up and next steps)
  • Timing:
    • Start after lunch (13:00) on Wednesday 7th
    • Full day Thursday 8th
    • Half day until lunch (12:30) Friday 9th
    • Visit MAX4 or other research facility on Friday afternoon after workshop.
  • Topic planning:
    • Requirements within the Kernel (Gab, Red Hat + support by: Kate, Chuck)
    • Topics from 2025 WG goals:
    • How far do we go on the hardware level? (Olivier, Wind River + support by: Gab, Igor)
      • Fits to minimal kernel/application
      • Starting point. Think about it
      • Doing is an integrator job.
      • Analysis what kernel already provides
    • Safe Linux vs. Safe(ty) Linux
      • Approaches
      • Levels of Enabling Linux in Safety Applications
    • Trustable Software Framework (Paul, Codethink + support by: Philipp)
  • Further considerations:
    • Balance:
      • WG specific,
      • Cross WG: Best practices Standard
      • Beyond ELISA activities: Kernel CI, Eclipse SDV collaboration
      • Fields: Linux Kernel, Process, Testing:
    • AI Kate, Min, Philipp: Rework CfP form to be more specific, add selection in topics of interest, and "lead discussion".
    • Reach out to KernelCI (Gustavo) -> Requirements Linkage topic. -> Code coverage (LoC, not Req) topic started in Kernel CI tools side

Optional: Short status from WGs (skipped)

Up to 3 bullet points

  • Aerospace/Space
  • Automotive
  • Medical
  • Arch
  • Linux Features
  • OSEP
  • Tools
  • Systems

AoB

Announcements

Topics for seminar series

  • To be defined: SDV seminar by EMQ to motivate the update and cloud part of HPC systems
  • RT webinar once PREEMPT_RT as last patch is mainline.🥳
  • Past webinars on website: https://elisa.tech/seminar-series/
  • Later this year:
  • ELISA user story by a company.
  • Julia Lawall about formal verification (derived from Lund Linux Con presentation)

Upcoming events

  • 11-13 Mar - Embedded World Nurenburg
  • 18-20 Mar - LF Member summit
  • 14-15 May - Linaro Connect
  • 20-21 May - safe.tech by TÜV
  • 27-28 May - Lund Linux Con

Remarks

Collaborative editing: https://mensuel.framapad.org/p/elisa-tsc-minutes-a9tp?lang=en