Skip to content

Commit a0569a4

Browse files
pellicoPLeVasseur
pellico
and
PLeVasseur
authored
Added 24-06-2026 Coding guidelines meeting minutes (#698)
* Added 24-06-2026 Coding guidelines meeting minutes * Remove blank lines for attendees Co-authored-by: Pete LeVasseur <plevasseur@gmail.com> --------- Co-authored-by: pellico <pellico@users.noreply.github.com> Co-authored-by: Pete LeVasseur <plevasseur@gmail.com>
1 parent aa89ff8 commit a0569a4

1 file changed

Lines changed: 126 additions & 0 deletions

File tree

  • subcommittee/coding-guidelines/meetings/2026-06-24

‎subcommittee/coding-guidelines/meetings/2026-06-24/minutes.md‎

Lines changed: 126 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
# **Coding Guidelines Subcommittee Meeting on 2026-06-24 @ 1600 CEST / 1100 EDT**
2+
3+
[Link](https://www.worldtimebuddy.com/?qm=1&lid=5,12,2643743,8,1850147,100,14,14,1835848&h=5&date=2026-6-24&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-06-17/minutes.md)
15+
3. Introduction of new members
16+
4. Solicit availability for RustConf 2026 SCRC Room (Pete)
17+
- Please put availability on this [LettuceMeet](https://lettucemeet.com/l/oYlvM)
18+
5. The SCRC as a member organization of the Rust Commercial Network (RCN)
19+
- [RFC PR](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-consortium-rfcs/pull/8)
20+
- RCN announcement goes out today with the SCRC as a founding member organization
21+
6. Draft document for usage of standards documents
22+
- Current draft: [Usage Terms of Standards Documents](https://docs.google.com/document/d/1ctOOMA81slp8N4Sja_FmeDLaneEmtyIplL9EtYilM3s/edit?usp=sharing)
23+
- Located in the publicly accessible folder on the SCRC Google Drive: [Standards Documents](https://drive.google.com/drive/folders/1fgcca7tbpc0iLoZf1AQR_v9Kh51rungp?usp=drive_link)
24+
- How do we feel about these? Suggestions?
25+
7. Discuss possible 2-3 coding guidelines to choose for Clippy lints (Pete)
26+
- How've we done in looking into these?
27+
8. First version of MISRA C \+ CERT C Appendices [live](https://coding-guidelines.arewesafetycriticalyet.org/appendices/standards-matrices/index.html)
28+
- Pete *must still* mine these appendices for creating issues for contributors
29+
9. Safety-Critical Rust: Items of Shared Value for Fund Pooling (Pete)
30+
- One of the action items Pete took from the SCRC Room at RustWeek 2026
31+
- Things seem to be heating up with the formation of the Rust Foundation Maintainers Fund (RFMF) and Ecosystem Fund and the Funding Team. Would be good to make sure we make our needs and requests obvious and clear.
32+
- Pete will screen share and show the draft and then share it afterwards for feedback
33+
- Would we like to form up a working group temporarily to get this in good shape?
34+
- A first (0th?) draft document is available here: [Safety-Critical Rust - Items of Shared Value for Fund Pooling](https://docs.google.com/document/d/1E39cNTjK-5azCeWWFWS1jORsz9nqzMs4CNa6Rm68jV4/edit?usp=sharing)
35+
10. Interest in the MISRA C++ mapping (mira / Pete)
36+
- Updates on new things in the MISRA C++ \=\> Rust mapping
37+
- In talks with MISRA folks still; but in practice the procedure outlined seemed reasonable to them
38+
- 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)
39+
11. Review batches for [CERT C Rust Mapping](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/336) (Pete)
40+
- Let's split up again, to get some feedback on batch 2
41+
- [428 \[CERT C Review Batch 2/5\] Review proposed Rust categorization](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/428)
42+
- **Group A**
43+
- xx
44+
- **Group B**
45+
- Xx
46+
12. Round table
47+
48+
## **Check-in area**
49+
50+
- Mira Baumann 🤧
51+
- Michael Henn 🥵
52+
- Julius Gustavsson
53+
- Pete LeVasseur 🏃
54+
- Oreste Bernardi ☀️
55+
- Max Jacinto 😵‍💫
56+
- Tshepang Mbambo 👍
57+
- Christof Petig 🌡️
58+
- Kangwon Lee ✈️
59+
- Andreas Weis 🥵
60+
61+
**Notetaker:**
62+
63+
- Oreste Bernardi
64+
65+
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.
66+
67+
## **Housekeeping section**
68+
69+
- Document space: [coding-guidelines](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/coding-guidelines)
70+
- Zulip: [safety-critical-consortium: Coding Guidelines](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Coding.20Guidelines)
71+
- [Kanban board](https://github.com/orgs/rustfoundation/projects/1/views/3)
72+
- [`contributor experience`](https://github.com/orgs/rustfoundation/projects/1/views/4) view
73+
- [`coding guideline`](https://github.com/orgs/rustfoundation/projects/1/views/5) view
74+
75+
## **Tasks**
76+
77+
- xx
78+
79+
## **Meeting Minutes**
80+
81+
- Previous meeting notes are approved
82+
- AdaCore agreed to sponsor RustConf safety critical consortium room.
83+
- Requested to register participation
84+
-
85+
86+
## **Material**
87+
88+
Any material to read before the meeting should be included here.
89+
90+
Overview of [Safety-Critical Rust](https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html) Rust Project Goals Roadmap (Pete)
91+
92+
- 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
93+
- 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
94+
- 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
95+
- 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
96+
- SCRC as a member organization of the Rust Commercial Network (RCN)
97+
- Asked to give feedback at [https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-consortium-rfcs/pull/8](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-consortium-rfcs/pull/8)
98+
- No change in government in SCRC. Code Conduct, Bylaws …. will not change.
99+
- Draft document for usage of standards documents
100+
- Draft available with rules about standard use.
101+
- Requested review
102+
- Standards will be not publicly available. Access shall be granted and they can be read but not downloaded.
103+
- First version of MISRA C \+ CERT C
104+
- Appendixes are live.
105+
- Provided to Toyota for internal use.
106+
- Interest in the MISRA C++ mapping
107+
- Question if FFI guidelines shall be considered or not.
108+
1. Proposed to handle as any other Misra C++ rules.
109+
2. Some doubts about preprocessor and FFI rule. E..g
110+
- rule 19.0.3. There are 2 rationale, the most safety relevant is the one about including code as copy and paste. Including in weird places change the semantic. This should be advisory for Rust.
111+
- Rust has a macro for textual include that is rarely used and if case we should have a guidelines “include\!”.
112+
- Rule 16.1 Apply to Rust
113+
1.
114+
- Rule 13.1.1 Inheritance
115+
1. The issue boils down to diamond inheritance but it seems not applicable to Rust.
116+
- Rule 10.1.2 about volatile
117+
1. Maybe it needs more thinking.
118+
- Rule 21.2.3
119+
1. Applicable to Rust
120+
- Rule 28.6.1
121+
1. Applicable to Rust because the C++ rule is about a move that can be converted to a copy
122+
- Safety-Critical Rust: Items of Shared Value for Fund Pooling
123+
- Presented document to describe what is worth to be funded
124+
- [Open for feedback:](https://docs.google.com/document/d/1E39cNTjK-5azCeWWFWS1jORsz9nqzMs4CNa6Rm68jV4/edit?usp=sharing)
125+
126+

0 commit comments

Comments
 (0)