long walks and parties.

Last week, in Nijmegen there were the
Vierdaagse
,
according to Wikipedia the largest marching event in the world. Roughly 40.000 people walked
for four days, every day between 30 – 50 km, depending on age and some other things. Only
~3000 did not make it. Those days go together with the “Zomerfeesten”, a week-long festival
in the whole city centre, attracting 1 Million people throughout the week, with a peak on
Friday, the finishing day of the Vierdaagse.

Friday was also the day when Kenny (our great aKademy overlord from Glasgow) came to Nijmegen,
as a part of his vacation. I’m not sure he was prepared for a city full of people partying,
30 – 40 stages in the whole city and the celebrations starting around noon. He’s chosen the
busiest day of the year to visit this city. =)

After aKademy, I was quite exhausted for roughly a week, and I had to catch up on other work
which has been left undone for the week before. I’m quite up to speed with all activities
again now. Today was mostly dealing with administrative stuff for the e.V., such as preparing
travels for the next months and hotel booking for the Board meeting we’re holding at the
beginning of August in Darmstadt.

My TODO list for the next days includes some aKademy aftermath (merchandising, logistics mainly)
and sorting out businesscards status. I’ll also do some more hacking on the
Battery plasmoid, but
that is really freetime / evening activities.

Writing Free Software is even better than dealing crack.

On the way back from Glasgow to the Netherlands, a 13 hour trip (after a technical problem
on the high-speed track between the Lille and Brussels even longer), I read
quite a bit. Adriaan got a copy of “Freakonomics”, a book by Steven D. Levitt and Stepen J.
Dubner, which I am now reading (he finished it while I was snoring 40m under the sea in the
Chunnel).

One of the chapters deals with the question “Why do drug dealers still live with their
moms?”

The answer to this question is that most drug-dealers can hardly make a living from their
“earnings” and that their incentive to choose dealing crack as their profession is the
perspective of becoming a top-notch drug dealer (small chance) and then earning a lot of
money. Of course, the chance to die in the process is much higher than actually succeeding.
(The chance to die while dealing crack is even considerably higher than the chance to die
when you’re on death row in a texan prison.)
The reason for choosing crack-dealer instead of “some other well-paid profession” is that
succeeding in crack-dealing is quite visible in their environment, whereas famous writers
(for example) have close to no visibility — hence more choose to get into the drugs
business.

Now you wonder what this has to do with Free Software? I think there’s an analogy that also
applies to
what we’re doing. Having students see that you can become successful (in whatever way)
by writing Free Software, so increasing the visibility of “Free Software developer” being
a profession, rather than a hobby and a good way to make a living should — following this
analogy — motivate folks to actually become Free Software developers.

Combine this with the situation that there’s actually a lack of Free Software
developers (at least in the KDE ecosphere, I know quite some companies who are looking for
competent Free Software developers they could hire).
Working on KDE gives you a track record and shows that you’re actually able to write good
code, work in a team, have technical understanding and a sense for accomplishing something.
I even dare saying “If you’re working
on KDE and are able to contribute in a meaningful way, you’ll almost certainly get a good
job in this industry.”
For some of us it might be obvious, lots of people have interesting and well-paid jobs in
the Free Software industry. The key is communication. Communicating that actively solves
various problems
at once: new apprentices, a healthier job market and of course more people participating
in Free Software projects. This is by the way also what I’m actively communicating to our
CodeYard students.

wrapping up.

Things at aKademy are starting to wrap up. The last few days have been very intensive,
lots of talking, meeting new and old people, solving problems such as “Where’s a free bed
because the hostel has screwed up *again*?”, “Where the hell did DHL deliver the
merchandise?” (Certainly not to the address that was written on the packages, but to a
random motorcycle shop where the box sat for a week. DHL wasn’t reliable for us at all.)

Great progress has been made on current state the KDE4 desktop, to a state where most
applications work quite well, Plasma is taking shape, lots of people are writing
DataEngines and Plasmoids … it’s shaping up really nicely now and we’re starting to
reap from the effort that has gone into it over the past years. We’re still in the phase
where pieces fall into place.

One of the most important things to me at aKademy is the community. It’s simply great to
meet such a lot of nice people. While I’m really tired after a whole week of conferencing,
hacking, BoF’ing and ‘socialising’, I’m extremely excited by the current state of the
community. There’s both, old and new people who are working on all kinds of things, the
community is really healthy as it is, and everything looks very promising. I’m right now
compiling kdegames for tomorrow’s 13-hour-train trip, and I’ve downloaded some of the
videos of talks from last weekend that I’ve missed. Back home, I’ll catch up on sleep and
start working on the aftermath of aKademy.

Yesterday, Danny Kukawka of kpowersave fame, Kevin Ottens, the Master of Solid and I sat
together to discuss how powermanagement in KDE 4 should look like. We came up with a nice
architecture, having a policy agent (which is a new version of kpowersave), a plasmoid to
show current state of things and of course Solid providing us with most of the API that’s
needed for this. Powermanagement in KDE has not exactly been unified in KDE3, but as it’s
now, things look very promising for KDE4.

