Compatibility/Meetings/Sync w Honza: Difference between revisions

Jump to navigation Jump to search
September 20 2022
(Updated meeting minutes from 07.09.2022)
(September 20 2022)
Line 1: Line 1:
== September 20 2022 ==
=== Onboarding Calin (SV) ===
- add sv-calin to Slack channel #webcompat-internal 
- add Calin to webcompat internal - for Google Calendar
Honza: I will do it in two weeks after the ALL HANDS and his PTO, so I can properly introduce him to the team as well, and so he can introduce himself as well.
=== iOS issues approach (SV) ===
We have received an issue coming from the Firefox iOS repository, but issues that are reproducible for Firefox iOS are being moved by us to the iOS repository, and not in our `needsdiagnosis milestones`:
https://github.com/webcompat/web-bugs/issues/109582#issuecomment-1238750705
Should we continue to move reproducible issues for Firefox iOS to the Firefox iOS repository? If yes, can we also let the Firefox iOS team about this, so their are aware of our flow, instead of them moving valid issues to our repository?
Oana: iOS was dropped from our team. We just move them to their repository. We have a Firefox iOS channel for webcompat on Slack (#webcompat-firefoxios
), but there is no activity there.
Link to iOS repository: https://github.com/mozilla-mobile/firefox-ios/issues/
Honza: Let's discuss this with the entire team at our meeting.
Tom: When the iOS team determines that an issue is with a website, not Firefox/iOS, they will move it back to us.And in those cases it will probably be non-compat, since the issue will also happen on Safari on iOS too.
Tom: So we can just leave those open as needscontact, but not specific to firefox (just iOS in general). That way if anyone ever wants to reach out to the site, they can.
=== Focus and Fenix repositories transition to Bugzilla (SV) ===
We have seen this on the Focus repository: https://github.com/mozilla-mobile/focus-android/issues/7621
Do we have any info regarding a date when this will happen?
How would this affect us and our workflow? And if specific bugs will continue to be reported in the old/new repositories, or on Bugzilla.
Honza: I don't have much info on that as well, but I will ask around. I think all reports related to Fenix and Focus will be reported in Bugzilla.
Oana: Will our repository be moved to Bugzilla as well?
Honza: So far, there are no plans regarding this.
=== Proposals for Q4 (SV) ===
We have gathered some proposals for Q4
https://docs.google.com/document/d/1qlI81okmrrdhvdxLeW337PG25_TRmNONio_bcob0vL8/edit#
Honza: Can you please explain more about the intervention OKR?
Oana: Before the release, we check if the Interventions or UA Override as still needed for the issue
Honza: And what about the OKR regarding the top 10-20 sites?
Oana: This will be based on the reports received and also trends.
Honza: We can also use the Trends OKR to help us with this. Looking at the Trends, we can see what we can focus on. Collecting data from the Trends OKR and checking if the Trends are really Trends or not.
Oana: Based on the current Trends, we could consider top 10-20 Streaming sites.
Honza: What about the Contact ready? What is the outcome of this? Does it work?
Oana: Sometimes we get a response that the issue is not reproducible. Sometimes the website contact is not reachable, and we can close them as incomplete.
Honza: This sounds like we can do this more often. Who is setting the milestone for this?
Oana: The person who is assigned to the issue.
Honza: Did you do this using other labels/milestones?
Oana: We did it for most of the milestones (sitewait/needsdiagnosis/needscontact). We usually do this at each quarter. We iterate around the milestones.
Honza: How many issues are in these milestones?
Oana: Around 63, but for `needscontact` around 500.
Honza: Regarding rechecking the ETP issue, we can ask Tom at the meeting. Will you be checking all the ETP issues on Bugzilla?
Oana: There is a component in anti-tracking on Bugzilla. Some of them might be complicated or complex.
* Update from TOM on ETP recheck OKR:
Tom: the anti-tracking team considers standard-mode issues important, but I believe strict-mode-only ones are generally assigned a severity quickly, and do not require a round of re-checking anytime soon after that. So we can skip non-standard issues if they have a severity of s2 or lower, and I don't think there are too many bugs left as s1 or which are standard-mode-only.
we have triage and diagnosis meetings every week, so I don't think there is too much value in going over them again.
Honza: Sounds good. Thanks for the list.
Oana: All the proposals depend on an estimate of the workload, so some might be dropped.
=== Trends (Honza) ===
* https://github.com/mozilla/webcompat-team-okrs/issues/262
  * YouTube videos don’t work ([bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1785149))
  * Entrata platform not supported in Firefox ([gh](https://github.com/mozilla/webcompat-team-okrs/issues/262#issuecomment-1211521618))
  * Yahoo mail ([gh](https://github.com/mozilla/webcompat-team-okrs/issues/262#issuecomment-1202993381))
  * Google Calendar ([gh](https://github.com/mozilla/webcompat-team-okrs/issues/262#issuecomment-1246669138))
Honza: What should be the workflow? Spotting trends or potential risks and checking the Bugzilla bugs already reported, or reporting a new one in Bugzilla are also part of the workflow.
Oana: For Firefox being unsupported, we can contact the site owner as well.
Honza: Should we go back and look in the comments if the issues are reproducible?
Oana: Yes, we already re-check the issues that have been signaled using the Trends if they are reproducible or fixed. We update them on the fly, with the corresponding Bugzilla bugs as well. We also follow up with users as well.
Honza: Do reporters show any interest? E.g asking questions, being willing to volunteer?
Oana: Not in our case, very low interest is shown to volunteer to do diagnosis, they are interested only for the issue to be fixed.
Oana: Dennis collaborates with other people (outreach) and part of the work they do is to learn how to diagnose issues.
Honza: I will talk to Dennis about it.
== September 06 2022 ==
== September 06 2022 ==


33

edits

Navigation menu