Keep in Contact!

Kar
Linuxtag was a very cool event, my second time at Linuxtag this year. KDE really was the project with
the highest profile — our booth looked slick (Oxygen-slick!) and we really had something to show — KDE4 in its current
(alpha) state. I met quite a lot of new and old KDE people, that shows that our community really is healthy
and growing. I gave a talk about KDE4 at Linuxtag, and it was very well received. People were excited that all the
improvements aren’t only eye-candy, but that there’s a profound improvement in pretty much every area of KDE
coming up.
For demoing KDE at this kind of events, one of the things we’ve missed in the past has been example data. For some
time already we have the kde-promo demo user in KDE’s SVN, a set of data that can be used to show application’s
coolness — think of photos for digikam and krita, free music to demo amarok and so on. One of the problematic
parts has been PIM data. You do need an address book with working email addresses, you want some emails in the inbox,
for being able to show kopete, you even need people that are online and can do a short chat. Enter
KeepInKontact.org. This site provides a Kolab server, for exactly this
kind of stuff. It’s a great way for people to contribute a bit of their time. So don’t hesitate and register
yourself!

One of the coolest things I saw in Berlin was Franz Keferbröck’s car — not sure if it’s a color from
the Oxygen palette, but it definitely impressed me (and others). There’s also a crate of beer in the trunk so
it has inner value.

Today, I spent most of the day on catching up on CodeYard things, it’s currently quite silent — summer
vacation is around the corner and students tend to go swimming, rather than coding. Oh well. My colleague
Donna has gone off to Brazil to promote techstuff and Free Software among the local women there.

Most of the afternoon, I spent working on the KDE e.V.’s
Supporting Membership Programme,
contacting companies (we have some announcements in the pipeline) for information and creating two folders
for advertising this programme. There’s also an extension to this, the Corporate Partnership Programme which
I’ll blog more about once I’ve got some things up in the air. Its purpose is to improve corporate access to
the KDE community and make it easier for companies to sell KDE-based solutions.

In the meantime, I’m keeping an eye on KDE development. I’ve got a couple talks about KDE4 coming up (if
they’re accepted, of course), and I’d like to demo the shiny and new stuff.

We are out of real life

Following our great tradition, here’s the remains of today:

  • Long Island Ice Tea didn’t help Ade’s sore throat
  • It’s not possible to order a cocktail called “orgasm” without having people making
    stupid comments
  • QOTD: “You know, the time I had a real life …” (You guessed right, danimo’s quote)
  • KDAB’s office has “women’s version of playboy”, but no wii (gotta read up on that,
    Birte promised me three copies)
  • The password for wireless access in the hotel is “southerncomfort” (no we didn’t choose it
    ourselves, there’s 37 minutes left on that account, happy hacking)

As you might’ve noticed, Linuxtag is going along really well. :-)

Guidance updates

Again, Sevilla's gorgeous castle
In bazaar style (Ha, I actually found a link with the picture I want to share with all of you), here’s
our wishlist for guidance in Kubuntu Gutsy:

  • Powermanager needs to be ported to Qt4, there is little KDE-specific in there, so it’s one of
    the obvious candidates to switch early. In the process, the ugly polling should be changed to
    an event-based approach, something which is not possible with PyQt3 since there’s a clash in
    the mainloops of Qt3 and DBus.
  • Serviceconfig needs some porting to upstart. It’s mostly trivial though. Instead of using
    symlinking in /etc/rc.X/ we should switch to update-rc.d. Upstart also makes some things much
    easier, for example finding out if a service is running or not.

    # status $SERVICE
    # start $SERVICE
    # stop $SERVICE	

    Those commands should be used by serviceconfig. Also, descriptions can be extracted from the services in /etc/event.d/, ultimately, those can be even localised. All in all, upstart seems to be a very nice step forward compared to the rather awkward init system.

  • Displayconfig needs additions. XRandR 1.2 will offer quite a lot of additional runtime-configuration, wrapping that kind of stuff from C to be able to use it in displayconfig (or the displayconfig-gtk backend) is necessary. Although only some drivers will support it in Gutsy, it seems like a good idea to have this kind of stuff. It could possibly easily be done using CTypes.
  • Userconfig should get some more meaningful default groups. We could make the interface a bit simpler by adding a “[ ] May become admin” button and move the group membership to an ‘advanced’ tab.

