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

Massimiliano Gori
27 March 2026

Modern Linux identity management: from local auth to the cloud with Ubuntu

Cloud and server Article

The modern enterprise operates in a hybrid world where on-premises infrastructure coexists with cloud services, and security threats evolve daily. IT administrators are tasked with a difficult balancing act: maintaining traditional local workflows while managing the inevitable shift toward cloud-native architectures. Identity has emerged ...

Abdelrahman Hosny
24 March 2026

Canonical welcomes NVIDIA’s donation of the GPU DRA driver to CNCF

Partners Article

At KubeCon Europe in Amsterdam, NVIDIA announced that it will donate the GPU Dynamic Resource Allocation (DRA) Driver to the Cloud Native Computing Foundation (CNCF). This marks an important milestone for the Kubernetes ecosystem and for the future of AI infrastructure. For years, GPUs have been central to modern machine learning and high ...

ijlal-loutfi
23 March 2026

Hot code burns: the supply chain case for letting your containers cool before you ship

Ubuntu Article

Zero CVEs doesn’t mean secure. It means unexamined. New code has zero CVEs because no one has studied it yet, and if you’re rebuilding nightly from upstream, you’re signing first and asking questions later. In software supply chain security, the freshest code isn’t always the safest. Sometimes the most secure component in your pipeline is ...