Compatibility/Meetings/Sync w Honza: Difference between revisions

Compatibility/Meetings/Sync w Honza (view source)

Revision as of 14:39, 15 January 2024

4,585 bytes added , 15 January 2024

Januar 9

Rbucata

33

edits

@@ Line 1: / Line 1: @@
+== January 9 ==
+=== 2024 Plan for QA (SV) ===
+Since we are unsure how our work style will change/be after the transition to the Dashboard, we have no new proposals for 2024. We will stick to the 2023 plan until then.
+For 2024, here is the updated [plan](https://github.com/mozilla/webcompat-team-okrs/projects/26) containing our OKRs
+Should we still split the OKRs for H1 and H2, meaning that we will create a new project for H2 in our Github repo, importing the tasks from H1? Or we can keep this one for the whole year?
+Honza: I would wait, for Q1 nothing changing too much.
+We should come up with a metric to measure the state of the webcompat and in the next quarter move it in the direction we want to.
+Let's wait on Q1 and in the 2nd quarter we will have a solid base for OKRs.
+=== QA Dashboard ===
+Do we have any updates on this?
+- The Dashboard is not ready yet, I assume we will need about 2 more months for it to be done.
+- There is a lot of data gathered through the Reporting tool from the Experiment that is live (see link from meeting)
+- So far, we receive in average of 200 reports per day, and it's growing. Mostly noise for now, but we managed to gather some data and categorize some reports.
+- The experiment is set at 10% of the population with the new Reporting tool. We are now around 7m, and we might get to 10m. That will mean an increase in the daily reports received.
+- The experiment will run for a couple more weeks, it's due on February 14th.
+When it's done, we need to see if we will keep the Categories drop down, and ship to all users, likely in Firefox 122, sometime in February. By then, we expect to see at least the Dashboard being usable.
+Paul: Firefox 122 is set to be released on the 23rd of January, it will be hard to release in 122 if the code still needs to land.
+Honza. Good point, that might be for version 123.
+Paul: That gives us more time to decide what to deploy.
+Honza: I'll ask Karen.
+Paul: You can also use a Nimbus rollout to release it if it's only about flipping a pref.
+Honza: Sure, most of the stuff is enabled by prefs. Good point
+=== Labeling (Honza) ===
+Honza: For the next 2 months, we are still foreseeing Github triage. However, what we produce of data with the Dashboard, should be trusted info.
+Eventually, we will come to the platform team with data, showing the most encountered and important issues, and how fixing them would impact our browser. We need to explain this data. This is one of the reasons why we are switching and collecting data.
+The big picture, the real State of Firefox Webcompat, is recommending trustful. There should be minimum human judgment for this. Each category should have simple steps to reproduce, and it should be as clear as possible. This might be easier in the new system, where people can choose the category.
+Paul: Do we want to automate this somehow, or we will still rely on QA to confirm the categories?
+Honza: I'm not sure we can automate this, although it would be nice.
+Paul: I think it would be hard to automate, as you'll need something specific like a keyword in the report to categorize it automatically. And each problem is specific.
+Paul: Also, some users might not select the correct category.
+Honza: There are 2 things, picking the category - which we know the limitations for this, and the 2nd thing should be creating labels. For now, we have 4 clear categories: Unsupported, ETP, Private Browsing, and  Performance.
+Paul: I think we should at least offer an "Other" category especially if it's mandatory to select one.
+If nothing applies, there is no label. Whatever we have in February, feedback for this will be taken into consideration.
+Honza: As a first update/enhancement for this flow, we are aiming to ship this for Firefox mobile as well.
+Also, we are thinking about screenshots provided by users - but that might be harder due to storing possibilities and other limitations.
+So a lot fewer labels, but trustful.
+Raul: Should we edit the labeling descriptions on Git Hub?
+Honza: I think for now we shouldn't edit anything since in around 2 months we are migrating to the new dashboard.
+Raul: Should we create a trend label for the private browsing issues? We normally have a label for private but not for trends.
+Honza: No action for now. Q2 will shed some light, as we will have more data then.
+=== Google is going to kill cookies soon ===
+What is Mozilla's position on this? Any plans to do the same?
+Honza: I do not know what will happen on Firefox's side, but that will be interesting from the webcompat point of view.
 == December 12 2023 ==
 === Top 100 Testing and Blockers (SV) ===
-The number of discovered issues is lower compared to when we started (most are known issues - discovered in previous runs). Also, for Google and other sites where a valid mobile number is needed, we are blocked due to our test account mobile numbers being used for other test accounts. Some blockers have been observed for Financial sites where a valid banking account is needed, or where the mobile app is needed to perform various operations (Netflix, Google relarted apps, etc)
+The number of discovered issues is lower compared to when we started (most are known issues - discovered in previous runs). Also, for Google and other sites where a valid mobile number is needed, we are blocked due to our test account mobile numbers being used for other test accounts. Some blockers have been observed for Financial sites where a valid banking account is needed, or where a mobile app is needed to perform various operations (Netflix, Google-related apps, etc)
 === Upcoming Holidays and Top 100 (SV) ===
@@ Line 9: / Line 84: @@
 Just a heads-up that this month we might not finish the whole Top 100 Test Suite for Q4 - Batch 1 due to upcoming holidays and PTO
-Honza: Sure, please add the PTOs into the Calendar.
+Honza: Sure, please add the PTOs to the Calendar.
 === Work Week in Berlin (Honza) ===
-Honza: I'll share the DevTools folder. This is a summary of planning in 2024. Our top-level goal is to improve webcompat compatibility.
+Honza: I'll share the DevTools folder. This is a summary of planning for 2024. Our top-level goal is to improve webcompat compatibility.
 *'''The first part is Webdriver BiDi'''