If you're a developer interested in RSS in KDE (and maybe you are at GCDS right now), please scroll to the end.
Akregator development was slowed down for quite some time: The development team was basically reduced to one person, me, and I had not much time for it. That's why Akregator only slowly recovered from porting regressions introduced during the KDE4 port. Also, the article storage layer showed its limitations (see startup time and memory consumption) and the metakit backend implementation lacks robustness, thus it became clear that something must happen to make both the user experience pleasant and hacking Akregator fun again. Another long outstanding wish of mine was to decouple feed list handling and item storage from the core Application to a central desktop service, to make both accessible to other applications without the need to run Akregator.
Nowadays, the natural choice to achieve al this is to use Akonadi (although the idea was already in my head, before Akonadi even existed, I think). Luckily, Dmitry Ivanov came along and implemented RSS support for Akonadi (SVN, Dev-Wiki) as his last year's GSoC project.
Dmitry did an excellent job here with designing and implementing krss, and also giving feedback (and sometimes debugging) to Akonadi. And, at least as important, he sticked around and now a year later, we decided that to go forward, stay motivated and to get to the real world usage scenarios, it's time for porting Akregator to Akonadi/krss, improving krss while doing so. We started with that a few weeks ago and to my own surprise, this went quite smoothly so far. After a weekend, we had the basics ported and most of the old Feed and Article classes removed. Now, the port is already usable for feed reading (for certain definitions of "usable", that is). Data migration from Akregator also works, even if importing large Akregator archives shows some performance issues and the need for some more optimization sessions. Here's the mandatory screenshot:
Doesn't look too exciting? The UI of course didn't change much while porting, the only notable change there is that krss doesn't group feeds in hierarchical folders but in a flat set of tags: Every feed can have n tags assigned, and the pseudo-tag "All Feeds" lists all of them.
So what are our plans with krss?
Moving RSS handling to Akonadi, krss could help to improve the "RSS experience" for all of KDE by sharing feed list and item storage within existing applications such as Amarok, KTorrent or RSSNow! or easily writing new ones, e.g. a Konqueror plugin or a dedicated stand-Podcast client. Integration of RSS-enabled applications in KDE could be vastly improved, a topic deserving at least another blog entry. Its also time to reach out to the developers of applications like the ones mentioned above to find out what's missing to fullfill their needs.
If you at GCDS and either working on an existing application using RSS, or have interest in krss and Akregator, just poke me. Or mail me, but it might take me some time until I read it). Depending on the interest, I might also set up a little BoF/informal meeting at the beach during next week. If you're not at GCDS, you are of course also invited to join the fun. It's the perfect time to get involved and make krss and its apps rock.