ARTICLE

Red Hat, Canonical and GNOME Contributions

by | Fri 30 Jul 2010

Earlier this week at GUADEC, the always affable Dave Neary presented his GNOME Census work. Unfortunately, I was not there to see it, but I read his [excellent post on the topic](https://blogs.gnome.org/bolsh/2010/07/28/gnome-census/).

One of the reactions from the survey was that Red Hat are responsible for 16% of the contributions to GNOME whereas Canonical are responsible for a measly 1%.

Of course, this has generated some flame, such as a [particularly angry post from Greg DeKoenigsberg](https://gregdekspeaks.wordpress.com/2010/07/29/red-hat-16-canonical-1/) and the [rather pithy response from Jeffrey Stedfast](https://jeffreystedfast.blogspot.com/2010/07/re-red-hat-16-canonical-1.html). Greg is clearly pissed, and Jeffrey is clearly pissed at Greg being pissed, and I suspect Greg is going to get even more pissed at Jeffrey being pissed. The worse thing is that they are both going to be pissed at me for this blog post.

First I want to put these figures in perspective and then I want to talk about how we read the figures we do have.

I think the GNOME Census report is excellent, and it provides some excellent visibility into contributions in GNOME, but it only takes into account upstream contributions to GNOME itself. What the report doesn’t take into account are upstream contributions that are built on the GNOME platform but (a) not part of official GNOME modules, and (b) hosted and developed elsewhere, such as [Launchpad](https://www.launchpad.net/). As such, while the report is accurate for showing code and contributions accepted into GNOME, there are also many projects built on GNOME technology that are not taken into account due to non-inclusion in GNOME modules or being developed outside of GNOME infrastructure.

As a general rule, Canonical staff develop inside Launchpad. The reason is simple; Launchpad and Bazaar provide a powerful development environment that was also built by Canonical and we therefore have lots of internal skills and best practice based on these tools. Launchpad is also a fundamental component in Ubuntu development and all the software we develop ultimately ships in Ubuntu, so using the same development forge makes sense. Finally, the site is a Free Software and Open Source project, so there really no philosophical reason to move, testified by the 18,000+ Free Software projects happily using Launchpad already.

Canonical is actively developing upstream desktop software, but doing it in Launchpad. Some examples include:

* [notify-osd](https://www.google.com/url?sa=t&source=web&cd=1&ved=0CBYQFjAA&url=https%3A%2F%2Flaunchpad.net%2Fnotify-osd&ei=KD1STN2yKNObnwej1bGhAw&usg=AFQjCNHcEtBlQ7ApgfchYlWutAt2HKss0w&sig2=B1X9XwgIr2UliaYglpl2bg)
* [Messaging Menu](https://edge.launchpad.net/indicator-messages)
* [Application Indicators](https://edge.launchpad.net/indicator-application)
* [Indicator Applet](https://edge.launchpad.net/indicator-applet)
* [Indicator Date Time Applet](https://edge.launchpad.net/indicator-datetime)
* [Sound Indicator](https://edge.launchpad.net/indicator-sound)
* [Me Menu](https://edge.launchpad.net/indicator-me)
* [Indicator Global Menu](https://edge.launchpad.net/indicator-appmenu)
* [Unity](https://edge.launchpad.net/unity)

This is by no means the full list, and is other work such as Simple Scan, the Hardware Drivers tool, Computer Janitor, and more. Many of these contributions (such as Application Indicators and Simple Scan) could bring real value to GNOME, but they have not been accepted. I know that the Canonical engineers who work on them would be delighted if they were included in GNOME.

The above list also doesn’t include significant upstream investment in other areas such as Upstart, Bazaar, Launchpad, and a full team building Ubuntu. I don’t want to turn this into a “*who contributed more*” competition, but I think for some to suggest Canonical is a bad citizen who is not contributing upstream code is unreasonable. To suggest that Canonical has limited code inside approved GNOME modules is fair.

So that was the first thing I wanted to clarify; Canonical *does* invest heavily in upstream work, but GNOME is *not the only home for upstream contributions*.

If there is one thing that the GNOME Census has really outlined is that we should all be proud of Red Hat and their contributions to GNOME. You only have to take a look at all the red items on [this image](https://www.neary-consulting.com/wp-content/uploads/2010/07/diagramme_inkscape_updated.png) to get a feeling for the wonderful work that Red Hat is doing inside GNOME. Novell too. Look the green items in there; Novell has done a wonderful job maintaining many modules inside GNOME. In fact, there are many companies investing inside GNOME modules and inside GNOME infrastructure. I don’t believe it would be fair to undermine these contributions in any way; they are testament to the ethos of those companies and their commitment to GNOME. All of the people working at those companies are doing good work within the spirit of Free Software.

Likewise, I don’t think it is fair to undermine Canonical’s contributions just because many of them exist outside of GNOME. Our engineers are also doing good work within the spirit of Free Software. I have never claimed for a second that Canonical are equal to Red Hat and Novell in terms of our accepted contributions in GNOME; it is clear that there are far few contributions from Canonical staff inside accepted GNOME modules, but this does not for a second mean that Canonical is not (a) producing upstream contributions and (b) heavily invested in the GNOME platform. Ubuntu, our primary product is a GNOME desktop, and the vast majority of our engineers are GNOME users and developers and they work every day on a GNOME based product.

So in a nutshell, this is my take: both Red Hat and Canonical invest heavily in Open Source development, but they do it in different ways and different places. The GNOME Census clearly outlines that within GNOME modules, Red Hat are doing far more, but that doesn’t mean that Canonical are sitting on their thumbs and doing nothing, far from it.

An invitation-only accelerator that develops industry-leading community engagement and growth via personalized training, coaching, and accountability...all tailored to your company's needs.

Want to read some more?

Happy Holidays

Happy Holidays

Just a quick note to wish all of you a happy, restful, and peaceful holidays, however and whoever you spend it with. Take care, folks, and I look forward to seeing you in 2015!

The Impact of One Person

The Impact of One Person

I am 35 years old and *people* never cease to surprise me. My trip home from Los Angeles today was a good example of this. It was a tortuous affair that should have been a quick hop from LA to Oakland, popping on BArt, and then getting home for a cup of tea and an...

Feedback Requested: Great Examples of Community

Feedback Requested: Great Examples of Community

Folks, I need to ask for some help. Like many, I have some go-to examples of great communities. This includes Wikipedia, OpenStreetmap, Ubuntu, Debian, Linux, and others. Many of these are software related, many of them are Open Source. I would like to ask your...

Ubuntu Governance Reboot: Five Proposals

Ubuntu Governance Reboot: Five Proposals

Sorry, this is *long*, but hang in there. A little while back I wrote [a blog post](https://archivedblog.jonobacon.com/2014/11/14/ubuntu-governance-reboot/) that seemed to inspire some people and ruffle the feathers of some others. It was designed as a...

Ubuntu Governance: Reboot?

Ubuntu Governance: Reboot?

For many years Ubuntu has had a comprehensive governance structure. At the top of the tree are the Community Council (community policy) and the Technical Board (technical policy). Below those boards are sub-councils such as the IRC, Forum, and LoCo councils, and...

Dealing With Disrespect: The Video

Dealing With Disrespect: The Video

A while back I wrote and released a free e-book called [Dealing With Disrespect](https://www.dealingwithdisrespect.com/). It is a book that provides a short, simple to read, free guide for handling personalized, mean-spirited, disrespectful, and in some cases,...