Skip to content

Commit

Permalink
Update charter.md
Browse files Browse the repository at this point in the history
Co-authored-by: Josh Triplett <[email protected]>
  • Loading branch information
2 people authored and compiler-errors committed May 17, 2024
1 parent 95dde0b commit b1a7412
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion charter.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ The style team is committed to building a diverse and capable team comprising in
6. Consent to Principles and Aims: Members are expected to align with and consent to the principles and aims of the style team, as outlined in the [Rust style guide principles](https://github.com/rust-lang/rust/blob/master/src/doc/style-guide/src/principles.md) and the style team's [charter](https://github.com/rust-lang/style-team/blob/style-policy/charter.md).
7. Pragmatic Approach: Members should prioritize pragmatism over dogmatism, even when dealing with style and formatting aspects they feel particularly strongly about. The ability to make practical and reasonable decisions that benefit the community at large is essential.
8. Openness to Change and Learning: Members should demonstrate a willingness to seek out and receive new information, be open to changing their opinions based on evidence and rationale, and adapt their perspectives accordingly.
9. Effective Communication in Charged Conversations: The ability to navigate charged conversations and respond constructively and empathetically to evocative commentary is important. Members should be able to handle passionate discussions about code style, recognize miscommunication and misunderstandings, and promote empathy and listening when discussing matters within the purview of the style team.
9. Effective Communication in Charged Conversations: Members will need to carefully navigate charged conversations and evocative feedback, and respond constructively and with empathy, to each other and to the community. Members should be able to handle passionate discussions about code style, recognize miscommunication and misunderstandings, and promote empathy and listening.
10. Interest in Language and Syntax: Members should show interest in tracking changes to the Rust language and syntax. Keeping up-to-date with the latest developments helps inform style decisions

[^1]: 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.

0 comments on commit b1a7412

Please sign in to comment.