|
| 1 | +# Tooling Subcommittee Meeting on 27 March 2026 @ 3pm 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 | +2. Review last time’s meeting minutes [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/596](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/596) |
| 13 | +3. Present new members |
| 14 | +4. Tooling Task Force |
| 15 | + 1. Tooling PR for website [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578) |
| 16 | + 2. Categorization of tooling (e.g. mutest-rs) [https://github.com/rustfoundation/safety-critical-rust-consortium/issues/571](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/571) postpone for when Felix Fischer can be present |
| 17 | +5. Rust Project Bridge Task Force |
| 18 | + 1. Updates from Rust Project [Safety-Critical Rust Roadmap](https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html) |
| 19 | + |
| 20 | +## Check-in area |
| 21 | + |
| 22 | +**Please add your name, and an emoji that describes your day.** |
| 23 | + |
| 24 | +* Alexandru Radovici 😀 |
| 25 | +* Arnaud Riess 👨🏼💻 |
| 26 | +* Pete LeVasseur 🏢 |
| 27 | +* Manuel Hatzl |
| 28 | +* Tony Aiello |
| 29 | +* Zalán Bálint Lévai 😀 |
| 30 | +* Stefan Akatyschew 🚄 |
| 31 | +* Tiago Manczak |
| 32 | +* Kartik Ohlan |
| 33 | + |
| 34 | + **Notetaker:** |
| 35 | + |
| 36 | +* Pete LeVasseur 📓✍️ |
| 37 | + |
| 38 | +## Housekeeping section |
| 39 | + |
| 40 | +## Tasks |
| 41 | + |
| 42 | +* xx |
| 43 | + |
| 44 | +## Meeting Minutes |
| 45 | + |
| 46 | +* Approved meeting notes from last time, merged |
| 47 | +* New member \- none new this time |
| 48 | +* Tooling Task Force |
| 49 | + * Tooling PR for website: [rendered preview](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578) |
| 50 | + * Migrated tooling list from YAML to JSON to make this easier to integrate with docusaurus |
| 51 | + * Might need to be rebased onto main |
| 52 | + * Forced line breaks for the SIL ones could be nice |
| 53 | + * Categories for tools could be nice to jump to and read about easily (e.g. testing) |
| 54 | + * \[todo\] @Everyone \- let’s all go leave comments on the PR |
| 55 | + * \[todo\] If not all are left Alexandru will go do this |
| 56 | + * Licensing of compilers \- claiming of these as being e.g. non OSS-friendly licenses could go the wrong way |
| 57 | + * Example workflow \- pull from upstream, apply patches; don’t change the license; cannot change the license; when compiler is delivered as compiled binary it’s also delivered with source |
| 58 | + * “Additional files” \- depends on category; if useful upstream will be upstreamed. “Raise everything to Tier 1, using Rust Project terminology” and those licenses are kept permissive for OSS and Commercial both |
| 59 | + * Categorization of tooling (e.g. mutest-rs) |
| 60 | + * [Discussion](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/571) on-going on how to best split up tooling categories on GitHub |
| 61 | + * Bringing it here to discuss |
| 62 | + * Testing |
| 63 | + * Profiling |
| 64 | + * Compiler |
| 65 | + * ... and so on |
| 66 | + * Formal verification itself may be wide enough and worthwhile to make that its own category |
| 67 | + * \[todo\] Manuel and Felix to discuss offline, draft up PR |
| 68 | + * Mutest could be mentioned to in the ISO 26262 gap analysis at 6-10 as 1c \- fault injection, PR will be sent for feedback |
| 69 | +* Rust Project Task Force |
| 70 | + * We have some defined Rust Goals for MC/DC \- [https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html](https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html) |
| 71 | + * Niko added the ability to track future road maps for Rust |
| 72 | + * We could add to those |
| 73 | + * \[todo\] [plevasseur@gmail.com](mailto:plevasseur@gmail.com)and [Alexandru Radovici](mailto:alexandru.radovici@oxidos.io) go through the survey results to find new goals |
| 74 | + * \[todo\] [plevasseur@gmail.com](mailto:plevasseur@gmail.com)link analysis page to the tooling page |
| 75 | + * \[todo\] We would need people to write safety critical clippy lints as a part of one of the goals |
| 76 | +* Meeting |
| 77 | + * In the face to face meeting, we would like to have more spntaneuty |
| 78 | + * morning will be structured |
| 79 | + * Afternoon \- unconference style |
0 commit comments