Skip to content

Commit c8f03a7

Browse files
add the minutes of the tooling subcommittee meeting from 2026/04/10 (#625)
1 parent 4cb1570 commit c8f03a7

1 file changed

Lines changed: 63 additions & 0 deletions

File tree

  • subcommittee/tooling/meetings/2026-04-10
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Tooling Subcommittee Meeting on 10 April 2026 @ 4pm GMT
2+
3+
| Search Key | Description |
4+
| :---- | :---- |
5+
| \[todo\] | Action Item |
6+
| \[decision\] | Something decided on |
7+
| \[important\] | Key information |
8+
9+
## Agenda
10+
11+
1. Solicitation of notetaker
12+
2. Review last time’s meeting minutes [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/622](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/622)
13+
3. Present new members
14+
4. Merge tools list [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578)
15+
5. [Safety-Critical Rust roadmap](https://rust-lang.github.io/rust-project-goals/2026/roadmap-safety-critical-rust.html) (Rust Bridge Task Force)
16+
1. Interest in contributing to them?
17+
2. In particular: [https://rust-lang.github.io/rust-project-goals/2026/safety-critical-lints-in-clippy.html](https://rust-lang.github.io/rust-project-goals/2026/safety-critical-lints-in-clippy.html) is relatively well-scoped. Seems possible to contribute one or two lints here or there
18+
3. Announce interest in this Zulip thread: [\#safety-critical-consortium \> Getting involved with Clippy for SCRC lints](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Getting.20involved.20with.20Clippy.20for.20SCRC.20lints/with/583090116)
19+
20+
## Check-in area
21+
22+
**Please add your name, and an emoji that describes your day.**
23+
24+
* Alexandru Radovici 🙂
25+
* Tony Aiello
26+
* Arnaud Fontaine 🙂
27+
* Zalán Bálint Lévai 🙂
28+
* Manuel Hatzl
29+
* Xander Cesari 🌧️
30+
* Oreste Bernardi 🏥
31+
* Pete LeVasseur 🐇
32+
* Tiago Manczak
33+
34+
**Notetaker:**
35+
36+
* Oreste Bernardi
37+
38+
## Housekeeping section
39+
40+
## Tasks
41+
42+
* \[todo\] Pete will go back to Clippy team to discuss with them about having some active mentorship like video calls to onboard us.
43+
* Zalan and Alexandru expressed willingness to support this activity
44+
* Please provide interest here: [https://rust-lang.zulipchat.com/\#narrow/channel/445688-safety-critical-consortium/topic/Getting.20involved.20with.20Clippy.20for.20SCRC.20lints/with/583090116](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium/topic/Getting.20involved.20with.20Clippy.20for.20SCRC.20lints/with/583090116)
45+
* Alexandru shall create a pull request to add link to coding guidelines in the website (https://arewesafetycriticalyet.org/).
46+
47+
## Meeting Minutes
48+
49+
* Merge tools list: [https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578](https://github.com/rustfoundation/safety-critical-rust-consortium/pull/578)
50+
* Fast review of rendered page. → appreciated the content and layout.
51+
* Merged \!\!\!\! 🥳
52+
* Safety-Critical Rust roadmap
53+
* Clippy lints is starting to overlap more with coding guidelines.
54+
* Started conversation with clippy team last year.
55+
* \~ 10 coding guidelines candidates for clippy
56+
* Everyone doesn't want a new tool but prefers to stick with clippy.
57+
* Collaboration with clippy team will be mostly async.
58+
* There is a Zulip thread to discuss with Clippy team.
59+
* Open source approach to tool that check coding guidelines is appreciated.
60+
* Coding guidelines
61+
* It needs more clarity about the status of single coding guidelines.
62+
* Described the activities of contributors to coding guidelines.
63+
* Big appreciation for Tiago and Manuel for the pages about tools.

0 commit comments

Comments
 (0)