I’ll stop rambling now and prepare for the night activities, which is “taking the
organising crew out in order to thank them for their outstanding contribution to KDE. The
conference went very smooth. This doesn’t happen by itself but requires a huge amount of
work, discipline and dedication.

A huuuuuuge thank you to Kenny Duffus and his team!

releasing.

Father…ooh…oh…oh…
I see the world, feel the chill
Which way to go, windowsill
I see the worlds on a rocking horse of time
I see the verse in the rain
Ohh…ohh…ohh…ohh…

Pearl Jam – “Release”

Mark Shuttleworth talked about what he thinks is a sensible
release rhythm. While you probably all know his proposal, here’s what I’m thinking about
releasing every six months (or in regular intervals anyway) and synchronising our releases with
the release of other Free Software communities.

Right now, we can say very little about KDE4. We will have to see how KDE4 pans out. My expectation is that it’ll
prove to be a reliable and stable platform that will suffer from little regressions after 4.0 is out. That means that
we should be able to put out a snapshot every so often and use some weeks (6, 8 maybe?) to stabilise it. Time-based
releases are possible in this scenario, but we should ask ourselves if we want to release on a regular basis (and in some cases
postpone shipping some new feature because it would’ve needed three more weeks to finish and polish).

On the other hand, KDE3 releases were very reliable. If I recall correctly, we only slipped once or twice slightly due to a
security problem (which would affect time-bases releases in the same way). So practically, we have time-based
releases for some time already.

What we can do to make it easier for vendors to ship the next version of our software is making it clear what needs to be done
before a release. That would mean: “Here’s a list with what the next release will look like, if you want to make it happen
earlier, help us hacking”
This could be as easy as recording this in bugzilla, marking it as “showstopper” or “required
for x.y.z” and then make the query showing those entries easily accessible through, for example, a direct link.

As to a pulse and having Free Software communities release at the same point in time would
— from a marketing point of view —
be a very bad idea. It would mean two things: Press coverage for Free Software only once in a while,
and smaller projects being snowed
under by those that are doing better PR work. I’m actually wondering why this is brought up by Mark since Canonical’s
umbrella branding fails miserably in this respect — measured by the press coverage that a Kubuntu release has got during the
last cycles.

High-speed internet connection.

Got up early today after yesterday night’s Pearl Jam concert which totally rocked. Those guys definitely are not burnt out. Although they’re clearly still suffering from a feeling of guilt for the person who died during their act at Roskile festival in 2001 (I understand they stopped touring for about 3 years), they delivered a staggering concert in our backyard (no really, 300m from my house). Being able to make contact with the 50k people at this Open Air, having a good mixture between older and newer material and rocking with songs like Neil Young’s “Keep on Rocking in a Free World” made my day (night) yesterday. The megalomaniac in me would love those guys for the KDE4.0 Release Party, but this might be a bit hard to realise. :-)

4 hours after hitting the hay, the alarm clock went off, kicking me back into the real world. 45 minutes later, I’m at Nijmegen Central Station to commence a 13 hour trip to Glasgow where aKademy kicks off tomorrow. To my surprise, there’s wireless network available on this train. It’s not cheap, but being able to sync email once during the day and svn up on some stuff is, I think worth it. (Ok, admitted, getting online on a train is new to me, and excites the gearhead in me.) So got up early, had lunch in London, will have dinner tonight with the other board members in Glasgow (supposedly in the Livingston tower pub where other gearheads are meeting tonight.)

Tomorrow during lunch in Glasgow, I’m trying to get people together for a first press team meeting, we do have a press room for this kind of purposes, it’s L13.02 in Livingston tower. Does the 13 mean 13th floor (or just be damned?), having a nice panorama of Glasgow? Find out by coming by! 12.15 L13.02!

aKademy preps and swag.

Silken hand-made konqi pillow
So yeah, I’m obviously on a blogging spree. Meanwhile, aKademy is getting closer, 1.5 days and the
most important conference of the year (to me, that is) gets kicked off by Lars Knoll in Glasgow.
Tomorrow, I’ll spend most of the day on various trains between Nijmegen (NL) and Glasgow. There’s
flooding in Northern England reported, so it’s a bit unsure whether Adriaan and I will arrive in
time for a quick meeting of the board in Glasgow.

Today’s packing, charging batteries and printing stuff (I usually take a cheatsheet with me,
containing address of the hotel and other things I might need on the journey) is pretty much
the climax of the preparations last week. And some things aren’t solved yet. Such as the Indian
contributor who was late deciding that he’d actually want to go to aKademy, and who’s visa was
refused the first time he applied. This means a couple of phonecalls to India, faxing the same
document various times and crossing fingers. Tonight, he’ll hear if his visa finally is accepted
so het can get on his plane tomorrow. Close call, let’s all hope we’ll see him in Glasgow.

