Add issue triage guidelines
Bug:1022301
Change-Id: Ibb1e3adec0b4507b1b838a979871a0474a935f6f
[email protected]
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2194878
Commit-Queue: Yang Guo <[email protected]>
Auto-Submit: Michael Hablich <[email protected]>
Reviewed-by: Yang Guo <[email protected]>
diff --git a/DESIGN_GUIDELINES.md b/DESIGN_GUIDELINES.md
index 0fd76c7..9548198 100644
--- a/DESIGN_GUIDELINES.md
+++ b/DESIGN_GUIDELINES.md
@@ -24,24 +24,29 @@
## Roles
### Individual Contributor (IC)
*LGTM*: N/A
+
This person is the creator of the feature and the creator of the design documentation.
### The Technical Leads (TL)
*LGTM*: Must have
+
An LGTM is needed from the DevTools TLs, which are Benedikt Meurer ([email protected]) and Rob Paveza ([email protected]) at this point, in order to ensure architectural consistency. The TLs are also responsible for finding the right LGTM providers (i.e. the domain experts) to sign off on the design.
In the absence of the TLs, the EnReOw takes over the responsibility.
### LGTM provider
*LGTM*: Must have
+
This is a person that is required to give LGTM. These are usually ICs which have significant knowledge about the areas in question.
### “Random” reviewer of the document (RRotD)
*LGTM*: Not required
+
This is somebody who is simply reviewing and comment on the proposal. Their input should be considered, although their LGTM is not required.
### The Eng Review Owners (EnReOw)
*LGTM*: Not required
+
Stuck proposals can be escalated to the [ENG_REVIEW_OWNERS](https://cs.chromium.org/chromium/src/third_party/devtools-frontend/src/ENG_REVIEW_OWNERS) Potential use cases of such an escalation:
- An LGTM provider is non-responsive.
- No consensus on the design can be reached.
