Compatibility/Meetings/Sync w Honza: Difference between revisions

Compatibility/Meetings/Sync w Honza (view source)

Revision as of 08:06, 8 February 2023

4,241 bytes added , 8 February 2023

February 7 2023

Rbucata

33

edits

@@ Line 1: / Line 1: @@
+== February 7 2023 ==
+=== MS Teams ===
+* Report on [GH](https://github.com/webcompat/web-bugs/issues/25070#issuecomment-1410107705)
+Honza: For this issue, we have mixed results. Now, the page fails in Nightly but works in Release. It seems that there are 2 versions of MS Teams, for regular users and for Enterprise users.
+Raul: We might have 1 for corporate and 1 for regular users, the free one is one that we kept receiving reports for and which we investigated.
+Honza: We are not sure if they blocked only Nightly or other versions as well such as Release and Beta.
+Raul: Normally only the meetings were not supported but now it seems the whole website is not supported on Linux. We could investigate it more since we had no new issues reporting this.
+Honza: That will help, how do I try? Do I need a test account?
+Raul: You can test with a regular account.
+Honza: Great, could have a look into it?
+Raul: Will do.
+*Notes:
+After the Team Meeting, Dennis concluded that team.microsoft.live is also affected. The reports came for teams.microsoft.com as well.
+=== Webcompat.com Analysis ===
+Analysis from Kate Hudson: https://docs.google.com/document/d/1AvULYoAAE4LqL20gUpeHzOmJFOi3scVOeQW-SmxD-nM/edit#
+Questions:
+* Does it make sense to optimize and get more reports?
+* We have limited resources to test all reports, but perhaps we could get more quality reports? What could be better?
+Honza:  We looked into some data about how users file the bugs and most of them give up after completing the first 3-4 steps (7 total). Maybe we could make the report easier, reducing the steps.
+Raul: We've noticed in reports that when they get to the description part, the users get frustrated and they will just fill the form with random words until they've met the minimum required to submit the report.
+Honza: Is the screenshot optional?
+Raul: Yes it is.
+Honza: How many people skip the screenshot part, how important is it for you?
+Raul: Yes, it is optional but it is very important for us. It is easier for us to identify the issue.
+Honza: If we somehow make the reporting much easier for the users, how you will handle the situation if we see an increase in the reports?
+Raul: We are not sure if that will cause an increase in the reports we receive but in the past, we have received way more and we had a hard time triaging while also doing OKRs, as we saw when the "Report an issue" button was added and ready for usage.
+=== Testing framework for shipped interventions ===
+Honza: Tom was working on the infrastructure on how we test/manage interventions. How does that work?
+Raul: At the moment we do Manual and Automatic testing and we do our testing on real devices. For now, these tests don't take that much time. The only issue is when we have to test payments or websites that require special accounts such as banking.
+Honza: So you run those tests with on/off interventions, what do you do if they fail?
+Raul: We keep them open and mark them as reproducible, if the issue is no longer reproducible we create a task on Bugzilla to remove the interventions because its no longer needed.
+Honza: Are there any factors to take into consideration when running the Interventions Tests - Automated?
+Raul: Besides having the environment set up, for example, bankofamerica.com requires a Mac device, since the tests are run on a Windows Machine, that will show as fail.
+Raul: Other factors to take into consideration are VPN Connections, UI update of the page, and a stable Internet connection.
+Honza: Do you feel that these runs of the Interventions are still needed?
+Raul: Yes. We can keep track of the issues, we can see if other issues are related to the Interventions, and running them once a month does not take extra resources.
+Honza: What is the flow of creating the Run for each cycle?
+Raul: We have a predefined list of Interventions that are in place, and following that list, we create the Run based on the environment and if the issues are CSS Injections or Overrides.
+Honza: Is the list stable regarding the number of issues?
+Raul: Yes, pretty much. The number of Interventions is roughly around 90 at each cycle. Some are new, some are old. It gets updated regularly.
+Honza: Glad to hear that
 == 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.
+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?
@@ Line 10: / Line 89: @@
 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.
+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.
+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.