2026‐01‐07 - elisa-tech/tsc GitHub Wiki

Roll call

  • indicates TSC voting members

Host

  • *Philipp Ahmann

Attended this meeting

  • Pierre Brangier
  • Pete Brink
  • Jaylin Yu
  • *Alessandro Carminati
  • *Gabriele Paoloni
  • *Igor Stoppa
  • *Olivier Charrier
  • *Matthew Weber
  • Michael Mahoney
  • *Paul Albertella (1st half)
  • *Sudip Mukherjee
  • Victor Lu
  • Pete Brink
  • *Luigi Pellecchia

Regrets

  • *Nicole Pappler

TSC members

  • *Alessandro Carminati
  • *Gabriele Paoloni
  • *Igor Stoppa
  • *Kate Stewart
  • *Luigi Pellecchia
  • *Matthew Weber
  • *Nicole Pappler
  • *Olivier Charrier
  • *Paul Albertella
  • *Sudip Mukherjee See: https://elisa.tech/about/tsc/

Community members attended recently in the past

  • Christopher Temple
  • Henrik Brandle
  • Jaylin Yu
  • Justin Stanley
  • Lukas Bulwahn
  • Michael Mahoney
  • Patrick Uven
  • Pete Brink
  • Pierre Brangier
  • Sebastian Hetze
  • Simone Weiss
  • Stephen Oresanya
  • Victor Lu

Topics & Notes

Check past action items

  • Action items in github issues
  • **AI: **TSC repo cleanup needed including issues
    • Ongoing
  • AI: TSC wiki sidebar needs rework
    • There may be an option to use Javascript to ease work on updating sidebar. Need to be checked further.

TSC chair vote

  • TSC chair election
  • TSC members are the voters and those who can nominate themselves as candidate.
  • Send nomination statement with bio and short pitch to the TSC-voting mailing list [email protected].
  • Nomination period: Start Jan 7 to 14th
  • Voting: Jan 15th to 20th
  • Conclude on next TSC meeting January 21st.
  • From ELISA project charter: TSC Chair “The TSC shall elect a TSC Chair, who will preside over meetings of the TSC and will serve for a one-year term (or until their earlier resignation or ceasing to be a voting member of the TSC). The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and the ELISA Fund of The Linux Foundation”
  • TSC chair is also part of the governing board as a voting member

Plumbers MC re-cap

  • See: https://lpc.events/event/19/sessions/221/#20251212
  • Many discussions around requirements and testing. Also different opinons among the maintainers, so not a common streamlined view yet. More discussions will continue on Friday during Architecture WG.
    • Greg was just around at OSS JP, but not plumbers. Suggestions was to remove most requirement formalisim from the current patch set, but feedback from other maintainers were looking for more formal machine readable format.
    • Really much feedback during plumbers and even more via e-mail, which is still in processing.
    • There was a patch set by Sasha Levin on how machine readable requirements can look like. https://lwn.net/ml/all/[email protected]/
    • Requirements are based on the what the code is supposed to do, but not on the code directly. When requirements are based on code they require a review that this is also their intention. So far we are limited to reverse engineering. With a reverse engineered requirement reviewed by a maintainer it becomes a requirement which describes which the code is supposed to do.
  • Johnathan Corbet also had a talk about usage of AI to generate documentation, but one core message was that the review has to be done on whatever is generated that it reflects exactly what you intended to be it.
  • One observation is, that it is important to see where to go with the kernel maintainers and which parts not to bother them with.
  • With EARS = Easy Approach to Requirements Syntax a way of writing formal requirements can be achieved
  • Question from participant in TSC meeting: https://martin.kleppmann.com/2025/12/08/ai-formal-verification.html Proof assistants and proof-oriented programming languages such as Rocq (https://rocq-prover.org/)), Isabelle (https://isabelle.in.tum.de/)), Lean (https://lean-lang.org/)), F* (https://fstar-lang.org/)), and Agda (https://agda.readthedocs.io/)) have been around for a long time —- which language is a fit for ELISA?
    • ELISA is flexible and has not assessed this so far. It needs to fit upstream and resonate with the Kernel community

FOSDEM

Virtual Working Group Updates

  • Have a virtual Working Group updates on 2025 achievements and 2026 planned activities end of January or early February.
  • SGL and Lighthouse-SIG are to be included.
    • SGL confirmation needed. Min will check with Ramon.
    • Lighthouse can present something.
  • Split to two days again. This time proposal February 11th and 12th.
    • Works for the WG leads. Cross-check with Paul needed
    • Nothing directly on Tools WG. Mention in the Introduction and during BASIL session.
      • As follow up have a dedicated webinar on BASIL as an update from the last one
  • Last years event: https://elisa.tech/event/working-group-annual-updates-2025/2025-02-12/
  • Agenda draft:
    • Session on February 11 will include updates from speakers/WG leads of the following Working Groups:
    • 15:00-15:15 UTC: ELISA Project Overview (Philipp Ahmann, ETAS)
    • 15:15-15:40 UTC: Systems and Automotive (Philipp Ahmann, ETAS)
    • 15:40-16:05 UTC: Open Source Engineering Process (Paul Albertella, Codethink)
    • 16:05-16:30 UTC: Safety Architecture (Gabriele Paoloni, Red Hat)
    • 16:30-16:55 UTC: Linux Features for Safety-Critical Systems (Alessandro Carminati, Red Hat)
  • Session on February 12 will include updates from speakers/WG leads of the following the use-case focused Working Groups and SIGs
    • 15:00-15:05 UTC: Welcome back (Philipp Ahmann, ETAS)
    • 15:05-15:30 UTC: BASIL & Tools WG evolution (Luigi Pellecchia, Red Hat)
    • 15:30-15:55 UTC: Lighthouse SIG (Philipp Ahmann, ETAS)
    • 15:55-16:20 UTC: Aerospace (Matthew Weber, The Boeing Company)
    • 16:20-16:45 UTC: Space Grade Linux (Ramon Roche, The Linux Foundation)
    • 16:45-17:00 UTC Closing and final thoughts (Philipp Ahmann, ETAS)

[Skipped] Survey/Research about Quality of Open Source

  • 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.

Short status from WGs

Up to 3 bullet points

AoB

Announcements

Topics for seminar series

Upcoming events

  • 31 Jan - 01 Feb: FOSDEM
  • 10-12 Mar: Embedded World
  • 29-30 Apr: Safe.tech TÜV
  • 18-20 May: OSS NA

Remarks

Collaborative editing: https://semestriel.framapad.org/p/elisa-tsc-minutes