Engineering Quality in a Fast-Moving Open Source Project: WPE WebKit - Mario Sanchez-Prada, Igalia

Why It Matters

WPE WebKit runs in millions of commercial embedded devices, so its engineering practices directly affect product reliability, vendor release schedules, and downstream reputations across the device ecosystem. Robust testing, CI, and upstream/downstream coordination reduce the risk that upstream changes will cascade into costly field failures.

Summary

Mario Sanchez‑Prada of Igalia outlined how the WPE WebKit project manages engineering quality amid rapid, large‑scale open‑source development. He emphasized that WPE is a mature WebKit port for Linux embedded devices used in millions of products, and that its diversity of ports, hardware, and configurations creates a combinatorial testing challenge. To sustain quality while code changes weekly, the team treats quality as a continuous process—relying on targeted testing strategies, CI/Q infrastructure, stabilization windows, and close upstream‑downstream alignment—and accepts that regressions are inevitable but must be detected and mitigated quickly. The talk framed practical governance and tooling choices Igalia uses to keep releases stable across constrained, hardware‑accelerated platforms.

Original Description

Join us at the premier vendor-neutral open source conference, where developers and technologists come together to collaborate, share knowledge, and explore the latest innovations and advancements in open source technology. Learn more at https://events.linuxfoundation.org/

Engineering Quality in a Fast-Moving Open Source Project: WPE WebKit - Mario Sanchez-Prada, Igalia

Building an embedded product on top of a large Open Source codebase like WPE WebKit is only the first step. The real challenge is keeping its quality stable as thousands of lines evolve and hundreds of changes land every week across multiple platforms.

In such an environment, errors and regressions are inevitable. What matters is detecting them quickly, understanding their impact, and reacting before they propagate further. This talk focuses on the engineering work that makes this possible, an effort that is essential yet often invisible.

Using WPE WebKit as a case study, we will explore how quality becomes a continuous engineering effort rather than a final validation phase and how CI and QA infrastructure, testing strategies, and processes (e.g. stabilization windows) sustain upstream development while supporting downstream deployments. We will show how these feedback loops reinforce each other and why aligning upstream and downstream processes is critical to keep quality stable over time.

This talk targets engineers, maintainers, and technical leaders working on large Open Source projects, as well as teams building products on top of them who need to sustain quality at scale.

How