Apparently, with my original posting here, I stepped on several people's toes. I'm sorry for that, and for this reason, I've simply removed this content (and also because - as some of you pointed out - some of the things I mentioned were not Plasma's fault, but workarounds or bugs in other areas, although to me as a user they appeared on Plasma).

Until a few weeks ago, I had Kubuntu running on my Acer Aspire 5630 laptop (as described here), and was more or less satisfied. It looked great, hardware support was satisfying, but I was missing the incremental package upgrades that I was used to on Debian (so that things break one small piece at a time, not everything at the same time when you do an upgrade).

As I wrote in my last blog, KOrganizer now has the ability to export the calendar to all different kinds of formats using technology called XSLT transformations. The only thing that I'm missing (because I'm entirely bad at those things) are good designs that I can implement. So I'm looking for nice and visually appealing designs of how calendar exports might look. Possible export formats are e.g.

XSLT is a W3 specification that allows general transformations from XML into practically any other format (mainly XML, but you can also create any text).
In the kdepim 3.5.5+ feature branch I just added a plugin to korganizer, that exports the calendar into XML and then applies an XSLT transformation to it to generate all different kinds of output... For example, one can write an XSLT style sheet for some fancy HTML export, or for CSV export, or to XSL-FO to generate nice PDFs. One might even generate SVGs from the calendar.

Once upon a time, there were all those nice, separate applications that were somehow meant for various PIM tasks like mail, calendar, addressbook, etc. To make the world an even better place (and to share resources), they decided to unite, join forces and create this wonderful application, called Kontact. Just like one large family, they worked together and due to the large number of active developers the project flourished.

About a week ago, my laptop broke -- completely broke in the sense that not only does the machine not work any longer, it even trashed my whole harddisk. Now I'm at aKademy without a laptop and still one whole afternoon of the KDE e.V. general assembly left to sit through... Oh, how much I envy all those developers sitting in there with their laptops, hacking on KDE stuff!

Fortunately I brought my book about Austrian criminal law with me to entertain me through lengthy boring discussions.

As I wrote in my last blog, my to-do list for KOrganizer keeps growing and growing (sure, I implement / fix lots of stuff, but it seems that its still a long way to make KOrganizer perfect). So, I thought, I bet there are a bunch of interested guys and gals out there who were always interested in kdepim development, but never really dared to take on some open issue.

So here is a short list of some Junior Jobs (JJs), which I think are not too hard to implement, and which would serve as nice small projects to get familiar with our code:

Actually, today I wanted to do some serious bug fixing and reduce the number of items on my to-do list, but then I didn't get beyond one of them: Multiple reminders in KOrganizer.
Actually, like so many other features, multiple reminders were already supported by libkcal as well as by korgac (the reminder daemon), it was just the GUI component that was missing. I added that today, so it's now possible to have :

KDE is simply amazing. There you are, the current developer and maintainer of your application, and you think you know your application inside out and you are aware of all the small features it provides to the user...

To be honest: While I really love the added functionality that subversion brings (offline diffs/reverts, atomic commits), websvn (or rather the viewcvs that we use on websvn.kde.org) just sucks for my use.