15 May 2024 - elisa-tech/tsc GitHub Wiki

Roll call

* indicates TSC voting members

Host

  • *Philipp Ahmann

Attended this meeting

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

Regrets

Attended recently in the past

  • Youssef Hajjioui
  • JE[A]Y
  • *Lukas Bulwahn
  • Vipul Gupta

Topics & Notes

Check past action items

  • Action items in github issues
  • Philipp to check with Eclipse SDV if someone can join the Lund workshop.
    • Hard to join for them due to parallel workshop. Want to cooperate on Automotive processes for OSS
    • Check if someone from SOAFEE wants to join for the SDV topic.
  • Philipp to check if someone from ZAL.aero is interested in joining the Lund workshop
    • ZAL.aero is not able to join the Lund workshop
    • They may be interested in hosting our fall workshop (follow up needed)
    • Their current PoC is close to the work of the systems WG

June workshop clarifications

  • Registration is here: https://forms.gle/HV9ciQTcbkSwLZ1BA
  • More information in past TSC meeting minutes.
  • Nearest airport Copenhagen CPH
  • Local transport from Airport to Lund almost every 20 minutes.

Status on Linux Plumbers miniconf

Automotive Processes for OSS (an Eclipse SDV collaboration?)

  • Eclipse SDV wants to drive the process on how to apply ASPICE and other Automotive standards to OSS or how to argue a compliance.
  • Goal is to collaborate with ELISA to enable more open Source component usage in Automotive
  • First meeting next week.
  • Has relevance to OSEP work, so Paul will be involved after kick-off meeting.

The core parts of the kernel workshop session preps

  • What is the definition of core?
    • minimal config
    • what is required in any configuration
      • Something everybody needs differs from the minimum for a use cases
    • everyone may be 90%.
  • Pick use cases and what constitutes core for them.
  • Select and remove configs
  • What are base definitions of integrators like Suse, Canonical, Red Hat, Windriver, Linuxtronics
    • Can we get some configs from Linutronics and/or Windriver how a core looks like?
    • Create a first framing first and then reach out to them.
  • 2 phases
      1. common subsystems used by almost every use case. (things that are always there)
  • Config is not analogues to "the thing".
  • Filesystem like vfs may be always there, but for higher criticality no other fs may be needed while for other levels it is.
    • We cannot say which filesystem, but one filesystem should be there, so e.g. initramfs. So it may be core.
  • Core definition helps to set priorities. What is most important to focus on. What are configs and properties
    • RT was one example, which people request. (Even if many use cases may not require it.)
  • This can also be an input for the plumbers session.
  • What do we want to reach with the core? Which demands do we put on the core (like requirements, design, testing, documentation).
  • We need to get acceptance by the kernel community that the core part is relevant.
  • Why are we defining this core set? The goal is as important as the analysis.
    • It should end in a higher quality for the kernel.
    • Is defining requirements and increase coverage the right approach?
    • Is it better to check on "what can go wrong"? What is the right approach?
    • Traceability for changes? Will the change impact my original functionality and will everything work as expected?
    • Give priority to subsystems and drivers most common to most use cases.
  • Agreeing to features (one by one) is also way to set the core. (Even if it is not your favourable feature, like specific fs).
  • ELISA can show "this is how you could do it".
  • Focus for now is really on kernel functionality.
    • Discussion about packages is taken at a later stage, e.g. by consulting CIP project on their definition of core packages and extended packages
  • To prepare for Lund a summary of Manchester and Munich workshop is needed, as this was a topic there as well.
  • Notes and ideas need to be sorted for the actual discussion and the time boxing.
  • Draft a description and finalize things and enhance during the workshop to discuss and agree towards next steps.
  • It is a cross working group activity. It will be tailored by use cases working groups.
  • Potential spot for the work: https://github.com/elisa-tech/tsc/wiki/The-core-parts-of-the-Kernel
    • Very first draft can be in wiki, but moving forward to github when things are a bit more stable.

AoB

  • none

Announcements

First half year topics for webinar series

  • Past webinars on website: https://elisa.tech/seminar-series/
  • Seminar on Coverage by university Illinois and Boeing (Steve) scheduled - May 22nd
  • 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.

Upcoming events

  • 22-23 May Lund Linux Con https://lundlinuxcon.org
  • 04-05 Jun ELISA Workshop in Lund (Sweden)
  • 16-18 Sep Open Source Summit Europe in Vienna (Austria)
  • 18-20 Sep Linux Plumbers in Vienna (Austria)