|
| 1 | +# **Coding Guidelines Subcommittee Meeting on 2026-03-11 @ 1600 CET / 1100 EDT** |
| 2 | + |
| 3 | +[Link](https://www.worldtimebuddy.com/?qm=1&lid=5,12,2643743,8,1850147,100,14&h=5&date=2026-3-11&sln=11-12&hf=1) to meeting time in common time zones. |
| 4 | + |
| 5 | +| Search Key | Description | |
| 6 | +| :---- | :---- | |
| 7 | +| \[todo\] | Action Item | |
| 8 | +| \[decision\] | Something decided on | |
| 9 | +| \[important\] | Key information | |
| 10 | + |
| 11 | +## **Agenda** |
| 12 | + |
| 13 | +1. Solicitation of notetaker |
| 14 | +2. Acceptance of [Previous Meeting Minutes](https://github.com/rustfoundation/safety-critical-rust-consortium/blob/main/subcommittee/coding-guidelines/meetings/2026-03-04/minutes.md) |
| 15 | +3. Introduction of new members |
| 16 | +4. CERT C \=\> Rust Mapping (Félix / David / Jubilee) |
| 17 | + * WIPs are resolved\! |
| 18 | +5. Coverage of MISRA C and CERT C in 2026 (Félix / Markus) |
| 19 | + * i.e. “create a table” and “create corresponding issues” |
| 20 | +6. Proposals and ideas for new rules (all) |
| 21 | +7. Progress on ongoing tasks (all) |
| 22 | +8. Round table |
| 23 | + |
| 24 | +## **Check-in area** |
| 25 | + |
| 26 | +* Pete LeVasseur 🦀🏃 |
| 27 | +* Douglas Deslauriers ⛷️ |
| 28 | +* Oreste Bernardi 🥷 |
| 29 | +* Markus Hosch 🫥 |
| 30 | +* Félix Fischer :) |
| 31 | +* Julius Gustavsson 🙂 |
| 32 | + |
| 33 | +**Please add your name, and an emoji that describes your day.** |
| 34 | + |
| 35 | +**Notetaker:** |
| 36 | + |
| 37 | +* Douglas Deslauriers |
| 38 | + |
| 39 | +For tips on how we take notes in the Safety-Critical Rust Consortium, please see the [Meeting Notetaker Role](https://github.com/rustfoundation/safety-critical-rust-consortium/blob/main/docs/notetaker-role.md) doc. |
| 40 | + |
| 41 | +## **Housekeeping section** |
| 42 | + |
| 43 | +* Document space: [coding-guidelines](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/coding-guidelines) |
| 44 | +* Zulip: [safety-critical-consortium: Coding Guidelines](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Coding.20Guidelines) |
| 45 | +* [Kanban board](https://github.com/orgs/rustfoundation/projects/1/views/3) |
| 46 | + * [`contributor experience`](https://github.com/orgs/rustfoundation/projects/1/views/4) view |
| 47 | + * [`coding guideline`](https://github.com/orgs/rustfoundation/projects/1/views/5) view |
| 48 | + |
| 49 | +## **Tasks** |
| 50 | + |
| 51 | +* \[Pete\] Use the review bot to assign producers to chunks of CERT C mapping rationales |
| 52 | +* \[Markus\] Open a PR for a MISRA C mapping in a separate appendix file |
| 53 | +* \[Félix\] Open a PR for the CERT C mapping in a separate appendix file |
| 54 | + |
| 55 | +## **Meeting Minutes** |
| 56 | + |
| 57 | +* Previous meeting minutes |
| 58 | + * Unanimous acceptance |
| 59 | +* CERT C \=\> Rust Mapping |
| 60 | + * First step in the process can be considered completed |
| 61 | + * A preliminary mapping has been created for |
| 62 | + 1. Rules that do NOT map to Rust |
| 63 | + 2. Rules that do map to safe Rust |
| 64 | + 3. Rules that map to unsafe Rust |
| 65 | + 4. Unsure if it maps |
| 66 | + * This mapping will add legitimacy to our guidelines, since safety critical assessors are already familiar with MISRA and CERT C |
| 67 | + * All CERT C rules have been reviewed, and have been sorted \[important\] |
| 68 | + * A request to review rationale for the entire table in the [Github issue \#336](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/336) has been made |
| 69 | + 1. The rules will be chunked and assigned with the bot \[todo\] |
| 70 | + 2. The reviews will occur and be placed in the issue |
| 71 | + * It was noted that the rationale for many mapping references Zulip, and a published document should embed the quotations or information directly |
| 72 | + * Most rationale for the mappings are quite short, especially for rules that do not map |
| 73 | + * The (much) longer rationales could be separated from the table, and just contain a short sentence with a link or footnote |
| 74 | + * Proposed placing the mappings in the Appendix \[decision\] |
| 75 | +* Round Table |
| 76 | + * Time could be used during meeting for detailed discussions on existing Github issues |
| 77 | + |
| 78 | +## **Material** |
| 79 | + |
| 80 | +Any material to read before the meeting should be included here. |
| 81 | + |
| 82 | +* Milestone: [Prepare for launch to wider Rust community](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/milestone/1) |
| 83 | + |
0 commit comments