Project team for the Rust Vision Doc 2025 effort #1694
+52
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dry-run check results |
|
@nikomatsakis The document gives a 403 Forbidden: |
ehuss
reviewed
Mar 19, 2025
|
@ZuseZ4 no-- I don't understand that, I thought all those docs were public. |
|
Heads up that we updated the charter and expectations of membership and I plan to add a few more folks to the list. |
|
@ZuseZ4 I've inlined the charter into the PR description, seems better anyhow. |
|
@nikomatsakis Are we expecting a T-council decision to gate merging this? (I don't have a super strong opinion, but it feels a bit odd to allow almost top-level team creation without some team approving it. In this case it's mostly longstanding project members so I'm not too worried, but still :) I'll mark this PR as draft, but please poke if we think this is only waiting on team repo admins... |
|
I hadn't quite thought about if this is needs some extra approval or not. I was just waiting on Niko to update the member list here and add a repo before merging. |
|
@Mark-Simulacrum I believe the general approval was given here when the project goal was approved, so I don't feel the need for a formal check-off... https://rust-lang.github.io/rust-project-goals/2025h1/rust-vision-doc.html#ownership-and-team-asks ...it's also not a project group, not a permanent team |
|
@jackh726 I thought I had pushed that...huh |
|
OK, pushed! |
|
This is nominated for council discussion on Friday: |
Co-authored-by: Eric Huss <[email protected]>
Co-authored-by: Eric Huss <[email protected]>
|
Rebased and updated. Given that leadership council approved this concept, can we get this merged? Would be helpful. |
nikomatsakis
force-pushed
the
vision-doc-team
branch
from
fd70b12 to
75105a9
Compare
Mark-Simulacrum
approved these changes
Mar 28, 2025
|
But looks like CI is failing... happy to get pinged on Zulip once that's fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context; this hackmd contains charter, expectations, and other info.
cc @jackh726
Charter
To author the Rust 2025 Vision RFC. See the Project Goal for more details.
Membership plan
Initial leads, charged with generally running the group and determining members and membership expectations.
Expectations of membership
The expectation of a team member is that you will be an active participant in gathering and analyzing data. This means that you'll setup and drive at least 2 or 3 interviews and discussions during April -- can of course be way more! There are no pre-defined focus areas, it's up to you to identify the kinds of things you want to focus on.
Time expectation: 2-3h/wk