Issue metadata
Sign in to add a comment
|
[Component Request] Infra>Platform>Admin |
||||||||||||||||||||||
Issue description1] Component Name: Tickets 2] Parent Component (e.g. Blink, UI>Browser, etc...): Infra>Platform 3] Description of Component: add/modify/remove config/groups/acls kind of tasks for components of Infra>Platform. 4] Admin/ Owner: estaab@ tandrii@ 5] Please specify what triage practices will be followed for the component Ops-Foundations team (which owns Infra>Platform), handled ~daily. Also, will I (tandrii@, proposed owner) be able to modify auto-cc for the new component? If no, please add me to auto-cc.
,
Dec 1 2017
Why not use "Infra>Platform and status=untriaged" and add a label for tickets? I am not too keen on the idea of adding a new component for tickets. We similarly do not do the same for Trooper queue and use the labels instead. Components should be used for functional areas or features and not request types. Note that the upcoming Trooper split will also be using labels.
,
Dec 1 2017
But we do have a component for Infra>Git>Admin for git/gerrit admin rotation, which is what I based my request on. However, I don't have a strong preference.
,
Dec 1 2017
I think Infra>Git>Admin was setup because there was a unique body of work to be administrators of our Git instances, while Infra>Git was the work required to both get Chrome onto Git and to track work/bugs against GoB or with our Git instances that isn't administrative. Personally, I feel like anything with "Tickets" is redundant, and eric's comment in Comment #2 is accurate. If there's something about just using "Infra>Platform status=untriaged" that is insufficient, let's talk about that.
,
Dec 1 2017
,
Dec 1 2017
Done. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tandrii@chromium.org
, Nov 30 2017