-
Notifications
You must be signed in to change notification settings - Fork 54
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
Lang team champions #247
Merged
nikomatsakis
merged 19 commits into
rust-lang:main
from
nikomatsakis:lang-team-champions
Feb 7, 2025
Merged
Lang team champions #247
nikomatsakis
merged 19 commits into
rust-lang:main
from
nikomatsakis:lang-team-champions
Feb 7, 2025
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
move away from completing RFC for now
* RTN, unsafe binders, AFIDT: nikomatsakis * generators, impl trait aliases, pin ergonomics: tmandry
(Worth pointing out that we can reassign these champions post RFC if we want to rejigger, the important thing is not to far outstrip our capacity.) |
This reverts commit edc3909.
and restore the RFC decision ask. Doesn't seem undoable.
I'll take pin ergonomics, if @tmandry wants. You two volunteered for quite of lot of these. |
@traviscross I'm gonna merge but let's discuss you me and tmandry. Could be good, I agree we need to spread out more. |
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.
This PR defines the lang-team champion role and revises our goals. I'm not sure that we've got it nailed yet. For one thing, I am championing perhaps a bit more than I would like (though it's not just about raw numbers, as some of the things I am championing are already fairly advanced, e.g. RTN).
This is a limited version of the champion role that I proposed. It basically means: this person is the main point-of-contact for the lang team. They are empowered to make decisions. They are expected to post regular updates that will be reviewed by the broader team. If concerns arise, the champion is the one that decides what to do in response -- though people with concerns may escalate to a blocking concern if they disagree, but that should be done with caution.
Champions (summarizing):
These champion assignments have not all been confirmed yet.
Rendered