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 13:36, 16 December 2022
, 16 December 2022December 13 2022
(15 November 2022) |
(December 13 2022) |
||
| Line 1: | Line 1: | ||
== December 13 2022 == | |||
=== Needsdiagnosis re-check issues Q4 - Done (SV) === | |||
We have finished the re-check of Needsdiagnosis issues. Below are the results: https://datastudio.google.com/u/0/reporting/a0034c41-70fd-4d7e-9dec-4275eb287b9f/page/p_ohx6mafb1c?pli=1 | |||
Honza: Awesome, thanks for that. | |||
Raul: Exploratory testing is on track, and will be finished in the coming week. | |||
Honza: Great news. | |||
=== DevTools Workweek (Honza) === | |||
* Engineering Roadmap 2023 H1 https://docs.google.com/document/d/13_eywN08ihHhTNAuUa-276oF0g-Y0zoKxNlJRHT3Y_o/edit#heading=h.6gpel5t2a3y7 | |||
Honza: Most of next year will be about those 3 subjects regarding webcompat (Webcompat Knowledge base, Webcompat Issue impact,Webcompat User retention) We are aiming for a dashboard that will show us the top 20 webcompat issues (top issues), based on scoring. That is addressed in Webcompat Issue impact, collecting data. Our current scoring logic is based on assumptions. All the data collected is stored in Web Query. The canonical list of webcompat issues is stored in Bugzilla, for every webcompat issue, there will be a corresponding core Bugzilla report. Webcompat Retention - finding the relation between fixing webcompat issues and user retention. In order words, could we say that fixing webcompat issues helps us retain users? Can we prove it? It is about producing a document on how we can do it, based on behavioral differences. | |||
So our focus for the next year is to build webcompat knowledge base, collect data, and user retention -impact user retention. | |||
Calin: Whenever a bug will be reported on Webcompat, there should be a corresponding Bugzilla Bug? | |||
Honza: If there already is a Bugzilla core bug for that, there is no need. If not, there should be a Bugzilla bug for that (core issue). We will talk about this flow with the whole team as well, in the near future. | |||
Honza: There will be some demos as well. | |||
Honza: I was also thinking about how to improve our triage, based on the data received. Could we simply the way we produce this data? The work you do is visible on the data, but are people looking at this data? Can we add a way to simplify the way people understand this data, outside of the project? So 2 things that we should be working on. 1- work becoming more visible, 2-learning from the data. This could be a goal for next year. | |||
Honza: There is a company that works for Firefox (Bocoup), that concentrates on platform gaps. Like features available on Chrome, but not on Firefox. We had to come up with the top 20 sites, based on the top 100 sites that they are working on. So that fits together with the current OKRs we have done, as we used some of the data from there, to justify our picks. | |||
Raul: Should we also think about future OKRs for 2023? | |||
Honza: We will discuss more on this at our meeting happening in January, next year. I will be on PTO when our next meeting is due this month. | |||
== November 15 2022 == | == November 15 2022 == | ||