Convert rustup and rustfmt from working groups to teams #723
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 originally started with the realization that some emails, e.g. recent ones from the Foundation, hadn't been received by some rustup and rustfmt folks because working group members are intentionally not included in the
all@rust-lang.org
distribution list.Subsequent discussion on Zulip with the dev tools team led to an overwhelming consensus that both rustup and rustfmt should be proper subteams under devtools, especially when considering their nature and operating models relative to RFC 2856.
Let me know if there's any additional changes required to make the conversion.
cc @kinnison @rbtcollins @Manishearth