Skip to content

2025‐10‐22

Jump to bottom
Philipp Ahmann edited this page Oct 22, 2025 · 4 revisions

Roll call

** indicates TSC voting members*

Host

  • *Philipp Ahmann

Attended this meeting

  • *Alessandro Carminati
  • *Gabriele Paoloni
  • Pete Brink
  • *Olivier Charrier
  • *Sudip Mukherjee
  • Jaylin Yu
  • *Luigi Pellecchia
  • *Matt Weber

Regrets

  • *Kate Stewart
  • *Nicole Pappler

Attended recently in the past

  • Justin Stanley
  • *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

Topics & Notes

Check past action items

  • Action items in github issues
  • AI: TSC repo cleanup needed including issues
    • First PRs and tickets closed or updated. Work continues
  • 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.

ELISA November Workshop at Red Hat in Munich

  • Registration still open. See: https://elisa.tech/event/elisa-workshop-munich-2025/
  • Currently 25 in person registrations and roughly 10 in-person seats left.
  • A bunch of new names among registrants
  • Ask Nicole if there is a good restaurant for the workshop dinner on first evening.

Tools WG chair

  • Any good candidates or volunteers?
  • There is a pending discussion on how to cross connect tools and how to create a demo around it. This is a good argument to keep an alignment meeting.
  • Currently meeting is every 14 days.
  • Discussions about specific tools can be also taken offline on GitHub or Discord.
  • For demos aligning during a dedicated meeting, this can be useful.
  • No constant flow of one thing or thread that ties the tools together, but changing topics
  • Align on Discord via Tools-WG channel and have meetings on demand.
  • Demos can be a clear scope, or promotion of existing tools can be a topic, but it definitely needs a clear statement what it is meant for and what not. This should be clarified before starting the working group again. This will be helpful for potential participants and what they can expect.
    • https://lists.elisa.tech/g/tool-investigation
    • Current description: "The Tool Investigation and Code Improvement WG focuses on application of tools, handling the tool results, and improving the kernel based on the tools' feedback."
  • Also it is important to look at the operation of tools to fulfill requirements demanded by standards, like ISO 26262 is demanding "Tool Qualification".
  • From the original scope the tools used were good to identify issues, and get fixes integrated into the Linux kernel. By this the original scope was fulfilled and the group could evolve.
    • Nowadays also maintainers focus on concrete bugs rather than Static Analysis fixes seen as "not real bugs".
  • Would KernelCI features enhancements (especially on safety topics) something to be taken into this group?
  • What other tools exist which can help? Investigation on this is useful.
  • Next step:
    • Update Tools repo landing page via PR to give a link to the Tools WG discord channel.
    • @Min we also need to update the contact on https://lists.elisa.tech/g/tool-investigation to point to discord
    • Cancel next two meetings
    • Use Discord to discuss the scope and see who is interested.
    • Create a shared text document to consolidate the ideas.
    • When there is a common sense reach out to community and public to look for new lead.

Renewal of TSC members and TSC chair

  • Working group chairs always are part of the TSC as long as they lead a working group.
    • In the past the people proactively stepped away from the TSC.
  • TSC chair will still be voted out of the TSC members.
  • People self nominate (or get nominated by a TSC member who cross checked interest by that person before)
  • WG leads do not have to nominate themselves.
  • Others send mail on the devel mailing list.
  • Working Group chairs have a special role as TSC members and are those who are eligible vote on participants in TSC
  • Annual election with terms from January to December.
  • TSC chair nomination follows early January after TSC member nomination.

[Skipped] Usage of AI in the Linux Kernel development process

  • See notes from last meeting for first discussion.
  • Blog draft: https://docs.google.com/document/d/1jUfVfmLfmXhLzU3834G0kS0Z5Fjn_kKSnwhCeZcHSSI
    • Could be published as a blog post, but would need to get through the review
  • Topic for Linux plumbers (after patch submission by Justin et al.)
    • Justin: "Automating Linux Kernel Documentation using AI" got accepted at Plumbers. A good topic to discuss and exhance within ELISA community in Japan.
  • Continue in next TSC

[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

  • Cancel next TSC meeting on Oct 29th due to LF Europe Member Summit.
  • ELISA will have a project table at the LF Europe member summit on October 28th.

Announcements

Topics for seminar series

Upcoming events

  • 28 Oct - ELISA Table at LF Europe Member Summit
  • 18-20 Nov - ELISA Workshop
  • 08-10 Dec - Open Source Summit Japan
  • 11-12 Dec - Linux Plumbers

Remarks

Collaborative editing: https://mensuel.framapad.org/p/elisa-tsc-minutes-a9tp?lang=en

Clone this wiki locally