-
Notifications
You must be signed in to change notification settings - Fork 11
Minutes 06 Mar 2025
Paul Albertella edited this page Mar 14, 2025
·
1 revision
Host: Paul Albertella
Participants: Pete Brink, Daniel Krippner, Mikel Azkarate, Gabiriele Paoloni, Florian Wuehr, Stephen Oresanya, Yana Hontyk
Agenda
- Updates on documents
- Trustable Software Framework
Discussion
Updates on documents
Pete: Review criteria
- Looking at existing examples of criteria, which can apply to any kind of document
- Might be a superset - not sure which of these may apply
- Paul: We may need to apply a subset for this
- Looking at metadata that we would want to see
- Describing a process, plus a checklist
- Not looking at it from a safety perspective - more quality
- Next step: Convert to markdown
Daniel: No progress to report
Igor: No progress to report
Trustable Software Framework
Paul presented about the TSF methodology.
This is public and open source in a temporary home on gitlab.com, but has been proposed as a project to the Eclipse Foundation (watch this space)
Questions:
- Q: How might this be useful if I want to satisfy some different objectives e.g. those of a safety standard?
- A: You can use Statements to capture the objectives of the standard and link these to statements in the TSF graph that satisfy them, or add new Statements to capture gaps
- Q: Are there any examples of this being applied?
- A: Not yet, but we plan to share sets of more specific statements to illustrate how the TA can be applied for the RAFIA methodology, and concrete criteria for managing Provenance, Construction and Changes using specific tools (e.g. GitLab, BuildStream). We will also be applying TSF to the public Safety Monitor project.