If you want to get your hands dirty on some python code, those are the things on our agenda. I myself will probably not have time to implement most of those, so drop me a note if you’d like to work on some of them.Guidance can be found in KDE’s Subversion repository, in svn.kde.org/home/kde/trunk/extragear/utils/guidance.

Did anyone see the sun?

Visiting Sevilla's stunning castle
The UDS in Sevilla slowly starts to conclude, tomorrow will be the last day, ending with a
dinner with all the nice people around here. The last day’s activities covered a lot of
joint-displayconfig-effort with the GNOME guys, sketching various aspects of Kubuntu and random KDE
activities, such as networking, writing alpha-release announcements, and compiling the latest and
greated KDE4 code for making screenshots. Side-effect: I can show some interested people how it
currently looks like.
After having enjoyed ourselves yesterday night in a bar in the centre, today I’ll
take it slow, try to find some food and provide my body with a bit of sleep — it seems to be asking
for it.

Somehow being tired and hacking away feels very much like a hackathon. It’s probably the
productive and constructive atmosphere here that makes it special. On the other hand, I’m feeling
very geeky for not having been outside the whole day, but sitting in a basement and typing away,
discussing and eating lots of cookies.
I’ll stay in Sevilla for the weekend and will spend the
second half of next week on an island in the wadden sea — without even a GSM network. At the end of
may, I’m going to Linuxtag in Berlin which will need some preparations as well, and of course aKademy
is getting closer, too.

As you can see, I’ve brought my camera to Sevilla, enjoy
the photos. I still have some
of them pending on my camera, they’ll be hitting the same page tomorrow.

Powermanagement improvements.

