33
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Jump to navigation
Jump to search
Compatibility/Meetings/Sync w Honza (view source)
Revision as of 07:26, 19 March 2024
, 19 March 2024March 4
(February 20) |
(March 4) |
||
| Line 1: | Line 1: | ||
== March 4 == | |||
=== Bugzilla triage (SV) === | |||
We have completed the Bugzilla backlog triage. Progress and data [here](https://docs.google.com/spreadsheets/d/1Vun7EDha-R6p7t_rgOTPu70K1FLCMTrukmHvHZr3vOQ/edit#gid=663205964). | |||
=== Firefox for Android 126 will be moved to mozilla-central (SV) === | |||
Is this something that might affect our project? | |||
Honza: I do not foresee any troubles. Maybe Sync with Tom regarding the Automation Interventions run, just to be on the safe side. I will talk with Dennis. | |||
=== New dashboard System (Honza) === | |||
Honza: I will share my screen, just to get an idea. We shipped the new reporting tool, available in Firefox - report broken sites. | |||
Watching the graph, we can see the number of received reports during the experimental phase, roughly 200 per day. Then we can see the numbers when the tool was shipped in 123. We can see 10x times more, which corresponds to what we were expecting. A lot of data. | |||
Tyler, from the Data Team, put together a dashboard to view what we are getting from users (broken site summary). The blue column shows the reports with comments, the red one without comments. In parallel, we are trying to group it in a way, to see the most useful comments. Ksenia is using ML to filter out without comments, or with high probability to be helpful. We can also see that most Firefox users are running Windows. | |||
We can see the reports by OS, and by reports in the last 24hr, also per site. We can see the Trend and what is important to look at. Something similar might be available in the QA Dashboard. | |||
The bottom piece allows filtering by URL and OS. Some things will be improved, this is just to get a general idea. It would be great to see the actual comment in the table. | |||
Based on this information, I would like to hear feedback, e.g. what would you like to see on the dashboard, useful data, to see only reports with comments, only useful comments, high probability for it to be useful, and automatic translations of comments. etc. | |||
We will try to automate sorting the issues automatically so it shows up on top, so we can connect the dots more easily. | |||
The next step might be that we need screenshots to better understand what is the issue. | |||
Dennis is working on the QA Dashboard, the only blocker is it is not yet deployed. Soon will have something for you to look over. Feedback will be most welcomed, we need to figure out what features you need to understand and do your work. | |||
Raul: Can the links be shared? | |||
Honza: Sure, will leave a DM with them. | |||
Honza: It would be a lot different work. For example, in Git, we will get more valuable reports. The new report will get a lot more reports per day, 2k+, but there will be less info there. We need to figure out how to be useful. Get the most from the data. Our goal is to locate the major problems that Firefox is having when surfing the web. As soon as the QA Dashboard is deployed, we will let you know. | |||
== February 20 == | == February 20 == | ||