Yesterday I woke up to the news that Canonical are no longer going to fund Riddell to work on Kubuntu. I've trying to figure out what that means for KDE and for community Linux generally.

Disclaimer: I work in the same role as Jonathan at SUSE, a competing Linux company that sponsors the openSUSE project. This is my personal opinion, not that of the openSUSE Board or SUSE Linux GmbH.

I'm sad for Jonathan personally. He has put a lot of his lifeblood into Kubuntu over the years, at no little cost to himself, and to be pulled off one's favourite project hurts. The same thing could happen to me if the powers that be decide, so I can easily empathise with him.

In the bigger picture, I have to say that this doesn't surprise me at all. For Canonical, Kubuntu fulfilled its purpose a few years ago already. Kubuntu, and the other official Ubuntu derivatives, have always been a spoiler move to tie up community contributors who believed in the early community-centric image of Ubuntu, but who didn't agree with the main Ubuntu's direction. Otherwise, there was the risk that Ubuntu design decisions would polarize the Linux community and send people towards Ubuntu's competitors. With the derivatives, they are safely occupied under the big tent of the Ubuntu brand.

If we look back at the Ubuntu game plan as history neatly lays it out for us, we have

1) Establish the Ubuntu brand amongst early adopters (check, by about 2005)
2) Expand it to the wider Linux user base (check, by about 2007)
3) Make Ubuntu the default Linux for non-technical users (2009)
4) Tie up a paying market. Initial targets have been enterprise desktop Linux (maybe next year ;)) or consumers in the massmarket netbook segment (but that was squashed by tablets and Microsoft rounding up the manufacturer back to the XP prison), and now they are aiming at embedding into consumer electronics (TVs) and will probably snare a tablet OEM as a cloud OS (hell, if KDE can do it...) or a bookseller or someone who wants a platform to digitally sell something else off of.
5) Profit
6) Buy more spaceflight (Probably. For some, 5) is enough)

Somewhere after 1), the massive demand for KDE on Ubuntu in KDE's main territories (Germany, via the ubuntu.de forums, which IIRC threatened an unofficial fork) caused Canonical to realise that it was better to control a large dissenting minority with some token gestures than to have them really doing their own thing. So Jonathan, at that point a KDE packager at Debian, was hired, and Mark Shuttleworth did his salesman job at a couple of KDE events making some insubstantial promises (If I had a dollar for every KDE eV board member at the time who told me "But Mark has promised to install and use Kubuntu on his workstation" multiplied by every Ubuntu developer overheard chuckling that "But they don't know that Mark *never* uses his workstation, he's always on a notebook"...), a few community people got flights to events, and Kubuntu was born, and legitimised by the then-leaders of the KDE community.

Once 2) was consolidated, Kubuntu was redundant to Canonical, but on the average professional Linux hacker's salary, Jonathan was an affordable luxury. Now, I suspect that with the trend at Canonical to develop more and more in-house to chase 4) rather than just distribute what the FLOSS community provides, putting paid man-hours on a mature product is no longer a good way to spend engineering budget.

By cheaply tying up competitors' resources, Kubuntu has hindered KDE's overall growth via other distributions and balkanized the KDE community. It can be argued that Kubuntu has brought users and contributors to KDE as part of the rapid initial growth of Ubuntu, and Kubuntu has been a success in focussing their developers on improving KDE, but this came at the price of cementing KDE in the role of a second class environment in the eyes of everyone who came to Linux via Ubuntu. I suspect that the GNOME community, which previously surfed the wave of Ubuntu's growth, will feel the pinch of necessity as Canonical moves towards its endgame, and having already been displaced as the default desktop for an inhouse development, will move further towards just being an anonymous organ donor to Unity and subsequent productisable UIs.

Why am I writing this? I don't want to be so crass as to just say 'come to my project instead'. I'd like to take this opportunity to suggest that you should have no illusions about what your community Linux distribution means to the businesses that sponsor it.

For openSUSE, it's some engineering contribution to and testing of SUSE enterprise products' codebase, and supporting the enterprise brand via a halo effect from the community brand. In setting up the openSUSE project, SUSE has been militant in giving the community complete control of the project and the distribution that comes out of it. Call it an insurance policy or a lifeboat, but by opening and freeing all the tools that create openSUSE (as well as the source code), we assure that the results of 20 years of work are indefinitely available. SUSE is secure enough in its business and believes strongly enough in free software to do this with the rootstock of its enterprise products, because the modular, federated Open Build Service allows SUSE to derive enterprise products from openSUSE without having to steer it.

Flat things are good. I'm at Tokamak 5 in Nijmegen, the KDE sprint where we plough a deep furrow into the future of the Free Desktop and sow KDE seeds that will grow into exciting, novel interfaces and make the stuff we already have even faster and more reliable.

So what about the flat things I mentioned? We've just guzzled our way through a stack of pancakes of geological proportions, produced for us by pancake-flipper and KDE allrounder par excellence Adriaan de Groot. Other good flat things are tablets (I won't call them 'tablet computers' in case I sound old fashioned), which are in evidence here in a variety of makes and models. We're working on several things that will make KDE on tablets as easy and fun to consume as Adriaan's pancakes.

