The Lenovo Thinkpad P50 is quite a nifty laptop. However installing Linux required some digging around, so I'm writing this up for others to stumble upon it when looking for answers to similar issues.

For quite some time now (OK, many years...) I haven't had time for Konqueror.
KDE Frameworks 5 and Qt 5 have kept me quite busy.

It's time to face the facts: Konqueror needs a new maintainer.

This is a good time to publish the thoughts we had many years ago about a possible new GUI for Konqueror.

On my desktop machine, I have always tried to compile "everything". At a time it was easy: about 18 SVN modules listed in kdesvn-buildrc, trunk for everything, done.
Nowadays there are many more git modules - I currently compile 234 modules, with the help of kdesrc-buildrc (I don't have to list all 234 modules, it expands them for me). Still it's a bit difficult to ensure I really have everything...

Due to popular request during my KDE Frameworks 5 presentation, in other words "where can I get KArchive today?", which is also a long-standing request from many developers of Qt applications, I experimented with making a Qt4-based release of the KArchive framework.

The Qt5-based karchive will be a lot thinner, thanks to much of the necessary functionality going into Qt5 (mimetypes, standard paths, safe saving...). For now, the Qt4 package has to come with all that stuff built in.

Here it is: http://www.davidfaure.fr/2012/karchive-qt4-1.0.0.zip

git: very powerful, not easy to use for simple tasks.
Especially when coming from svn, where updating a local checkout was simply "svn up", and with git it's "git pull --rebase, and if that fails, stash, pull --rebase, stash pop".

Finally, all this can be automated, so that one can simply keep the good old habits from svn and type "git up"!

Here's the recipe. In your ~/.gitconfig, write
[alias]
up = !gitup

Then download the script http://www.davidfaure.fr/scripts/gitup and put it in your $PATH.
Done!
(Should have done that years ago...)

My wife's assistant uses KMail (obviously) and KOrganizer (for a Kolab shared calendar).
To spare her from akonadi trouble, I installed OpenSuse-11.4 for her, which comes with KDEPIM 4.4.

After 6 years of absence, I participated again in a KDEPIM meeting, to fix some issues in Akonadi in order to improve my daily life :-)

Here's a report of what I did:

Fixed: "incomplete collection" error in mixedmailresource (bug 285973)
Fixed: mixedmaildir resource can lose email when changing message flags (bug 289428)
Fixed: Assert in imap resource when resuming work after going offline (bug 291810)
Fixed: cancelling mail check doesn't really work (two different bugs)

I got a HP Pavilion g6 for my birthday -- this must be the first time I have a personal laptop, all my previous ones having been bought by KDAB (or by IBM as KDE sponsoring, for the very first one).

Main purpose: Windows music software. But also reading KDE email of course. So I installed linux (openSUSE, to try it out for the first time).

We often need to check for a system function or library availability, like HAVE_XZ_SUPPORT, and we put that into a cmake-generated file like config.h (much better than -DFOO because changing that requires recompiling everything).

That's fine. However a single config.h at the toplevel of kdelibs is not modular; every change requires recompiling everything, and at some point we would like to split up the libraries to make their adoption easier by other people.

As a followup to my previous post: I just added a feature to kdesrc-build which makes it possible to run the tests and upload the result to http://my.cdash.org. Just add the line "run-tests upload" in your module definition for kdelibs, and others if wanted.