Issue metadata
Sign in to add a comment
|
[Component Request] Infra>UI Component |
||||||||||||||||||||||
Issue description1] Component Name: Infra>UI 2] Parent Component (e.g. Blink, UI>Browser, etc...): Infra 3] Description of Component: This is a component to file ChopsUI bugs under since we've currently been filing them under Infra>Sheriffing 4] Admin/ Owner: zhangtiff, seanmccullough 5] Please specify what triage practices will be followed for the component (i.e. what team will do it and how frequently). We could add this component to the go/som-bug-triage since Sheriffing team owns ChopsUI.
,
Apr 20 2018
The term UI is very broad. Please define this further. As in, is this the component for ALL UI? Or just the shared elements? For example, if it's the latter, it should be Infra>UIElements or something similar. Also, please provide a description that can we used directly in the component drop-down with a clear description of the component usage and what it pertains to. Thanks!
,
Apr 20 2018
I originally considered Infra>ChopsUI but it's not recommended to have specific team names as part of a component. UIElements doesn't feel totally right since I think this project will also encompass things like defining general best practices for UI. Maybe Infra>Frontend? I could see how users could get confused and file bugs for miscellaneous frontend issues though I think a broad-ish UI/Frontend component wouldn't be too different from components like Infra>Monitoring. For the description: Issues related to the overall UI of Chops services.
,
Apr 20 2018
Acknowledging that the component name generally shouldn't include team names, what about Infra>DevX>UI? What kinds of bugs do we want to fall into this component? CLI flag naming issues? Usability issues in Milo's web frontend? Or should it be more restricted to web frontends for apps like Monorail, SoM, test-results, (Gerrit, code search...) and components shared between them?
,
Apr 20 2018
A motivating example: https://bugs.chromium.org/p/chromium/issues/detail?id=824898#c10 Setting up WCT test runner for all Infra frontend apps should *not* be just an Infra>Sheriffing>Sheriff-o-Matic issue, but that's the only place we have for it currently (I have tried to find a new home for it but those component owners have rejected those attempts).
,
Apr 20 2018
How about Infra>Frontend>WebUI or something along these lines? CCing Ben Henry to comment and create while I am out.
,
Apr 20 2018
One quite note, I would like to avoid using team name "DevX" at all costs. My 10 cents.
,
May 4 2018
Ping? Tiffany/Sean?
,
May 4 2018
How about Infra>Frontends>WebUI ? (plural on Frontends to help emphasize that this is for our whole collection of frontends rather than a single one). Otherwise, this SGTM (checked with Sean as well who thinks it's fine).
,
May 15 2018
How about Infra>UI? We have top level UI, and we can expand this component to be useful for all chops-ui@ related work.
,
May 15 2018
Infra>UI works well for me. Thanks, Ben! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by zhangtiff@chromium.org
, Apr 19 2018