Proposal for about:glean updates
Categories
(Toolkit :: Telemetry, task)
Tracking
()
People
(Reporter: perry.mcmanis, Unassigned)
Details
About:Glean is in line to get a new coat of paint. We need a proposal for how that's going to look.
| Reporter | ||
Comment 1•2 years ago
|
||
Link to proposal:
https://docs.google.com/document/d/1gdx7qpK6A2zFUR_20hooXfrBm91vZOhA0uzXVpszaTI/edit?usp=sharing
Comment 2•2 years ago
|
||
Comments in the doc.
Overall:
- Taking it step-by-step is an excellent idea. There's plenty to gain by applying best principles to what we have currently before exploring other use cases. Though I worry that too much design churn will fatigue our users.
- "I want to look at a (specifically the one I just added, if applicable) metric's value" being the prime use case to drive design feels correct.
- I want to see (and play with) prototypes.
Comment 3•2 years ago
|
||
Comments in doc.
I'm definitely pro redesigning about:glean.
Exposing recorded values would be nice and I'm a fan of that, we just need to be careful about dev's expectations around that.
Comment 4•2 years ago
|
||
I'm excited to see this work happen. I left a couple of comments, but I think the design criteria and drivers are all appropriate and will make about:glean more useful to everyone.
Comment 5•2 years ago
|
||
I left a few smaller comments in the doc; mostly just emphasizing things I agree with. I like the idea of keeping about:glean and the DPV separate and making about:glean more local. I am excited to see the changes!
If there are any more questions about the plotting libs used in the DPV or how we could maybe have some sort of theming consistency between the two, feel free to reach out to me when you are working on implementation!
I left few clarification questions (that you already clarified) and comments in the doc. They are centered around finding out the group of users we are trying to solve problems for and whether we are missing something in addition to what is already proposed in doc to solve problems for all of those users.
Thanks a lot for this initiative.
Comment 7•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Comment 8•2 years ago
|
||
Chris, is the proposal in a good enough state to call it closed?
Comment 9•2 years ago
|
||
Yes, the proposal has completed its feedback round.
Description
•