-
Notifications
You must be signed in to change notification settings - Fork 14
19 Feb 2025
Philipp Ahmann edited this page Feb 19, 2025
·
2 revisions
** indicates TSC voting members*
- *Philipp Ahmann
- 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
- Julien Spanneut
- *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
- 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 January.
- Thanks for the great organization and active participation
- Results will be made available soon.
- Presentations have been collected and will be added to https://directory.elisa.tech/
- Videos are being processed and will be uploaded to ELISA YouTube channel: https://www.youtube.com/@elisaproject8453
- Deutsche Bahn & SNCF cannot join today.
- No response from Scheidt-Bachmann yet.
- Henrik from RWTH Aachen joined today also interested in the group.
- Idea is to have initial discussions out of TSC row. Meeting poll will come.
- Draft for the Railways WG is created for discussion in such a meeting.
- Philipp will send the poll for a separate call.
- TSC New WG proposal template can be found here https://github.com/elisa-tech/tsc/blob/master/new-wg-template.md
- Bring this to the agenda on next TSC again.
- Railway is interesting for ELISA as this belongs to the safety regulated industries.
- There is also information on usage of Linux in trains ;-)
- SIL2 use cases are on the way for automated trains.
- Railway has safety layer with certain components (e.g. communication) supporting the safety application without being the safety application. Where are these middleware layers located.
- This is not limited to Railways, but also fit to other industries (like Automotive)
- Derived discussions (not Railway specific):
- Two approaches: Safety requirements allocated to Linux and Linux without safety responsibility, but being used in safety applications (as "QM / SIL0")
- "Linux in safety applications" also does not clearly define what it includes. If it is only the kernel or the Linux systems.
- Could be implemented in a cross functional (industries) working group defining the requirements towards Linux
- Linux Features looks into a minimal application cross industries.
- Linux should behave as expected by its implementation (e.g. by its documentation)
- Systems WG addresses an ASIL decomposition and systems where Linux may be QM
- Watchdog is also common to most architectures and industries.
- Maybe it is enough to make this more clearly and defining a framework that the verticals can frame main features and map them to Linux. This need to be more formalized to be aligned.
- Point was made that the same OS can be sold to different industries. Though the way to express expectations of the industries are not identical
- AI: Need to follow up on this. Systems or Arch WG meeting is a good place for this.
- Tentative May 20-22 somewhere in Europe
- Like in past: First 1/2 day in the afternoon + 2nd full day + 3rd 1/2 day in the morning (for better traveling)
- Tuesday to Thursday is nice for people joining from US (No travel on Weekend)
- Being more intentional to include more time for discussions
- Closer to unconference sessions (e.g. 10 minute topic introduction, 30 min discussion, 10 min wrapup and next steps)
- Min will prepare a poll to check availability for May 20-22 and May 7-9 being okay or not.
- https://docs.google.com/document/d/1c7S7YAledHP2EEQ2nh26Ibegij-XPNuUFkrFLtJPlzs
- Scripts prepared by Alessandroare (PR exist) to generate the Requirements Id
- Can check, where requirements IDs are missing, add ids and find suspective Ids (when something chagned).
- Consider live demo for one of the following TSC meetings, when PR is merged.
- topic for next TSC meeting.
- ...
Up to 3 bullet points
- Aerospace/Space
- Automotive
- Medical
- Arch
- Linux Features
- OSEP
- Tools
- Systems
- From last TSC
- Goddard Blog is out: https://elisa.tech/blog/2025/01/22/recap-of-the-elisa-workshop-at-nasa-goddard-advancing-space-grade-linux/
- FOSDEM Blog is out: https://elisa.tech/ambassadors/2025/02/13/elisa-project-and-linux-foundation-community-shine-at-fosdem-2025/
- Standards Atlas next deep dive under planning: https://lists.elisa.tech/g/devel/message/2324
- Questions/Intro from Panos (joining first time):
- Background: Systems knowledge with containers, DevOPs. Security focus from time at Red Hat. Likes also lowlevel stuff.
- Potential working groups to get involved:
- Linux Features WG to look deep inside the kernel and how to build it.
- Systems WG for creating system images and how to get them into DevOPs.
- https://github.com/elisa-tech/wg-systems/blob/main/Documentation/xen-demo-zcu102/Readme.md
- Check the mailing lists: https://lists.elisa.tech/calendar
- 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)
- 26-27 Feb - AGL AMM Tokyo
- 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
Collaborative editing: https://mensuel.framapad.org/p/elisa-tsc-minutes-a9tp?lang=en