Skip to content

04 Sep 2024

Jump to bottom
Philipp Ahmann edited this page Sep 4, 2024 · 6 revisions

Roll call

* indicates TSC voting members

Host

  • *Philipp Ahmann

Attended this meeting

  • Olivier Charrier
  • Pete Brink
  • *Matt Weber
  • *Alessandro Carminati
  • *Gabriele Paoloni
  • *Sudip Mukherjee
  • *Lukas Bulwahn (1st half)
  • *Kate Stewart (2nd half)

Regrets

  • *Paul Albertella

Attended recently in the past

  • *Matt Kelly

  • *Christopher Temple

  • Naresh Ravuri

  • Steve VanderLeest

  • Youssef Hajjioui

  • JE[A]Y

  • Vipul Gupta

Topics & Notes

Check past action items

  • Action items in github issues
  • AI-Paul: Discuss in OSEP WG meeting where to put the "good practices for Open Source" document
  • DONE AI-Min/Paul: Enable GitHub pages
    • Enabled including sub-domain setting. Github pages should work

Next workshop timing/location considerations

  • Survey to confirm availability is still open: https://forms.gle/n2uphHagQa4wB4Ek8
  • Target December 10 to 12th.
  • Location is not set yet.
    • ZAL.aero events team contacted, no feedback yet. AI-Philipp: Reach out to ZAL again as dates are clear now.
    • NASA (East coast) as potential location: AI-Kate: Reach out to NASA again as dates are clear now.

Systems WG: Good Quality Practices in Open Source [cont.]

  • Draft to reach out to others prepared
  • Link to document
  • Now get in touch with foundations, universities and companies
  • Discussions took place in OSEP WG Aug 22nd
    • Recaps from meeting:
    • This does not meet the understanding of quality as Pete sees it.
    • Low bug rate is a definition of quality it is just a valid measurement.
    • For non-business-critical systems SW could be deployed and response (in form of incidents) can create valid/invalid requirements.
      • This is not seen as an option for safety-critical systems
    • Companies have own definition on quality and do things differently to achieve same result.
    • Bug is a requirement bug or an implementation bug.
    • Requirements: What is written? What is implemented? How is this interpreted/understood by the user?
      • This is crucial when talking about Linux as the user experience on Linux/Unix was established 30 years+
    • Quality processes is the other element to consider.
  • Look and feel work started in WIP PR https://github.com/elisa-tech/wg-systems/pull/16/
  • Some further reading on the definition of quality and sw quality:

The core parts of the kernel [cont.]

  • Last TSC meeting discussion 21 Aug 2024
  • Small repo prepared with buildroot patch to build bare minimal kernel with only initramfs (no mem or storage devices).
  • Active discussion in LFSCS meetings ongoing. [Meeting Minutes]
  • Boeing (Yanmei Guo) participated in LFSCS to talk about Boeing's minimal configuration. (Follow up from last TSC meeting)
  • first topic elaborated "chacha" as a dependency from crypto subsystem -> this was unexpected
    • This is related to Random number generation, which is enabled in minimal kernel.
    • Switching it off is possible. This will impact security. In this case safety and security may not have same requirements.
  • The framework and how the analysis is done is very important. So this analysis could be applied to different use cases later on.
    • Consistency on what you do and how you do the analysis will be very valuable.
    • Currently focus on system tracing with expected and unexpected behaviour.
    • A bit of system top-down with subject matter experts to look at it from bottom up.

Short status from WGs

Up to 3 bullet points

  • Aerospace
  • Automotive
    • meta-elisa porting from needlefish to ricefish is started as needlefish is out of support.
    • Features ic-demo-support changed since needlefish, so investigation on new dependencies is ongoing
    • Automotive meeting planned for OSS EU together with AGL (Walt)
  • Medical
    • no report today
  • Arch
  • OSEP
    • see above for "what is quality"
  • Tools
    • ksnav/delta-kernel conversation on next steps for change impact analysis
    • talked about updating the kernel config checker to have profiles
  • Systems
    • Good practices proposal making progress
    • WIP PR started to also document some first thoughts.
    • Feedback welcome. 😉
  • Linux Features
    • It was discussed why chacha is needed and why we need some crypto parts even in a very small configuration.
    • Minimal config is discussed
    • See above

AoB

  • No TSC Meeting Sep 18th due to OSS Europe and Plumbers
  • New KernelCI Webinar following this meeting.
  • Zephyr Meetup October 17th at ZAL.aero (ELISA will talk about Systems WG there)
  • AI: EMQ SDV WG ideas to be added to next TSC meeting agenda

Announcements

First half year topics for seminar series

Upcoming events

Clone this wiki locally