27 Nov 2024 - elisa-tech/tsc GitHub Wiki

Roll call

** indicates TSC voting members*

Host

• *Philipp Ahmann

Attended this meeting

• *Igor Stoppa
• *Paul Albertella
• *Alessandro Carminati
• *Olivier Charrier
• *Christopher Temple
• *Gabriele Paoloni
• Qasim

Regrets

*Kate Stewart *Nicole Pappler

Attended recently in the past

• *Olivier Charrier
• *Alessandro Carminati
• *Gabriele Paoloni
• Naresh Ravuri
• *Nicole Pappler
• *Matt Kelly
• *Kate Stewart
• *Igor Stoppa
• *Matt Weber
• Elana Copperman
• *Sudip Mukherjee
• *Paul Albertella
• Pete Brink
• *Lukas Bulwahn
• *Christopher Temple
• Steve VanderLeest
• Youssef Hajjioui
• JE[A]Y
• Vipul Gupta

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

TSC chair 2025

• Philipp is confirmed as a TSC Chair for another year

ELISA Workshop at NASA Goddard

• Location: Goddard Space Flight Center https://maps.app.goo.gl/NoVcCPoSEk38ardU6
• Registration open: https://elisa.tech/event/elisa-workshop-at-at-nasa-goddard-space-grade-linux/
• Remaining issue is timing of the site tour. -> May cause changes in the schedule for day 1
• Virtual on second day!
  • Recording is not decided yet
• First and 3rd day no virtual participation planned.
  • Workshop material for knowledge base to be clarified with speakers from that days.
• We also need to clarify with the participants in case we are not recording and sharing, as the presenter may expect that everything is shared and published.
  • We will make it clear for future events.
    • We also need to make clear that this is a "member event" with invited guests/speakers which may limit material distribution.
• AI: Philipp will make sure to check with the speakers at the workshop if they want their material to be published or not (expectation is "slides sharing is okay")

ELISA result database [cont.]

• Publish an index of previous workshop presentations
• https://github.com/elisa-tech/wg-osep/issues/41
• https://github.com/elisa-tech/wg-osep/pull/46
• https://github.com/elisa-tech/wg-osep/pull/49
• We need to get review guidelines established.
• Should we have something for each working group or do we publish everything in one.
  • We can have WG sub domains as well as a central ELISA one
  • ELISA one could include TSC reviewed content.
    • This is similar to how we did for whitepaper
  • We get a "who approved this" in the github and have publish documentation or put the approvers in the merge commit.
    • Have a link back from the documentation to the PR can improve trace to the approvers and review process.
• Some things are technical related, others are closer to safety processes and standards
  • This may require different teams to review content.
• Approval means: I have been through the checks (review criteria) and bring sufficient skills to judge against the review criteria.
• Request to TSC members who have workshop material to share: Plese submit a PR or provide link to presentations which can be published so that a PR is created for you.
  • Also, review the content upfront according to the checklist where possible ;)
• Add a link to the knowledge base from workshops here: https://elisa.tech/workshop-series/
• Add a link to the general knowledge base under Resources as "Knowledge Base"
  • Create a general
  • This can be a topic also for the ambassadors meeting
  • We need to brin also other topics forward like the good practices proposal, systems WG sytem composition, Aerospace use case analysis. (Once content is stable and "ready to publish")
• Have a single github project with an index, which links to the various WGs

Publishing of (individual) results [cont.]

• Review and publish 'Contributions' material as 'official' ELISA guidance
• https://github.com/elisa-tech/wg-osep/issues/40
• Get a more coherent way and how we get excellent work discoverable by others.
• Results could be made better available with the right linking and forum.
• Fits to previous topics "result database" and will join these topics for the next meeting.
• https://github.com/elisa-tech/Safety_Architecture_WG/blob/main/Kernel_Documentation/Evaluating_and_improving_the_Linux_Kernel_documentation.md
  • Should we publish these results which are intermediate
  • Publishing is good. It can help to create contribution.
  • Stages
    • Documentation in repo
    • Published as github pages
    • On ELISA website.
• Discuss next time about an index project in GitHub linking to different content in repos or on github pages.
• Note: The content is already there, people can just not find it. We can provide more content on how to judge this.

Requirements within the Kernel - Skipped

• ...

Optional: Short status from WGs - Skipped

Up to 3 bullet points

• Aerospace/Space
• Automotive
• Medical
• Arch
• Linux Features
• OSEP
• Tools
• Systems

AoB

• Call for participation in preparation for OSS good practices
  • Working with LF Europe to come to a press release to get more participation
  • Maybe a topic for the Joint Development Foundation (tbd.)
• **Next TSC Meeting will be December 18th **

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 next year:
• ELISA user story by a company.
• Julia Lawall about formal verification (derived from Lund Linux Con presentation

Upcoming events

• 10-12 Dec ELISA Workshop at Nasa (Washington DC, US)
• 01-02 Feb Fosdem in Brussels (Belgium)

Remarks

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