Weekly Triage Process
The weekly triage process is pretty straightforward. The intention of the public triage is to make sure that our community is getting responses to issues they’ve submitted in a reasonable timeframe. With the advent of the weekly goalie this meeting will hopefully become less and less necessary which should allow us to use this time to do things like share progress on the roadmap of have talkback on whats happening in the project.
Note: Core team members are expected to push their issues into the backlog when they are opened. More often than not there is a specific reason a core team member would open an issue there isn’t really a need to triage that as much as have it get scooped up by our prioritization process.
Launching the Call
The Habitat team will start an internal Zoom call. A representative from the Supervisor team and the Builder team should plan on attending. This call will be recorded and published on the Chef triage channel in Youtube.
When the recording is completed, please contact the marketing team and ask who should receive the recording.
Triaging Issues
The process for triaging issues is lightly documented in the “Workflow Bugs” document on google docs. The rundown is as simple as this - Sort the ZenHub board to not show open PRs in chronological order from newest to oldest. Go down the lefthand “needs to be triaged” column on the board card-by-card.
The team will discuss each card and determine whether the card will be “accepted” (and thus moved into the backlog), “denied” (and thus closed), or “Help Wanted” (in which the card will be labeled “Help Wanted” put into the backlog). When doing standup and replenishment calls it is necessary to filter out “Help Wanted” issues.
The team member running the Triage session should be responsible for tagging issues and keeping the high-level flow of the session going, but for expediency, any follow-up messages to an issue should be written by another team member on the call.
Accepted
Accepted issues must be labeled with the following categories - Area (A-), Category (C-), Language (L-), Priority (P-), Vertical (V-). The following categories are nice to have optionally - Tags (T-), Status (S-), Effort (E-), Impact (I-).
Help Wanted
Help Wanted issues must be labeled with the same categories as Accepted issues. As an added requirement they must be labeled with the T-help-wanted.
Denied
Close those suckers out. Please make sure to include notes on the issue regarding why it is denied, making sure to thank the submitter for spending the time opening the issue.
RFCs and Un-Triagable Issues
Any issue that requires more discussion or research should stay in the “Needs to be triaged” column of the board. Doing so enables us to revisit the issue the following week ad infinitum until a decision has been made. For these issues be sure to add the S-needs-discussion label.