propose 2025h2 Goals #3849
propose 2025h2 Goals #3849
Conversation
|
As in prior rounds, we'll follow an unusual FCP process here. Leads must check their boxes, others are encouraged but not required to do so. bootstrap
cargo
compiler
crates-io
infra
lang
lang-docs
leadership-council
libs
libs-api
opsem
project-exploit-mitigations
rustdoc
spec
testing-devex
types
wg-compiler-performance
wg-mir-opt
|
|
I love seeing how many goals are like "this builds on work from previous goals," or "this goal resolves blockers discovered in previous goals." It shows the goal program has been going long enough that it's starting to build some momentum throughout the project. |
|
Similar to last time, I would recommend changing leadership-council to not be optional. |
So, that falls out from not having a lead. I can definitely tweak the script but I'm curious to hear your reasoning on that. Is it because you think the LC should generally be aligned on the "goal slate overall" or is it related to the Vision Doc goal, which is the only one that cited the LC. |
Just the Vision Doc goal. It's just a formality, since I believe we've already says "yes" to it. I would just like to be careful with teams that don't have a lead to avoid things slipping through without consensus. Last time there were goals we weren't even aware of, so it was a bit different. |
|
@ehuss ok, I'll make the change |
Co-authored-by: lcnr <[email protected]> Co-authored-by: Josh Triplett <[email protected]> Co-authored-by: Eric Holk <[email protected]>
|
Huzzah! All team leads have checked their boxes. Much appreciated y'all! I'm going to declare this accepted. |
Per https://blog.rust-lang.org/inside-rust/2025/06/23/project-goals-2025h2-call-for-submissions/, here is the proposed slate of 2025H2 goals.
Rendered