1] Component Name: Lab Tools

Guideline 1 (Clarity): Component name should be descriptive beyond the core
project team
(i.e. please avoid using non-industry standard abbreviations, code words,
project names, etc...)

Guideline 2 (Permanence): Component names should describe features/
functions and not team names, code locations, etc..., which are more
subject to change and make the hierarchy less predictable for people
triaging issues.

Guideline 3 (Specific): Components are meant to explicitly track functional
work areas.  If you are trying to track a Proj(ect) or an on-going effort
(e.g. Hotlist-Conops), please instead request a label for a (Proj- or
Hotlist-)

Guideline 4 (Discoverable/ Predictable): Components should be parented
where people would logically expect to find them (i.e. follow product
decomposition when naming versus team decomposition)

2] Parent Component (e.g. Blink, UI>Browser, etc...): Enterprise

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
components as parents.

3] Description of Component: Tools for deploying and managing enterprise labs for testing.

4] Admin/ Owner: feiling@chromium.org

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).

Enterprise test team will triage issues that are already labelled as they are filed. Volume is expected to be low.

The audience of the toolchain is very limited. Therefore we expect issues that are filed to be either labeled properly or the issues communicated to the test team directly. Thus for the moment there won't be a process for triaging all incoming bugs to label them as Enterprise>Lab Tools.