Beyond that, this meta-work is really needed, for the project overall. We've been bumping into limits here for a while. Rust is now large enough that if it were a startup, some people would argue that it's no longer a startup.
(I should also note the roadmaps have been trending this way for a while. See the change over time for yourself:
* 2020: https://github.com/rust-lang/rfcs/blob/master/text/2857-road...
* 2019: https://github.com/rust-lang/rfcs/blob/master/text/2657-road...
* 2018: https://github.com/rust-lang/rfcs/blob/master/text/2314-road...
* 2017: https://github.com/rust-lang/rfcs/blob/master/text/1774-road...
We didn't do this before 2017.)
The closest thing to this is that the situation with Mozilla jumpstarted actually finally creating the Rust Foundation, and deciding its relationship to the project is a governance matter. But that's not in scope for this roadmap, and so has nothing directly to do with it.
Edit: This was just speculation and people with better information have weighed in elsewhere
Super important stuff.
[0] https://github.com/Mark-Simulacrum/rfcs/blob/roadmap-2021/te...
Please don't get me wrong -- governance is important. But concentrating on governance for the entirety of 2021 leaving technical roadmaps to the teams is surprising. What problems is this roadmap trying to solve?
1. Is the existing governance model inadequate and needs to be urgently fixed?
2. Is Rust becoming a "designed by committee" language? This model does not seem to work despite the best intentions.
3. It would be very useful to see not only "what" is in the roadmap but also "why".
EDIT: formatting...
I'd be much more interested to see "rust 2021 language/development/... roadmap" - I sort of expect I will be seeing this soon.