Design Systems Team/Chores

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.

Legend
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).
 * 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.
 * Triaging 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.
 * 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.

Non-scrum meeting ownership
For meetings outside the scrum framework (see Design Systems Team/Team Processes 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

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.