- Defining the style for new Rust constructs
- Evolving the existing style over the course of Rust editions (without breaking backwards compatibility)
- Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms
- Style Guide
- T-style team repo
- #T-style Zulip stream
- #T-style/private Zulip stream
rust-lang
issues with theT-style
orI-style-nominated
labels
The active membership of the style team can be found on rust-lang.org/governance.
The Rust style team shall have at least 3 members and at most 8. If the team has fewer than 3 members it shall seek new members as its primary focus.
Members of the style team are nominated by existing members. All existing members of the team must affirmatively agree to the addition of a member, with zero objections; if there is any objection to a nomination, the new member will not be added. In addition, the team lead or another team member will check with the moderation team regarding any person nominated for membership, to provide an avenue for awareness of concerns or red flags.
Contributors who believe they'd be a good fit for the style team are encouraged to request an invite1 to the team, by reaching out via Zulip private message to one or more team members. The style team will consider all such requests as as a proposal to become a team member and provide clear feedback to the contributor if there are any objections so that any issues may be resolved and the contributor can apply again in the future. The style team will not consider having previously been rejected as a basis for future rejections.
Footnotes
-
We suggest reaching out via zulip DM to one of the current team members, and contacting the lead by default if you're unsure who to reach out to. ↩