-
Notifications
You must be signed in to change notification settings - Fork 3
Aug 14, 2024 ‐ 15:00 UTC
Philipp Ahmann edited this page Aug 26, 2024
·
8 revisions
Note: Meeting took place August 12th. Kept wrong subject to maintain link history and tracking.
Host:
- Philipp Ahmann
Participants:
- Alfred Strauch
- Steven Carbno
- Karen Bennet
- Nicole Pappler
Regrets:
- ...
Attended Recently
- Guy Lunardi
- Andreas Bartelt
- Thomas Mittelstädt
- Stewart Hildebrand
- Kate Stewart
- Olivier Charrier
- Walt Miner
- Daniel Weingaertner
- Axel
- ...
- Draft
- Conclusion from last meeting: Bring the "objective of proposal" forward so that it can form a base for "whatever kind of funding/financing".
- Related paper: Open source software development process: A systematic review
- Recent discussions inside ELISA
- We should check which good practices regarding quality and OSS already exist.
- We recent standards are under preparation for quality management of software (hardware or systems) taking into account CI/CD practices
- Have a clear goal on what we want to achieve with "a new standard".
- Most QM systems are start with formal requirements where Open Source is different and also modern CI/CD driven SW development often starts with code.
- Artifacts are hardly visible and the process is not fully formally described (mainly how-tos)
- This also relates to the Safe Systems with Linux MC at Linux Plumbers
- In self driving car space they feed accident/incident reports and let AI prepare regression tests. Can this be something also for open source?
- This may also need to create a requirement out of the reports.
- The issues for functional safety is essence of the discussion. How can you say something is good or sufficient?
- What is quality practices and what is quality? How is the relationship between safety and quality?
- Is there a way to define a threshold for good enough? At the end even the assessor is seeing numbers, but only has confidence and not a number saying "good enough".
- Can it be easier to say what is insufficient? This may be far easier to say: If you don't meet this threshold it is clearly insufficient.
- The impact also defines the rigour which need to be taken and judge sufficiency/insufficiency
- Components and interaction of components makes the process also more complicated and how does a continuous validation process look for a single and for a set of components.
- This topic is explicitly interesting for product developers and integrators/distributors.
- Distributed systems add another dimension to the complexity.
- It can also be a moving target when phrasing a standard or best practices and measuring the "good enough" state.
- Above points can be integrated in the motivation to define a clear goal of the good practices standard.
- Karen may be able to share some references for papers also handling the topic.
- Karen Bennet: Works in automotive and with AI, brings interest with ISO & IEEE and where they do a lot of best practices.
- Dec 16, 2024
- Dec 02, 2024 - Eclipse SDV
- Nov 25, 2024
- Nov 18, 2024
- Nov 11, 2024
- Nov 04, 2024
- Oct 21, 2024
- Sep 30, 2024
- Sep 23, 2024
- Sep 02, 2024
- Aug 26, 2024
- Aug 12, 2024
- Aug 05, 2024
- Jul 08, 2024
- Jul 01, 2024
- Jun 24, 2024
- Jun 10, 2024
- May 27, 2024
- May 13, 2024
- Apr 29, 2024
- Apr 22, 2024 HBOM
- Apr 08, 2024
- Mar 18, 2024
- Mar 11, 2024
- Mar 04, 2024
- Feb 19, 2024
- Feb 12, 2024
- Jan 29, 2024
- Jan 22, 2024
- Jan 15, 2024
- Jan 08, 2024
2023 and earlier minutes
(still empty)