You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you may have noticed, the August PM update had broader scope. It included deeper dive into the reflection and variadic generics features and took the opportunity to describe what the Leadership Council and the Foundation Project Director roles are about.
13
+
As you may have noticed, the August PM update had a broader scope than earlier ones. It included a deeper dive into the reflection and variadic generics features and took the opportunity to describe the nature of the Leadership Council and the Foundation Project Director roles.
14
14
15
-
I think it's useful to share details on what's happening throughout the broader Project in addition to the thing I personally have done.
15
+
I think it's useful to share details on what's happening throughout the broader Project in addition to the things I have personally done.
16
16
17
-
Please [let me know][tomas-zulip] whether this is indeed valuable to you. Or whether these updates should only focus on the direct PM work, or whether there's anything else you'd like.
17
+
Please [let me know][tomas-zulip] whether this is indeed valuable to you, whether these updates should only focus on the direct PM work, or whether there's anything else you'd like.
The Council representatives have been selected. We have one new face joining: [Jakub Beránek](https://github.com/Kobzol/). Jakub will represent the infrastructure team.
23
+
The Council representatives have been selected. We have one new representative: [Jakub Beránek](https://github.com/Kobzol/). Jakub will represent the Infrastructure team.
The Foundation Project Director selection process is still ongoing.
29
+
The Foundation Project Director selection process has completed.
30
30
31
-
I have gathered all the nominations, verified whether the nominees accept and asked everyone to provide a statement for their candidacy.
31
+
I gathered all the nominations, verified that the nominees had accepted their nominations, and asked everyone to provide a statement for their candidacy.
32
32
33
-
All of that is listed in the [Project Director Candidate Nominations 2025 hackmd][pd-hackmd].
33
+
Those statements are listed in the [Project Director Candidate Nominations 2025 hackmd][pd-hackmd].
The elections were scheduled on Friday2025-10-03 where the Leadership Council were selected the three new Project Directors in accordance with the [election process][election-process] (be on the lookout for the official announcement!).
37
+
The elections were held on Friday, October 3rd, 2025, during which the Leadership Council selected the three new Project Directors in accordance with the [election process][election-process].
I did not travel to RustConf and haven't participated live much, due to the sizeable (9 hours) time difference.
43
+
I did not travel to RustConf and haven't participated live much, due to the sizable (9-hour) time difference.
44
44
45
45
I did, however, remotely join the C++ interoperability session that Jon Bauman organized on 2025-09-02 and took notes while I was awake.
46
46
47
-
There was an overview of the current tooling (bindgen, CXX, Zngur, Crubit), people talked about how they're handling interop in their organizations and discussed the next steps to move forward.
47
+
There was an overview of the current tooling (bindgen, CXX, Zngur, Crubit); attendees talked about how they're handling interop in their organizations and discussed the next steps to move the work forward.
48
48
49
49
The [notes are here][cpp-interop] and I'm writing a blog post to summarize what happened.
50
50
@@ -54,15 +54,15 @@ The [notes are here][cpp-interop] and I'm writing a blog post to summarize what
54
54
55
55
I attended [Kangrejos, the annual Rust for Linux workshop in Spain, Oviedo][kangrejos]. Rust for Linux is a project that aims at making Rust the second official language in the Linux kernel (C is the first one).
56
56
57
-
This was an absolutely packed two-day event. The roughly thirty attendees were all sitting in the same room, had lunch at the same space, went to dinner together.
57
+
This was an absolutely packed two-day event. The roughly thirty attendees were all sitting in the same room, had lunch in the same space, and went to dinner together.
58
58
59
-
Miguel Ojeda told me this is by design -- that way there's a lot of opportunity for everyone to get to know everyone else even without lengthy and potentially awkward introduction sessions. Everyone learns about the various efforts going on, people can talk, share information, and collaborate.
59
+
Miguel Ojeda told me this is by design — that way there's a lot of opportunity for everyone to get to know everyone else even without lengthy and potentially awkward introduction sessions. Everyone learns about the various efforts going on, people can talk, share information, and collaborate.
60
60
61
-
It was a really intense experience, but it worked as advertised. I ended up speaking with a good chunk of the people, learned a lot about what's going on and got to know the Rust for Linux team I'm working with.
61
+
It was a really intense experience, but it worked as advertised. I ended up speaking with a good number of the attendees, learned a lot about what's going on, and got to know the Rust for Linux team I'm working with.
62
62
63
-
And the attendees were a pretty diverse bunch. The majority were people working on various aspects of Rust for Linux, but we also had representatives from the Linux kernel (Greg KH who's directly supporting the effort), LWN.net, Debian, individual contributors and Rust (Tyler Mandry and yours truly).
63
+
The attendees were a pretty diverse bunch. The majority were people working on various aspects of Rust for Linux, but we also had representatives from the Linux kernel (Greg KH who's directly supporting the effort), LWN.net, Debian, and the Rust Project (Tyler Mandry and yours truly).
64
64
65
-
The event was a list of talks/presentations/workshops. Some to provide a status update, others to showcase a new tool or process. The event is intentionally not recorded or minuted so everyone can speak freely and openly.
65
+
The event consisted of a series of talks, presentations, and workshops— some to provide a status update, others to showcase a new tool or process. The event was intentionally not recorded or minuted so that everyone could speak freely and openly.
66
66
67
67
To get a sense, you can see the [topics and some of the slides on the Kangrejos 2025 page][kangrejos-talks].
68
68
@@ -81,24 +81,27 @@ Here are some things I personally found interesting:
81
81
82
82
**Rust for Linux needs are beneficial to the evolution of the Rust language**
83
83
84
-
Rust aims to be a low-level language that you can (among other things) write kernel code in. This is exactly what Rust for Linux is doing -- in a large, well-established kernel at that.
84
+
Rust aims to be a low-level language that you can (among other things) write kernel code in. This is exactly what Rust for Linux is doing — in a large, well-established kernel at that.
85
85
86
-
Any areas for improvement that RfL hits will likely also serve other low-level projects (kernels, embedded, filesystems, etc.).
86
+
Any areas for improvement that RfL encounters will likely also benefit other low-level projects (kernels, embedded, filesystems, etc.).
87
87
88
88
**[Coccinelle for Rust](https://rust-for-linux.com/coccinelle-for-rust)**
89
89
90
90
This is a tool that lets you describe transformations you want to make and then apply them across the code base.
91
91
92
92
It supports relatively straightforward things such as renaming a function or reordering parameters. But it operates on AST level and lets you do things like turning:
93
93
94
-
info!("Window resized to: {}x{}", width, height);
94
+
```rust
95
+
info!("Window resized to: {}x{}", width, height);
96
+
```
95
97
96
98
to:
97
99
98
-
info!("Window resized to: {width}x{height}");
99
-
100
-
across the codebase. Across all such format!-like invocations, parameters etc. And taking care to not interpolate field accesses or function calls (which are currently not allowed in the "format strings").
100
+
```rust
101
+
info!("Window resized to: {width}x{height}");
102
+
```
101
103
104
+
across the codebase. Across all such `format!`-like invocations, parameters etc. And taking care to not interpolate field accesses or function calls (which are currently not allowed in the "format strings").
102
105
103
106
**Clippy**
104
107
@@ -122,9 +125,9 @@ Miguel Ojeda stressed that the most important thing for Rust for Linux usage is
122
125
123
126
Pierre-Emmanuel Patry talked about an alternative implementation of the Rust compiler within the GNU compiler toolchain.
124
127
125
-
This effort is valuable because it provides a completely separate compiler (which could for example compile rustc at some point and therefore bootstrap Rust). It can help specification efforts by highlighting areas where the compilers interpret things differently (then force a decision and have both align on it) and provide Rust for people who either require the GNU toolchain or who would benefit from the platforms that are supported by GNU but not LLVM.
128
+
This effort is valuable because it provides a completely separate compiler (which could for example compile rustc at some point and therefore bootstrap Rust). It can help specification efforts by highlighting areas where the compilers interpret things differently, which can then force a decision and have both compilers align on it, and provide Rust for people who either require the GNU toolchain or who would benefit from the platforms that are supported by GNU but not LLVM.
126
129
127
-
The "Front-End" here means that GCCRS reads Rust code and transforms it into an [immediate representation (IR)][ir] that GCC tooling turns into binary code, similarly how the Rust compiler outputs LLVM IR.
130
+
The "front-end" here means that GCCRS reads Rust code and transforms it into an [intermediate representation (IR)][ir] that GCC tooling turns into binary code, similar to how the Rust compiler outputs LLVM IR.
@@ -134,16 +137,16 @@ Their main target is to compile Rust's [core library][core].
134
137
135
138
[core]: https://doc.rust-lang.org/core/
136
139
137
-
After that, they've set their sights on compiling Linux (including the Rust part). Linux can currently be built with either GCC or LLVM, but it is strongly recommended that everything use one or the other. Some projects have a requirement to use the GCC tooling and this will be beneficial to them.
140
+
After that, they've set their sights on compiling the Linux kernel (including the Rust part). Linux can currently be built with either GCC or LLVM, but it is strongly recommended that everything use one or the other. This will be beneficial to some projects that are required to use the GCC toolchain.
138
141
139
-
Interestingly, the project is completely ignoring a borrow checker for now. Instead, their goal is to compile *correct* Rust programs -- i.e. only those that `rustc` itself would compile. In the future, they plan to look into [Polonius][polonius], but it would be premature at this point.
142
+
Interestingly, the project is completely ignoring a borrow checker for now. Instead, their goal is to compile *correct* Rust programs — i.e. only those that `rustc` itself would compile. In the future, they plan to look into [Polonius][polonius], but it would be premature at this point.
140
143
141
144
[polonius]: https://github.com/rust-lang/polonius
142
145
143
146
144
147
## T-Content
145
148
146
-
Several members of the [Content team][t-content] attended RustConf and recorded several interviews there. The first of these, talking to [Jan David Nose][jdno] from the crates.io team is up:
149
+
Several members of the [Content team][t-content] attended RustConf and recorded several interviews there. The first of these, an interview with [Jan David Nose][jdno] from the crates.io team, is up:
@@ -158,21 +161,21 @@ We've managed to record a few and after we edit them, we'll start publishing the
158
161
159
162
This has been a fascinating experience. I've been (remotely) interviewed once, but I've never seen the behind the scenes. Mostly, I've helped Tyler get things set up and kept an eye on all the microphones and cameras to make sure everything was recording (one or our cameras had a silent 30 minute recording limit).
160
163
161
-
But I did take the opportunity to step in front of the camera and interview one of the attendees. I worried I was going to mess up and ruin the interview, but watching the raw footage, it seems to have turned out fine in the end.
164
+
But I did take the opportunity to step in front of the camera and interview one of the attendees. I was worried I was going to mess up and ruin the interview, but watching the raw footage, it seems to have turned out fine.
162
165
163
-
I thought my role in the Content team would be mainly support and possibly in writing/publishing. But now I'm open to the recording as well. Especially if we'll have more time to prepare ahead of time and won't have to squeeze it between lunch and conference sessions :-).
166
+
I thought my role in the Content team would be mainly support and possibly in writing/publishing. But now I'm open to being part of the recording process as well. Especially if we'll have more time to prepare ahead of time and won't have to squeeze it between lunch and conference sessions :-).
164
167
165
168
## 2025H2 Goals
166
169
167
170
Niko Matsakis opened the [RFC for Project goals for the second half of this year](https://github.com/rust-lang/rfcs/pull/3849).
168
171
169
-
Rémy (lqd) and I reviewed the RFC and followed-up on the checklists -- making sure that every required person checked their box (after helping to resolve their concerns).
172
+
Rémy (lqd) and I reviewed the RFC and followedup on the checklists — making sure that every required person checked their box (after helping to resolve their concerns).
170
173
171
-
Niko plans to make things easier by providing a page that always shows the current status of all goals. The idea is that each team would be able to review it periodically and see if e.g. there's something they can do to get a goal unstuck.
174
+
To make things easier, Niko plans to provide a page that always shows the current status of all goals. The idea is that each team would be able to review it periodically and see if e.g. there's something they can do to get a goal unstuck.
172
175
173
176
I will continue to write the regular updates and this should help with that work too. And I plan to set up a retrospective and see if there's anything people would like to change.
174
177
175
-
Niko introduced me to Nandini who's a post-doc at Carnegie Mellon, researching how open source communities organize themselves. She started to conduct in-depth interviews with people from the Project about Goals specifically. That work is ongoing, but once we have it, that will be really valuable data, too.
178
+
Niko introduced me to Nandini who's a post-doc at Carnegie Mellon, researching how open source communities organize themselves. She started to conduct in-depth interviews with people from the Project about Goals specifically. That work is ongoing, but once it is complete, it will provide really valuable data.
176
179
177
180
178
181
## Variadic generics micro survey
@@ -183,13 +186,13 @@ Olivier Faure [announced a survey][vargen-blog] to gather information from the R
0 commit comments