Skip to content

minutes.md

Latest commit

 

History

History
126 lines (105 loc) · 7.58 KB

minutes.md

File metadata and controls

126 lines (105 loc) · 7.58 KB
Raw

Coding Guidelines Subcommittee Meeting on 2026-06-24 @ 1600 CEST / 1100 EDT

Link to meeting time in common time zones.

Search Key Description
todo Action Item
decision Something decided on
important Key information

Agenda

  1. Solicitation of notetaker
  2. Acceptance of Previous Meeting Minutes
  3. Introduction of new members
  4. Solicit availability for RustConf 2026 SCRC Room (Pete)
  1. The SCRC as a member organization of the Rust Commercial Network (RCN)
  • RFC PR
  • RCN announcement goes out today with the SCRC as a founding member organization
  1. Draft document for usage of standards documents
  1. Discuss possible 2-3 coding guidelines to choose for Clippy lints (Pete)
  • How've we done in looking into these?
  1. First version of MISRA C + CERT C Appendices live
  • Pete must still mine these appendices for creating issues for contributors
  1. Safety-Critical Rust: Items of Shared Value for Fund Pooling (Pete)
  • One of the action items Pete took from the SCRC Room at RustWeek 2026
  • 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.
  • Pete will screen share and show the draft and then share it afterwards for feedback
  • Would we like to form up a working group temporarily to get this in good shape?
  • A first (0th?) draft document is available here: Safety-Critical Rust - Items of Shared Value for Fund Pooling
  1. Interest in the MISRA C++ mapping (mira / Pete)
  • Updates on new things in the MISRA C++ => Rust mapping
  • In talks with MISRA folks still; but in practice the procedure outlined seemed reasonable to them
  • Please register interest on this Zulip thread
  1. Review batches for CERT C Rust Mapping (Pete)
  1. Round table

Check-in area

  • Mira Baumann 🤧
  • Michael Henn 🥵
  • Julius Gustavsson
  • Pete LeVasseur 🏃
  • Oreste Bernardi ☀️
  • Max Jacinto 😵‍💫
  • Tshepang Mbambo 👍
  • Christof Petig 🌡️
  • Kangwon Lee ✈️
  • Andreas Weis 🥵

Notetaker:

  • Oreste Bernardi

For tips on how we take notes in the Safety-Critical Rust Consortium, please see the Meeting Notetaker Role doc.

Housekeeping section

Tasks

  • xx

Meeting Minutes

  • Previous meeting notes are approved
  • AdaCore agreed to sponsor RustConf safety critical consortium room.
    • Requested to register participation

Material

Any material to read before the meeting should be included here.

Overview of Safety-Critical Rust Rust Project Goals Roadmap (Pete)

  • Soliciting those interested in Normative Documentation for Sound unsafe Rust goal
    • Register interest here on Rust Zulip
  • Soliciting those interested in Establish a Spot for Safety-Critical Lints in Clippy goal
    • Register interest here on Rust Zulip
  • SCRC as a member organization of the Rust Commercial Network (RCN)
  • Draft document for usage of standards documents
    • Draft available with rules about standard use.
    • Requested review
    • Standards will be not publicly available. Access shall be granted and they can be read but not downloaded.
  • First version of MISRA C + CERT C
    • Appendixes are live.
    • Provided to Toyota for internal use.
  • Interest in the MISRA C++ mapping
    • Question if FFI guidelines shall be considered or not.
      1. Proposed to handle as any other Misra C++ rules.
      2. Some doubts about preprocessor and FFI rule. E..g
    • 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.
    • Rust has a macro for textual include that is rarely used and if case we should have a guidelines “include!”.
    • Rule 16.1 Apply to Rust
      1.
    • Rule 13.1.1 Inheritance
      1. The issue boils down to diamond inheritance but it seems not applicable to Rust.
    • Rule 10.1.2 about volatile
      1. Maybe it needs more thinking.
    • Rule 21.2.3
      1. Applicable to Rust
    • Rule 28.6.1
      1. Applicable to Rust because the C++ rule is about a move that can be converted to a copy
  • Safety-Critical Rust: Items of Shared Value for Fund Pooling