Jekyll2026-09-07T00:18:01+00:00https://www.igalia.com/feed.xmlIgaliaIgalia is an open source consulting firm specialised in the development of innovative projects and solutions. Our engineers have expertise in a wide range of technological areas, including browsers and client-side web technologies, graphics pipeline, compilers and virtual machines. We have the most WPE, WebKit, Chromium/Blink and Firefox expertise found in the consulting business, including many reviewers and committers. Igalia designs, develops, customises and optimises GNU/Linux-based solutions for companies across the globe. Our work and contributions are present in many projects such as GStreamer, Mesa 3D, WebKit, Chromium, etc.IgaliaCall for Proposals: Interop 20272026-09-03T00:00:00+00:002026-09-03T00:00:00+00:00https://www.igalia.com/news/Call-for-Proposals-Interop-2027Today marks the launch of the seventh annual Interop project! Each year, the process begins with a call for proposals, asking the larger web development community what features they want to see included in the next year’s Interop project. For 2027, that call begins today and lasts through September 23, 2026, and the submission form is open to one and all. For insight into how proposals will ultimately be chosen, see the Interop 2027 proposal selection process.

If the past is any guide, there will be many more proposals than the group can accept. By the same token, we’ll doubtless see vast interoperability improvements for the chosen proposals. You can see this by looking at the score trends for 2025 (from 29% to 97%) and even the current status for 2026 (from 39% to 89% as of late August).

So if you have a standards-based web feature you’d really like browsers to align on fully supporting, submit a proposal! And even if you don’t, you can still help by liking and commenting on the submissions of others. To widen the scope even further, please boost the signal through public discussions on social media, blogs, and everywhere else.

Forward to a more interoperable web!

]]>IgaliaLinux 7.2 Released2026-08-19T00:00:00+00:002026-08-19T00:00:00+00:00https://www.igalia.com/2026/08/19/Linux-72-ReleasedLinux 7.2 Released

Linux 7.2 was tagged and released this week, on the regular schedule.

This cycle was one of the busiest ever, only been beaten by 6.7. This is considered the “new normal”, given that the last 3 or 4 cycles had been pretty busy, especially regarding fixes. There’s some interesting achievements this cycle, like cache-aware scheduling, improvements on MGLRU, the concept of sub-schedulers for sched_ext (a good introduction on the topic by LWN), automatic creation of multi-size transparent hugepages (also a good intro on LWN ) and more - check the LWN articles (part 1 and part 2) for the full picture.

Igalia as usual had a good share of contributions, mainly the DRM scheduler fair policy, which had a regression reported at the 11th hour (see below), hence is present as opt-in. Other than that, we landed very nifty runtime power management for GPUs in the Raspberry Pi 4 and 5, improvements in sched_ext, futex, and general bugfixing. Let’s review the highlights!

Igalia Changelog

DRM scheduler fair policy

For this release cycle we planned to land and enable the DRM scheduler fair policy which brings significant improvements in scenarios where multiple clients are sharing the GPU, and also when a light interactive client competes for the GPU with a demanding one. Unfortunately, due a last-minute regression report during the 7.2-rc7 week, the default policy will remain the old first-in/first-out (FIFO) scheduler. As the fix for the fair policy regression is already known and early testing looks promising, we are hopeful it will get re-enabled in a next kernel release.

sched_ext

We improved sched-ext observability to simplify debugging. When a custom sched-ext scheduler hits a runtime error – such as failing to schedule a task for over 30 seconds – the kernel ejects it and reverts to the default scheduler. To help diagnose these failures, the kernel dumps the status of each CPU. However, especially on high-core systems, these dumps can be truncated due to buffer size limits between kernel space and user space. We mitigated this by prioritizing the exit CPU (the CPU that triggered the error) so it is dumped first, while also surfacing its CPU ID directly to BPF schedulers and userspace tools.

Power Management to Raspberry Pi GPUs and more

In this release, we landed support for Runtime Power Management on the Raspberry Pi 4 and 5 GPUs.

Until now, the V3D driver had a very simple power model: the GPU clock was enabled during probe and remained enabled for the entire lifetime of the driver. Although this approach was simple and functional, it meant that an idle GPU would still consume power even when it was not actively executing jobs.

With Runtime PM, the GPU is powered only when it is actually processing work, and its clock can be disabled while the GPU is idle. This reduces power consumption when the Raspberry Pi is not using the GPU. We wrote a blog post about this feature with more details and some power measurements.

