From 52c808b12a109c2c8a2bc7fa271dfe321788c833 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 24 Jan 2024 12:05:44 -0800 Subject: [PATCH] Update charter.md reorder one bullet and renumber the rest accordingly --- charter.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/charter.md b/charter.md index e6135fb..c37c3bf 100644 --- a/charter.md +++ b/charter.md @@ -34,11 +34,11 @@ The style team is committed to building a diverse and capable team comprising in 2. Familiarity with Rust: Prospective members should have a general familiarity with Rust, including a solid understanding of its constructs, how they interact, and the overall language ecosystem. This knowledge is crucial for making informed decisions regarding style and formatting guidelines. 3. Interest in Rust Style: Members should have a genuine interest in Rust style and a willingness to contribute to the team's efforts. It is important that members are not solely focused on advocating for their personal style preferences but are dedicated to promoting a collective and consensus-based approach. 4. Effective Collaboration Skills: Successful candidates will have a proven track record of effective collaboration, showcasing their ability to work together with others, consider diverse perspectives, navigate conflicts, and address emotional challenges in a constructive manner. -5. Familiarity with Rust Project: Members should be familiar with the Rust project's structure, culture, and expectations upon maintainers. This knowledge helps members navigate the ecosystem more effectively, and align their style decisions with the project's broader goals. -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, introspect on their underlying values, change their opinions based on evidence and rationale, and adapt their perspectives accordingly. -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. +5. 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. +6. Familiarity with Rust Project: Members should be familiar with the Rust project's structure, culture, and expectations upon maintainers. This knowledge helps members navigate the ecosystem more effectively, and align their style decisions with the project's broader goals. +7. 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). +8. 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. +9. Openness to Change and Learning: Members should demonstrate a willingness to seek out and receive new information, introspect on their underlying values, change their opinions based on evidence and rationale, and adapt their perspectives accordingly. 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. 11. Ability to weigh subjective decisions, and seek out "better" rather than "perfect": We need a default Rust style, and even in the face of conflicting requirements we still need to make a decision. Style team decisions will attempt to best satisfy most members of the Rust community, but can never be perfect. Members will need to keep this in mind and help the style team make the best consent-based decisions it can.