From MozillaWiki
Jump to: navigation, search


Scribed by Ksenia

Site Interventions and Firefox Nightly (karl) How hard would it be to have Site Interventions working on Firefox Nightly "immediately", and then the normal release process for beta and releases. Do we gain things, do we shoot ourselves in the foot?

  • karl: one of the engineers asked when the patch is testable in nightly. how hard it will be to do a site intervention on nightly first instead of pushing it to github first?
  • dennis: this creates some additional work when creating patches and creating phabricator review. and there is an issue with version numbers
  • james: could you move the process to be in mozilla-central?
  • thomas: mozilla-central is not the only place we have to import the patch, it's also has to be in gecko. there is a problem with syncing, so removing one place to sync theoretically could improve that
  • dennis: if we want to have an ability to ship to release user we need to have our code in mozilla extensions repo. we have all the tooling helping with building extension
  • thomas: to implement that in mozilla-central it may require lots of work
  • james: we import releases to github, but the main codebase is gecko
  • thomas: there are known issues in terms of addons standpoint with converting
  • dennis: wonder if we gain anything from it?
  • karl: sometimes we need to fix something quickly
  • ksenia: I had an intervention in the past that was deployed seperately because it was urgent. So it's a matter of determining the urgent ones.
  • thomas: we would gain to do dogfooding on our site interventions. we also could add an ability for interventions to select a channel, so it's only released on nightly
  • dennis: the main problem is we want to ship faster, so it's a separate concern
  • thomas: we can make it ship faster on case by case basis
  • dennis: we do accelerate some patches occasionally if it's urgent.
  • ksenia: No too hard to do. It's pretty fast.
  • thomas: just need the buy-in from who owns the beta cycle.
  • m:

2021H2 Work (karl)

We need to organize our work for 2021H2. * Automation test suite for site interventions and shims (at scale) * Firefox iOS UA overrides from site interventions at Build time. * Firefox iOS ETP shims mechanism * Auto-labeling of old webcompat issues by the ML bot. * Freezing UA work (web standard) * WebDriver-BiDi * wpt (priorities tbd) * … other priorities? * … Guillaume, kate, you are also welcome to put something if you want.

  • karl: it's a reminder to come up with thoughts and ideas on future webcompat work

Two Minutes ( 👹 )

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

  • Dennis: diagnosis archaeology.
  • Guillaume:
  • James: Re-refactoring. Got some feedback on WebDriver-BiDi PRs. Reviewed lots of py3 cleanup PRs on wpt; adding more static type analysis.
  • Karl: diagnosis. deploying webcompat. CDPs. Planted the mango seed. And trying to grow roots of a pineapple. The brain is an amazing thing.
  • Kate:
  • Ksenia: finished adding github support for bugbug http service, a bit of diagnosis
  • Oana: Triage and moderation. Bike, Hike & Gardening (transfered the cucumber and radish outside)- Awesome weather.
  • Raul: The usual triage and moderation. Enjoyed the wonderful weather. No dead plants at the moment in my small in-door garden.
  • Thomas: I was asked to roll out a fix for bz1707795 on short notice. Also more shim research-and-development and diagnosis. The weather here continues to improve, and I'm looking forward to enjoying it.

PTO / Travel ( 👹 )

(no more travel until the end of 2021… probably) Coming holidays across the world June 9 (TomW, taking the day off due to having to drive surprisingly far for a Covid vaccine) June 22-26 (TomW, PTO)

FYI: 2021H1 Ideas (karl)

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