Skip to content

22 Jan 2025

Philipp Ahmann edited this page Jan 22, 2025 · 3 revisions

Roll call

** indicates TSC voting members*

Host

  • *Philipp Ahmann

Attended this meeting

  • Sebastian Hetze
  • Pierre Brangier
  • *Alessandro Carminati
  • *Gabriele Paoloni
  • *Igor Stoppa
  • *Matthew Weber
  • *Nicole Pappler
  • *Olivier Charrier
  • Pete Brink
  • *Paul Albertella
  • *Kate Stewart

Regrets

Attended recently in the past

  • *Christopher Temple
  • *Matt Kelly
  • Michael Mahoney
  • Jaylin
  • Naresh Ravuri
  • Elana Copperman
  • *Sudip Mukherjee
  • *Lukas Bulwahn
  • Steve VanderLeest
  • Youssef Hajjioui
  • JE[A]Y
  • Vipul Gupta
  • Qasim

Topics & Notes

Check past action items

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

ELISA Annual Virtual WG Updates

Goddard Workshop re-cap

  • Stats: ~30 attended in person ~40 virtually, 18 sessions, 20+ speakers, 40 survey responses
  • Philipp gave an overview of attendee survey results
  • For future workshop: Where do technology applies and what does it mean for functional safety? To which criticality level it does apply (is it level A or E)? Put the talks into context to standards.
  • Having also metrics to where does the talk fit to like which space grade or DO-178 or ISO-26262.
  • Lot of stuff presented was on non-human space flight.
  • Blog post will go live today!
  • YouTube playlist link: https://www.youtube.com/playlist?list=PLuDNrzTpK8zqUX6OEuh2hEz3vmqyjlwYu

Directory is setup

  • https://github.com/elisa-tech/directory is prepared
  • first content is live
  • Thanks to Paul for guiding us through GitHub Actions setup.
  • When you start to use GitHub pages for results in your working group, remember to put a link to the directory in the Content overview.

License to use for code contributions

  • License setting for working groups repos.
  • Documentation is considered as CC-BY-4.0 as per project charter.
  • Do we need to extend the existing default "GPL-2.0-only" for code repos? (May result in project charter update)
  • From SGL / AeroWG discussions (bullets from Matt Weber)
  • The project charter states: "If an exception using an OSI-approved license is approved, it must be documented within the “LICENSE” file within the ELISA Project’s code repository (the “Project License”)"
    • Proposal is to use MIT license for SGL and AeroWG repo.
    • TSC voting members approve the MIT license use.

standards-atlas introduction (by Sebastian Hetze)

  • https://github.com/shetze/standards-atlas
  • A tool useful for ELISA members?
  • Question the tool wants to address: How to travel between domains from different industries? What do they have in common and how do they correlate?
  • v-model and lifecycle phases are some similarities.
  • Bring standards into markdown and narrow them down to get them into doorstop. Doorstop creates yaml/html documents with links to trace them.
  • Not limited to functional safety.
  • Whenever you enter a standard into the tool make sure you have the approval from the issuing authority like IEC or ISO.
  • For in depth discussion and analysis you need to be of possesion of the respective standard(s) with their wording. Without wording of the standard it is not really convenient. The links from one to another standard are still visible and you can navigate between documents (but on heading level and not context).
  • The tool does not have a chat interface to an LLM directly, but there is an interface to the LLM.
    • (An idea could be to let an assessor talk to the AI model directly, but to show that the LLM is correct is also hard to proof.)

Requirements within the Kernel (skipped)

Minimal Kernel Config Updates (skipped)

  • ...

Optional: Short status from WGs - Skipped

Up to 3 bullet points

  • Aerospace/Space
    • Navigating content licensing as development is ramping up (SGL and Aero) - https://github.com/elisa-tech/meta-sgl/pull/1
    • Kicked off an Aero use case demo wkly call in mid-Jan to develop https://github.com/elisa-tech/wg-aerospace/tree/main/demos/copilot (Ivan Perez , Martin Halle, Paul Mani and Matt Weber)
    • Working with Sudip on CICD options for the project (some combo of Gitlab/Github)
    • Split into a Aerospace focused call early in the month and SGL mid month
    • Michael Monaghan and Matt Weber are presenting at the Flight Software Workshop 24th-27th March
      • "Making Penguins Fly" - objectives, challenges, and developments of the ELISA foundation's Aerospace and Space Grade Linux working group (WG.) The presentation will include specific topics from a Dec 10-12 Goddard Space Flight Center workshop.
    • SGL discussing meta layer with flight software example/demo configurations "quick start mindset" with targeted devkits
    • Lingering need is to publish a safety standards matrix to help people navigate the content presented/share
  • Automotive
  • Medical
  • Arch
  • Linux Features
  • OSEP
  • Tools
  • Systems

AoB

  • Some talks around Safety (e.g. by Codethink) at FOSDEM, some also from ELISA community like from Luigi Pellecchia, Nicole Pappler, Kate Stewart.
  • Pierre Brangier (Microchips): FuSa Manager for HW and have a few SW tools.

Announcements

Topics for seminar series

  • 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

Upcoming events

  • 01-02 Feb Fosdem in Brussels (Belgium)
  • e/o Feb AGL AMM Tokyo
  • 11-13 Mar Embedded World Nurenburg
  • LF Member summit

Remarks

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