We also fixed two long-standing bugs in the Raspberry Pi 3 GPU driver that had been affecting RetroPie users for years, causing random GPU hangs and complete system crashes. The problems were traced to how the kernel handled tile memory when the GPU ran out of space while processing a frame. Our fixes ensure that each graphics job only writes to its own memory area and that reused memory is properly cleared before being used again, preventing stale or corrupted data from reaching the GPU. With these fixes, RetroPie users should no longer experience the crashes that could occur while navigating the menus.

Finally, we landed several fixes for GPU resets on Raspberry Pi 4 and 5, making the reset process more reliable and consistent.

Futex tests and documentation

We continue to work to improve and maintain futex(), an important system call used by all types of workloads to create synchronization mechanisms. In this cycle, we helped to design and land a solution for a 14 year old bug that has been affecting the robust list mechanism with data corruption in some edge cases.

General bugfixing

We have fixed a long-standing issue in the ueagle-atm driver, which could hit a race condition between kernfs create and remove operations during device probe and disconnect, through the request_firmware API, and generated several bug reports in syzbot over the years.

We helped to improve the correctness of the inline-assembly implementation of memcmp() used during x86 boot, preventing subtle potential bugs due to compiler optimization and instruction reordering.

Towards full HDMI 2.1 support

Part of the HDMI 2.1 Fixed Rate Link (FRL) support released in this version dates back to the work of Rodrigo Siqueira from Igalia during his time at AMD. This work implements the initial support that allows the amdgpu driver to communicate with HDMI 2.1 monitors (primarily the FRL implementation). This implementation was outside the main code for several years before being incorporated into the source code, with some parts kept virtually as originally written and others reworked throughout the process. At Igalia, we have experience with various DRM/KMS drivers, and this hands-on experience with HDMI 2.1 features complements the knowledge necessary for vendors to enable cutting-edge features to their own drivers.

Authored (82)

André Almeida

Changwoo Min

Helen Koike

John Harrison

Jose Maria Casanova Crespo

Mauricio Faria de Oliveira

Maíra Canal

Thadeu Lima de Souza Cascardo

Tvrtko Ursulin

Reviewed (74)

André Almeida

Changwoo Min

Christian Gmeiner

Iago Toral Quiroga

Luis Henriques

Maíra Canal

Melissa Wen

Tvrtko Ursulin

Acked (13)

Maíra Canal

Melissa Wen

Thadeu Lima de Souza Cascardo

Tvrtko Ursulin

Maintainer SoB (5)

Christian Gmeiner

Maíra Canal

]]>IgaliaBringing Edge AI to the Raspberry Pi GPU2026-08-12T00:00:00+00:002026-08-12T00:00:00+00:00https://www.igalia.com/2026/08/12/Bringing-Edge-AI-to-the-Raspberry-Pi-GPUGoogle AI Edge and Raspberry Pi have published a joint announcement on running on-device AI on the Raspberry Pi 5 with LiteRT, Google’s on-device inference runtime, and the Gemma family of open models. The announcement — published on the Google for Developers blog and the Raspberry Pi website — shows a Raspberry Pi 5 running language, vision, and speech models entirely locally, including the Reachy Mini robot demo, where object detection, speech recognition, and a Gemma 4 E2B language model work together in real time with no cloud dependency.

Igalia contributed the GPU driver side of this work as part of our long-standing collaboration with Raspberry Pi on its open-source graphics stack. José María Casanova, from Igalia’s Graphics Team, enabled the experimental WebGPU support in Mesa’s V3DV Vulkan driver that LiteRT’s WebGPU backend needs to run on the VideoCore VII GPU, through the Dawn WebGPU implementation. This experimental support makes it possible to run inference on the GPU alongside the CPU, so continuous workloads can execute without competing for the CPU cycles that language-model inference and application logic need — as the Reachy Mini demo does, running its object detection on the GPU while Gemma runs on the CPU. It can be enabled with the V3D_WEBGPU_OVERRIDE=1 environment variable in the updated official Raspberry Pi OS Mesa package.

