From 1c9156c5045071d6c1133fcedf93f9ea59129169 Mon Sep 17 00:00:00 2001
From: Joe Previte <jjprevite@gmail.com>
Date: Tue, 4 May 2021 11:57:00 -0700
Subject: [PATCH] docs(maintaining): add triage to workflow

---
 docs/MAINTAINING.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/MAINTAINING.md b/docs/MAINTAINING.md
index 13a1abe65..69337f8a3 100644
--- a/docs/MAINTAINING.md
+++ b/docs/MAINTAINING.md
@@ -5,6 +5,7 @@
 - [Maintaining](#maintaining)
   - [Workflow](#workflow)
     - [Milestones](#milestones)
+    - [Triage](#triage)
     - [Project Boards](#project-boards)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
@@ -36,6 +37,18 @@ Here are the milestones we use and how we use them:
 
 With this flow, any un-assigned issues are essentially in triage state and once triaged are either "Backlog" or "Backlog Candidates". They will eventually move to "On Deck" (or be closed). Lastly, they will end up on a version milestone where they will be worked on.
 
+### Triage
+
+We use the following process for triaging GitHub issues:
+
+1. a submitter creates an issue
+1. add appropriate labels
+   1. if we need to look into it further, add "needs-investigation"
+1. add to milestone
+   1. if it should be fixed soon, add to version milestone or "On Deck"
+   1. if not urgent, add to "Backlog"
+   1. otherwise, add to "Backlog Candidate" if it should be considered
+
 ### Project Boards
 
 We use project boards for projects or goals that span multiple milestones.