< Design Systems Team
Technical chores
Technical chores rotate every two weeks among the following people:
- Anne Tomasevich
- Roan Kattouw
- Eric Gardner
- Volker E.
Doing the technical chores involves:
- Doing the Codex release on the second Tuesday; follow these instructions.
- When necessary, doing an OOUI release on the second Tuesday; follow these instructions.
Period | Person | Chore | Due date | Status |
---|---|---|---|---|
June 12 - 25, 2023 | Anne | Codex release | June 20 | ✅ v0.13.0 released |
June 26 - July 9, 2023 | Roan | Codex release | July 5[1] | |
OOUI release | July 5[1] | |||
July 10 - 23, 2023 | Eric | Codex release | July 18 | |
July 24 - August 6, 2023 | Roan[2] | Codex release | August 1 | |
August 7 - 20, 2023 | Anne | Codex release | August 15 | |
August 21 - September 3, 2023 | Roan | Codex release | August 29 | |
September 4 - 17, 2023 | Eric | Codex release | September 12 | |
September 18 - October 1, 2023 | Volker | Codex release | September 26 |
Legend
✅ | is fine |
⚠️ | needs attention |
🚨 | is on fire |
🎉 | for your attention but positive |
Link someone's username in the edit-summary to ping them! This will send them an Echo notification!
Team Practices chores
Team practices chores rotate every two weeks among the following people:
- Anne Tomasevich
- Bárbara Martínez Calvo
- Christopher Ciufo
- Eric Gardner
- Roan Kattouw
- Volker E.
Doing the Team Practices chores involves:
- Facilitating our four scrum events: Demo, Estimation, Planning, and Retro.
- What does success look like? Scrum events are meeting their intended purposes (see: Meetings & their purposes).
- Meeting agenda templates can be found in their respective meeting notes docs.
- EasyRetro guidance
- Responding to questions/requests submitted on Slack (typically in #talk-to-design-systems-team):
- At minimum, provide a "first touch" response within 24 hours, and ensure a "next step" response happens within one week.
- If applicable, ensure a Phabricator task is created using the task template linked in Design Systems Team/Working with us
- Ensure that the right people have provided input according to our DACI.
- What does success look like? The requester and DST have a shared understanding of next steps.
- Review & respond to new Phabricator tasks (helpful query: https://phabricator.wikimedia.org/W2927)
- If created by DST, move to appropriate column. If unsure, move to Backlog column.
- If created by someone outside DST: add a comment to the task indicating that we have received the request and will let them know what to expect within one week. Post in #design-systems-team and/or add to next Planning/Estimation agenda.
- Ensure that the right people have provided input according to our DACI.
- Maintaining the DST calendar in partnership with meeting owners.
- What does success look like? Team calendar reflects reality during your assigned chore wheel rotation, accounting for vacations, holidays, etc.
- Maintaining the Team Practices chore wheel
- What does success look like? This page reflects reality for the next 2-3 chore wheel rotations, accounting for vacations, holidays, etc.
Period | Person | Chore | Notes (if needed) |
---|---|---|---|
June 26 - July 9, 2023 | Chris | Team practices | |
July 10 - 23, 2023 | Bárbara | Team practices | |
July 24 - August 6, 2023 | Eric | Team practices | |
August 7 - 20, 2023 | Roan | Team practices | |
August 21 - September 3, 2023 | Volker | Team practices | |
September 4 - 17, 2023 | Anne | Team practices | |
September 18 - October 1, 2023 | Chris | Team practices |
Non-scrum meeting ownership
For meetings outside the scrum framework (see Design Systems Team/Team Processes#Non-scrum events for a complete list), DST follows separate norms outside the chore wheel:
- Rotate meta-facilitator every 3 months; responsibilities include:
- Ensuring an agenda exists for the meeting
- Offering to cancel/reschedule if needed
- Assigning facilitator/timekeeper/notetaker if needed
- Ensure agenda topics are ordered by priority & have assigned time
- If individual topics go over time, the room can take a vote on whether to extend a topic, typically by just 5 mins, or to parking lot it
- When the meeting starts, (optionally) the team votes on ordering
Meeting | Meta-facilitator for July-September 2023 | Meta-facilitator for October-December 2023 | Meta-facilitator for October-December 2023 |
---|---|---|---|
Design Sync | N/A | ||
Engineering/Design Sync | Bárbara | ||
Engineering Enclave | Roan | ||
Tea Time | N/A | ||
Steering | Chris | ||
Front-End Standards Group | Anne | ||
Live Code Review | Roan | ||
Strategy | Chris | ||
Team Processes Task Force | N/A |
Slackbot reminders
DST has two Slackbot reminders:
- Codex release reminder: biweekly on Mondays, in #design-systems-engineering
- Collaborators: Anne, Eric, Nat, Roan, Volker
- DST Daily Standup: daily on weekdays, in #design-systems-standup
- Collaborators: Chris, Eric, Nat (members of Team Processes Task Force)
To view DST's Slackbot reminders in Slack, go to Wikimedia Foundation > Tools > Workflow Builder. You can view/edit Slackbot reminders for which you are a collaborator.
Notes
This article is issued from Mediawiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.