Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

An error occurred while submitting your form. Please try again or file a bug report. Close

  1. Blog
  2. Article

Canonical
on 8 November 2013

Trademarks, community and criticism


Recently some concerns were expressed by fixubuntu.com, a website focusing on Ubuntu privacy, about a routine trademark enforcement email that Canonical sent. We want to provide some context around this issue.

In Ubuntu we cherish an open and diverse discourse, and we welcome differing and challenging views and perspectives; it is the cornerstone of our community, as exemplified by our open Ubuntu Developer Summit, mailing lists, IRC channels and more. Our Code of Conduct and Trademark policy simply provide guardrails for those conversations to flourish.

Canonical owns the family of Ubuntu trademarks and we have a responsibility to protect those trademarks. In trademark law a mark owner is expected to protect the authenticity of a trademark otherwise they risk losing the mark.

Our trademark policy is unusually permissive. We have a global community of Ubuntu contributors, LoCo teams, translators, developers, advocates, and others who want to use these marks to within the spirit and governance of the project. Therefore, our policy has been crafted in such a way that we can protect the marks and what they stand for, but also ensure our community has the freedom to use them.

In the case of fixubuntu.com, we were concerned that the use of the trademark implied a connection with and endorsement from the Ubuntu project which didn’t exist. The site owner has already agreed to remove the Ubuntu logo and clarified that there is no connection; from our perspective the situation has been resolved, and we have no issue with the site or the criticism it includes.  In fact, far from an trying to silence critics, our trademark policy actually calls out parody and criticism and other uses as being allowed when the marks are used appropriately.  (Please make the parodies funny – we need a good laugh as much as anyone!)

We aim to communicate our policies and actions clearly and openly, and I welcome feedback on how to do that better.

UPDATE:  I should have mentioned that we do listen closely to constructive criticism and user’s requests about the Online Search function. And in response we already added a simple way for you to limit your search to local results only if you wish.  If you’re running the latest version of Ubuntu, check Settings -> Security & Privacy -> Search.

Related posts


Canonical
22 October 2025

Alibaba Damo Academy and Canonical partner to deliver Ubuntu on XuanTie and drive RISC-V innovation

Ubuntu Article

Alibaba Damo Academy and Canonical today announce a new collaboration to bring the Ubuntu operating system to the latest XuanTie C930 processor. This collaboration will give users access to a robust, reliable and production-ready platform for modern workloads running on the XuanTie processor family, helping to advance RISC-V adoption.  En ...


Gabriel Aguiar Noury
22 October 2025

Discover your fully open source robotics observability at ROSCon 2025

Robotics Article

Another year, another ROSCon! This year we’re heading to Singapore, and Canonical is once again thrilled to sponsor this important community event. Just like last year in Odense, Denmark, we’re looking forward to the talks and workshops, which always inspire us and teach us new things about robotics. We’re excited to reconnect with our So ...


ijlal-loutfi
21 October 2025

What’s new in security for Ubuntu 25.10? 

Ubuntu Article

Ubuntu 25.10 Questing Quokka has landed, marking the final interim release before Ubuntu 26.04 LTS,  and it’s a bold one. Interim releases have always been the proving grounds for features that define the next LTS, and this cycle is no exception. From memory-safe reimplementations of foundational tools to hardware-backed encryption, post- ...