I'm here for a few days to make KConfigXT, KDE's proven automatic configuration persistence layer, work with user interfaces programmed in Qt Quick, and to support the Plasma Active work going on in the openSUSE Build Service with my geeko skills.

Did that get your attention? Good, it was supposed to. Now get back to making KDE 4 rock in whatever way you are able and resist the temptation to put 'KDE 5' in your blog title to get some clicks. KDE 4 is not going anywhere in the foreseeable future because GNOME just increased their major release number.

I'm feeling very lucky today. Why? Because in a few hours I'll be getting on a plane to Bengaluru, India and attending conf.kde.in. Pradeepto has been asking me for years to look outside the cosy confines of the US-Europe Axis of KDE, and thanks to my role in the openSUSE Boosters team, this has finally become possible.

I'll be giving a talk on contributing to KDE in the openSUSE project and a long talk/practical workshop on using the openSUSE Build Service as used by openSUSE, Novell, Dell, Intel, Nokia, Broadcom and Cray, to spread free software: your own, update existing software on openSUSE, or package for it and for many other distros at one go. But mainly I'm looking forward to meeting the people who make up a whole side of KDE. So if you haven't made up your mind what you're doing next week, how about coming to the RV College of Engineering in Bengaluru?

Like many others,

PS: I'm bringing a load of openSUSE loot to give away, so just look for the guy staggering under the huge carton!

I couldn't resist snapping as many KDE folk at the openSUSE conference as I could, and editing them together into: a short video.

If anyone can tell me how to embed in kdedevelopers.org or enable the download of the OGG version from blip.tv, let me know!

Next week is openSUSE Conference week! I'm using both my openSUSE and KDE blogs to remind everyone that we're having a pre-conference meetup at 6pm for the KDE team before the real conference begins at Barfüßer in the Nuernberg old town. Remember a morning of keynotes is only fun if you have a thumping hangover from microbrewed beer (and if you're a keynote speaker, from local schapps too)! If you are attending the conference or if you are just a friend of KDE in the area, please join in.

If you add your name to the wiki I'll have an idea how big a table we need, I've provisionally got space for 20.

Will

Yes, this is basically a job ad. The openSUSE Boosters team is expanding again (when will it ever stop?) and we're looking for another member. If you want to work full time on Linux, enjoy the idea of building a community around the distribution and think you have the right skills why not apply and have the chance to work with me, Lubos Lunak, Stephan Kulow, Klaas Freitag and many other people you know from the KDE and wider Free Software scene?

Today openSUSE 11.3 is released, concluding 8 months of intense and enjoyable work. This release has been especially enjoyable for me, as it was the first openSUSE release where the community KDE team really took the driving seat and made decisions about what to include, updated packages and intensively tested. Instead of just being a slave to a feature list this release, I was more occupied in enabling, advising and reviewing others' contributions. I'd like to say "Excellent work!" to the whole openSUSE team here in Nuremberg, Prague, the rest of Novell and to every openSUSE contributor who has tested milestones, reported bugs, learned how to use osc and build.opensuse.org and made a difference.

By our recent standards, openSUSE 11.3 is a conservative release; it doesn't have bleeding edge features shoehorned in at the last minute by product management or novelty for its own sake. Instead it's what a Linux distribution should be: a careful composition of the all the newest stable elements from upstream. The KDE SC 4.4.4 that we ship is now stable and feature complete, by most accounts, and contains many tweaks and upstream patches to be an elegant, good-looking but also stable and usable desktop. I hope that it will provide its users a lot of pleasure and utility, inspire many of them to jump on board at the openSUSE project, and others to explore all the possibilities and smoking hot new stuff available in the openSUSE Build Service.

Oh and in case you wondered why I wasn't at Akademy in Tampere, here's why:

After 9 months of enjoyable and intense work, our daughter Anna was released a couple of weeks ago. At the moment she's quite unimpressed by computers, desktops and operating systems, but I hope that Free Software will be of benefit to her life as it already is to millions around the world.

Did you know every app built with KDE 4 can save files as easily to a FTP server or a remote computer using SSH as easily as it accesses your local hard disk? You should! This is a feature that I take for granted since it was introduced in the days of KDE 2.0, but it's easy to forget that the majority of KDE users only started using it since then.

A few of our community people got together and wrote this thorough overview of network transparent file management in KDE at the weekend. Cookies to them for writing it and even if you think you are an old KDE hand, give it a read - I didn't know about the handy protocol selector in Dolphin, and that let me discover the settings:/ protocol - now I can access my Settings directly in Dolphin.

KDE Developers may have noticed that the developer documentation server at api.kde.org is down. This is due to a hardware failure which will be recovered next week. That need not put the brakes on your work though, since if you have the source code on your system you can build the API docu locally yourself, as HTML, as man pages, or as Qt Assistant help files to view in Qt Assistant or Qt Creator.

Read all about it on techbase: http://techbase.kde.org/Development/Tools/apidox