As with all of our graphics work, these improvements were developed in upstream Mesa, so they benefit every Vulkan and WebGPU user on Raspberry Pi devices, not just AI workloads. Work continues on the V3DV driver to improve compute and 16-bit floating-point performance, bringing more of the platform’s capabilities to on-device AI.

]]>IgaliaIgalia and Bocoup: Cooperatives Unite2026-08-12T00:00:00+00:002026-08-12T00:00:00+00:00https://www.igalia.com/2026/Igalia-and-Bocoup-Cooperatives-UniteIgalia is pleased to announce that we have reached an agreement with the workers of Bocoup to become part of our collective effort, bringing their well-aligned experience and values.

Igalia has grown steadily in recent years, expanding our cooperative with more and more people who care deeply about open source, the web, and collaborative ways of working. This union with the workers of Bocoup continues that trajectory, strengthening our collective with people whose commitments align closely with our own.

We’re delighted to welcome our new members. Their work, leadership, and long experience in the web community, along with their dedication to cooperative models, make this a meaningful moment for us. As part of this agreement, Igalia will also acquire Bocoup’s brand assets and continue to maintain the website for some time, ensuring continuity for the identity and legacy Bocoup has built over the years.

This marks an exciting milestone for our cooperative. It reflects our belief that collaboration strengthens us — and that cooperatives can grow not only by scaling, but by joining together. We’re looking forward to what we’ll accomplish as a unified collective.

our two logos with a plus between them

You can also read the announcement on bocoup.com.

]]>IgaliaIgalia at FOSSY 20262026-08-06T00:00:00+00:002026-08-06T00:00:00+00:00https://www.igalia.com/2026/08/06/Igalia-at-FOSSY-2026FOSSY (Free and Open Source Yearly), hosted by the Software Freedom Conservancy, is happening this weekend, in Vancouver, Canada! It’s taking place from August 6-9, 2026.

Igalia is there, and will be presenting two talks about the company from different perspectives:

  • “From Corporate To Co-op: Working on Chrome at Igalia and Google” by Sharon Yang - Igalia is a small, cooperative consulting firm specializing in open source. Google is one of the world’s largest publicly traded corporations. Both have teams working on Chromium, a massive open source project. As a new Igalian and former Googler, Sharon gives an insider’s take on contributing to Chromium at both organizations.
  • “An Open Source Stack - Running a company using FOSS” by Danielle Mayabb - Igalia is an open-source consulting firm specializing in areas such as web standards, web engines and accessibility. In this talk, Danielle Mayabb, from Igalia’s tools team, will talk about how Igalia uses FOSS to power the company. She will cover the technologies Igalia uses, how using an open stack compares to a corporate stack, and the pros and cons of each.

Come say hi if you’re there too! And if you have questions about any of our talks or just want to learn more about Igalia, feel free to get in touch.

]]>IgaliaIgalia at GUADEC 20262026-07-15T00:00:00+00:002026-07-15T00:00:00+00:00https://www.igalia.com/2026/07/15/Igalia-at-GUADEC-2026GUADEC, the GNOME community’s annual conference, is coming to A Coruña — Igalia’s hometown — this year, taking place from July 16th to 20th at the Facultade de Informática of the Universidade da Coruña. Igalia has a long history of contributing to GNOME, and we’re glad to see the community gathering so close to home.

Several Igalians will be there in person, and we’re presenting three talks:

  • “Some more governance” by Emmanuele Bassi  — Governing a project the size of GNOME isn’t something you can improvise in an afternoon; it develops over time as you learn what works and what doesn’t. Emmanuele looks at how GNOME’s governance is taking shape, starting with the Platform Team and the components of the application development platform that GNOME itself is built on.
  • “Taking Out the Garbage Once and for All” by Tim Chevalier and Emmanuele Bassi  — The “Tardy Sweep” bug has forced GNOME Shell to run a garbage collection cycle every ten seconds for the better part of eight years. A proof-of-concept fix has existed for a while, but landing it without making memory usage worse required the in-depth profiling and research that Igalia stepped up to support. This talk covers how that work finally crossed the finish line.
  • “JavaScript in GNOME 2026, Types, Types and More Types” by Philip Chimento  — Types make a medium-to-large JavaScript codebase much easier to statically analyze. Philip covers the ongoing work to make writing GNOME apps in TypeScript easier, some new debugging capabilities, a sneak peek at this year’s JS engine upgrade, and project ideas for anyone who wants to get involved.

