Component Request: Program>Alignment |
|||
Issue description1] Component Name: Alignment 2] Parent Component (e.g. Blink, UI>Browser, etc...): Program We have a number of programs that will need backlogs. Existing components don't work because these don't map to features or bugs in the product in many cases. So, we need some component to put on them. This also gives a shared place we can look for Program backlogs. 3] Description of Component: Web Platform Ecosystem Alignment effort tracking 4] Admin/ Owner: ojan@chromium.org 5] Please specify what triage practices will be followed for the component (i.e. what team will do it and how frequently). It will just be backlogs with next checkin dates. It doesn't map to a feature in the product, so there's no regular triage process needed beyond the usual staying on top of the backlog.
,
Jan 7 2017
[I'm not averse to the idea, just trying to vet potential solutions] Hey Ojan, Historically we've used Proj-* labels for this purpose. Any sense for how these components would differ (for tracking sake) from Proj-* labels, the upcoming Hotlist feature or using Meta issues (i.e. issues w/ children that blocked on them)? Each program could have it's own Proj-Foo label/ hotlist/ meta issue, with an owner and associated issues. The nice part about the Hotlists and Meta Issues is that they afford complete decentralization (i.e. doesn't require an admin to configure).
,
Jan 7 2017
I don't have strong opinions about label vs component, but these issues need *some* component, right? I want the program leads to have ownership over when the issues get closed, etc. If we use existing components, then there'd be some coordination overhead between team leads and program leads that I'm not quite sure how we'd make work. Definitely open to alternate suggestions. I started with labels, but got stuck on figuring out what component to put on them, e.g. https://bugs.chromium.org/p/chromium/issues/list?can=2&q=label%3ABacklog-Alignment
,
Jan 10 2017
Ping
,
Jan 10 2017
,
Jan 18 2017
Poke.
,
Jan 20 2017
Created https://bugs.chromium.org/p/chromium/components/detail?component=Programs%3EAlignment. Before we expand it out to other programs, let's experiment w/ Alignment. I'd like to get a sense of the usage, in practice, before broadening.
,
Jan 20 2017
What do we gain by being conservative here? If we decide we don't like how it plays out, we can always change it. There will be a very small number of people modifying/managing bugs in the Programs component, so I don't see a risk of getting to a place where change would be difficult. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ojan@chromium.org
, Jan 7 2017