Then there’s lots of merchandising stuff that has been designed and ordered during the last weeks.
A couple of t-shirts which will change owner in Glasgow to travel on to Canada and the United States
and quite some other really cool swag. I’m sure you’ll see some of this on the blogs from
Glasgow in the course of next week. We’re seeking at making this stuff available online, but not
all the details have been sorted out yet. If you’re looking for something really special for a
gearhead,
have a look at this page.
I’ve got one of those silken pillow those, they’re really nice (and you know what you’ll be
dreaming of).

See you on Saturday!

Battery Plasmoid.

Battery plasmoid and engineexplorer showing the dataengine
Some weeks ago, I’ve started to learn a bit of C++. Trying something new once in a while
is fun and earlier programming experience didn’t make it too hard to learn some of the basics.

About two weeks ago, I’ve started hacking on a Plasma::DataEngine which works quite nicely
already although it has some smallish bugs I’ll need to look into. Now I’ve got the
Plasma::Applet that visualises the data mostly working. As basis, I’ve taken the battery SVG
Ken has made for me for powermanager. I needed to merge the different images. Ken had made
one for every frame, I’ve put them into layers. Plasma:Svg is quite nifty, parts of the SVG can
be rendered separately, so one only needs to decide which layers to render (and in what order,
of course), that’s it.

Right now, the applet does little more than showing the current status of the battery and
if the AC Adapter is plugged in. I’ve also basically implemented formfactors, so depending on
what one wants to use the plasmoid for, it changes its size.

I’ve put the code into playground
(dataengine,
applet)
for those who want to have a look at it and improve it. While
looking at it, please bear in mind that I’m fairly new to C++, so don’t bash me right away.
Comment is welcome (and ontopic on the
panel-devel list, but of course
I’ll also be at aKademy).

Talks.

Rainbow above Nijmegen
I just found an email in my inbox from Alasdair Kergan, who I met in Berlin and
who is also organising this year’s edition of LinuxConf
Europe
. I had sent in an abstract about KDE4 (what it’s about, frameworks, new
technologies, a pretty broad overview of the status and what to expect). So my talk
is accepted and I’ll be travelling to Cambridge in September. Kim told me the city is
very nice, so I’m looking forward to this.

Last week, I got two acceptance notice for another conference,
FrosCon, which is a very nice community event in
Bonn / Germany. I’ve been there last
year and enjoyed myself quite a lot.
Danimo (who happens to live near the conference venue) has kindly offered me to stay at
his place. For FrosCon, I had sent in two talks, one about KDE4 (see above) and another
one about CodeYard (also sponsoring the
KDE-EDU day at aKademy).
As I understood, there will be an Edu-track at FrosCon, so that’s definitely a good
opportunity to spread the CodeYard word some more across this country’s borders.

The photo of the rainbow was taken the day before yesterday, when this thing suddenly
turned up on the other side of the window. I think I’ve never seen a rainbow well-visible
like this. And I know exactly where the gold is (and so does the attentive reader).

We are out of whiteboard.

Today and tomorrow, Mirko Boehm, Giorgos Gousios, Adriaan de Groot have a
meeting of the SQO-OSS project here in the
(today) sunny Nijmegen / NL. Today, we filled a couple of whiteboards working on
the system architecture and trying to get some concepts straight. We agreed on
the basic use case that the system should provide information about the quality
of the code to developers, think defect count with attached information why
something is defect and possibly how to fix it.

For this purpose, the SQO-OSS system will mirror source code repositories, keep
mailinglist archives and have a copy of bugzilla databases (or other
issue-tracking systems ‘normalised’ to Bugzilla format). Metrics are done as
plugins to the system, those metrics can be simple things such as “count words
on a group of files”, but also compound metrics such as “show the development of
number of bugs per line of code over the last 36 months (with a certain
granularity)”.

The system will partly be implemented in Java, using the OSGI framework. Some
things such as job queueing will be implemented using good old UNIX tools, such
as cron.

During aKademy there will be a talk about
the SQO-OSS project given by Paul Adams of Sirius, another project partner. This
talk will also offer the possibility to provide feedback relatively early in the
process. If you’re interested in the field of software quality, don’t miss the
presentation. Paul is right now at DebConf, presenting the SQO-OSS project there
and gathering feedback so we make sure that the outcome of this project is
actually what the people would like to use it for.

The Radboud University of Nijmegen is kindly
hosting this meeting, providing infrastructure and a meeting room for us. Having
a meeting in Nijmegen is actually quite funny. On the one hand, it’s nice to be
able to sleep in your own bed. On the other hand, I’m pretty much removed from
the normal way things go. Being at home means distraction, although I’m trying
to not have too many things interfering with the meeting. It’s quality time.

Now let’s see what happens if we add beer to the design process. :-)