Clarifications to network bug triage process.

net/docs/bug-triage.txt

Index: net/docs/bug-triage.txt
diff --git a/net/docs/bug-triage.txt b/net/docs/bug-triage.txt
index 7139a983f6b6244088f8b976a42fd2d6bb387bab..a09b56edb2824261191d601c03f74e86dc693364 100644
--- a/net/docs/bug-triage.txt
+++ b/net/docs/bug-triage.txt
@@ -4,15 +4,30 @@ label seems suitable.
 
 Responsibilities
 
-To be done on each rotation.  These responsibilities should be tracked, and
-anything left undone at the end of a rotation should be handed off to the next
-triager.  The downside to passing along bug investigations like this is each new
+Required:
+* Identify new crashers
+* Identify new network issues.
+* Request data about recent Cr-Internals-Network issue.
+* Investigate each recent Cr-Internals-Network issue.
+* Monitor UMA histograms and gasper alerts.
+
+Best effort:
+* Investigate unowned and owned-but-forgotten net/ crashers
+* Investigate old bugs
+* Close obsolete bugs.
+
+All of the above is to be done on each rotation.  These
+responsibilities should be tracked, and anything left undone at the
+end of a rotation should be handed off to the next triager.  The
+downside to passing along bug investigations like this is each new
 triager has to get back up to speed on bugs the previous triager was
-investigating.  The upside is that triagers don't get stuck investigating issues
-after their time after their rotation, and it results in a uniform, predictable
-two day commitment for all triagers.
+investigating.  The upside is that triagers don't get stuck
+investigating issues after their time after their rotation, and it
+results in a uniform, predictable two day commitment for all triagers.
+
+More detail:
 
-Primary Responsibilities:
+Required activities:
 * Identify new crashers that are potentially network related.  You should check
     the most recent canary, the previous canary (if the most recent less than a
     day old), and any of dev/beta/stable that were released in the last couple
@@ -25,9 +40,12 @@ Primary Responsibilities:
     last day of the previous triager's rotation until the same time on the last
     day of their rotation.
 * Request data about recent unassigned Cr-Internals-Network bugs from reporters.
-    "Recent" means issues updated in the past week or so.
+    "Recent" means issues updated in the past week or so.  Note that
+    this means both pinging reporters for more information and
+    updating the bugs apporpriately when/if that information has come
+    in. 
 * Investigate each recent (New comment within the past week or so)
-    Cr-Internals-Network issue until you can do one of the following:
+  Cr-Internals-Network issue until you can do one of the following:
   * Mark it as WontFix (working as intended, obsolete issue) or a duplicate.
   * Mark it as a feature request.
   * Remove the Cr-Internals-Network label, replacing it with at least one more
@@ -43,9 +61,14 @@ Primary Responsibilities:
     Available.  Future triagers should ignore bugs with this status, unless
     investigating stale bugs.
 * Monitor UMA histograms and gasper alerts.
-    TODO (mmenke):  Add a suggested workflow.
+  * For each Gasper alert that fires, the triager should determine if
+    the alert is real (not due to noise), and file a bug with the
+    appropriate label if so.  Note that if no more specifical label

[mmenke, 2015/03/02 19:15:13]

"no more specifical label" -> "no label more specific than"

[Randy Smith (Not in Mondays), 2015/03/03 15:08:02]

Done.

+    than Cr-Internals-Network is appropriate, the responsibility
+    remains with the triager to continue investigating the bug, as
+    above. 
 
-Best Effort (As you time):
+Best Effort (As you have time):
 * Investigate unowned and owned but forgotten net/ crashers that are still
     occurring (As indicated by go/chromecrash), prioritizing frequent and long
     standing crashers.