MozillaWiki

Compatibility/Meetings/Sync w Karl: Difference between revisions

Page Discussion

Compatibility/Meetings/Sync w Karl (view source)

Revision as of 08:39, 21 April 2022

23,753 bytes added ,  21 April 2022
Added meeting minutes from 19.04.2022
(Added meeting minutes from 27.07.2021)
(Added meeting minutes from 19.04.2022)
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
== April 19 2022 ==
=== OKR task proposal Q2 (SV) ===
We were thinking of adding a task to perform Exploratory testing for the top 10-20 Leading Online Marketplaces Worldwide sites
* https://www.practicalecommerce.com/ecommerce-marketplaces-worldwide
* https://heraldbee.com/the-biggest-marketplaces-for-e-commerce-by-country-or-region/
What is your input on this?
karl: sure, that is a good idea
karl: we can also check the domains and see if we have reports on them on webcompat
oana: created OKR task https://github.com/mozilla/webcompat-team-okrs/issues/257
=== Product Team Task (SV) ===
Are there any news regarding this?
karl: not yet
=== Checking issues that are specific for v100, but not reproducible on versions below 100 (SV) ===
Since the Release version of Firefox will receive the 3 digit UA string, should we check if issues are specific for Firefox 100, but not reproducible on versions below 100 (since we will not have a build for Firefox 99 anymore after that date), by running a `mozregression` with v99 to compare the results and see if the issue is specific for v100 (not reproducible on v99 from the mozregression build)?
karl: you can download an older Firefox build 
raul: maybe we can also change UserAgent to an older version (maybe from about:config)
karl: you can change the UserAgent also from Responsive design mode.
karl: you can create a profile with an older Firefox version (Mac: cd ~/Library/Application\ Support/Firefox/)
=== Issues that have non-SSL (not secured) websites (SV) ===
As seen in: https://github.com/webcompat/web-bugs/issues/102351#issuecomment-1097275632, can we automatically close issues that have non-SSL pages (on all browsers) as `wontfix`?
karl: too many domains are added there, plus porn sites - a bit spammy, they have lots of ads and finding a contact for them is hard
karl: for normal sites continue moving to Needscontact and add the SSL Lab result.
karl: if Chrome displays the site, Firefox doesn't display the site, both display connections not secured in "Site information" option of the toolbar - move to Needsdiagnosis and assign it to me
=== Bugzilla issues that are submitted in the wrong Product, but are clearly webcompat issues (SV) ===
As seen in: https://bugzilla.mozilla.org/show_bug.cgi?id=1764428, the issue seems like a perfect candidate for webcompat. But because it is not in the right Product/Component in Bugzilla, can we move them if they meet the requirements to be a webcompat issue, regardless if they are previously moved/created by other team-mates from Bugzilla or the bot?
karl: don't move it, you can leave a comment, add the webcompat issues (if available) to "See also", maybe ping one of us
=== Checking sites that stream or offer illegal downloads (SV) ===
Is there a way to double-check (like a list of Google removing sites) for sites that streaming illegally?
karl: no point in diagnosing them and no way/hard way to find contact
== April 5 2022 ==
=== Product Team task (SV) ===
Since we are blocked on this task, what is the next step for it?
oana: I've sent the email with the performance profiles as you requested.
karl: I'll look over them and communicate them to the product team
karl: no further steps for now
=== Waterfox issues (SV) ===
As per: https://github.com/WaterfoxCo/Waterfox/issues/2649, issues related to Waterfox should we move them to the designated repository from now on?
karl: don't spend too much time on it, just move them
raul: can we move issues from other browsers on the designated repository?
karl: yes they can also be moved
raul: issues reproducible on Safari/Edge is there anyone to ping?
karl: no yet on Safari, Harald -Egde - but not very responsive
===PWA issues (SV) ===
As found while performing Bugzilla mobile clean-up (see https://bugzilla.mozilla.org/show_bug.cgi?id=1459594), if issues related to PWA are submitted and they are reproducible, do we treat them as non-compat or as valid issues?
karl: indeed non-compat. I'll look over it
== March 22 2022 ==
=== Metrics dashboards (SV) ===
We finally have some metrics dashboards for Weekly/Monthly/Quarterly/Yearly triage and also for issues based on milestones.
karl: this would be nice to present in the team meeting
paul: percentage metric dashboard is work in progress
=== Product Team task (SV) ===
We received the subscription, on Chrome it loads and we can perform tests, unfortunately on Firefox with Chrome UA it does not load.
Should we report the findings via the thread from the email or is there another way?
In this case, should we still test on Chrome?
oana: I managed to share the link in Firefox, and it seems that both Firefox and Chrome can't run in parallel (due to "out of memory")
oana: even in the case above Firefox was not able to load the workplace (15% max)
karl: we are blocked on Firefox,
karl: record a performance profile, and also gather the error log
=== [FYI] Automation TS (SV) ===
oana: With Tom's help I've managed to configure and run the Automation TS (desktop) on Windows
oana: after discussing with Tom, test cases for Android are work in progress (connection to the emulator is being investigated)
oana: all encountered issues were reported to Tom and James is working on them
karl: report any bugs on webcompat-tooling
== March 08 2022 ==
=== ETP issues Triage (SV) ===
Taking into consideration the discussion from slack and the ideas provided in the shared document, in regards to the large number of ETP issues reported, what is expected from us?
What are your thoughts on this subject?
oana: we can help with triage from time to time (maybe have an OKR for this) but Webcompat has priority 
oana: we can also help guide anyone that would start triaging those issues 
karl: we should not use Webcompat resources for the Tracking Protection team 
karl: yes we can help and guide the new resources (maybe some new SV resources)
paul: we've talked internally and if SV resources are needed Florin Mezei is the person to contact about this
karl: I'll contact Ethan and Philip from Mozilla
=== Product Team task (SV) ===
Is there any news about the subscription?
karl: I'll contact Karen
=== ML Bot closes valid issues (SV) ===
We have observed that the ML Bot is closing valid issues, such as:
- https://github.com/webcompat/web-bugs-private/issues/48899
- https://github.com/webcompat/web-bugs-private/issues/48912
- https://github.com/webcompat/web-bugs-private/issues/48914
- https://github.com/webcompat/web-bugs-private/issues/48890
Should we signal them, and see if maybe the ML Bot needs some adjustments to be made?
karl: Ksenia would be interested in this, so you can contact her
== February 22 2022 ==
=== Regression for Firefox Mobile- Android (SV) ===
According to: https://bugzilla.mozilla.org/show_bug.cgi?id=1556042 mozregression is not yet supported for Android.
As discussed in https://github.com/webcompat/webcompat.com/issues/3671, for issues that require a regression for Android (not reproducible in desktop, just in mobile) is there another way to make/help with the regression?
=== Product Team task (SV) ===
[FYI] Activation link is working, we have access
karl: perform some tests using Chrome and then check with Firefox spoofing as Chrome.
oana: subscription is needed
== February 8 2022 ==
=== Issues reproducible on other browsers (e.g Waterfox, Comodo IceDragon, SeaMonkey) (karl) ===
karl: there should be left unassigned, maybe someone can diagnose them.
karl: we need to find someone to look over them (work in progress) based on each browser
=== Product Team task testing (SV) ===
We have access now but we don't have a subscription.
oana: if I access the site using Firefox, I get the unsupported message and missing subscription
karl: I will have a look, it was working on my side a while ago, with Chrome UA
oana: maybe the subscription is outdated?
=== UA Override/Intervention verification automation (SV) ===
Since Automation Test Suite is almost complete, can we get access to it so we can do a bit of research?
karl: Firefox source code is needed to run the TS
karl: progress is available here: https://bugzilla.mozilla.org/show_bug.cgi?id=1715900
oana: we'll spend some time on this, when time permits
=== SmartBlock verification (SV) ===
We've asked about performing verification on the new section SmartBlock from `about:compat`.
oana: I've talked with Ethan and it seems that this part is also checked using Automation.
=== Suspicious sites (SV) ===
As discussed with Dennis on Slack, for pages that present a Safe Site warning, we will be closing them as Non-compat as sons as the access on the page presents the Safe Site warning message (see: https://github.com/webcompat/web-bugs/issues/99266).
Sometimes these warnings are present in one browser, but not in another.
Are there any tools besides comparing the site in other browsers that might help us better identify pages like this?
Sometimes they pass as legit, when actually they are not
karl: don't spent time on them, just close them as Non-compat.
=== Illegal streaming sites (SV) ===
For sites that are illegally streaming content, how can we better identify which ones are legally doing this and which ones are not legally doing this?
(e.g. Karl- loads of pop-ups present might be a clue, see: https://github.com/webcompat/web-bugs/issues/81434)
karl: don't spent time on them, just close them as Non-compat.
== January 11 2022 ==
=== 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 ==
=== Issues that are reproducible using other browsers, and not when using Firefox (SV) ===
Should we keep the same approach for issues that are reproducible using other browsers (as the ML BOT does not auto-assign people when the milestone is changed to `needsdiagnosis`)?
karl: we have 3 options:
1. don't triage
2. triage but don't diagnose them, point out to someone who works on that browser (e.g Chrome - Mike Taylor)
3. triage and create an add-on to open a bug on the specific repository
Created task: https://github.com/mozilla/webcompat-team-okrs/issues/246
raul: investigate the number of issues coming from Firefox and the rest of vendors, since that also affects the number of Needsdiagnosis issues
karl: indeed, we need to better understand how many bugs from each browser vendors, and their versions and platforms
Created task: https://github.com/mozilla/webcompat-team-okrs/issues/247
=== Testing account needed (SV) ===
Are there any news about our testing account for Product team proposal task? We've checked the email but there was nothing related to it. We could also use our Mozilla accounts, if the testing account is not preferred.
karl: no news yet
karl: we can discuss with Karen more info
karl: I'll create a slack channel for it
=== iOS versioning (karl) ===
The iOS version number will reach a similar number as Android version of Firefox
karl: iOS Firefox Daylight is planning to align with Fenix starting in January 2022 with v96
karl: iOS Firefox Release will not have "Report issue" button - less issue probably.
=== [FYI] PTOs ===
Oana: 20-22th, December
Raul: 24th, December & 29th-31st, December
== November 16 2021 ==
=== 2022 Planning (SV) ===
We've added our proposal for 2022 as discussed.
https://github.com/mozilla/webcompat-team-okrs/projects/15
karl: waiting for all the team members to add their OKRs task untill the end of the week and we'll discuss them after
=== Site intervention verification (SV) ===
We'll be performing the 2nd verification for Interventions/UA Overrides on the 17th of November.
The 3rd verification will take place on 22nd of December since the soft freeze Firefox Release 97 is scheduled for 2022-01-06.
Based on the OKR task https://github.com/mozilla/webcompat-team-okrs/issues/199, there is no Bugzilla issues created for the Firefox 97.
karl: I'll create the Bugzilla issue.
=== Product Team proposal task (SV) ===
Based on the document provided, should we start investigating and create a testing plan or we should leave this for the first quarter in 2022.
karl: let's wait for access on the SV test account and discuss it after
=== Webcompat Roadmap document (SV) ===
We had a document with all the team tasks for 2020. 
https://docs.google.com/document/d/1hjlAfVK2W1Y3E4Jr8aDG_ikwacZt2wNi0qGceKnyIrw/edit#heading=h.94q8e5sloqvw
Should we revive & update it or we have enough documents and tracking places for this?
karl: I'll look over it and see if it needs to be revived.
=== Webcompat Team log (SV) ===
We've added all our work each week on the Team log document, but we haven't seen much activity on it from the rest of the team. Should we continue adding our work there or not?
https://docs.google.com/spreadsheets/d/15ONn602MHXzuhCl5c2ODo5xmdDNnYUzJ9ptGsJTd-8E/edit?skip_itp2_check=true#gid=876973640
karl: we'll discuss it in the our channel
=== Enable/disable Firefox v.100 (SV) ===
Is there a config pref that can be switched of to enable/disable Firefox v.100 experiment?
oana: I found that `nimbus.syncdatastore.firefox100.firefoxVersion` set to `0` is for latest Firefox Nightly 96 and if it is set to `100` it is for Firefox Nightly 100.
Could you confirm this is the correct pref?
karl: talk with C. Peterson for more details.
oana: it is the correct pref (confirmed on slack)
karl: Fyi the experiment will continue on Firefox Dev Edition too
=== [FYI] PTOs (SV) ===
Oana: 18th-19th of November
Oana: 29th of November - 3rd of December
National Holidays: 30th of November and 1st of December
== November 2 2021 ==
=== Issues reproducing just in Private Browsing Mode - Fenix (SV) ===
For some issues that are reproducing in Private Browsing mode and in Firefox Focus, but not on the regular build of Nightly, where should we log this kind of issues? (In Webcompat repository, the Focus repository, etc)
karl: this is similar to ETP, so ask Tom
=== OKR Q4 checklist (SV) ===
What do you think about our OKR Q4 proposal from the tasks dashboard?
https://github.com/mozilla/webcompat-team-okrs/projects/14
karl: manual testing, I'll talk with product team and figure out what feature/top web sites is worth being tested, I'll keep you in the loop
=== Firefox v.100 (SV) ===
We did received some issues related to Firefox v.100. How is the experiment seen overall?
oana: I have an older profile that received v.100 and a new profile with v.95, so I've been checking sites on both versions.
karl: all good, we don't receive many reports
=== 2022 Planning (SV) ===
We've started considering some OKR tasks already.
karl: add them to the new dashboard https://github.com/mozilla/webcompat-team-okrs/projects/15
karl: after discussing with product team, we'll add new tasks
== October 19 2021 ==
=== Chrome - Safe browsing (SV) ===
Chrome also has a Tracking Protection system now chrome://settings/security
Should we also test compatibility between Firefox and Chrome in regards to Tracking Protection?
karl: no, ETP in Chrome has different implementation then Firefox, so no need to focus on this part
=== Adding labels to ETP issues on Bugzilla at the "Project Flags" section (SV) ===
Should we add any status for "Webcompat priority"? (e.g "?") when reportin a bug in Bugzilla?
karl: ask Tom (ETP/Privacy team is working on this part)
=== OKR Q4 checklist (SV) ===
We've added our OKR proposal to the tasks dashboard.
https://github.com/mozilla/webcompat-team-okrs/projects/14
Let us know if there is something else we need to work on besides this.
karl: I'll look over it tomorrow
karl: we need to figure out if we drop the iOS reporting and testing. I'll keep you in the loop
=== Firefox v.100 (SV) ===
We did not received any new issues related to Firefox v.100, so we'd like to check also if it really works, by testing top Alexa 50 sites.
karl: the experiment needs to be restarted
karl: postpone our testing for after the experiment
=== Firefox Focus ETP issues (SV) ===
Since we are going to report Focus ETP issues on Bugzilla, which type on protection should we consider (Strict/Standard)? We only have ETP enabled or disabled.
karl: consider it as Standard 
=== 2022 Planning (karl) ===
We should start planning our work for 2022.
oana: we'll start this.
== September 21 2021 ==
=== Firefox Version 100 experiment (SV) ===
How is the experiment going?
oana: from our side, we don't see many issues logged with Firefox version 100. Could this be an indicator that not many sites are broken or that not many people are testing and reporting the issues?
karl: it seems to be working, but indeed there are not many reports
karl: it seems the experiment is only for Desktop
karl: I will talk to Chris about it (if there are special requirements for people to get Firefox 100)
raul: in `about:studies` the Firefox 100 UA is active for all users, even if we still have Firefox 94 UA
=== Request info from users - Bugzilla Triage (SV) ===
How should we handle issues from Bugzilla triage when users that we have requested info from do not reply, but they remove the "need info" tag?
E.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1183994
karl: close as usual if we can't reproduce
== August 24 2021 ==
=== Firefox version 100 Testing (SV) ===
We were thinking of checking a few sites using the Firefox 100 UA to make sure everything works correctly.
At the same time we are planing a volunteer event, probably in October, where they can test different sites using the UA string (we'll will provide guidelines for them).
The event will probably be a week, but volunteers are welcome to continue testing until Firefox reaches version 100.
Probably a test Party will be held in SV with the same objective. What do you think about this plan?
karl: that sounds nice, but wait until version 94 is released
karl: there will be an experiment (one month/one release) where Nightly users will get version 100
karl: if we get too many issues (thus too many sites broken) the experiment will be stopped and a different approach will be taken in consideration regarding the versioning
karl: pref change will be inside Firefox Nightly, can be switched off when needed
=== UA Overrides and Interventions dashboard missing (SV) ===
The link https://arewehotfixingthewebyet.com/list/android-components used to display the list of current interventions and overrides, but now it redirects to Wiki page
https://wiki.mozilla.org/Compatibility/Interventions_Releases#Currently_Released_Interventions/
The dashboard was really useful for us when performing the verification.
karl: Dennis removed it, talk with him about it
oana: I've talked with Dennis and he will create a similar dashboard for the next round of verification
=== UA Overriding on Slack testing (SV) ===
Dennis asked if we would be interesting in testing this.
Bugzilla issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1626121
Webcompat issue: https://github.com/webcompat/web-bugs/issues/82623
Should we schedule a testing session using Chrome UA to test Slack video conferencing?
karl: talk with Dennis for more info (what is expected from the test)
oana: I've talked with Dennis and he will keep us in the loop and provide the necessary info for testing in 2-3 weeks
== August 10 2021 ==
=== Culture Amp goals (SV) ===
Do we need to add goals to https://mozilla.cultureamp.com/performance/teams or this is just for Mozilla employees?
karl: no need, this is mostly for Mozilla employees to have visibility on their performance and goal achievement
karl: for SV team tasks are available in the OKR dashboard
=== Beta versions of mobile OS (SV) ===
We have received a few issues that occur on OS that are in beta version (iOS 15, Android 12).
Should we keep telling the users that the beta versions are expected to fail and that there is nothing we can do until the release version is out, or should we follow a new approach?
karl: approaches:
  1. put them on the waiting list - to review it later when the new iOS/Android version is released
  2. tell them to reopen it if it is still reproducible when the new release is available.
raul: approach 1 - issues will pile up,
raul: approach 2 - probably the issue will not occur on the new OS, but if it will the affected users will reopen the old issue or report a new one
=== WebCompat team internal logs (SV) ===
We've added the progress for week 30 and 31 in the document.
Should we have a separate tab per person or we can go simply with SV?
oana: preferably we should have a tab for the SV team - and we'll add our weekly progress and highlights there
Do we need to add all the issues we worked on for Triage/Moderation/Investigation/Verification?
oana: we have daily status that we add to our internal tool every day, should we add that here too?
karl: add the most important things in the highlight tab (how many issues/finished a task/blog post/test party)
=== Hulu account (SV) ===
We don't have an account to test and can't seem to use Alex's account (it is blocked).
oana: he does comment on the issues if pinged, but it would be useful for us to have an account
karl: I'll talk with Alex.
=== [FYI] PTOs (SV) ===
Oana: 30th of August - 3rd of September
Raul: 6th of September - 17th of September
Mozilla: 27th of August Wellness day
Karl: 30 of August - 31th of August
== July 27 2021 ==
== July 27 2021 ==


Line 564: Line 1,136:
Karl: Yes, add all the proposed items as cards.
Karl: Yes, add all the proposed items as cards.


=== Finish every week with 0 untriage and 0 unmoderated bugs (SV) ===
=== Finish every week with 0 untriaged and 0 unmoderated bugs (SV) ===


This was proposed last quarter by Mike, in order to see if we can handle all issues by the end of the week. Since the number of issues was not high, we successfully managed to triage and moderate all of them.  
This was proposed last quarter by Mike, in order to see if we can handle all issues by the end of the week. Since the number of issues was not high, we successfully managed to triage and moderate all of them.  
OanaArbuzov
83

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1237070...1242003"