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
Things were a bit busy in the personal life. We had to temporarily move to a smaller apartment which was quite time-consuming and energy-draining. And after that, I took a week off and we spent it in the mountains.
13
+
Things were a bit busy in personal life. We had to temporarily move to a smaller apartment which was quite time-consuming and energy-draining. And after that, I took a week off and we spent it in the mountains.
14
14
15
-
So things were a bit slower in July. In addition to meetings, what clearly dominated was the Project Goals work.
15
+
So things were slower in July. What dominated was the Project Goals work.
16
16
17
17
## Wrapping up 2025 H1 goals
18
18
19
19
As we entered the second half of the year, it was time to wrap up the current Project Goals and get the new ones going. In the spirit of helping people focus on other things, I took this over.
20
20
21
-
First, I've sent a couple requests for goal updates. This lead me to noticing and fixing an issue with the triagebot. See [the `ping-goals` section](#ping-goals-retry-issue).
21
+
First, I've sent a couple requests for goal updates. This lead me to noticing and filing an issue with the triagebot. More details in the [`ping-goals` retry section](#ping-goals-retry-issue).
22
22
23
23
After people provided their final messages, I've published the final 2025H1 Project Goals update:
Based on the feedback we've received, we've made some changes:
39
+
Based on the feedback we've received, we've made some changes in this period:
40
40
41
41
* We're getting the proposals in front of the Teams and their leads earlier (well before the final RFC is written) so they are aware and have input into what's being proposed.
42
42
* We're asking them to suggest what they'd like to see as a flagship goal before the final selection is made.
43
-
* For each proposed goal, we've asked each team with asks mentioned in the goal to select a "champion" who commits to making sure the goal is not blocked by that team.
43
+
* For each proposed goal, we've requsted each team with asks mentioned in the goal to select a "champion" who commits to making sure the goal is not blocked by that team.
44
44
45
45
Once all the champions are selected, we'll meet with the team leads, go over the goals and figure out which ones we want to accept.
46
46
@@ -51,137 +51,133 @@ As the goals were being proposed, Niko, Rémy and I looked at the PRs, fixed any
51
51
52
52
For each team, I've opened a call for champions Zulip thread listing goals that requested their support. [Here's an example for the Lang team](https://rust-lang.zulipchat.com/#narrow/channel/213817-t-lang/topic/2025H2.20Goal.20Review).
53
53
54
-
As with any new process, people had questions. I was there to help clarify we're asking for, the overall plan and next steps. When there were specific questions for a goal, I made sure to connect the right people.
54
+
As with any new process, people had questions. I was there to help clarify what we're asking for, the overall plan and next steps. When there were specific questions for a goal, I made sure to connect the right people.
55
55
56
-
### Rust for Linux
56
+
##Verification and Secure Mirroring for crates.io
57
57
58
-
Continuing the Rust for Linux effort, I'll be the point of contact for the two goals they're proposed ([compiler][rfl-compiler] and [language][rfl-lang] features for getting Rust for Linux into stable Rust).
58
+
We now have a detailed update on the crates.io code signing program and its status.
59
+
60
+
Quick summary:
61
+
62
+
* We've settled on using TAP-16 Merkle Tree implementation of [TUF (The Update Framework)][tuf] for crates.io.
63
+
* We've settled on maintaining a top-level quorum but removing immediate levels for simplicity.
64
+
* We've reached a consensus with the Infrastructure team for deployment planning.
65
+
* A public MVP implementation is coming Soon™ (by the end of August).
66
+
* We will test various optimizations to settle on something that works for our tooling (Rustup, releases, crates.io, update, signing etc.).
67
+
* Role keys will live in KMS (Key Management Service).
68
+
69
+
Open Questions and Next Steps:
70
+
71
+
* Which specific optimizations will fit our needs.
72
+
* How to implement the Merkle tree to reduce round-trips.
73
+
* Stand up infrastructure to host this.
74
+
75
+
76
+
For more details, read this [goal update for more details](https://github.com/rust-lang/rust-project-goals/issues/271#issuecomment-3133590786) and/or reach out to @walterhpearce.
77
+
78
+
One of the things on my radar is to start publishing more frequent and detailed updates. I've joined the signing meetings to be more aware of what's happening.
79
+
80
+
[tuf]: https://theupdateframework.io/
81
+
82
+
## Rust for Linux
83
+
84
+
I took over running the Rust for Linux effort from the Rust Project side.
85
+
86
+
I helped Miguel propose two 2025 H2 goals ([compiler][rfl-compiler] and [language][rfl-lang] features for getting Rust for Linux into stable Rust) and should they be accepted I will be the point of contact for them.
I will set up the agenda, run the meetings and keep the tracking issues up-to-date.
91
+
I took over running the meetings, preparing the agenda, and making sure the tracking issues are up-to-date and bringing any requests or concerns to the relevant Project teams or people.
92
+
93
+
This let Niko disengage from the program completely.
94
+
64
95
65
96
## Misc
66
97
67
98
### `ping-goals` retry issue
68
99
69
100
The request for updates is done by the `ping-goals` command of the @triagebot. This returned an error ("Failed to await at this time: connection closed before message completed"), but did actually ping everyone.
Having taken over the minutes for the Leadership Council meetings in June, I've now closed the loop by cleaning them up and publishing them in [the leadership-council repository][leadership-council-minutes].
124
+
Having taken over the minutes for the Leadership Council meetings in June, I've now closed the loop by making them more readable and publishing them in [the leadership-council repository][leadership-council-minutes].
I wasn't here in May so these can serve as a comparison.
168
+
169
+
Meetings attended: 0
170
+
171
+
Average word count:
172
+
* cargo: 857
173
+
* Lang triage: 1.4k
174
+
* Libs: 1.3k
175
+
* Leadership council: 1.5k
176
+
177
+
### Caveat emptor
178
+
179
+
More words doesn't necessarily mean better and there are other aspects that affect this: number of people in the meeting, how much discussion a topic needs, etc. And this is not a target I or anyone else is holding me to.
180
+
181
+
But it is kind of interesting to see.
182
+
183
+
If you have an idea for any more useful things to track, please let me know!
0 commit comments