-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC for project goals #3672
RFC for project goals #3672
Conversation
eb59f09
to
4fc3a00
Compare
Co-authored-by: lcnr <rust@lcnr.de>
Hi everyone! This RFC follows an unusual ratification procedure. Team leads are asked to review the list of asks for their team (see the reference-level-explanation) and confirm that their team is aligned. Leads should feel free to consult with team members and to raise concerns on their behalf. Once all team leads have signed off, the RFC will enter FCP. (As they have no leads, I am not counting the leadership council here.) Note that your name may appear more than once! I'm going to add one comment per team to avoid Github's limit of "max mentions per comment". |
This comment was marked as outdated.
This comment was marked as outdated.
|
clippy
|
compiler
|
crates-io
|
edition
|
This comment was marked as outdated.
This comment was marked as outdated.
lang
|
leadership-council
|
libs-api
|
rust-analyzer
|
rustdoc
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really fantastic. Thank you @nikomatsakis for the work you've done to assemble this.
@jackh726 when it comes to blog posts, I wasn't sure how to think about it. My general feeling is:
I'd be happy to say "it's assumed that anything tied to a project goal can have blog posts on any Rust blog". |
NEW GOALS * User-wide caching (orphaned, cargo team) REMOVED GOALS * Experiment with relaxing the Orphan Rule dropped for bandwidth concerns. (We may reframe.) SIMPLIFIED GOALS * Patterns of empty types -> moral support
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @nikomatsakis for your work driving and assembling all of this. I'm really optimistic about this process and how it will impact the Rust Project's ability to coordinate longer-term work of strategic importance.
You have said you wanted this initial goal slate to be a learning experience, and I can see it already has been. I'm hoping for and looking forward to a blog post with everything you learned putting it together. :)
As for the goal slate itself, I think it is good and definitely meets the bar to move forward and start executing during the rest of the year. We will learn even more in the next six months!
@rfcbot reviewed edit: ofc this doesn't work :3 very happy about the work on Project Goals btw ❤️ |
text/0000-Project-Goals-2024h2.md
Outdated
* resolving the "send bound problem", thus enabling foundational, generic traits like Tower's [`Service`](https://docs.rs/tower-service/latest/tower_service/trait.Service.html) trait; | ||
* stabilizing async closures, thus enabling richer, combinator APIs like sync Rust's [`Iterator`](https://doc.rust-lang.org/std/iter/trait.Iterator.html); | ||
* reorganizing the async WG, so the project can benefit from a group of async rust experts with deep knowledge of the space that can align around a shared vision. | ||
* [**Resolve the biggest blockers to Linux building on stable Rust**](https://rust-lang.github.io/rust-project-goals/2024h2/./rfl_stable.html) via: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of the blockers mentioned by @ojeda for RfL is the Rust GCC backend. I think it should be mentioned in this list as well.
Summary of recent updates: NEW GOALS
REMOVED GOALS
SIMPLIFIED GOALS
|
Hear ye, hear ye! This RFC is now entering final comment period. With the latest round of updates, we now have sign-off from the team leads of all required teams! Barring concerns or other procedural changes, the RFC will exit FCP July 28th (10 days from today). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this rename broke the "rendered" link at the top of the issue
Thanks, should be fixed now. |
Huzzah! This RFC has been accepted. Tracking issues for each goal can be found on the 2024h2 milestone of the rust-lang/rust-project-goals repository. Goals owners will be getting regular pings on Zulip to post updates and I plan to assembly ~monthly blog posts collecting updates and highlighting progress. The next immediate step once this RFC is merged will be to author an announcement blog post with the roadmap along with an accompanying Inside Rust post (and email) laying out the procedural steps. Thanks to everyone who submitted goals along with all the team members who gave feedback! And special thanks to @joshtriplett for many conversations along with diving in at various points to do legwork. 💜 |
This RFC presents the Rust project goal slate for 2024H2. The slate consists of 26 total project goals of which we have selected 3 as our "flagship goals":
Flagship goals represent the goals expected to have the broadest overall impact.
This RFC is now in final comment period. We are following an unusual ratification procedure. Team leads are asked to review the list of asks for their team (see the reference-level-explanation) and confirm that their team is aligned. Now that all team leads have signed off, the RFC has entered FCP.
More details at https://rust-lang.github.io/rust-project-goals/.
Rendered