There’s quite some discussion about powermanagement here at the Ubuntu
Developers Summit in sunny Sevilla. There are quite some Intel people around
here, providing lots of insight in powermanagement on a hardware and driver
level. Here’s a couple of points that have come up.

  • First, the good news. KDE is in a pretty good shape when it comes to
    sleeping applications. Applications using timers can wake up
    the CPU from sleep states (or even prevent sleeping in the worst case). The CPU
    sleep states (usually named C-states) greatly reduce CPU power draining. The
    worst offenders are currently kopete (responsible for 40% of the wakeups on a
    Fedora test system) and HAL polling the CD-ROM drive every two seconds. Will
    Stephenson told me that kopete in KDE4 is fixed already, and that fixing the
    KDE3 version is on his radar. This makes KDE even more battery friendly.
    Generally, KDE’s technical design makes it rather easy to fix those issues
    system-wide. Kudos to the people working on this!
  • Tickless kernel. The new dynticks and hi-res timers make a
    *huge* difference. Ben Collins mentioned 30 – 40 minutes of extra battery life
    with dynticks and hi-res timers enabled. This stuff is new in 2.6.21, and
    already in the Gutsy kernel. dynticks also make it possible for the CPU to sleep
    much more. Another thing that’s important in that respect is HPET, basically
    doing something similar, but less effective. Every bit helps, however.
  • Intel has a nice tool to analyse userspace misbehaviour. It’s called
    ticktool and tells you which applications keep the CPU from
    sleeping. Having identified those, stracing the process in question can give you
    a better idea of what’s going on. Next step: Fixing it. Intel will release the
    tool on their website intellinuxpower.org (not up yet) shortly, rumours are
    “within a few days”.
  • Synchronising timer events can also help a lot. 5
    timers spread over the second force the cpu to wake up much more often than 5
    timers running all at once. Result: the CPU sleeps longer, you save battery
    life. There seems to be a patch doing this flying around in Oslo, although there
    are probably some things that need consideration before this can be widely
    deployed.
  • Intel will be working on a profile manager that should
    make it easy for userspace to specify power-profiles for various scenarios.
    Switching of devices and putting devices into a lower powerstate when they’re
    not used. Especially USB is a big offender, although recent kernels (2.6.21,
    especially) have mechanics to suspend those battery-drainers when they’re not
    uses). A proposal will pop up on relevant mailinglists within a couple of weeks.
  • Powermanager (the battery applet used in Kubuntu) will
    be ported to Qt4 for Gutsy. There’s very little KDE specific stuff in there, so
    it should be possible without losing lots of functionality. Kpowersave is deemed
    to complicated from a user’s point of view. Still, it would be interesting to
    know if kpowersave is being ported to KDE4, or if one should think about that
    functionality. powermanager is not distro-dependant, it does everything via HAL.
    I don’t think a python application is a viable option to have in KDE4 default
    and running since it adds about 8MB of extra memory in use and takes a bit long
    to start, especially with cold caches.
  • AMD/ATI’s fglrx driver is a total pain in the ass. In
    fact, it is the one component driver that is most complained about. ATI just
    doesn’t seem to care (“Increase your market share by a factor of 5 and we might
    fix the drivers”). I can only encourage people to actively avoid buying hardware
    containing ATI chips. Try to get an intel one. Given the bad quality of the
    fglrx driver and the lack of features, you’re Free Desktop will be able to take
    advantage of much more eye-candy and powermanagement features.
    ATI’s fglrx module is needed on my notebook, there’s a x1300 chip in
    there, which is currently not supported by a free driver. Finding a
    kernel-version / drvier-version combination that actually does suspend with this
    blob loaded took me a week and probably two dozen recompiles of various kernel
    versions. ATI’s engineers seem to actively ignore this issue. One of the latest
    releases contained a new user interface tool which makes it possible to change
    for example anti-aliasing setting for the video card. It doesn’t support things like
    texture_to_pixmap (useful for compositing features), proper suspend support
    (refuses to resume properly in >1 of 10 cases), you often have to wait for it to
    support recent kernels (happened with 2.6.20, took roughly 2 months while a patch was
    in the wild). AMD/ATI engineers seem to completely ignore the user’s
    needs. So by all means: Avoid buying ATI chips if you want your Free Operating
    system to run well.

So there’s a lot of exciting stuff going on in the powermanagement world.
Battery life and power consumption of your device will improve on the software
side.

On Desktop Wars.

Yesterday, after arriving at the Ubuntu Developer Summit in Sevilla,
I had three people in a row claiming one
of the following: “You’re a KDE guy, I’m GNOME guy, so we should be fighting
(rather than drinking beer together)”, “KDE? Sorry, I’m a GNOME user.” or “…
(silence)”.

