Last weekend a group of developers gathered in Berlin at the KDAB office for an Akonadi sprint. The goal was simple, getting Akonadi in shape for the first public release of Akonadi when KDE 4.1 is released. In the couple of days they met, they made an amazing amount of 270 modifications to the KDE repository, and worked on average from 10am to 3am to make a big step into reaching that goal. Read on for details.
From left to right: Kevin Krammer, Tobias Koenig, Volker Krause, Tom Albers, Thomas McGuire and Frode Døving.
Akonadi is the framework that will be used by the PIM-applications to cache their data. That means that it can contain your address book, e-mails and agenda items, or any other data you want in there. It will be the framework that will be used by most of the KDE PIM applications for the KDE 4.2 release.
During the sprint the current problems were identified, discussed in detail and prioritised. There now is a complete list of things that need to be done before the 4.1 release and things that would be nice to have before 4.1, but are not crucial.
The developers also moved the KDE specific library to the final destination in the subversion tree. The Akonadi server still needs to be moved to a desktop neutral position, but that is currently blocked by one issue, which at the end of the meeting was properly documented with a very complex testcase which has been passed onto the appropriate people.
The third major task completed during the meeting was a review of that library. Each and every part of the Akonadi library has been evaluated to make sure the naming is consistent and logical. The developers identified over a hundred issues, most of them simple renamings, but some more complex changes are required as well.
The Mailody developers were around to share the experiences they have had with working with the library. Because that will be the first application that will be available using Akonadi, they could give feedback about the current pitfalls of the library.
During the sprint an amazing amount of work was put into Akonadi and related KDE PIM code. In the time equivalent to 6 person weeks the developers committed about 270 modifications to the repository.
We can easily say that this meeting was one of the most productive Akonadi meetings in the past years and the developers are looking forward to the first public release of their software.