From 77fc18b3e1cf0320da363d83d68246c1e611525e Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 1 Dec 2022 01:00:38 +0000 Subject: [PATCH 01/42] Add initial team policy document --- team-policy.md | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 team-policy.md diff --git a/team-policy.md b/team-policy.md new file mode 100644 index 0000000..dcbd6b1 --- /dev/null +++ b/team-policy.md @@ -0,0 +1,50 @@ +# Style Team Policy Document + +This is a living document tracking the active policies of the style team. It is intended to fill a similar role to the books that many[^1] teams[^2] maintain[^3] independently[^4] with the intent that eventually these can be integrated into a central policy repository for all teams in the rust-lang organization. + +**Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html + +## Aims: Evolving the Rust Style over time + +1. Selecting styling for new Rust constructs +1. Evolving the existing style over the course of Rust editions (without breaking backwards compatibility) +1. Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms + +## Domains + +1. [Style Guide] +1. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) +1. [#T-style] and #T-style/private zulip streams +1. rust-lang issues with the `T-style` or `T-style-nominated` labels + +## Membership + +* Lead: Caleb Cartwright ([@calebcartwright](https://github.com/calebcartwright)) +* Jane Losare-Lusby ([@yaahc](https://github.com/yaahc)) +* Josh Triplett ([@joshtriplett](https://github.com/joshtriplett)) +* Michael Goulet ([@compiler-errors](https://github.com/compiler-errors)) + +## Meetings + +The style team meets weekly on wednesdays at 11:30am PST for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. + +Unless otherwise noted, all of our meetings are open to the public for anyone to attend. You will find the timing and event details on our [style team calendar](TODO). We publish notes and minutes in written form in this github repository. + +## Membership + +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. + +## Style Guide Evolution + +The Rust style guide will generally match the latest version of the Rust style; the style team does not plan to maintain multiple branches of the style guide for different editions, in part because formatting for new constructs will apply to any edition supporting those constructs. + +Whenever possible, style decisions should be made before a new construct is stabilized. However, style decisions shall not be considered a blocker for stabilization. + +[^1]: https://rust-lang.github.io/compiler-team/ +[^2]: https://lang-team.rust-lang.org/ +[^3]: https://std-dev-guide.rust-lang.org/ +[^4]: https://rust-lang.github.io/types-team/ +[Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md +[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style \ No newline at end of file From 32ecf6ab69c196d10264dfd5de387b719ee5b85a Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 1 Dec 2022 01:04:45 +0000 Subject: [PATCH 02/42] fix broken citations --- team-policy.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/team-policy.md b/team-policy.md index dcbd6b1..a09fcd9 100644 --- a/team-policy.md +++ b/team-policy.md @@ -42,9 +42,10 @@ The Rust style guide will generally match the latest version of the Rust style; Whenever possible, style decisions should be made before a new construct is stabilized. However, style decisions shall not be considered a blocker for stabilization. +[Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md +[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style + [^1]: https://rust-lang.github.io/compiler-team/ [^2]: https://lang-team.rust-lang.org/ [^3]: https://std-dev-guide.rust-lang.org/ -[^4]: https://rust-lang.github.io/types-team/ -[Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md -[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style \ No newline at end of file +[^4]: https://rust-lang.github.io/types-team/ \ No newline at end of file From c63c3d4da2e1e26733bc348b64ea23aee40c7da2 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:00:13 +0000 Subject: [PATCH 03/42] update policy doc and split out charter --- charter.md | 29 +++++++++++ team-policy.md | 129 +++++++++++++++++++++++++++++++++++++++++-------- 2 files changed, 137 insertions(+), 21 deletions(-) create mode 100644 charter.md diff --git a/charter.md b/charter.md new file mode 100644 index 0000000..9bfcbcd --- /dev/null +++ b/charter.md @@ -0,0 +1,29 @@ +# Style Team + +## Aims: Evolving the Rust Style over time + +1. Selecting styling for new Rust constructs +1. Evolving the existing style over the course of Rust editions (without breaking backwards compatibility) +1. Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms + +## Domains + +1. [Style Guide] +1. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) +1. [#T-style] and #T-style/private zulip streams +1. `rust-lang` issues with the `T-style` or `T-style-nominated` labels + +## Membership + +* Lead: Caleb Cartwright ([@calebcartwright](https://github.com/calebcartwright)) +* Jane Losare-Lusby ([@yaahc](https://github.com/yaahc)) +* Josh Triplett ([@joshtriplett](https://github.com/joshtriplett)) +* Michael Goulet ([@compiler-errors](https://github.com/compiler-errors)) + +## Membership + +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. + +TODO note about people being able to ask for an invite to be considered \ No newline at end of file diff --git a/team-policy.md b/team-policy.md index a09fcd9..9e94529 100644 --- a/team-policy.md +++ b/team-policy.md @@ -3,38 +3,124 @@ This is a living document tracking the active policies of the style team. It is intended to fill a similar role to the books that many[^1] teams[^2] maintain[^3] independently[^4] with the intent that eventually these can be integrated into a central policy repository for all teams in the rust-lang organization. **Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html +**Charter**: TODO -## Aims: Evolving the Rust Style over time +## Meetings -1. Selecting styling for new Rust constructs -1. Evolving the existing style over the course of Rust editions (without breaking backwards compatibility) -1. Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms +The style team meets weekly on wednesdays at 12:30am PST for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. -## Domains +Unless otherwise noted, all of our meetings are open to the public for anyone to attend. You will find the timing and event details on our [style team calendar](https://calendar.google.com/calendar/embed?src=d0564ed914a41cf4915bd5ebe6e2e4ec0ee1293fdc1d09d6f5bdb27d4f91c083%40group.calendar.google.com&ctz=America%2FLos_Angeles). We publish notes and minutes in written form in this github repository. -1. [Style Guide] -1. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) -1. [#T-style] and #T-style/private zulip streams -1. rust-lang issues with the `T-style` or `T-style-nominated` labels +### [Agenda, Backlog, and Minutes](https://hackmd.io/@yaah/B1GZrzv4j) -## Membership +The style team stores it's agendas, backlog, and meeting minutes in a single live hackmd document (rotating as necessary when the documents reach their length limit). -* Lead: Caleb Cartwright ([@calebcartwright](https://github.com/calebcartwright)) -* Jane Losare-Lusby ([@yaahc](https://github.com/yaahc)) -* Josh Triplett ([@joshtriplett](https://github.com/joshtriplett)) -* Michael Goulet ([@compiler-errors](https://github.com/compiler-errors)) +The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the secretary and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The secretary is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. -## Meetings +#### Inform / Explore / Decide agenda item classification + +Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as reports or status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. + +We identify the desired outcome in advanced to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitators responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the secretary to read out loud what has been written in the notes. + +The agenda backlog and minutes document is structured according to this template: + +```md +# T-style Minutes + +Meeting Link: https://meet.jit.si/t-style-style-team-task-force + +## Action Items + +### Pending + +* owner: bullet point list of items that are in progress and assigned to a specific person + +### Completed + +- [ ] owner: check list of items that are completed or assumed to be complete +- [x] owner: items are checked off once they've been reviewed in a meeting, confirmed complete, and given any relevant final status updates. +- [x] owner: after a meeting the items that were checked off are moved into the `#### Completed Action Items` section of the meeting they were reviewed in by the secretary + +## Backlog + +* Bullet point list of items that have not been started or assigned yet + +## Next Meeting Date + +### Attendance + +### Agenda + +* (inform) bullet point list of proposed agenda items (labeled either inform, explore, or decide) +* Meeting Check-out + +### Minutes + +#### Individual Agenda Items + +Notes related to the given agenda item + +#### Completed Action Items + +## Previous Meeting Dates + +``` +### Meeting Check-out + +The style team wraps up the content part of our meetings 5-10 minutes before team members have to leave to make room for regular meeting evaluations. Meeting evaluations are an integral part of every meeting. We end the meeting with one or two rounds on: + +* “What worked well in the meeting?” +* “What could be improved in future meetings?” +* “Is there anything you are carrying out of the meeting that you’d like to get off your chest now?” + +Meeting evaluations are an opportunity to learn from our meetings. We can either talk about content, process, or interpersonal dynamics. We utilize meeting evaluations to help ourselves inhabit a growth mindset. Our goal is to have meetings which are well-run, refreshing, connecting, and energizing. We achieve this goal by giving space for people to speak up about both the positive and negative aspects of how we're working together so that we can prioritize continuous improvement and positive connections. + +## Operational Roles + +The style team has various operational roles to delegate releated and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement. + +### Operational Lead + +Current Holder: @calebcartwright +Next Feedback Date: TODO + +In order to stay in touch with where we want to be heading in the future, we need leadership. A team leader is paying attention to the team’s operations in relation to the team’s aim. What needs to be done, who agreed to do it. What is in the future to decide? + +Responsibilities: + +* Pays attention to the operation of the team +* Pays attention to the team members +* Reports wider context to the team + +### Facilitator + +Current Holder: @yaahc +Next Feedback Date: Wednesday 2023-02-01 + +In order to be present with each other, we need a good facilitator . Facilitators run meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. + +Responsibilities: + +* Facilitates team meetings. +* Pays attention to equivalence[^5] during meetings. +* Supports planning of the agenda. +* Distinguishes facilitator voice from team member voice. -The style team meets weekly on wednesdays at 11:30am PST for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. +### Secretary -Unless otherwise noted, all of our meetings are open to the public for anyone to attend. You will find the timing and event details on our [style team calendar](TODO). We publish notes and minutes in written form in this github repository. +Current Holder: @calebcartwright +Next Feedback Date: TODO -## Membership +In order to manage continuity with the team’s past, we need to have written records. The secretary manages the notes during the meeting, makes sure the minutes are distributed and accessible. The secretary also manages the records of the team and is the interpreter of policies. -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. +Responsibilities: -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. +* Makes sure meeting minutes are taken, approved, and stored. +* Keeps track of all documents of the team. +* Interprets the meeting minutes in case of disagreement. +* Supports planning the agenda from the backlog. + * Tracking when policies and roles are due for review. ## Style Guide Evolution @@ -48,4 +134,5 @@ Whenever possible, style decisions should be made before a new construct is stab [^1]: https://rust-lang.github.io/compiler-team/ [^2]: https://lang-team.rust-lang.org/ [^3]: https://std-dev-guide.rust-lang.org/ -[^4]: https://rust-lang.github.io/types-team/ \ No newline at end of file +[^4]: https://rust-lang.github.io/types-team/ +[^5]: Equality, making sure everyone's voices and feedback are receiving equitable attention. \ No newline at end of file From 429714475a5c45853b85e366450d37023ec1e2f7 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:01:56 +0000 Subject: [PATCH 04/42] add missing links --- charter.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/charter.md b/charter.md index 9bfcbcd..7d2457f 100644 --- a/charter.md +++ b/charter.md @@ -26,4 +26,7 @@ The Rust style team shall have at least 3 members and at most 8. If the team has 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. -TODO note about people being able to ask for an invite to be considered \ No newline at end of file +TODO note about people being able to ask for an invite to be considered + +[Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md +[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style \ No newline at end of file From 14fd9f60872152dcfa53add076466bfb5ca722b6 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:02:33 +0000 Subject: [PATCH 05/42] leave roles in the team-policy rather than charter --- charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.md b/charter.md index 7d2457f..8c4777b 100644 --- a/charter.md +++ b/charter.md @@ -15,7 +15,7 @@ ## Membership -* Lead: Caleb Cartwright ([@calebcartwright](https://github.com/calebcartwright)) +* Caleb Cartwright ([@calebcartwright](https://github.com/calebcartwright)) * Jane Losare-Lusby ([@yaahc](https://github.com/yaahc)) * Josh Triplett ([@joshtriplett](https://github.com/joshtriplett)) * Michael Goulet ([@compiler-errors](https://github.com/compiler-errors)) From 2beefa212a797e91319000fc85df9a7de540ecde Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:13:01 +0000 Subject: [PATCH 06/42] expand todo on requesting invites --- charter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/charter.md b/charter.md index 8c4777b..3bdec7d 100644 --- a/charter.md +++ b/charter.md @@ -26,7 +26,9 @@ The Rust style team shall have at least 3 members and at most 8. If the team has 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. -TODO note about people being able to ask for an invite to be considered +### Becoming a member of T-Style + +Contributors who believe they'd be a good fit for the style team are encouraged to request an invite to the team. 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. [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md [#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style \ No newline at end of file From ad5c7f993c8d4af5745e39e1e97148b68d45982b Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:14:12 +0000 Subject: [PATCH 07/42] switch to bullets for links at top of doc --- team-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/team-policy.md b/team-policy.md index 9e94529..9c9ee7f 100644 --- a/team-policy.md +++ b/team-policy.md @@ -2,8 +2,8 @@ This is a living document tracking the active policies of the style team. It is intended to fill a similar role to the books that many[^1] teams[^2] maintain[^3] independently[^4] with the intent that eventually these can be integrated into a central policy repository for all teams in the rust-lang organization. -**Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html -**Charter**: TODO +* **Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html +* **Charter**: TODO ## Meetings From 2b5fb8f3b411ce99b46d4d35a79549c7048a52d4 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:16:16 +0000 Subject: [PATCH 08/42] add everytimezone link --- team-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/team-policy.md b/team-policy.md index 9c9ee7f..4eba1f8 100644 --- a/team-policy.md +++ b/team-policy.md @@ -7,9 +7,9 @@ This is a living document tracking the active policies of the style team. It is ## Meetings -The style team meets weekly on wednesdays at 12:30am PST for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. +The style team meets weekly on wednesdays at 12:30am PST [(everytimezone link)](https://everytimezone.com/s/3f88a253) for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. -Unless otherwise noted, all of our meetings are open to the public for anyone to attend. You will find the timing and event details on our [style team calendar](https://calendar.google.com/calendar/embed?src=d0564ed914a41cf4915bd5ebe6e2e4ec0ee1293fdc1d09d6f5bdb27d4f91c083%40group.calendar.google.com&ctz=America%2FLos_Angeles). We publish notes and minutes in written form in this github repository. +Unless otherwise noted, all of our meetings are public and open for anyone to attend. You will find the timing and event details on our [style team calendar](https://calendar.google.com/calendar/embed?src=d0564ed914a41cf4915bd5ebe6e2e4ec0ee1293fdc1d09d6f5bdb27d4f91c083%40group.calendar.google.com&ctz=America%2FLos_Angeles). We publish notes and minutes in written form in this github repository. ### [Agenda, Backlog, and Minutes](https://hackmd.io/@yaah/B1GZrzv4j) From 094c7417973b7845e3acba2f7fdd26f74e67c43b Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:18:03 +0000 Subject: [PATCH 09/42] switch link to more intuitive location --- team-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/team-policy.md b/team-policy.md index 4eba1f8..eee0f0a 100644 --- a/team-policy.md +++ b/team-policy.md @@ -11,9 +11,9 @@ The style team meets weekly on wednesdays at 12:30am PST [(everytimezone link)]( Unless otherwise noted, all of our meetings are public and open for anyone to attend. You will find the timing and event details on our [style team calendar](https://calendar.google.com/calendar/embed?src=d0564ed914a41cf4915bd5ebe6e2e4ec0ee1293fdc1d09d6f5bdb27d4f91c083%40group.calendar.google.com&ctz=America%2FLos_Angeles). We publish notes and minutes in written form in this github repository. -### [Agenda, Backlog, and Minutes](https://hackmd.io/@yaah/B1GZrzv4j) +### Agenda, Backlog, and Minutes -The style team stores it's agendas, backlog, and meeting minutes in a single live hackmd document (rotating as necessary when the documents reach their length limit). +The style team stores it's agendas, backlog, and meeting minutes in a single live [hackmd document](https://hackmd.io/@yaah/B1GZrzv4j) (rotating as necessary when the documents reach their length limit). The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the secretary and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The secretary is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. From 8b7f95e748391e6e3d938717e42246065f2bdf1f Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:19:02 +0000 Subject: [PATCH 10/42] place operational roles section before meeting section so it can backreference it --- team-policy.md | 92 +++++++++++++++++++++++++------------------------- 1 file changed, 46 insertions(+), 46 deletions(-) diff --git a/team-policy.md b/team-policy.md index eee0f0a..cf927cd 100644 --- a/team-policy.md +++ b/team-policy.md @@ -5,6 +5,52 @@ This is a living document tracking the active policies of the style team. It is * **Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html * **Charter**: TODO +## Operational Roles + +The style team has various operational roles to delegate releated and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement. + +### Operational Lead + +Current Holder: @calebcartwright +Next Feedback Date: TODO + +In order to stay in touch with where we want to be heading in the future, we need leadership. A team leader is paying attention to the team’s operations in relation to the team’s aim. What needs to be done, who agreed to do it. What is in the future to decide? + +Responsibilities: + +* Pays attention to the operation of the team +* Pays attention to the team members +* Reports wider context to the team + +### Facilitator + +Current Holder: @yaahc +Next Feedback Date: Wednesday 2023-02-01 + +In order to be present with each other, we need a good facilitator . Facilitators run meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. + +Responsibilities: + +* Facilitates team meetings. +* Pays attention to equivalence[^5] during meetings. +* Supports planning of the agenda. +* Distinguishes facilitator voice from team member voice. + +### Secretary + +Current Holder: @calebcartwright +Next Feedback Date: TODO + +In order to manage continuity with the team’s past, we need to have written records. The secretary manages the notes during the meeting, makes sure the minutes are distributed and accessible. The secretary also manages the records of the team and is the interpreter of policies. + +Responsibilities: + +* Makes sure meeting minutes are taken, approved, and stored. +* Keeps track of all documents of the team. +* Interprets the meeting minutes in case of disagreement. +* Supports planning the agenda from the backlog. + * Tracking when policies and roles are due for review. + ## Meetings The style team meets weekly on wednesdays at 12:30am PST [(everytimezone link)](https://everytimezone.com/s/3f88a253) for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. @@ -76,52 +122,6 @@ The style team wraps up the content part of our meetings 5-10 minutes before tea Meeting evaluations are an opportunity to learn from our meetings. We can either talk about content, process, or interpersonal dynamics. We utilize meeting evaluations to help ourselves inhabit a growth mindset. Our goal is to have meetings which are well-run, refreshing, connecting, and energizing. We achieve this goal by giving space for people to speak up about both the positive and negative aspects of how we're working together so that we can prioritize continuous improvement and positive connections. -## Operational Roles - -The style team has various operational roles to delegate releated and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement. - -### Operational Lead - -Current Holder: @calebcartwright -Next Feedback Date: TODO - -In order to stay in touch with where we want to be heading in the future, we need leadership. A team leader is paying attention to the team’s operations in relation to the team’s aim. What needs to be done, who agreed to do it. What is in the future to decide? - -Responsibilities: - -* Pays attention to the operation of the team -* Pays attention to the team members -* Reports wider context to the team - -### Facilitator - -Current Holder: @yaahc -Next Feedback Date: Wednesday 2023-02-01 - -In order to be present with each other, we need a good facilitator . Facilitators run meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. - -Responsibilities: - -* Facilitates team meetings. -* Pays attention to equivalence[^5] during meetings. -* Supports planning of the agenda. -* Distinguishes facilitator voice from team member voice. - -### Secretary - -Current Holder: @calebcartwright -Next Feedback Date: TODO - -In order to manage continuity with the team’s past, we need to have written records. The secretary manages the notes during the meeting, makes sure the minutes are distributed and accessible. The secretary also manages the records of the team and is the interpreter of policies. - -Responsibilities: - -* Makes sure meeting minutes are taken, approved, and stored. -* Keeps track of all documents of the team. -* Interprets the meeting minutes in case of disagreement. -* Supports planning the agenda from the backlog. - * Tracking when policies and roles are due for review. - ## Style Guide Evolution The Rust style guide will generally match the latest version of the Rust style; the style team does not plan to maintain multiple branches of the style guide for different editions, in part because formatting for new constructs will apply to any edition supporting those constructs. From b4d6b5b25adf54e95c437c48b541c73337bed472 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:19:38 +0000 Subject: [PATCH 11/42] add bullet points to roles section --- team-policy.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/team-policy.md b/team-policy.md index cf927cd..61198ea 100644 --- a/team-policy.md +++ b/team-policy.md @@ -11,8 +11,8 @@ The style team has various operational roles to delegate releated and ongoing wo ### Operational Lead -Current Holder: @calebcartwright -Next Feedback Date: TODO +* Current Holder: @calebcartwright +* Next Feedback Date: TODO In order to stay in touch with where we want to be heading in the future, we need leadership. A team leader is paying attention to the team’s operations in relation to the team’s aim. What needs to be done, who agreed to do it. What is in the future to decide? @@ -24,8 +24,8 @@ Responsibilities: ### Facilitator -Current Holder: @yaahc -Next Feedback Date: Wednesday 2023-02-01 +* Current Holder: @yaahc +* Next Feedback Date: Wednesday 2023-02-01 In order to be present with each other, we need a good facilitator . Facilitators run meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. @@ -38,8 +38,8 @@ Responsibilities: ### Secretary -Current Holder: @calebcartwright -Next Feedback Date: TODO +* Current Holder: @calebcartwright +* Next Feedback Date: TODO In order to manage continuity with the team’s past, we need to have written records. The secretary manages the notes during the meeting, makes sure the minutes are distributed and accessible. The secretary also manages the records of the team and is the interpreter of policies. From e0c8a426eaf08a5ef465430de9865a0c3e9f7485 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:20:36 +0000 Subject: [PATCH 12/42] hyperlink github names --- team-policy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/team-policy.md b/team-policy.md index 61198ea..2c2d3dc 100644 --- a/team-policy.md +++ b/team-policy.md @@ -11,7 +11,7 @@ The style team has various operational roles to delegate releated and ongoing wo ### Operational Lead -* Current Holder: @calebcartwright +* Current Holder: [@calebcartwright](https://github.com/calebcartwright) * Next Feedback Date: TODO In order to stay in touch with where we want to be heading in the future, we need leadership. A team leader is paying attention to the team’s operations in relation to the team’s aim. What needs to be done, who agreed to do it. What is in the future to decide? @@ -24,7 +24,7 @@ Responsibilities: ### Facilitator -* Current Holder: @yaahc +* Current Holder: [@yaahc](https://github.com/yaahc) * Next Feedback Date: Wednesday 2023-02-01 In order to be present with each other, we need a good facilitator . Facilitators run meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. @@ -38,7 +38,7 @@ Responsibilities: ### Secretary -* Current Holder: @calebcartwright +* Current Holder: [@calebcartwright](https://github.com/calebcartwright) * Next Feedback Date: TODO In order to manage continuity with the team’s past, we need to have written records. The secretary manages the notes during the meeting, makes sure the minutes are distributed and accessible. The secretary also manages the records of the team and is the interpreter of policies. From 407c94c2ba6d33d2862b86fef98b81bff58cdb36 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:24:52 +0000 Subject: [PATCH 13/42] remove some redundant language --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index 2c2d3dc..db0301d 100644 --- a/team-policy.md +++ b/team-policy.md @@ -65,7 +65,7 @@ The agenda should be prepared in advanced of each meeting by the facilitator wit #### Inform / Explore / Decide agenda item classification -Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as reports or status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. +Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. We identify the desired outcome in advanced to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitators responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the secretary to read out loud what has been written in the notes. From e67931f22557e85388ba650377f093688cd2b447 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 19:25:58 +0000 Subject: [PATCH 14/42] improve language --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index db0301d..3a27f74 100644 --- a/team-policy.md +++ b/team-policy.md @@ -69,7 +69,7 @@ Agenda items are labeled according to their desired outcome. There are three pos We identify the desired outcome in advanced to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitators responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the secretary to read out loud what has been written in the notes. -The agenda backlog and minutes document is structured according to this template: +The agenda backlog and minutes document is structured according to the following template: ```md # T-style Minutes From e02e90b085bc02d24d4a7ea1f28e26a549af9be8 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 13:54:57 -0800 Subject: [PATCH 15/42] Update team-policy.md Co-authored-by: Michael Goulet --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index 3a27f74..b646770 100644 --- a/team-policy.md +++ b/team-policy.md @@ -53,7 +53,7 @@ Responsibilities: ## Meetings -The style team meets weekly on wednesdays at 12:30am PST [(everytimezone link)](https://everytimezone.com/s/3f88a253) for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. +The style team meets weekly on wednesdays at 12:30pm PST [(everytimezone link)](https://everytimezone.com/s/3f88a253) for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. Unless otherwise noted, all of our meetings are public and open for anyone to attend. You will find the timing and event details on our [style team calendar](https://calendar.google.com/calendar/embed?src=d0564ed914a41cf4915bd5ebe6e2e4ec0ee1293fdc1d09d6f5bdb27d4f91c083%40group.calendar.google.com&ctz=America%2FLos_Angeles). We publish notes and minutes in written form in this github repository. From b0c4f8e58e62628a315675aac597c637a005fc60 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 22:00:25 +0000 Subject: [PATCH 16/42] remove redundant header --- charter.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/charter.md b/charter.md index 3bdec7d..aa9da81 100644 --- a/charter.md +++ b/charter.md @@ -20,8 +20,6 @@ * Josh Triplett ([@joshtriplett](https://github.com/joshtriplett)) * Michael Goulet ([@compiler-errors](https://github.com/compiler-errors)) -## Membership - 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. From 48f1e6e903fd896e01602a1e505175f747936a3d Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 15:31:27 -0800 Subject: [PATCH 17/42] Update charter.md Co-authored-by: Josh Triplett --- charter.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charter.md b/charter.md index aa9da81..7692ae5 100644 --- a/charter.md +++ b/charter.md @@ -3,8 +3,8 @@ ## Aims: Evolving the Rust Style over time 1. Selecting styling for new Rust constructs -1. Evolving the existing style over the course of Rust editions (without breaking backwards compatibility) -1. Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms +2. Evolving the existing style over the course of Rust editions (without breaking backwards compatibility) +3. Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms ## Domains From bcfb47bbdb4bc0161259e4c704208adc6769675d Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 21 Dec 2022 15:31:34 -0800 Subject: [PATCH 18/42] Update charter.md Co-authored-by: Josh Triplett --- charter.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/charter.md b/charter.md index 7692ae5..2406131 100644 --- a/charter.md +++ b/charter.md @@ -9,9 +9,9 @@ ## Domains 1. [Style Guide] -1. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) -1. [#T-style] and #T-style/private zulip streams -1. `rust-lang` issues with the `T-style` or `T-style-nominated` labels +2. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) +3. [#T-style] and #T-style/private zulip streams +4. `rust-lang` issues with the `T-style` or `T-style-nominated` labels ## Membership From 517e482ef3707889d106e7ec4292a29f80f1f314 Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Tue, 3 Jan 2023 14:54:27 -0800 Subject: [PATCH 19/42] Fix typo s/T-style-nominated/I-style-nominated/ --- charter.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charter.md b/charter.md index 2406131..12737b9 100644 --- a/charter.md +++ b/charter.md @@ -11,7 +11,7 @@ 1. [Style Guide] 2. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) 3. [#T-style] and #T-style/private zulip streams -4. `rust-lang` issues with the `T-style` or `T-style-nominated` labels +4. `rust-lang` issues with the `T-style` or `I-style-nominated` labels ## Membership @@ -29,4 +29,4 @@ Members of the style team are nominated by existing members. All existing member Contributors who believe they'd be a good fit for the style team are encouraged to request an invite to the team. 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. [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md -[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style \ No newline at end of file +[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style From 17bf5975fe8985a73472d264276e90e3eaaef33c Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 4 Jan 2023 10:28:43 -0800 Subject: [PATCH 20/42] Update team-policy.md Co-authored-by: Caleb Cartwright --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index b646770..c4450c2 100644 --- a/team-policy.md +++ b/team-policy.md @@ -7,7 +7,7 @@ This is a living document tracking the active policies of the style team. It is ## Operational Roles -The style team has various operational roles to delegate releated and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement. +The style team has various operational roles to delegate related and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement. ### Operational Lead From cfc72e46d9640e0627fa99c9cb447be08e15a4b8 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 4 Jan 2023 10:28:54 -0800 Subject: [PATCH 21/42] Update team-policy.md Co-authored-by: Caleb Cartwright --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index c4450c2..dec2419 100644 --- a/team-policy.md +++ b/team-policy.md @@ -27,7 +27,7 @@ Responsibilities: * Current Holder: [@yaahc](https://github.com/yaahc) * Next Feedback Date: Wednesday 2023-02-01 -In order to be present with each other, we need a good facilitator . Facilitators run meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. +In order to be present with each other, we need a good facilitator. The facilitator runs meetings according to the format of meetings and decision making adopted by the group. Leader and facilitator are separate roles because facilitation and overseeing operations are different skill sets. They can be held by the same individual. Responsibilities: From 85b6c61c26ad35e91c89e3221700d67dd6647cdc Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 4 Jan 2023 10:32:39 -0800 Subject: [PATCH 22/42] Update team-policy.md Co-authored-by: Caleb Cartwright --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index dec2419..547966f 100644 --- a/team-policy.md +++ b/team-policy.md @@ -59,7 +59,7 @@ Unless otherwise noted, all of our meetings are public and open for anyone to at ### Agenda, Backlog, and Minutes -The style team stores it's agendas, backlog, and meeting minutes in a single live [hackmd document](https://hackmd.io/@yaah/B1GZrzv4j) (rotating as necessary when the documents reach their length limit). +The style team stores its agendas, backlog, and meeting minutes in a single live [hackmd document](https://hackmd.io/@yaah/B1GZrzv4j) (rotating as necessary when the documents reach their length limit). The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the secretary and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The secretary is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. From 473c7f998141846e69045b5c2600f8d5e6b87173 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 4 Jan 2023 10:36:14 -0800 Subject: [PATCH 23/42] Update team-policy.md Co-authored-by: Caleb Cartwright --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index 547966f..ad0b60a 100644 --- a/team-policy.md +++ b/team-policy.md @@ -67,7 +67,7 @@ The agenda should be prepared in advanced of each meeting by the facilitator wit Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. -We identify the desired outcome in advanced to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitators responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the secretary to read out loud what has been written in the notes. +We identify the desired outcome in advance to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitator's responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the secretary to read out loud what has been written in the notes. The agenda backlog and minutes document is structured according to the following template: From 9db701b5dde90d2d45aa692b51f8b2421c016ce1 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 4 Jan 2023 18:53:36 +0000 Subject: [PATCH 24/42] move important policy to the top --- team-policy.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/team-policy.md b/team-policy.md index ad0b60a..5031e13 100644 --- a/team-policy.md +++ b/team-policy.md @@ -5,6 +5,12 @@ This is a living document tracking the active policies of the style team. It is * **Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html * **Charter**: TODO +## Style Guide Evolution + +The Rust style guide will generally match the latest version of the Rust style; the style team does not plan to maintain multiple branches of the style guide for different editions, in part because formatting for new constructs will apply to any edition supporting those constructs. + +Whenever possible, style decisions should be made before a new construct is stabilized. However, style decisions shall not be considered a blocker for stabilization. + ## Operational Roles The style team has various operational roles to delegate related and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement. @@ -122,12 +128,6 @@ The style team wraps up the content part of our meetings 5-10 minutes before tea Meeting evaluations are an opportunity to learn from our meetings. We can either talk about content, process, or interpersonal dynamics. We utilize meeting evaluations to help ourselves inhabit a growth mindset. Our goal is to have meetings which are well-run, refreshing, connecting, and energizing. We achieve this goal by giving space for people to speak up about both the positive and negative aspects of how we're working together so that we can prioritize continuous improvement and positive connections. -## Style Guide Evolution - -The Rust style guide will generally match the latest version of the Rust style; the style team does not plan to maintain multiple branches of the style guide for different editions, in part because formatting for new constructs will apply to any edition supporting those constructs. - -Whenever possible, style decisions should be made before a new construct is stabilized. However, style decisions shall not be considered a blocker for stabilization. - [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md [#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style @@ -135,4 +135,4 @@ Whenever possible, style decisions should be made before a new construct is stab [^2]: https://lang-team.rust-lang.org/ [^3]: https://std-dev-guide.rust-lang.org/ [^4]: https://rust-lang.github.io/types-team/ -[^5]: Equality, making sure everyone's voices and feedback are receiving equitable attention. \ No newline at end of file +[^5]: Equality, making sure everyone's voices and feedback are receiving equitable attention. From 3f3399d2a4a7ba0387ecfe345c591077259f957d Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 4 Jan 2023 17:56:39 -0800 Subject: [PATCH 25/42] Update charter.md Co-authored-by: Josh Triplett --- charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.md b/charter.md index 12737b9..54cde6c 100644 --- a/charter.md +++ b/charter.md @@ -26,7 +26,7 @@ Members of the style team are nominated by existing members. All existing member ### Becoming a member of T-Style -Contributors who believe they'd be a good fit for the style team are encouraged to request an invite to the team. 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. +Contributors who believe they'd be a good fit for the style team are encouraged to request an invite 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. [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md [#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style From ff74ae236cd24d00ddbc1227d63b151a8125ce98 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 18 Jan 2023 19:20:38 +0000 Subject: [PATCH 26/42] add new policy from 2023-01-11 meeting action items --- team-policy.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/team-policy.md b/team-policy.md index 5031e13..bb4b9eb 100644 --- a/team-policy.md +++ b/team-policy.md @@ -69,6 +69,8 @@ The style team stores its agendas, backlog, and meeting minutes in a single live The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the secretary and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The secretary is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. +Consent not needed to add to items to the backlog, anybody is welcome to add items to the backlog, but consent needed to move from backlog to agenda (since agendas themselves require consent). An item being present on the backlog does not represent a commitment by the style team. + #### Inform / Explore / Decide agenda item classification Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. @@ -105,7 +107,9 @@ Meeting Link: https://meet.jit.si/t-style-style-team-task-force ### Agenda * (inform) bullet point list of proposed agenda items (labeled either inform, explore, or decide) +* Review Action Items * Meeting Check-out + * Do not record in minutes, exceptions can be made with consent of team ### Minutes @@ -128,6 +132,8 @@ The style team wraps up the content part of our meetings 5-10 minutes before tea Meeting evaluations are an opportunity to learn from our meetings. We can either talk about content, process, or interpersonal dynamics. We utilize meeting evaluations to help ourselves inhabit a growth mindset. Our goal is to have meetings which are well-run, refreshing, connecting, and energizing. We achieve this goal by giving space for people to speak up about both the positive and negative aspects of how we're working together so that we can prioritize continuous improvement and positive connections. +Meeting check-outs are considered private and internal to the style team and are not recorded as part of our minutes. Exceptions to this can be made via an operational consent decision by the team, and are often useful in cases such as when new backlog or action items come up during the check-out. + [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md [#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style From 5a52fc74d185195177895d80d73e09e324c4b30f Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 01:25:08 +0000 Subject: [PATCH 27/42] address zulip contact and be a little extra in the process --- charter.md | 31 +++++++++++++++++++++++++------ 1 file changed, 25 insertions(+), 6 deletions(-) diff --git a/charter.md b/charter.md index 54cde6c..ed649eb 100644 --- a/charter.md +++ b/charter.md @@ -15,18 +15,37 @@ ## Membership -* Caleb Cartwright ([@calebcartwright](https://github.com/calebcartwright)) -* Jane Losare-Lusby ([@yaahc](https://github.com/yaahc)) -* Josh Triplett ([@joshtriplett](https://github.com/joshtriplett)) -* Michael Goulet ([@compiler-errors](https://github.com/compiler-errors)) +* Caleb Cartwright + * Github: ([@calebcartwright](https://github.com/calebcartwright)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/320317-Caleb-Cartwright) +* Jane Losare-Lusby + * Pronouns: she/her + * Github: ([@yaahc](https://github.com/yaahc)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/220273-Jane-Losare-Lusby) + * Spoken Languages: English + * Timezone: PST (GMT-8) + * Other Project Roles + * Error Handling Project Group: Lead + * Rust Foundation: Project Director of Collaboration +* Josh Triplett + * Github: ([@joshtriplett](https://github.com/joshtriplett)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/239881-Josh-Triplett) +* Michael Goulet + * Github: ([@compiler-errors](https://github.com/compiler-errors)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/426609-Michael-Goulet-(compiler-errors)) + +### Membership Policy 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. -### Becoming a member of T-Style +#### Becoming a member of T-Style -Contributors who believe they'd be a good fit for the style team are encouraged to request an invite 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. +Contributors who believe they'd be a good fit for the style team are encouraged to request an invite[^1] 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. + + +[^1]: We suggest reaching out via zulip DM to one of the current team members, and we suggest to defaulting to contacting the lead if you're unsure who to reach out to. [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md [#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style From 23cf5125f98dfed517ceefacd622d560e1778ea6 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 25 Jan 2023 17:32:25 -0800 Subject: [PATCH 28/42] Update charter.md Co-authored-by: Josh Triplett --- charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.md b/charter.md index ed649eb..b6e8059 100644 --- a/charter.md +++ b/charter.md @@ -8,7 +8,7 @@ ## Domains -1. [Style Guide] +1. [Style Guide](https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md) 2. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) 3. [#T-style] and #T-style/private zulip streams 4. `rust-lang` issues with the `T-style` or `I-style-nominated` labels From e89fd3e61076a4cd9018942edcb4bfcc8530caf0 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 25 Jan 2023 17:32:51 -0800 Subject: [PATCH 29/42] Update charter.md Co-authored-by: Josh Triplett --- charter.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/charter.md b/charter.md index b6e8059..066272e 100644 --- a/charter.md +++ b/charter.md @@ -10,8 +10,9 @@ 1. [Style Guide](https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md) 2. [T-style team repo](https://github.com/rust-lang/fmt-rfcs/) -3. [#T-style] and #T-style/private zulip streams -4. `rust-lang` issues with the `T-style` or `I-style-nominated` labels +3. [#T-style](https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style) Zulip stream +4. [#T-style/private](https://rust-lang.zulipchat.com/#narrow/stream/353175-t-style.2Fprivate) Zulip stream +5. `rust-lang` issues with the `T-style` or `I-style-nominated` labels ## Membership From 9c598b1d0905ebf3dd72a441d39552c4b4e27ecc Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 01:45:37 +0000 Subject: [PATCH 30/42] move membership details elsewhere --- README.md | 25 +++++++++++++++++++++++++ charter.md | 26 +++----------------------- 2 files changed, 28 insertions(+), 23 deletions(-) diff --git a/README.md b/README.md index 10de6b2..dd7866e 100644 --- a/README.md +++ b/README.md @@ -87,3 +87,28 @@ principles (in priority order): To see how these principles were decided, see [issue 4](https://github.com/rust-lang-nursery/fmt-rfcs/issues/4). + +## TODO: Rework readme + +For now moving this from the charter.md, will include smoothly in the future + +### Membership + +* Caleb Cartwright + * Github: ([@calebcartwright](https://github.com/calebcartwright)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/320317-Caleb-Cartwright) +* Jane Losare-Lusby + * Pronouns: she/her + * Github: ([@yaahc](https://github.com/yaahc)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/220273-Jane-Losare-Lusby) + * Spoken Languages: English + * Timezone: PST (GMT-8) + * Other Project Roles + * Error Handling Project Group: Lead + * Rust Foundation: Project Director of Collaboration +* Josh Triplett + * Github: ([@joshtriplett](https://github.com/joshtriplett)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/239881-Josh-Triplett) +* Michael Goulet + * Github: ([@compiler-errors](https://github.com/compiler-errors)) + * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/426609-Michael-Goulet-(compiler-errors)) diff --git a/charter.md b/charter.md index 066272e..b495453 100644 --- a/charter.md +++ b/charter.md @@ -16,37 +16,17 @@ ## Membership -* Caleb Cartwright - * Github: ([@calebcartwright](https://github.com/calebcartwright)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/320317-Caleb-Cartwright) -* Jane Losare-Lusby - * Pronouns: she/her - * Github: ([@yaahc](https://github.com/yaahc)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/220273-Jane-Losare-Lusby) - * Spoken Languages: English - * Timezone: PST (GMT-8) - * Other Project Roles - * Error Handling Project Group: Lead - * Rust Foundation: Project Director of Collaboration -* Josh Triplett - * Github: ([@joshtriplett](https://github.com/joshtriplett)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/239881-Josh-Triplett) -* Michael Goulet - * Github: ([@compiler-errors](https://github.com/compiler-errors)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/426609-Michael-Goulet-(compiler-errors)) - -### Membership Policy +The active membership of the style team can be found on [rust-lang.org/governance](https://github.com/rust-lang/team/blob/master/teams/style.toml). 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. -#### Becoming a member of T-Style +### Becoming a member of T-Style Contributors who believe they'd be a good fit for the style team are encouraged to request an invite[^1] 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. - -[^1]: We suggest reaching out via zulip DM to one of the current team members, and we suggest to defaulting to contacting the lead if you're unsure who to reach out to. +[^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. [Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md [#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style From 1b3a4f5f26ac9af32815191b4cd74ac2c45a650b Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 25 Jan 2023 17:50:52 -0800 Subject: [PATCH 31/42] Update charter.md Co-authored-by: Josh Triplett --- charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.md b/charter.md index b495453..58c2d5a 100644 --- a/charter.md +++ b/charter.md @@ -2,7 +2,7 @@ ## Aims: Evolving the Rust Style over time -1. Selecting styling for new Rust constructs +1. Defining the style for new Rust constructs 2. Evolving the existing style over the course of Rust editions (without breaking backwards compatibility) 3. Defining mechanisms to evolve the Rust style while taking backwards compatibility into account, such as via Rust editions or similar mechanisms From 6b6c22a64b8e237843b6b1eb043af366d93db1c5 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 25 Jan 2023 17:51:06 -0800 Subject: [PATCH 32/42] Update team-policy.md Co-authored-by: Josh Triplett --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index bb4b9eb..58198bd 100644 --- a/team-policy.md +++ b/team-policy.md @@ -1,6 +1,6 @@ # Style Team Policy Document -This is a living document tracking the active policies of the style team. It is intended to fill a similar role to the books that many[^1] teams[^2] maintain[^3] independently[^4] with the intent that eventually these can be integrated into a central policy repository for all teams in the rust-lang organization. +This is a living document tracking the active policies of the style team. It is intended to fill a similar role to the books that many[^1] teams[^2] maintain[^3] independently[^4]. If in the future Rust establishes central linking/indexing/aggregating of policies, these will need to appear there. * **Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html * **Charter**: TODO From c236db43ad9958c7c05cf3d3693cef66a38cf141 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 01:52:56 +0000 Subject: [PATCH 33/42] add charter link --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index 58198bd..fb10b21 100644 --- a/team-policy.md +++ b/team-policy.md @@ -3,7 +3,7 @@ This is a living document tracking the active policies of the style team. It is intended to fill a similar role to the books that many[^1] teams[^2] maintain[^3] independently[^4]. If in the future Rust establishes central linking/indexing/aggregating of policies, these will need to appear there. * **Original RFC**: https://rust-lang.github.io/rfcs/3309-style-team.html -* **Charter**: TODO +* **Charter**: https://github.com/rust-lang/fmt-rfcs/blob/master/charter.md ## Style Guide Evolution From 65a0437781a475b2cc3cdfdc8d0f86c84ad3b556 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 25 Jan 2023 17:56:22 -0800 Subject: [PATCH 34/42] Update team-policy.md Co-authored-by: Josh Triplett --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index fb10b21..a4ba23c 100644 --- a/team-policy.md +++ b/team-policy.md @@ -59,7 +59,7 @@ Responsibilities: ## Meetings -The style team meets weekly on wednesdays at 12:30pm PST [(everytimezone link)](https://everytimezone.com/s/3f88a253) for a weekly video sync. Agendas are posted in the [#T-style] zulip stream. +The style team meets weekly on Wednesdays at 12:30pm PST [(everytimezone link)](https://everytimezone.com/s/3f88a253) for a weekly video sync. Agendas are posted in the #T-style zulip stream. Unless otherwise noted, all of our meetings are public and open for anyone to attend. You will find the timing and event details on our [style team calendar](https://calendar.google.com/calendar/embed?src=d0564ed914a41cf4915bd5ebe6e2e4ec0ee1293fdc1d09d6f5bdb27d4f91c083%40group.calendar.google.com&ctz=America%2FLos_Angeles). We publish notes and minutes in written form in this github repository. From 28e8c6e37abd7577337fc2c2aa2e904bd9d960f5 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 01:59:35 +0000 Subject: [PATCH 35/42] remove unused links --- charter.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/charter.md b/charter.md index 58c2d5a..db68f30 100644 --- a/charter.md +++ b/charter.md @@ -27,6 +27,3 @@ Members of the style team are nominated by existing members. All existing member Contributors who believe they'd be a good fit for the style team are encouraged to request an invite[^1] 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. [^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. - -[Style Guide]: https://github.com/rust-lang/fmt-rfcs/blob/master/guide/guide.md -[#T-style]: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style From 2bb813d98c3219551ec3ebff88326f5bb1e8fd6d Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 02:04:10 +0000 Subject: [PATCH 36/42] remove changes to readme --- README.md | 25 ------------------------- 1 file changed, 25 deletions(-) diff --git a/README.md b/README.md index dd7866e..10de6b2 100644 --- a/README.md +++ b/README.md @@ -87,28 +87,3 @@ principles (in priority order): To see how these principles were decided, see [issue 4](https://github.com/rust-lang-nursery/fmt-rfcs/issues/4). - -## TODO: Rework readme - -For now moving this from the charter.md, will include smoothly in the future - -### Membership - -* Caleb Cartwright - * Github: ([@calebcartwright](https://github.com/calebcartwright)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/320317-Caleb-Cartwright) -* Jane Losare-Lusby - * Pronouns: she/her - * Github: ([@yaahc](https://github.com/yaahc)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/220273-Jane-Losare-Lusby) - * Spoken Languages: English - * Timezone: PST (GMT-8) - * Other Project Roles - * Error Handling Project Group: Lead - * Rust Foundation: Project Director of Collaboration -* Josh Triplett - * Github: ([@joshtriplett](https://github.com/joshtriplett)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/239881-Josh-Triplett) -* Michael Goulet - * Github: ([@compiler-errors](https://github.com/compiler-errors)) - * Contact: [Zulip](https://rust-lang.zulipchat.com/#narrow/pm-with/426609-Michael-Goulet-(compiler-errors)) From 9cf35e8022e20efe2903dff4606bbe1f2bcb0748 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 02:11:54 +0000 Subject: [PATCH 37/42] remove meeting link pending further discussion --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index a4ba23c..83040fd 100644 --- a/team-policy.md +++ b/team-policy.md @@ -82,7 +82,7 @@ The agenda backlog and minutes document is structured according to the following ```md # T-style Minutes -Meeting Link: https://meet.jit.si/t-style-style-team-task-force +Meeting Link: ## Action Items From 8eddad2428c8365966a51e9c4ef4e9837632f78d Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 02:34:58 +0000 Subject: [PATCH 38/42] secretary to scribe --- team-policy.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/team-policy.md b/team-policy.md index 83040fd..2d27da9 100644 --- a/team-policy.md +++ b/team-policy.md @@ -42,18 +42,18 @@ Responsibilities: * Supports planning of the agenda. * Distinguishes facilitator voice from team member voice. -### Secretary +### Scribe * Current Holder: [@calebcartwright](https://github.com/calebcartwright) * Next Feedback Date: TODO -In order to manage continuity with the team’s past, we need to have written records. The secretary manages the notes during the meeting, makes sure the minutes are distributed and accessible. The secretary also manages the records of the team and is the interpreter of policies. +In order to manage continuity with the team’s past, we need to have written records. The scribe manages the notes during the meeting, makes sure the minutes are distributed and accessible. Responsibilities: * Makes sure meeting minutes are taken, approved, and stored. * Keeps track of all documents of the team. -* Interprets the meeting minutes in case of disagreement. +* Default interpreter of meeting minutes in cases of disagreement. * Supports planning the agenda from the backlog. * Tracking when policies and roles are due for review. @@ -67,7 +67,7 @@ Unless otherwise noted, all of our meetings are public and open for anyone to at The style team stores its agendas, backlog, and meeting minutes in a single live [hackmd document](https://hackmd.io/@yaah/B1GZrzv4j) (rotating as necessary when the documents reach their length limit). -The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the secretary and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The secretary is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. +The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the scribe and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The scribe is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. Consent not needed to add to items to the backlog, anybody is welcome to add items to the backlog, but consent needed to move from backlog to agenda (since agendas themselves require consent). An item being present on the backlog does not represent a commitment by the style team. @@ -75,7 +75,7 @@ Consent not needed to add to items to the backlog, anybody is welcome to add ite Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. -We identify the desired outcome in advance to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitator's responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the secretary to read out loud what has been written in the notes. +We identify the desired outcome in advance to avoid aimless discussions with unclear goals. The desired outcome can change during discussion as new information becomes available. It is the facilitator's responsibility to notice when this happens and formally make the change in the desired outcome with consent from the rest of the team. Extra clarity can be gained if, for every agenda item, we end by measuring whether we have achieved the desired outcome. Facilitators can make it a habit to pause before moving to a new agenda item by assessing whether the desired outcome has been achieved and by asking the scribe to read out loud what has been written in the notes. The agenda backlog and minutes document is structured according to the following template: @@ -94,7 +94,7 @@ Meeting Link: - [ ] owner: check list of items that are completed or assumed to be complete - [x] owner: items are checked off once they've been reviewed in a meeting, confirmed complete, and given any relevant final status updates. -- [x] owner: after a meeting the items that were checked off are moved into the `#### Completed Action Items` section of the meeting they were reviewed in by the secretary +- [x] owner: after a meeting the items that were checked off are moved into the `#### Completed Action Items` section of the meeting they were reviewed in by the scribe ## Backlog From 8e7be8e198a32f458e7e1d8defbdbc3c89f7575e Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 26 Jan 2023 02:36:04 +0000 Subject: [PATCH 39/42] remove hackmd link --- team-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-policy.md b/team-policy.md index 2d27da9..65574a3 100644 --- a/team-policy.md +++ b/team-policy.md @@ -65,7 +65,7 @@ Unless otherwise noted, all of our meetings are public and open for anyone to at ### Agenda, Backlog, and Minutes -The style team stores its agendas, backlog, and meeting minutes in a single live [hackmd document](https://hackmd.io/@yaah/B1GZrzv4j) (rotating as necessary when the documents reach their length limit). +The style team stores its agendas, backlog, and meeting minutes in a single live hackmd document (rotating as necessary when the documents reach their length limit). The agenda should be prepared in advanced of each meeting by the facilitator with the assistance of the scribe and the lead. The lead is responsible for looking forward and adding agenda items such as new requests from other teams and users or new priorities and goals. The scribe is responsible for looking backwards and adding agenda items from existing work such as items from the backlog or policies that are due for review. The agenda proposal is then presented at the beginning of each meeting by the facilitator for the rest of the team to consent or object too. From d1ca97025e8d1e95557c1bf328627ec38da1e193 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 6 Jul 2023 09:51:34 -0700 Subject: [PATCH 40/42] Update team-policy.md --- team-policy.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/team-policy.md b/team-policy.md index 65574a3..7a5aac8 100644 --- a/team-policy.md +++ b/team-policy.md @@ -71,6 +71,12 @@ The agenda should be prepared in advanced of each meeting by the facilitator wit Consent not needed to add to items to the backlog, anybody is welcome to add items to the backlog, but consent needed to move from backlog to agenda (since agendas themselves require consent). An item being present on the backlog does not represent a commitment by the style team. +#### Interrupting the Agenda + +The style team acknowledges that urgent needs may arise during the meeting. To address these needs, participants may interrupt the meeting by speaking up and immediately saying "Point of Order." This signals to the meeting facilitator and other participants that the following point is not an out-of-order interruption but rather an urgent need that must take priority. This tool is designed for meta-level concerns that take priority over the current discussion, such as the scribe interrupting the meeting to address issues preventing the recording of minutes (and stopping the discussion until they can resume recording minutes), or a team member interrupting a discussion to raise questions of time bounds or team scope. + +The meeting facilitator will then pause the current discussion, allow the participant to raise the point of order to state their concern and allow the team to address that point of order. After resolving the urgent matter, the facilitator will resume the previous discussion or return to the agenda. This policy is intended to ensure that the team can address urgent issues promptly without unnecessarily interrupting the flow of the meeting. + #### Inform / Explore / Decide agenda item classification Agenda items are labeled according to their desired outcome. There are three possible outcomes for any given agenda item, inform, explore, or decide. Each of these outcomes builds upon the previous outcomes. In order to explore an item it must first be understood, and in order to make a decision one must both understand and explore the item first. Inform is used for things such as status updates, and usually involves first a report, followed by a round of clarifying questions. Explore is used for situations where one would like feedback on a potential issue or proposal, and usually involves reaction rounds. Decide is used when the team must reach a decision as a group, and it is usually achieved via a consensus round. From d0cf617d45db02237c38f6c9c2c30ce7e0a7863f Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Thu, 6 Jul 2023 10:06:08 -0700 Subject: [PATCH 41/42] Update team-policy.md Co-authored-by: Josh Triplett --- team-policy.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/team-policy.md b/team-policy.md index 7a5aac8..d100939 100644 --- a/team-policy.md +++ b/team-policy.md @@ -101,6 +101,9 @@ Meeting Link: - [ ] owner: check list of items that are completed or assumed to be complete - [x] owner: items are checked off once they've been reviewed in a meeting, confirmed complete, and given any relevant final status updates. - [x] owner: after a meeting the items that were checked off are moved into the `#### Completed Action Items` section of the meeting they were reviewed in by the scribe +### Granularity + +Action items should not generally list individual feedback/response comments within GitHub threads. An action item should generally be at the level of a GitHub PR, and people can look at the GitHub PR to find out its current status. That status may affect whether the action item is blocked, or who needs to look at it, or whether there are aspects of the action item to discuss in a meeting. ## Backlog From ca7c74b3f495b8a9602d1dce2a9854dd1e42fa71 Mon Sep 17 00:00:00 2001 From: Jane Losare-Lusby Date: Wed, 12 Jul 2023 11:52:39 -0700 Subject: [PATCH 42/42] Update team-policy.md --- team-policy.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/team-policy.md b/team-policy.md index d100939..9ffe260 100644 --- a/team-policy.md +++ b/team-policy.md @@ -11,6 +11,21 @@ The Rust style guide will generally match the latest version of the Rust style; Whenever possible, style decisions should be made before a new construct is stabilized. However, style decisions shall not be considered a blocker for stabilization. +## Policy Review Process + +To maintain the effectiveness and relevance of our policies, the style team implements a policy review process. The following guidelines outline how we conduct policy reviews: + +1. **Associated Review Dates**: Each policy should have a designated review date documented alongside the policy. These review dates are also added to the team's backlog for easy tracking and planning. +2. **Consideration Factors**: When selecting review dates for policies, we consider several factors. These include: + 1. **Confidence Level**: If a policy has recently changed or is relatively new, we opt for a shorter review period. This allows us to course correct quickly if needed. + 2. **Stability and Effectiveness**: Policies that have remained unchanged for a considerable period and have proven effective can have longer review periods. This prevents unnecessary time spent on policies that are working well. +3. **Integration into Regular Meetings**: Policy reviews are treated as regular agenda items during our team meetings. They are discussed and evaluated alongside other topics of importance. +4. Review Process: Policy reviews should use a discussion approach that encourages each team member to provide feedback regarding the policy under review and creates a constructive environment where everyone is heard equally. Our current process is a *round*, in which each person is heard once before anyone responds or chimes in a second time. We start with the prompt, "How effective has this policy been in your experience? Is it serving its intended purpose? How has it worked well, and how can it be improved? Are there other issues with the policy that we should consider?". +5. **Regular Review Cadence**: We review our policies regularly to identify any issues before they escalate into urgent problems proactively. By conducting these reviews systematically, we ensure that our policies remain up-to-date and aligned with our evolving needs. + 1. **Default disposition**: In organizations without a policy review process, policies often remain in effect by default until explicitly rescinded. The policy review process partly reverses that default disposition: policies require regular review and must be renewed to remain in effect. (Such review and renewal still consider all of these other factors, such as the degree of previously established confidence in the policy and its stability over time.) + +By adhering to this policy review process, we aim to maintain a high standard of quality and relevance in our style team policies. + ## Operational Roles The style team has various operational roles to delegate related and ongoing work to specific individuals, to clarify on our operations, and to coordinate sharing feedback with the members in those roles to enable iterative self improvement.