Skip to content

Minutes 06 02 2025

Paul Albertella edited this page Feb 6, 2025 · 2 revisions

Host: Paul Albertella

Participants: Pete Brink, Igor Stoppa, Florian Wuehr, Sebastian Hetze, Daniel Krippner, Naga Gamidi

Agenda

Discussion

Working Group Update

Accomplishments

  • Igor’s various contributions were added to the repo
  • Establish a set of expectations about how an open source project can contribute towards the evidence an application needs to support arguments about the integrating system’s properties (safety, security, quality)
  • Specifically, can we identify design limitations or unspecified / uncontrolled characteristics that need to be addressed or considered when planning to use Linux in a safety application?
    • Modelling a potential fault and its impact on a system to illustrate this
    • Allows us to consider ways to control these or mitigate their effects
  • Addressing these limitations requires either a change in the software itself, or a mitigation in the integrating system (prevent, detect, react)
  • Feasibility of addressing these issues is affected by the complexity of the solution, or the size of the target (what needs to be monitored) or the ‘analytical surface’ (what needs to be analysed in order to design an effective solution)
  • Approach for publishing peer-reviewed material as web content rather than git repo

Plan for this year

  • Publish some peer-reviewed material
  • Write more material
  • Write short explanation of agreed approach within working group
    • To invite input from others

Collaboration opportunities

Planned document status updates

  • Guidance for reviewing documents published by ELISA (Pete)
    • Using “Specification Quality Control” paper by Tom Gilb as a source of inspiration ( link )
    • Writing up some criteria for us to consider (or recommend)
    • Aiming for end of Feb for a first draft
  • Supply chain models & roles for products involving FOSS (Daniel)
    • No news
  • Linux Memory Management Essentials (Igor)
  • Using Linux in a Safe System (Igor)
  • ARM64 interference scenarios
    • Some progress (Paul did some reviews)
    • Numbered paragraphs to aid reference - @Paul to look at numbering headers
  • Proven In Use (Sebastian)
    • Low priority at the moment

Standards Atlas

  • Interest from Aerospace WG

FOSDEM

  • Trustable Software Framework
    • Paul to talk about this in future (he is deeply involved)
    • See docs and project for more information
  • Some talks about community processes, CRA may have some overlap
    • Sebastian has been involved in CRA discussions, so can talk about it
Clone this wiki locally