Apart from that being serious or not, I’ll take it as an invitation to state my
stance about the relationship between KDE and GNOME:

  • Uptake of one is positive for the other. It’s easier to switch from KDE to
    GNOME and the other way round than it is to switch from Windows or Mac to Linux,
    BSD OpenSolaris or one of the other Free platforms supported.
  • If it’s either KDE or GNOME (or Windows or Mac for that matter), in the
    end that sounds like we’re heading from one monopoly into another. That is
    something we’re actively fighting at the moment. Priorities should be: “Free
    Software” and provide choice to the user. KDE and GNOME need
    each other.
  • How much sense does it make to put energy in competing with 2 – 3% of
    the market when 90%+ is still running a non-free desktop? (Hint: Zero) Instead
    the energy should be put into increasing the market share of the Free Desktop
    and then having the user choose. Healthy competition might exist, it might even
    make sense, but I’m getting tired of this KDE vs. GNOME stuff. It’s showing a
    deep lack of understanding and vision.
  • Emerging technologies (in this case desktop operating system, and yes,
    this clearly is not a mature market yet) always start in a monopoly-like situation. A
    stable market’s characteristic is that there are a couple of different offerings
    and that the user has choice. Maturing the market means:

    • A good portion of the market for the Free Desktop (wild
      estimation: 30%+ for the Free Desktop as soon as the market
      is matured.
    • Various offerings that operate together well.
    • Raising awareness of choice for the user. (How many people know
      that there’s something beyond Windows to run on a computer?)

So it might be easy for KDE and GNOME to pick on each other, but it doesn’t make
sense at all. Maturing the platform and the market is what we should aim for,
that strategy will give us a broader userbase than we expect.

Maybe 10×10 isn’t realistic because people failed to see that. Maybe
interoperability would already be better if people had understood that earlier.

Personally, being at the Ubuntu Summit in Sevilla at the moment gives me the
unique opportunity to work on that. Some weeks ago, Michael Vogt and
Sebastian Henlein
sent me a note that they’re working on a GTK-based UI for displayconfig. We’ll sit
together this week and think about how we can make configuration of X on the
Free Desktop easier and more reliable for the user.

That is Doing The Right Thing.

You know you’re in good company …

Papadum

… when the people around you recognise Plan9
instead of mundane things like Easter,
or (possibly) worse: Playboy. In fact, the picture shows a piece of
Papadum on a hot Nepalese curry.

In other news, it’s totally summer in the Netherlands, had my first bbq yesterday (not on a
roof,
admittedly) a lovely biological Ribeye steak.
On May 31st, I’ll be giving a presentation about KDE4 in the maintrack at
Linuxtag, I
started with preparations for it today. The rest of the day was mainly the business you’d expect
after
returning from a couple of days being away: emailing people, reading other people’s email (the
longer ones
you don’t get around to).

Tomorrow we’ll announce the students that will make it into the finals of the
CodeYard award.

While reading various announcements on
The Dot, I’m extremely thrilled by the programme for this
year’s
aKademy. I do hope the
Call For Locations for aKademy 2008 will not be
completely snowed under. So think about it!

Travelling at the speed of snort

I’m currently on a train that left an hour ago in Brussels, and about to descend into a
large black
hole
which will I’ll travel through for roughly 20 minutes, at 160km/h and at 40m below sea
level.
Exciting, if you’re aware of that. Other than that, having a cold and being in environment with
changing
airpressure sucks since the cold makes it harder to decompress your ears.
It seems travel season is in full swing again, mostly for the sake of Free Software (and
admittedly a bit
of sightseeing and beer in between). I’ve been blogging very little lately since I just didn’t
feel like
(which I should because communication is important, oh well).

Late February, I’ve been to FOSDEM in Brussels (beer!), it’s been a great event, met lots of
nice people
among them Trolltech’s community manager Knut Yrvin, some people from the SQO-OSS project, more
KDE
people. Knut, friendly as he is invited me to Oslo to sit down with Trolltech’s marketing people
in order
to have a look at how KDE and Trolltech can work together more closely on this topic. We synced
the
meeting with Aaron touching down for 36 hours in Oslo. Turns out that within Trolltech, most
developers do
know KDE very well, whereas the marketing it’s actually not that ubiquitous. :-) The meeting
was
very productive in terms of short-term items that we can work on (there’s new accessibility
features in
Qt4 that might be very important points when organisations think about deploying KDE, for
example). We
could also think about creating marketing material together — for Trolltech, it’s showcasing
Qt, for KDE
it’s showing our balls.

So the train got into this big dark hole and the journey to London continues. Later today, we’ll
join a
meeting of the British Computer Society’s Open Source Specialist Group, featuring a talk about
an Open
Source approach to Healthcare automation, not exactly my domain of expertise, most probably
interesting,
definitely followed op by a beer or two.

