83
edits
OanaArbuzov (talk | contribs) (Added meeting minutes from 14.12.2021) |
OanaArbuzov (talk | contribs) (Added meeting minutes from 11.01.2022) |
||
| Line 1: | Line 1: | ||
== January 11 2021 == | |||
=== Happy New Year !!! === | |||
=== [FYI] OKR Q1 2022 tasks (SV) === | |||
We've added our OKR tasks and started executing them | |||
https://github.com/mozilla/webcompat-team-okrs/projects/15 | |||
oana: if you have anything else in mind please let us know. | |||
=== Product Team Proposal testing (SV) === | |||
We've created our accounts (Mozilla addresses), we just need access to the features under test. | |||
karl: I'll ask Karen | |||
=== Interventions/UA Override verification (SV) === | |||
Currently there is no OKR task for this, should we create one and continue checking them manually until the automation test suite is up and running? | |||
oana: I've talked with Tom, and he was working on the automation test suite, but stumble upon some problems with to 2f authentication/phone code verification/geo-location (which seem to be harder to automate). Probably these cases will be done manually. | |||
karl: automation test suite is almost done, but some issues will need to be verified manually, so yes an OKR task can be added for reference | |||
=== about:compat - SmartBlock Fixes verification (SV) === | |||
A new section is available in "about:compat" - "SmartBlock Fixes". Should we consider doing some verification for that section too? | |||
karl: no, the privacy team should own what they do. It is manual work there. | |||
oana: I've discussed with the SV team that works on Tracking Protection part, and they are not checking "SmartBlock Fixes" issues | |||
oana: we could consider adding an OKR task for this, to perform verification once a quarter. | |||
karl: I'll talk with Tom and Ethan | |||
=== Alexa.com ranking retire (SV) === | |||
Since Alexa.com will be shut down (May 1st, 2022), how will this impact our project? Are we going to use a different service? | |||
karl: we have a task about this and we need to rethink this strategy. | |||
https://github.com/mozilla/webcompat-team-okrs/issues/249 | |||
karl: probably we'll find similar services | |||
=== Webrender enabled by default (SV) === | |||
We have noticed that Webrender shows as enabled now, regardless if the settings for Webrender (are enabled or disabled (boolean set to true: gfx.webrender.all & dom.webgpu.enabled). | |||
raul: For issues that have the WebRender label, should there be a change in our approach? | |||
karl: no need to test with the changed setting. | |||
=== [FYI] New devices Android 12 (SV) === | |||
SV mobile team can give us an Android 12 device for testing. | |||
== December 14 2021 == | == December 14 2021 == | ||
edits