-
Notifications
You must be signed in to change notification settings - Fork 14
2025‐09‐17
Philipp Ahmann edited this page Sep 17, 2025
·
3 revisions
** indicates TSC voting members*
- *Philipp Ahmann
- Pete Brink
- *Alessandro Carminati
- *Gab Paoloni
- *Nicole Pappler
- *Kate Stewart
- Henrik Brandle
- Jielink Yu
- Justin Stanley
- *Olivier Charrrier
- Pierre Brangier
- *Sudip Mukherjee
- Simone Weiss
- *Igor Stoppa
- Matt Kelly
- Matt Weber
- *Luigi Pellecchia
- *Gab Paoloni
- *Igor Stoppa
- *Paul Albertella
- *Christopher Temple
- *Nicole Pappler
- *Olivier Charrier
- *Kate Stewart
- *Paul Albertella
- *Igor Stoppa
- *Alessandro Carminati
- *Gabriele Paoloni
- *Matthew Weber
- *Matt Kelly
- *Sudip Mukherjee
- *Lukas Bulwahn
- Henrik Brandle
- Pierre Brangier
- Patrick Uven
- Sebastian Hetze
- Panos Kalorog
- Pete Brink
- Michael Mahoney
- Jaylin Yu
- Victor Lu
- Naresh Ravuri
- Elana Copperman
- Steve VanderLeest
- Qasim
- Stephen Oresanya
- Justin Stanley
- Action items in github issues
- https://github.com/elisa-tech/tsc/issues
- To be cleaned up.
-
Done AI-Philipp: Draft a revised meeting recordings and transcription policy and put it under TSC GitHub
- Proposal merged: https://github.com/elisa-tech/tsc/pull/83
- Date: Nov 18th to 20th
- Location: Red Hat Office Munich (https://www.openstreetmap.org/node/3150576032#map=17/48.101710/11.757479))
- Topics to be discussed in TSC meeting.
- Fill in form to submit your topics: https://forms.gle/PrvR4JAEbCFQTVPy9
- Registration for workshop will be done separately.
- Agenda draft: https://docs.google.com/document/d/1cwNQHfnix56SlouGea3yJQoKZuW33Egxlh2Aal21WWg
- Topics to consider:
- Aerospace and/or Space Grade Linux session (?Martin Halle? AFST Hamburg)
- Automated Train (check with Sebastian Hetze who may want to present)
- AGL SDV EG reference system (get in touch with Jan-Simon, Kusakabe-san and Walt)
- Stef Tatschner on his thesis (lighthouse-oss related): https://researchrepository.ul.ie/entities/publication/e4b7b543-f927-4bad-8946-bca9454e48d0
- Lighthouse-OSS Template examples (Simone Weiss)
- Requirements within the Kernel sources (Gab) and the role of BASIL+KernelCI (?Luigi?)
- Topics for workshop/breakout session:
- meta-elisa update and roadmap towards AGL SDV EG system (AGL+Android+Zephyr+Xen).
- SBOM generation on system (all OS parts) level of interest
- CVE report
- SBOM & CVE could be a breakout session. (There was also a session at OSS EU in the area)
- Upfront setup a nightly build on latest Yocto to create SBOM and CVE report.
- Relates also to Lighthouse-OSS template.
- meta-elisa update and roadmap towards AGL SDV EG system (AGL+Android+Zephyr+Xen).
- Can Boeing nominate new WG lead?
- Boeing can propose a new chair/lead, but TSC need to approve the new working group lead.
- Philiipp will drop a mail to the TSC-voting mailing list to get their view and potentially approval.
- Anyone wants to take over the tools WG (or knows a candidate)?
- No direct feedback during TSC meeting on volunteers or candidates.
- Adjust term to Jan -> Dec?
- Yearly re-election (as other projects do annual elections)?
- What is not clear is how we define voters.
- Other projects check with contributors
- ELISA has more pieces of contributions.
- Project charter also need to be taken into account. https://elisa.tech/wp-content/uploads/sites/19/2020/08/elisa_technical_charter_082620.pdf
- Philipp will also send a mail on tsc-voting mailing list.
- See notes from last meeting for first discussion.
- Continue in next TSC
- Kate is currently checking with LF Research on possibilities and if there is overall benefit seen in such a survey.
- Continue the discussion also in person during OSS EU in Amsterdam (potentially with the LF Research people like Hillary) and also during TSC meeting.
Up to 3 bullet points
- Aerospace/Space
- Automotive
- Medical (paused)
- Architecture
- Linux Features
- OSEP
- Tools
- Systems
- Cleaning up TSC repo information
- https://github.com/elisa-tech/tsc/pulls
- Also Automotive WG repo requires a cleanup
- ToC for TSC wiki could be restructured
- Check if there can be something like a hierarchy
- Proposal for Safe Systems With Linux MC
- First submissions received.
- Requirements within the Kernel. Any thoughts in handling expertice of the author properly?
- Basically, in the patch set you can find an intermediate state in introducing the requirements.
- 1st patch guideline and best practice to write code specification. (e.g. how to use may, shall, shall not)
- 2nd patch examples for mem.c
- 3rd patch self test linked and traced to function expectations for /dev/mem
- Self contained patch set
- Guideline should be part of Linux Kernel Documentation to help developers in writing good specifications
- Review guideline for maintainers may become also important.. So far it is implicit. Like today already need to work against guidelines.
- 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)
- 08-10 Dec - Open Source Summit Japan
- 11-12 Dec - Linux Plumbers
Collaborative editing: https://mensuel.framapad.org/p/elisa-tsc-minutes-a9tp?lang=en