If you’re attending GUADEC, come say hi — many of us are based in A Coruña, so you’ll have no trouble finding Igalians around. And if you have questions about any of our talks or just want to learn more about Igalia, feel free to reach out.

]]>IgaliaIgalia and Wind River Collaborate to Deliver Production-Ready Web Runtime for Embedded Linux Devices2026-07-06T00:00:00+00:002026-07-06T00:00:00+00:00https://www.igalia.com/2026/07/06/Igalia-and-Wind-River-Collaborate-to-Deliver-Production-Ready-Web-Runtime-for-Embedded-Linux-DevicesIgalia, an open source engineering consulting firm with over 25 years of experience in Linux-based systems and Web engine development, is pleased to announce a collaboration under the umbrella of the Yocto Project with Wind River, a global leader in embedded Linux platforms, to deliver a production-ready Web runtime for embedded devices.

The joint solution combines WPE WebKit, the open source Web engine port created and maintained by Igalia specifically for embedded Linux environments, with Wind River Linux, a commercially supported, Yocto-based embedded platform. Together, the two companies provide embedded product teams with a fully integrated, standards-based Web runtime backed by direct access to upstream maintainers.

A critical component of the solution is the meta-webkit Yocto layer, maintained by Igalia since 2017. This layer contains the necessary build recipes, supports multiple Yocto versions, and provides backported security fixes. It also serves as the foundation for upstream WebKit’s continuous integration (CI) infrastructure on real hardware targets, including the popular Raspberry Pi platform. This CI infrastructure allows to identify and resolve issues before they reach downstream product teams, meaningfully reducing risks for product teams.

Together, Wind River and Igalia provide embedded developers and product teams with:

  • A production-grade embedded Linux platform integrated with WPE WebKit
  • A standards-based Web runtime designed for constrained and headless devices
  • Direct access to upstream maintainers of WebKit and the WPE stack
  • A fully open source solution, minimizing dependency on proprietary frameworks

A Web engine provides a full application runtime that includes rendering, scripting, networking, and multimedia support, making it a compelling alternative to proprietary UI stacks. This is why modern embedded devices are increasingly adopting Web-based runtimes, including devices such as industrial human-machine interfaces, automotive systems, home appliances, smart TVs, and set-top boxes. Igalia’s deep and broad experience with Web engines, along with our foundational focus on open source development, gives us a unique skill set to bring to projects that use Web engines and similar open technologies.

This collaboration between Igalia and Wind River is the latest entry in our long history of helping others meld the power of the Web with their projects to deliver truly robust solutions, creating a strong foundation for building modern, Web-based embedded applications. It allows product teams to accelerate development, reduce integration complexity, and maintain long-term control over their software stacks using open source technologies. Embedded teams that need upstream support and long-term WebKit alignment now have a production-grade Linux platform to pair with it.

If you’d like to work with us, please get in touch to learn more and see how we can help your project get further, faster.

]]>IgaliaThat’s a Wrap on the 2026 Web Engines Hackfest2026-06-25T00:00:00+00:002026-06-25T00:00:00+00:00https://www.igalia.com/2026/Thats-a-Wrap-on-the-2026-Web-Engines-HackfestLast week (June 15–17), Igalia hosted the 2026 edition of the Web Engines Hackfest at Palexco in A Coruña. More than 150 browser developers, standards tinkerers, low-level engineers, and interested folks from around the world joined us, in person and remotely, for three days of talks, breakout sessions, and in-depth conversations. Thanks to everyone who came — the event wouldn’t be the same without you!