Tomorrow morning, the third SQO-OSS project meeting will kick off. Those meeting are essential
for the
success of a European research project such as SQO-OSS, it gives us the opportunity to talk
about the
stuff we’re doing, mind you, not everyone is evenly communicative when it comes to email and
commitlogs,
so I’m looking forward to some of the stuff others have been up to. Socialising with your
colleagues that
are usually located across half of the continent is a good thing, too. Not at least, sitting on
trains for
six hours mandates to talk with your direct colleague (ade, taking a nap right next to me
typing). I’ve
taken a week off from work-work last week, the yield of that is some detailed ideas of what I’ll
be
working on within KDE the next time. It involves merchandising (made some mockups for t-shirts
for
aKademy, for example) and bringing KDE’s business
directory
back
to life by coupling it with KDE e.V.’s Supporting
Membership programme
. The latter needs more
thinking, both issues did not yet enter implementation stage.

In early May, I’ll be at the Ubuntu Developer Summit in Sevilla, later in May, I’ll probably
travel to
Berlin for Linuxtag2007. Oh, and Kim asked for a bit of vacation, too. ;-)

Join the KDE Event Coordination Task Force now!

KDE is visiting a lot of events on a yearly basis. In most cases, the booth is staffed by
volunteers. A successful event attendance depends on a number of factors, if those aren’t
considered, it might end in frustrated, or even burnt out contributors. But getting it right
is not just about “went good / bad”, there are various shades of grey. Having a look at past
events, the most important factors seem to be in two groups, general considerations and
planning
and per-event planning. Let’s see what those two are about:

General

  • What events are there, when and where?
  • Are there people who would like to represent KDE at this event?
  • Is there material for events, such as demo hardware, demo data, flyers?
  • Is there merchandising material and goodies available? Where can that be
    gotten from? What material is there? Can we have special stuff made?

Per Event

  • How do I get the boothmaterial?
  • What do I need to know to run a booth?
  • How can I get merchandising material? What do I need to know to handle it?
  • What event-specific planning is required?

Parts of those problems have solutions already. For example, we know who can get us
merchandising
material, we have some booth material in the form of the boothbox. The
SpreadKDE team is
working on a module for the SpeadKDE platform to make planning easier. What we’re really
lacking is
cool stuff, such as well-designed merchandising materials. Doing an event should be more or
less
a routine task, so we can concentrate on the fun stuff and on what exactly we want to show.
So
let’s try to get the organisation in place so that event planning and attending is an easy
and
fun task.

So to tackle this, we’re putting together the KDE Event Coordination Task Force (KECTF).
This group of people will
think about how to solve all those issues (Most of them are fun to deal with for the right
people!).
If you want to be part of it, if you’ve input on those issues, or just would like to design
a flyer,
a t-shirt, …, subscribe to the
kde-events mailinglist now
and
start your carreer as part of the Event Coordination Task Force today!

FOSDEM 2007.

I’ve just submitted a last-minute talk for the
KDE Devroom at FOSDEM in
Brussels.
FOSDEM, the biggest European Free Software Community Event is, I think a great
opportunity to give the KDE e.V. some more exposure and at the same time KDE – The
Organisation
some more transparence. So my talk will give deals about the what and the why of
KDE e.V., the foundation that deals with legal and
administrative details behind KDE.

I’ve picked the slot on Sunday afternoon from 16:30 – 17:00, so I am still able to
attend the talks I’m
personally very interested in, Andrew Morton’s and Dave Neary’s talks do definitely
attract my interest. Apart from that, I’m really looking forward to seeing a lot of people
again this weekend, and then Brussels is quite a lovely city…

If you’re in Brussels this weekend, definitely do FOSDEM, and drop by the
KDE devroom for some chit-chat or hacking on KDE4!

Now playing: Heather Nova, Oyster