Skip to content

Commit 465ad1d

Browse files
MerrimanIndMerrimanInd
authored
Added minutes from Tooling subcommittee 2025-07-25 meeting (#379)
1 parent 341efc9 commit 465ad1d

1 file changed

Lines changed: 129 additions & 0 deletions

File tree

  • subcommittee/tooling/meetings/2025-07-25

‎subcommittee/tooling/meetings/2025-07-25/minutes.md‎

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
# Tooling Subcommittee Meeting on 25 July 2025 @ 4pm GMT
2+
3+
| Search Key | Description |
4+
|:------------- |:-------------------- |
5+
| \[todo\] | Action Item |
6+
| \[decision\] | Something decided on |
7+
| \[important\] | Key information |
8+
9+
## Agenda
10+
11+
1. Solicitation of notetaker
12+
13+
2. Review [last time’s meeting minutes](https://github.com/rustfoundation/safety-critical-rust-consortium/blob/main/subcommittee/tooling/meetings/2025-06-27/minutes.md)
14+
15+
3. Present new members
16+
17+
4. Chat about a first safety-critical standard which need be applied (Pete)
18+
19+
1. ISO 26262?
20+
2. DO 178C?
21+
3. Some sort of NASA standard?
22+
4. Rail safety critical?
23+
5. Who would like to lay out the path to safety-certify code and required tooling?
24+
25+
5. Chat about safety-critical tools to add to the database in support of ISO 26262 (Pete)
26+
27+
6. Review the initial procedure for submitting new tools \- [tooling new submission](https://docs.google.com/document/d/1hZGU5MCx_sb_8qEhww4l-KtLYyDNdQihQP7Tgtu4QSg/edit?tab=t.0) (Pete)
28+
29+
7. Update from Woven by Toyota on MC/DC support upstream (Pete)
30+
31+
1. [Why MC/DC?](https://hackmd.io/@i-aMA8ZOS92HAYpU8f_8eg/S1-KTICmee/edit)
32+
33+
2. [Notes](https://hackmd.io/@i-aMA8ZOS92HAYpU8f_8eg/rkIRw0wXlx/edit) of Woven by Toyota implementors
34+
35+
## Check-in area
36+
37+
**Please add your name, and an emoji that describes your day.**
38+
* Pete LeVasseur 🛬
39+
40+
* Xander Cesari 🪐
41+
42+
* Stephen Hedrick ⚡️
43+
44+
* Tiago Manczak
45+
46+
* Arnaud Fontaine 😀
47+
48+
* Oreste Bernardi
49+
**Notetaker:**
50+
51+
* Xander Cesari
52+
53+
## Housekeeping section
54+
55+
## Tasks
56+
57+
* See \[todo\] below ⏬
58+
59+
## Meeting Minutes
60+
61+
* Approving last meeting’s minutes
62+
63+
* SC Tooling Issue template was approved and merged
64+
* [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/337](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/337)
65+
* SC Tooling Request issue template is still open and in draft
66+
* [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/336](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/336)
67+
68+
* Following up on a discussion topic from last in-person meeting, we would like to look at the process of certifying software for a safety-critical standard and map out the tooling and standards required.
69+
70+
* Which standard to start with?
71+
* ISO-26262
72+
* DO-178C
73+
* Likely a very difficult standard to start with and not the first standard to adopt
74+
* We should pick the standard/industry where Rust is a first mover. Most likely automotive but if there’s an aero/space/defense standard that’s moving fast we should go there.
75+
* Who can start on this?
76+
* [Xander Cesari](mailto:xander.cesari@pictor.us) will be doing a similar project for some marketing efforts (running through a simulated cert process in Rust with some tooling) so about 60-80% of his work will likely overlap.
77+
* In standard ISO-26262 processes they don’t point to specific tools, the standard is process-oriented and this often drives specific tools or manual processes. So there are many paths to certification.
78+
* The process of certifying a tool itself for ISO-26262 is a further stretch goal, this should focus on the product focused process.
79+
* Artifact output will be a page on the website and in the writing of this page identify any gaps in the process.
80+
* Target ASIL D but highlight lower safety level requirements as well.
81+
* Oreste has some templates and documentation that may be publicly shareable.
82+
* Eclipse S-CORE may have some process documentation for using Rust in safety critical contexts. [tiago.manczak@infineon.com](mailto:tiago.manczak@infineon.com) to look for links and add them.
83+
* [https://github.com/eclipse-score](https://github.com/eclipse-score) \- main github repo
84+
* [https://eclipse-score.github.io/process\_description/main/process\_areas/tool\_management/index.html](https://eclipse-score.github.io/process_description/main/process_areas/tool_management/index.html) \- tool management process description
85+
* [https://eclipse-score.github.io/process\_description/main/process\_areas/tool\_management/guidance/tool\_management\_checklist.html](https://eclipse-score.github.io/process_description/main/process_areas/tool_management/guidance/tool_management_checklist.html) \- checklist (suggestion: we could prepare such checklist for the SCORE project for the tools we are listing)
86+
* Might be interesting to “upstream” some of these blueprints/processes to orgs like SOAFEE or Eclipse SDV after we develop them internally. This could use the Eclipse Trustable Software Framework.
87+
88+
* Who came with ideas for safety-critical tools to add to the database?
89+
90+
* Tools
91+
* Pete
92+
* TrustInSoft tool \- static analysis
93+
* HighTec Compiler
94+
* Kani
95+
* Arnaud
96+
* Ferrocene Compiler
97+
* Mantra requirement tracing
98+
* Verifast
99+
* creusot
100+
* Oreste
101+
* OpenFastTrace \- requirements tracing
102+
* Lautherbach debugger
103+
* UDE Pls debugger
104+
* Reqtify \- [https://www.3ds.com/products/catia/reqtify](https://www.3ds.com/products/catia/reqtify)
105+
* Stephen
106+
* Sphinx Needs \- requirements tracing
107+
* AdaCore GNAT Pro for Rust
108+
* Clippy
109+
* Xander
110+
* OxidOS RTOS \- OS / Libraries
111+
* [Rapita](https://www.adacore.com/press/rapita-embraces-rust-via-adacore-partnership)
112+
* OSS tooling
113+
* Cargo extensions (deny, audit, etc)?
114+
* Editor (Safety Evaluation as a part of the process is done. May not be included explicitly in DB, but could be highlighted as a step that need be done.)
115+
* RustRover
116+
* VSCode
117+
* ?
118+
* OS / libraries
119+
* OxidOS RTOS
120+
* Note that target audience for this website is existing safety-critical developers who know software and some SC processes but want to learn the state of the Rust ecosystem
121+
* Task: submit Github issue using the Tool template adding these tools to the database
122+
* [https://github.com/rustfoundation/safety-critical-rust-consortium/issues/new?template=submit\_tool.yml](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/new?template=submit_tool.yml)
123+
* Submitted an issue live to dogfood the process
124+
125+
* MC/DC at Woven by Toyota
126+
127+
* The Woven by Toyota team working on MC/DC was an internship program and they won’t be able to finish it in time. So they’re switching over to a project that’s completable in the scope of their internship. Most likely their work won’t get merged but they have some interesting work done.
128+
* There are still some interesting question marks in the Rust ecosystem about how Rust and MC/DC overlap.
129+
* This may be an opportunity for the Consortium to highlight the Rust MC/DC gap and try to find someone to continue the work.

0 commit comments

Comments
 (0)