14
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 15:29, 10 January 2023
, 10 January 2023January 10 2023 minutes with Honza
(December 13 2022) |
(January 10 2023 minutes with Honza) |
||
| Line 1: | Line 1: | ||
== January 10 2023 == | |||
=== OKRs for 2023 (SV) === | |||
Should we make new OKRs for Trends: https://github.com/mozilla/webcompat-team-okrs/issues/262, or can we transfer the old one, as we did not close it at the end of 2022. The same question is in place for : https://github.com/mozilla/webcompat-team-okrs/issues/259. | |||
We are thinking of some OKRs to be added in Q1 for 2023. But given the RoadMap for 2023, are there any possible OKRs that we should focus on first? | |||
Raul: Should we open a new OKR for the Untriaged/Triaged issues from 2022? | |||
Honza:The ones that are in progress from the last year should be closed. I think a new project should be created as well. | |||
Raul: Dennis created the project for 2023. | |||
Honza:What about new OKRs? I've seen that Top streaming websites OKRs is already done. Maybe we should move to a different area now. | |||
Raul: We should probably test Top social media websites. | |||
Honza: Have you tested them already in the past? | |||
Raul: We had some testing before. | |||
Honza:Nice, if you have documents to review please send them to me. | |||
Raul: If we have any idea for new OKRs we will let you know or maybe, if you have any suggestions for the roadmap. | |||
Honza: First, any other ideas for Q1 OKRS? | |||
Raul: We had a cleanup on bugzilla before with bugs related to webcompat, some that were really old and kept piling up in the backlog. | |||
Honza: That sounds like a candidate for a new OKR for Q1. | |||
Raul: We could do that again. | |||
Honza: I am wondering when you are performing triage, do you find any other issues besides the reported issue?If you find any issues that reproduce, how do you proceed? | |||
Raul: We ping Ksenia or Tom to look into it. There are issues that are Firefox issues but not necessarily WebCompat issues, such as features of the browser. | |||
Honza:What is the amount of bugs in our Product (WebCompat)? | |||
Raul: We don't know exactly...We can perform a search query in Webcompat Mobile and Desktop Component, based on the NEW or UNASSIGNED status. | |||
Honza: Cleanup on Bugzilla could be a great OKR as well. We should talk more about that on the upcoming meeting with the team. | |||
Raul: For the top sites Social Media OKR, should we use the Beacoup list? | |||
Honza:We have like 1000s sites there, I don't think that category of top 10/20 social media sites is there, I will send you the sheet: https://docs.google.com/spreadsheets/d/128x7npL8THeiGbXsYoiSRN3W19Ha7VrGN3zBUH5w3ik/edit#gid=0. Also, Dennis might assist with another list. | |||
=== Issues that are reproducible on Release version, but not on Nightly version (SV) === | |||
Usually we close such issues as WontFix, but we were wondering if we could discuss about it with other team members before adding a resolution to the issue, depending on the importance of the page (users, popularity, etc) or number of reports received for one website. | |||
As seen here: https://github.com/webcompat/web-bugs/issues/115740#issuecomment-1361317178, an uplift to Beta/Release helps in this kind of situations, especially if we are looking at user retention as well. | |||
Raul: Based on the issues we've received, we've noticed a trend with Azure. A bug that reproduced on Firefox release but not with Nightly. | |||
Raul: Using the methology of the trends we've managed to identify the issue regarding Azure. This also shows how important it is to identify the trends that are happening. But because the issue is a classic Wontfix issue, Ksenia pitched in and we were able to successfully solve the issue, without waiting for the next 110 release version, thus retaining users. | |||
Honza: I saw the thread, good job there. This is what the trend OKR should be about. Also, yes, it is a good idea based on that issue that we should prioritize websites that could use a uplift/patch. | |||
Honza: If we are on the subject, we are thinking since Trends seems to help us a lot, to integrate Trends in the Knowledge base -real data base which can be easily integrated in Bquery. HTTPArchive and telemetric data are stored there. This can be merge together. The next base should be built in the same system. Read data and learn from them. For example Webcompat issues with CSS Properties failing, we can query the archive and see how much that property is used across the web, and it can help identify the impact of the issue.It would help provide a state of webcompat report. Having trends intergrated there that would be something. My point is that the OKR is on github, and somehow to store it in Bquery. Maybe we can do something similar for trends. Fetching data from web bugs. Fetching the trends and process them. This is something to think about for Q2 OKR. | |||
=== Verified Paypal account (SV) === | |||
We were unable to add Paypal as a payment option when ordering on ubereats (non-compat) and we believe it's because we do not have a verified account. | |||
Context: https://github.com/webcompat/web-bugs/issues/116245 | |||
Other: https://github.com/webcompat/web-bugs/issues/116379 | |||
Honza: When you say verified account, who sould verify the account and how? | |||
Calin; The account needs to be verified by Pay Pal, with a valid ID. | |||
Honza: I will ask around. | |||
== December 13 2022 == | == December 13 2022 == | ||
| Line 69: | Line 147: | ||
=== NeedsDiagnosis Re-check issues(SV) === | === NeedsDiagnosis Re-check issues (SV) === | ||
We have finished the list with reports submitted by users: | We have finished the list with reports submitted by users: | ||