From MozillaWiki
Jump to: navigation, search


Scribed by James

action-needspatch labeling (ksenia)

"Please add more action-needsitepatch". Ksenia will explain.

  • Would be nice to collect the issues that require a site patch.
  • If you come across an issue that requires an intervention then add the label
  • Should be liberal in adding the label, but we will have to prioritize when it comes to implementation
  • For really important ones, maybe add a bmo bug and link to the next intervention bug

More agressive site interventions (karl)

We should probably think on being more systematic on Site Interventions. Ultimately we want to improve the user experience. Questions? Performance.

  • Should site patch more often even where sites aren't top sites.
  • Does this create perf issues? Specifically on Android?
  • Do patch and then move the bug to outreach.
  • There are costs to each site patch, but it's small compared to e.g. uBlock
  • Maintainability and code size are concerns
  • Two things to worry about: maintainability and internal policy. Previously we tried to create site patches where we can't afford breakage on a top site or when we have a clear plan to remove after outreach.
  • For big sites we have specific contacts. Small sites can be really important to specific groups. If patch is easy might be better to just add it and help someone. For big patches it might only make sense for big sites.
  • Shims can already be used to fix things across sites e.g. lib bugs. That can be higher impact. Can also cause breakage, but risk is worthwhile.
  • Fastclick for example.
  • Where libs are sufficiently sepearate from site logic we can fix them.
  • How is lifecycle of the patches managed? Could lead to breakage if the site tries to update and we're still applying a patch designed for the old site.
  • Automated tests will help here. Firefox will inform the site in the console, so they can be aware of the patch. We have also tried to contact the site manually.
  • Worth having extension for Chrome that advertises patches on Firefox?
  • Maybe would work better if the Chrome team were involved.
  • Could propose to foolip.
  • Problem is that it requires the site developer to care about Firefox which they probably aren't since their site is broken in Firefox. Might be more effective if it was in default tools.
  • Could make users aware, so they inform the site.
  • Some chance for collaboration with Safari?

FYI: 2021H1 Bucket List (karl)

We had collected some ideas as a project list. a couple of months, do you still feel strongly about some of these?

  • [TODO] For everyone in the team, read the list again, and assign it to me with a comment if you think we should still do that. I will add it to JIRA as backlog for future before projects.

FYI: Firefox iOS process for UA override status (karl) (Moz NDA only) (Moz NDA only) (Public View) We started discussions on defining a process for UA override (and more largely site interventions in Firefox iOS). There are some questions to address.

FYI: DevTools / Webcompat Team work (karl) (Moz NDA only) The devtools team will start working on 2021H2 on fixing some of the priority bugs for webcompat diagnosis work. It's a good opportunity to remind everyone in the Webcompat team and contributors, that if there is something not working properly, buggy or a missing tool, please do file a report about it on Not everything will be fixed, but only things which are known can be fixed. And add it

  • Diagnosis in Fenix can be tricky due to disconnections etc. Geckoviewexample can be used instead and is more reliable. It also has fewer features so you can tell if it's a Gecko problem vs a feature problem (e.g. tracking protection)
  • Responsive design mode on desktop can also be used to tell if the problem is gecko specific

Incompat add-on (SV) Useful add-on we QA use to check if other issues were reported on the same domain.

  • Only works with right now
  • Bugzilla support would be a good feature.

Two Minutes ( 👹 )

The useful, the silly, the things you did since the last meeting. Pro and Perso accepted.

  • Dennis: Pentested the blood-pressure and sleep-regulation mechanisms in my body, found several critical exploits. Continued work on documenting the SAO update rollout process. Diagnosing some new and some old issues.
  • Guillaume: merge some dependencies, working on improving the dashboards.
  • James: wdspec test profile usage yak shaving. Writing up something about when we author wpt in gecko.
  • Karl: diagnosis. Jira organization. Deployed Coding some PRs to solve simple issues. Missing doing code reviews. Starting to reorganize webcompat strategy document. Started to create a small playhouse in wood for my son (which is a cafe for him).
  • Kate:
  • Ksenia: working on adding support for using our model in bugbug http service. In lockdown again
  • Oana: Triage and moderation. Easter holiday and a bit of hiking.
  • Raul: Triage and moderation. Easter holiday. And seems that I have green thumbs - started a new hobby with house plants.
  • Thomas: So much ETP shim work (but it's going very well). It's like doubling my diagnosis, in a fun way. The weather is getting nicer here too (it's interesting having a rainy season again), and I suddenly have my old dog who likes regular walks back. I'm still waiting for the cold to go away so my grass will grow, but patiently watering it feels oddly humanizing somehow (COVID coping continues!)

PTO / Travel ( 👹 )

(no more travel until the end of 2021… probably) Coming holidays across the world June 22-26 (TomW, PTO)

FYI: 2021H1 Ideas (karl)

Let's keep this around so we have a reference.