is there something i need to provide here ?  or should this be in a diff tracker (like monorail) ?

BugProcess sure sounds like the right component, although I have no idea who handles that. Adding some people who might know what to do with this.

@laforge, did we set up a rotation or process for triaging this label?

Unfortunately no (to the triage rotation), I've still been processing all the component requests.

That said, bug process component isn't the right place for these, should be against Admin>ComponentRequest w/ answers to the following template:

https://bugs.chromium.org/p/chromium/issues/entry?template=Component%20Request

1] Component Name: _____

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...): _____

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: _______

4] Admin/ Owner: ______

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

Apologies, I mis-understood the request (i.e. thought it was a request to create the component, not a template).

The current template system isn't scaling well (i.e. the discovery properties of the list are poor), especially as it has grown, so for that reason we're not adding any new templates (i.e. making the problem worse).

Our recommendation would be create/distribute a bug template url.

https://www.chromium.org/issue-tracking/creating-a-bug-template-url

thanks, that should suffice for our needs