On Monday, we had nine talks, all live-streamed on the Hackfest’s YouTube channel. Individual recordings will be posted soon; in the meantime, you can watch the full livestream:

  • “Accessible Testing in WPT: From Dream to Reality” by Valerie Young  — Cross-browser test suites have long helped browsers track interoperability, but until recently they couldn’t tell you whether a feature’s accessibility support was complete. This talk covers the tests you can now write in WPT and WebDriver, the challenges along the way, and the work still in progress.
  • “HarfBuzz at 20!” by Behdad Esfahbod  — A look back at twenty years of the HarfBuzz text shaping engine, its current state, and its future, with significant focus on the Rust port, HarfRust. Behdad’s slide deck is well worth a read — and far too long to have presented in full.
  • “Iterable Streams” by James Snell  — Node.js and Cloudflare Workers have been experimenting with an async-iterator-based stream API that’s faster than both Node.js streams and Web streams. A look at the approach, to prompt a conversation about how to move forward.
  • “Decoupling Extensions from Chrome: The Journey to a Modular Extensions Layer” by Miyoung Shin & Lorenzo Tilve  — The ongoing effort to decouple Chromium Extensions from the Chrome layer for a more modular, embeddable architecture, covering the motivation, migration strategy, lessons learned, and current progress, with a live demo.
  • “The EU Cyber Resilience Act: what is it, and how does it affect web browsers?” by Aki Rose Braun & Daniel Ari Ehrenberg Goldberg  — The EU Cyber Resilience Act applies to nearly all software in Europe, no matter where it’s built. Aki walks through the broad strokes of the regulation, and Dan digs into the specific obligations of browsers and what makes them special.
  • “Introduction to the RustNN ecosystem” by Markus Tavenrath  — An overview of RustNN, a high-performance WebNN implementation, including its model exporters for PyTorch and ONNX and bindings for Python, JavaScript, and the browser.
  • “DOM Localization” by Eemeli Aro  — A proposal for a set of core HTML attributes that would let developers bind DOM elements and fragments to localized messages, defined using Unicode MessageFormat, so users can experience the web in their native languages.
  • “How to ship a registry when nobody wants to run one” by Aki Rose Braun & Ethan Arrowood  — TC55 (formerly WinterCG) needed a runtime keys registry, but nobody wanted to operate the infrastructure. This talk explains how they solved that by publishing it as an Ecma Technical Report instead.
  • “npmx: a fast, modern browser for the npm registry” by Daniel Roe & Matias Leandro Capeletto  — A community-built alternative npm registry browser, with features for choosing modern packages, promoting JS standards adoption, and collaborating with communities like e18e and atproto.

On Tuesday morning, we also ran a dedicated WPE WebKit track, with sessions on building an embedded browser on Raspberry Pi with the new WPEPlatform API, refactoring composition with Skia, reducing GPU usage, profile-guided optimization, QA practices, and the WPEPlatform API for Android.

On Tuesday and Wednesday, we had more than twenty breakout sessions on everything from memory safety in WebKit and the Web security model, to MathML Core, AsyncContext, Servo DevTools, FedCM, and Web Components. Standards bodies took the opportunity to meet face-to-face on site too, including a WHATWG meeting and a CSS Working Group meeting. The full schedule is on the Hackfest wiki.

The Web Engines Hackfest is an event that brings people together to discuss and work on different browsers and web standards. Our goal is to foster collaboration in benefit of the open web.

Many thanks to our outside sponsors, Mullvad Browser, ARM, and Huawei, for helping make this year’s Hackfest possible, and to everyone who attended in person or remotely for being a part of the growing Hackfest community. See you all next year!

]]>IgaliaLinux 7.1 Released2026-06-17T00:00:00+00:002026-06-17T00:00:00+00:00https://www.igalia.com/2026/06/17/Linux-71-ReleasedLinux 7.1 Released

Linux 7.1 has been tagged and released, closing this development cycle with over 15,000 commits.

This second release in the 7.x cycle brings quite a few noteworthy things: a brand-new NTFS driver, proper battery metrics on MacBook laptops with the Apple SMC driver, and several improvements across the graphics and DRM stack. It also continues the ongoing cleanup of older and unmaintained drivers, dropping support for things like ISDN and ham radio. Notably, Linux 7.1 begins the process for retiring Intel 486 CPU support (“i486”) in the future. For more details and a full list of changes, check the corresponding KernelNewbies page.

As usual, Igalia has been busy contributing fixes and improvements to different areas during this release. Below are some of our highlights from this cycle.

Igalia Changelog

V3D and VC4 fixes and improvements

The V3D and VC4 drivers saw several robustness and maintainability improvements this cycle. As part of the Raspberry Pi 5 upstreaming effort, we added the V3D GPU device-tree node for BCM2712, enabling V3D support on fully upstream kernels.

We also continued improving the V3D interface by migrating performance monitor tracking from IDR to XArray in both V3D and VC4. In parallel, a series of fixes addressed reference counting, scheduler integration, cache synchroniztion, and error handling issues in V3D’s compute intrastructure, improving the stability of CPU job execution paths.

On the power-management side, we refined Raspberry Pi firmware clock handling by moving clock rate management into prepare/unprepare callbacks. These changes reduce unnecessary power consumption for clock users and lay the groundwork for V3D Runtime PM support, which will land in the next kernel release.

AMDGPU User Queue Cleanup

