Skip to content

Commit 7b71b5b

Browse files
luckymachiPLeVasseur
luckymachi
and
PLeVasseur
authored
coding guidelines meeting notes - 2026/06/03 (#674)
* coding guidelines meeting notes - 2026/06/03 * Remove meeting breakout info Co-authored-by: Pete LeVasseur <plevasseur@gmail.com> --------- Co-authored-by: Pete LeVasseur <plevasseur@gmail.com>
1 parent 80abb94 commit 7b71b5b

1 file changed

Lines changed: 119 additions & 0 deletions

File tree

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

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

Lines changed: 119 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,119 @@
1+
# **Coding Guidelines Subcommittee Meeting on 2026-06-03 @ 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-3&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-05-27/minutes.md) and [Previous Asia Pacific \+ Americas Meeting Minutes](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-consortium/blob/main/subcommittee/coding-guidelines/meetings/2026-05-29/minutes.md)
15+
3. Introduction of new members
16+
4. Coverage of MISRA C and CERT C in 2026 (Félix / Markus updates)
17+
- MISRA C one has a [PR up](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/pull/432) from Markus
18+
- Félix is working on CSS to make the tables more legible by allowing them to be shown more widely.
19+
- Oreste: Pick up CERT C Markdown tables in tracking issue and open up a PR similar in nature to the [PR from Markus](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/pull/432)
20+
1. Issue, where it’s written up in Markdown: [https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/336](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/issues/336)
21+
2. Turn into a PR with the tables in ReStructured Text (RST)
22+
5. Interest in the MISRA C++ mapping
23+
- Pete/Alex are working out how we can have some kind of copy of the MISRA documents (C, C++) held in the jurisdiction of the Rust Foundation in support of members to be able to work on coding guidelines. Still in communication with MISRA folks.
24+
- 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)
25+
6. Review batches for [CERT C Rust Mapping](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/336) (Pete)
26+
- Let's split up again, to get some feedback on batch 2
27+
- [428 \[CERT C Review Batch 2/5\] Review proposed Rust categorization](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/428)
28+
- **Group A**
29+
- Wednesday, June 3 · 11:30am – 12:00pm
30+
- Time zone: America/New\_York
31+
- Google Meet joining info
32+
1. Achim
33+
2. Daniel Dia
34+
3. Kaneko Satoshi
35+
4. Marcos Borges
36+
- Xxxxxx
37+
- **Group B**
38+
- Wednesday, June 3 · 11:30am – 12:00pm
39+
- Time zone: America/New\_York
40+
- Google Meet joining info
41+
1. Max
42+
2. Michael
43+
3. Mira
44+
4. Pete
45+
5. Oreste
46+
-
47+
7. Round table
48+
49+
## **Check-in area**
50+
51+
* Marcos Borges 😀
52+
* Max Jacinto 🏋️
53+
* Daniel Dia 🦀
54+
* Oreste Bernardi
55+
* Mira Baumann
56+
* Pete LeVasseur ⚰️➕➕
57+
* Michael Henn 🏃
58+
59+
**Notetaker:**
60+
61+
- Max Jacinto
62+
63+
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.
64+
65+
## **Housekeeping section**
66+
67+
- Document space: [coding-guidelines](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/coding-guidelines)
68+
- Zulip: [safety-critical-consortium: Coding Guidelines](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Coding.20Guidelines)
69+
- [Kanban board](https://github.com/orgs/rustfoundation/projects/1/views/3)
70+
- [`contributor experience`](https://github.com/orgs/rustfoundation/projects/1/views/4) view
71+
- [`coding guideline`](https://github.com/orgs/rustfoundation/projects/1/views/5) view
72+
73+
## **Tasks**
74+
75+
- xx
76+
77+
## **Meeting Minutes**
78+
79+
- Confirmation if everything’s alright with previous meetings’ minutes; all good, none against
80+
- Introduction of new members\! Two new members join us
81+
- **\[MISRA C\]**
82+
- Work on the appendix’s formatting is being done; mainly fixes in how the tables are shown
83+
- **\[CERT C\]**
84+
- Pending task to format the tables accordingly (Markdown conversion \- formatted text); should be sent as a PR to be merged
85+
- Suggestion to use `pandoc` to convert Markdown to other formats (like RST)
86+
- **\[MISRA C++\]**
87+
- Interest in checking out rules specific to C++ that may involve concepts like polymorphism
88+
- Communication through the Zulip thread is highly encouraged\! If there’s any need for a review or help with a rule volunteers are more than encouraged to leave a message
89+
- **\[Walk-In Items\]**
90+
- Consortium mailing list has been sent a Lettucemeet to check availability for RustConf of SCRC members that will attend
91+
- ADACore has agreed to fund a room at RustConf; ongoing talks to figure out the best structure for the deal
92+
- *Suggestion regarding GH organization:* creation of topics that combine common subjects to better keep track of conversations; aim is to reduce fragmentation
93+
- **\[CERT C Review Batches\]**
94+
- **Group 1:**
95+
- ARR38: Full agreement
96+
- STR32: Agreement for safe Rust, but when doing interop with C libraries you will likely work with raw pointers that point to zero terminated and non-zero terminated buffers, which could be confused. Therefore, it should be considered to update the classification from “Does not map to Rust” to “Maps directory to Unsafe Rust”. Furthermore, the \`CString\` and \`CStr\` types should be acknowledged by the Rationale explicitly for completeness.
97+
- **Group 2:**
98+
- **ERR33:**
99+
- Suggest that there’s a Clippy lint (`clippy::unused_results`) that can force `Return` return values ([https://play.rust-lang.org/?version=stable\&mode=debug\&edition=2024](https://play.rust-lang.org/?version=stable&mode=debug&edition=2024))
100+
- Extra context: [https://play.rust-lang.org/?version=stable\&mode=debug\&edition=2024\&gist=ec6c707cad086431258894b336654df8](https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=ec6c707cad086431258894b336654df8)
101+
- **INT33:** Suggestion to add a reference link to the specific rule that covers it if that’s the case
102+
- **\[ROUNDTABLE\]**
103+
- Clarification regarding the established rules found in, for example: [https://coding-guidelines.arewesafetycriticalyet.org/coding-guidelines/expressions/index.html](https://coding-guidelines.arewesafetycriticalyet.org/coding-guidelines/expressions/index.html)
104+
- Request for PR regarding the clarification issues
105+
106+
## **Material**
107+
108+
Any material to read before the meeting should be included here.
109+
110+
Overview of [Safety-Critical Rust](https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html) Rust Project Goals Roadmap (Pete)
111+
112+
- 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
113+
- We had a meeting with two Rust Project Operational Semantics Team members yesterday.
114+
- Some initial useful feedback obtained; next steps are to develop small reproducible examples of the full iceoryx2 library portions there are questions on
115+
- 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
116+
- 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
117+
- Meeting with Jason Newcomb of Rust Project Clippy Team was immediately prior to this meeting
118+
- 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
119+

0 commit comments

Comments
 (0)