Skip to main content
  1. Blog
  2. Article

Jane Silber
on 8 December 2010

Thanks and good luck to Matt Asay


Matt Asay joined Canonical in February this year and quickly proved instrumental in aligning strategic goals and operational activities. Unfortunately for us, Matt will be leaving Canonical December 17 for the lure of an early-stage start-up. While his time here has been relatively short, we all appreciate the positive impact he has had in many areas and I will personally be very sorry to see him go.

Matt is joining Strobe, an early stage start-up at the nexus of open source and the open web, much like Matt himself. He will be taking a senior business development position, and that opportunity provides an irresistible forum for him to exercise his skills in a customer-facing role at a small start-up.

While we will miss Matt, Canonical operations remain strong. We will recruit to replace Matt, hoping to find someone who carries on his love of Dilbert cartoons and The Smiths! We all wish Matt well in his new adventure.

Related posts


Hugo Huang
28 May 2026

Canonical announces optimized Ubuntu images for TPU virtual machines by Google Cloud

AI Article

Canonical and Google Cloud announced the availability of certified Ubuntu images for Google’s Cloud TPU Virtual Machines. ...


David Beamonte
28 May 2026

VMware hypervisor deployment using MAAS

MAAS Article

Most modern datacenters are inherently heterogeneous. VMware environments coexist with container platforms, databases, and other bare-metal workloads, often on the same hardware over several years. Servers are bought once, but their role changes as requirements evolve. However, ESXi (the VMware hypervisor) provisioning is often handled se ...


Rob Gibbon
28 May 2026

Migrating from Apache Spark 3 to Spark 4

Data Platform Article

The purpose of this guide is to highlight the key differences between Apache Spark 3 and Spark 4, and provide advice on how to plan a migration. Let’s get started. The biggest changes Let’s talk about the biggest changes between Apache Spark 3.x and Spark 4. Scala 2.12 no more First up, there’s no support ...