Habitat Weekly Issue Triage

community
ops

#1

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.

Launching the Call

In order to launch the triage call you’ll need to be added to the habitat team youtube channel. Without this access you will be unable to host the call. To get started follow these steps:

  • Navigate to youtube.com (the call must be run from chrome or safari, firefox does not support google hangouts)
  • Sign in with your habitat team connected account
  • Click the Habitat logo in the top right corner
  • Click “Creator Studio”
  • Click “Live Streaming” on the left-hand Nav
  • Click “Events” on the left-hand Nav
  • Click “Schedule a New Event” in the right Pane
  • Fill out the basic info including the “Also Share on Twitter” section of this page
  • Click “Go Live Now”

At this point a hangouts call will be instantiated but you will not yet be live.

  • Click the “Invite to this call” button (it’s the person icon with a plus symbol beside it, located along the top edge of the page), copy the url and send to the #joseph-directs private channel for the core team.

  • Click the “Links” button in the bottom right hand corner, copy the URL, and share it in the #general channel in Habislack. When you have quorum for the call, click the Start Broadcast button and you’ll be live in a couple of seconds.

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.


Onboarding checklist