On the AMD side, we continued our efforts to clean up the user queue submission code. This cycle, we focused on removing resource leaks in the wait and signal ioctls, consolidating exit paths to prevent deadlocks, and ensuring that userspace cannot trivially trigger kernel warnings. These changes improve the overall security and stability of the amdgpu driver when interacting with complex user-space workloads.

AuxCCS Support for Intel Xe Driver

We finalized Alderlake support for AuxCCS (Auxiliary Color Compression Support) in the Intel Xe driver. This includes adding support for frame buffer modifiers, ensuring proper invalidation of auxiliary tables, and quiescing memory traffic during cache invalidation. These changes reduce the memory bandwith consumed by UI composition and graphical rendering, improving power efficiency and overall performance on this platform.

DMA-Fence improvements for module unload scenarios

Building on the cross-system dma-fence work we did for the 6.17 kernel release, we helped upstream extend this protection to module unload scenarios. We’ve also fixed warnings related to __rcu annotations to keep the codebase clean and static-analysis friendly.

Debugging Infrastructure improvements

For developers relying on pstore and ftrace, Linux 7.1 brings important fixes. Previously, systems with KASLR enabled would cause offsets saved in debug sessions to be bogus when decoded. This has been fixed along with other pstore improvements, and an improved debugfs interface for the reserve_mem parameter. These changes should provide better visibility into memory reservation states and improve the overall state of these subsystems for debugging kernel crashes or hangs.

Another round of general fixes and cleanup

Beyond the major subsystem updates, Igalia also helped with several “odd fixes” and general maintenance work to keep the kernel healthy.

In the filesystems area, we fixed a null pointer dereference in JFS during unmount and resolved an uninitialized value issue in the FUSE layer.

For Bluetooth, we reworked the reset path in the HCI core to ensure clean adapter teardown, preventing protocol issues caused by pending work.

On the peripherals side, we implemented proper URB tracking in the libertas Wi-Fi driver to prevent use-after-free issues, and added stricter validation checks for USBTMC endpoints.

We also investigated a data race in the Real Time Clock (RTC) subsystem reported by syzbot and detected by the Kernel Concurrency Sanitizer (KCSAN). The race was determined to be safe, and the code was annotated to prevent future false-positive reports.

Finally, we’ve improved documentation for ttm_bo_swapout and implemented the corresponding KUnit tests.

Authored (76)

Alberto Garcia

Guilherme G. Piccoli

Heitor Alves de Siqueira

Helen Koike

Luis Henriques

Mauricio Faria de Oliveira

Maíra Canal

Melissa Wen

Thadeu Lima de Souza Cascardo

Tvrtko Ursulin

Co-developed (4)

Maíra Canal

Reviewed (45)

Iago Toral Quiroga

Maíra Canal

Melissa Wen

Rodrigo Siqueira

Tvrtko Ursulin

Tested (4)

Guilherme G. Piccoli

Melissa Wen

Umang Jain

Reported (1)

Tvrtko Ursulin

Maintainer SoB (7)

Christian Gmeiner

Maíra Canal

Melissa Wen

Tvrtko Ursulin

]]>IgaliaIgalia at Open Source Summit North America 20262026-05-14T00:00:00+00:002026-05-14T00:00:00+00:00https://www.igalia.com/2026/05/14/Igalia-at-Open-Source-Summit-North-America-2026Next week, Open Source Summit North America 2026 takes place in Minneapolis, MN, on May 18–20, with the Embedded Linux Conference running alongside it.

Organized by the Linux Foundation, OSS NA is a vendor-neutral gathering that pulls together maintainers, developers, and community leaders from across the open source ecosystem. It also acts as an umbrella for a number of co-located events — including cdCon, the Zephyr Project Developer Summit, and the PX4 Developer Summit — with tracks spanning Linux, embedded systems, cloud, AI and data, safety-critical software, and digital trust.

Mario Sánchez Prada, from Igalia’s WebKit team, will give a talk titled “Engineering Quality in a Fast-Moving Open Source Project: WPE WebKit” on Monday, May 18 at 3:35pm in Room 208C+D. Using WPE WebKit (one of the most prominent projects we maintain) as a case study, he’ll walk through the CI and QA infrastructure, testing strategies, and day-to-day processes that keep upstream development moving while still serving the needs of downstream deployments. He’ll also make the case for treating quality as something you build in continuously, rather than something bolted on at the end.

If you’ll be in Minneapolis, we hope to see you there!

]]>Igalia