Skip to content

Commit 1ca12fd

Browse files
cpetigChristofPetig
cpetig
and
ChristofPetig
authored
coding guidelines minutes 2026-07-15 (#703)
Co-authored-by: Christof Petig <christof.petig@aptiv.com>
1 parent 042ac5a commit 1ca12fd

1 file changed

Lines changed: 93 additions & 0 deletions

File tree

  • subcommittee/coding-guidelines/meetings/2026-07-15

‎subcommittee/coding-guidelines/meetings/2026-07-15/minutes.md‎

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
# **Coding Guidelines Subcommittee Meeting on 2026-07-15 @ 1600 CEST / 1100 EDT**
2+
3+
[Link](https://www.worldtimebuddy.com/?qm=1&lid=5,12,2643743,8,1850147,100,14,14,1835848,1816670&h=5&date=2026-7-15&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/Safety-Critical-Rust-Consortium/safety-critical-rust-consortium/blob/main/subcommittee/coding-guidelines/meetings/2026-07-08/minutes.md)
15+
3. Introduction of new members
16+
4. Interest in the MISRA C++ mapping (mira / Pete)
17+
- Updates on new things in the MISRA C++ \=\> Rust mapping
18+
- In talks with MISRA folks still; but in practice the procedure outlined seemed reasonable to them
19+
- Please register interest on [this Zulip thread](https://rust-lang.zulipchat.com/#narrow/channel/579369-safety-critical-consortium.2Fcoding-guidelines/topic/MISRA.20C.2B.2B.20Mapping.20Interest/with/584764785)
20+
5. Working session: review feedback on the [CERT C to Rust coding guidelines mapping](https://coding-guidelines.arewesafetycriticalyet.org/appendices/standards-matrices/cert-c-2016-mapping.html)
21+
- Parent tracking issue: [\#336 Mapping of CERT C to Rust Guidelines](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/336)
22+
- Review batches: [1/5](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/427), [2/5](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/428), [3/5](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/429), [4/5](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/430), and [5/5](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/431)
23+
- The [2/5 batch](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/428) has the most as-yet unreviewed mappings, but some others have them here or there too.
24+
- Goal: work through review feedback, confirm or revise the proposed Rust categorization, and capture decisions and follow-up work in the relevant issues
25+
- **Group A \- first 7 rules from 2/5**
26+
- [https://meet.google.com/muk-bsjv-oke](https://meet.google.com/muk-bsjv-oke)
27+
- Group:
28+
1.
29+
- **Group B \- 4 last rules from 2/5 and 4/5**
30+
- [https://meet.google.com/svx-rtsv-izb](https://meet.google.com/svx-rtsv-izb)
31+
- Group:
32+
1.
33+
6. Round table
34+
35+
## **Check-in area**
36+
37+
- Mira Baumann 🌞
38+
- Daniel Dia 💾
39+
- Christof Petig 🤖
40+
- Samuel Wright 🐻
41+
- Alex Celeste ☕
42+
- William Barsse 🌡️
43+
- Achim Kriso 🦆
44+
- Markus Hosch🤯
45+
46+
**Notetaker:**
47+
48+
- Christof Petig
49+
50+
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.
51+
52+
## **Housekeeping section**
53+
54+
- Document space: [coding-guidelines](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/coding-guidelines)
55+
- Zulip: [safety-critical-consortium: Coding Guidelines](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Coding.20Guidelines)
56+
- [Kanban board](https://github.com/orgs/rustfoundation/projects/1/views/3)
57+
- [`contributor experience`](https://github.com/orgs/rustfoundation/projects/1/views/4) view
58+
- [`coding guideline`](https://github.com/orgs/rustfoundation/projects/1/views/5) view
59+
60+
## **Tasks**
61+
62+
- n.a.
63+
64+
## **Meeting Minutes**
65+
66+
- Meeting minutes were accepted with no objections
67+
- No new members on the call
68+
- Mira reported that there are four items left for grab on MISRA C++ mappings
69+
- One group will go for the first seven rules of 2/5, the other group for the last four of 2/5 and all three in ⅘
70+
- The second group was unable to join the sub-meeting without invitation from the organizer, so the group returned to the main meeting for the discussion
71+
- Subgroups returned to the main meeting.
72+
- Group 2 will create an issue with their comments which then can be linked from the review issue.
73+
- [https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/131](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/131)
74+
- [https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/pull/132/changes](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/pull/132/changes)
75+
-
76+
- Group 1: FIO39 is more unclear on how it is actually implemented in Rust
77+
- [https://doc.rust-lang.org/std/io/index.html\#io-safety](https://doc.rust-lang.org/std/io/index.html#io-safety) \- it feels like this might need some rule about file I/O
78+
- New issue [https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/428\#issuecomment-4982470186](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/428#issuecomment-4982470186)
79+
- Roundtable:
80+
- Do we want to recommend the format for justification for required rules?
81+
- MISRA 2020 has guidance on these
82+
- Standardizing on the existence of a reason field for required rules feels like consensus, but the contents of the field are left to the implementer
83+
84+
## **Material**
85+
86+
Any material to read before the meeting should be included here.
87+
88+
Overview of [Safety-Critical Rust](https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html) Rust Project Goals Roadmap (Pete)
89+
90+
- Soliciting those interested in [Normative Documentation for Sound unsafe Rust](https://rust-lang.github.io/rust-project-goals/2026/safe-unsafe-for-safety-critical.html) goal
91+
- Register interest [here](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/SCRC.20.3C.3D.3E.20t-opsem.3A.20Normative.20Documentation.20for.20Sound.20.60unsafe.60/with/586198564) on Rust Zulip
92+
- Soliciting those interested in [Establish a Spot for Safety-Critical Lints in Clippy](https://rust-lang.github.io/rust-project-goals/2026/safety-critical-lints-in-clippy.html) goal
93+
- Register interest [here](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Getting.20involved.20with.20Clippy.20for.20SCRC.20lints/with/583090116) on Rust Zulip

0 commit comments

Comments
 (0)