Congratulations to those elected to the 2011-2013 CC, and thanks both to those who were willing to serve and all of those who participated in the poll. We’ll use the results of the poll should we need to fill in for any members who cannot for any reason complete their two year term.
This is an important CC, as I think there is an opportunity to develop a response to the challenge thrown down recently, which is to give *purpose* to community leadership in the project.
Every role has purpose in its own context; those who set out to achieve a goal, like producing complete server documentation, or moderating a difficult mailing list (you know who you are ;-)) or translating a work into a new language, have no trouble identifying their purpose. And there are essentially no limits on the goals one can set for oneself in the project; we have community members engaged in pretty much everything we do.
Nevertheless, there has been a shift in the nature of the project, and that shift is not yet fully reflected in community leadership. Specifically, our mission has shifted from being defined by integration-and-delivery, to one that includes design and development as well as integration and delivery.
When we started, we said we would deliver the world’s free software, on a tightly integrated and free basis, on a cadence. We made some choices about defaults, but broadly left it up to others to define what ‘the software’ would do.
After doing that for several years, it became clear to me that limiting ourselves to that pattern meant we were leaving it to others to decide if we could really deliver an alternative to proprietary platforms for modern computing. We were doing a lot of work, which was not recognised by some of the projects we were supporting heavily, and still treading water when it came to the real fight for hearts and minds, against Windows, against MacOS, and against Android. So, even though it was clearly going to be a difficult choice, we set out to grow the contribution Canonical makes directly to the body of open source. We said we’d be design-led, and we’d focus on the areas that matter most to pioneer adopters; the free software desktop, mobile computing, and the cloud.
The result is work like Unity, uTouch, and Juju. I’m proud of all three, I think they are worthy bannermen in our effort to bring free software to a much wider audience, and I think without them we would have no chance of fixing bug #1.
At the same time, we’ve now created a whole new dimension to Ubuntu: the design and definition of products, essentially. And that begs the question: what’s the community role in defining and designing those products.
We haven’t taken a step backwards. It’s not as though there are responsibilities that have been taken away from anybody. It’s just that we’ve taken on some bolder, bigger challenges, and community folk rightly say “how can we be part of that?” And that’s an interesting question, which the new CC will be in a good position to discuss with me and Jono.
It’s not healthy to offer the ability to vote for money. Nobody should feel they have a right to decide how someone else spends their time or money. But I do think the relationship between Canonical and community is as important now as ever, and there is an opportunity to break new ground. Ubuntu represents the best chance GNU/Linux has to bring free software to the foreground of everyday computing. I have no doubt of that. After us, it’s Android, and that’s not quite the same. So our interests are all very aligned; there is a huge opportunity, and a once-in-a-lifetime chance to use what we know and love in a way that changes millions of lives for the better.