|
24 | 24 | - How do we feel about these? Suggestions? |
25 | 25 | 7. Discuss possible 2-3 coding guidelines to choose for Clippy lints (Pete) |
26 | 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) |
| 27 | +8. One-off feedback session on Clippy lint mapping to usefulness for safety-critical purposes (David / Pete) |
| 28 | + - David and Félix will run this session; they are looking at around Thursday, July 16th (2026-07-16) |
| 29 | + - Please note your interest in [this Zulip thread](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Clippy-linters/with/607612630)! |
| 30 | +9. First version of MISRA C \+ CERT C Appendices [live](https://coding-guidelines.arewesafetycriticalyet.org/appendices/standards-matrices/index.html) |
28 | 31 | - [CERT C](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/milestone/3) and [MISRA C](https://github.com/Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines/milestone/4) milestones now established |
29 | 32 | - New labels (and board views): [`rationale needed`](https://github.com/orgs/Safety-Critical-Rust-Consortium/projects/4/views/12), [`guideline needed`](https://github.com/orgs/Safety-Critical-Rust-Consortium/projects/4/views/11), [`clippy lint needed`](https://github.com/orgs/Safety-Critical-Rust-Consortium/projects/4/views/13) |
30 | | -9. Safety-Critical Rust: Items of Shared Value for Fund Pooling (Pete) |
| 33 | +10. Safety-Critical Rust: Items of Shared Value for Fund Pooling (Pete) |
31 | 34 | - One of the action items Pete took from the SCRC Room at RustWeek 2026 |
32 | 35 | - 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. |
33 | 36 | - Pete will screen share and show the draft and then share it afterwards for feedback |
34 | 37 | - Would we like to form up a working group temporarily to get this in good shape? |
35 | 38 | - 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) |
36 | | -10. Interest in the MISRA C++ mapping (mira / Pete) |
| 39 | +11. Interest in the MISRA C++ mapping (mira / Pete) |
37 | 40 | - Updates on new things in the MISRA C++ \=\> Rust mapping |
38 | 41 | - In talks with MISRA folks still; but in practice the procedure outlined seemed reasonable to them |
39 | 42 | - 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) |
40 | | -11. Review batches for [CERT C Rust Mapping](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/336) (Pete) |
| 43 | +12. Review batches for [CERT C Rust Mapping](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/336) (Pete) |
41 | 44 | - Let's split up again, to get some feedback on batch 2 |
42 | 45 | - [428 \[CERT C Review Batch 2/5\] Review proposed Rust categorization](https://github.com/rustfoundation/safety-critical-rust-coding-guidelines/issues/428) |
43 | 46 | - **Group A** |
44 | 47 | - xx |
45 | 48 | - **Group B** |
46 | 49 | - Xx |
47 | | -12. Round table |
| 50 | +13. Round table |
48 | 51 |
|
49 | 52 | ## **Check-in area** |
50 | 53 |
|
|
0 commit comments