The NL-PIM Meeting is a variation on the theme of the Osnabrück Meetings. For the past three years, KDE PIM has held meetings in Osnabrück every January, where the developers of KDE PIM get together at the offices of Intevation GmbH to spend one concentrated weekend of effort in improving KDE PIM -- programming, bugfixing and communicating effectively as only a face- to-face meeting can provide. This year, the KDE NL organization would like to ramp up productivity by scheduling an additional meeting, in the Netherlands, in May. This additional meeting provides a way to evaluate the effects of the Osnabrück meeting, evaluate the latest KDE 3.4 version, and plan KDE PIM efforts leading up to the KDE 4.0 release.
May 27th to May 29th, 2005, in Annahoeve (Netherlands). We will be using the facilities offered by the convention center Wallsteijn.
The KDE PIM NL meeting is timed to coincide with several conferences in the Netherlands, so that the KDE PIM developers also have venues to discuss their work with people outside the KDE project.
The following people have confirmed attending the KDE NL PIM meeting (assuming they are in range; Duncan might still be in Chile at the time).
We hope for a few more, from the RSS and Handhelds communities.
The PIM meetings do not normally start with an agenda, but this time we have put together a list of likely topics to work on before hand.
The NL-PIM meeting is organized by KDE NL and the following individuals:
Organizational details and the budget can be found on the KDE NL website for the PIM meeting.
This is the comprehensive NL PIM meeting report. The NL PIM meeting 2005 was sponsored by
From Friday May 27th until Sunday May 29th the developers of the KDE collaboration and groupware application suite KDE PIM (Personal Information Management) came together to discuss several important topics and to boost development efforts.
KDE is the leading desktop for UNIX and Linux systems, with work underway to make the key applications also available for Microsoft Windows and Apple Mac OS X. The KDE PIM application suite consists of several applications for e-mail, calendaring, messaging and more, which are also integrated together in the flagship application Kontact, a powerful replacement for applications like Microsoft Outlook and the Lotus Notes client. KDE and the KDE PIM application suite are developed as Free Software, which means that all code of the applications is freely available for anyone who is interested and that contributions from other people are strongly encouraged.
The meeting took place at the Annahoeve, which is a country house near Zundert in the very south of the Netherlands, close to the Belgian border. Developers from all across Europe, representing all the key KDE PIM applications gathered for coding work, together with usability experts who specialize in making computer software more user friendly.
The event started on Friday morning with several presentations from the sponsors and key developers with topics related to the meeting. After the lunch the meeting itself took off. Between this afternoon and Sunday evening the developers were able to fix several bugs, improve the user friendliness in a couple of places and to discuss several key topics, which will be discussed in detail below. During the end of the meeting many smaller discussions were held about upcoming work. The result of these smaller discussions is only now, about a week after the event, slowly becoming visible, with more interesting developments still going on.
Looking back at the event several very important results were made, most notably in the area of decision-making, which works best when the involved people meet in person. One of the key factors to the success of the meeting has certainly been the excellent location. The quiet area, away from crowded city streets, the nice weather and the luxury of everything being taken care of, including high-quality catering helps a lot in focussing on the issues at hand and stimulating healthy discussions. The event certainly would not have been as successful without the sponsors who made it possible to work in this location in the first place.
Perhaps the most important discussion held during the event was the overall roadmap for the KDE PIM applications. Roadmap discussions really require the developers to be physically together to be effective, so the event was an excellent opportunity for this.
The discussion focussed on the upcoming releases of KDE 3.5, the next generation desktop KDE 4 and the vision for the long term. The key factor for the roadmap is that there is not sufficient man power to develop for KDE 3.5 and KDE 4 simultaneously, so a decision had to be made on whether to participate in KDE 3.5 at all, and if so, when to move towards KDE 4.
Summarizing the discussion the following major decisions were made:
Roadmap discussions lasted late into the night. The complete roadmap document can be viewed below.
This part of the report was contributed by Ingo Klöcker.
Martijn Klingens, Thomas Zander and I discussed how to improve Sieve support in KMail. We discussed which filters should be uploaded and how we should present the status of the filters (server side vs. local) to the user. Martijn has sent an extensive report to kmail-devel.
Several people added smaller usability improvements to KMail (making menus more consistent within KMail, making shortcuts more consistent with other Kontact components, removing unnecessary buttons from the toolbar, progress screen for slow loading IMAP folders, show the message which is associated to an event in a separate reader window instead of in the main window). All those improvements were the immediate result of discussions between the participants.
Jan Mühlig and I discussed how to improve spam filtering and in particular the anti-spam wizard. Thomas also came up with some suggestions for improvements. Andreas Gungl (who didn't attend the meeting) implements those suggestions and has committed the first improvements recently.
Before the meeting, KOrganizer's development stalled. During the meeting, a lot of new development is planned for KDE's calendar application. Lutz Rogowski, maintainer of the KO/Pi project, joined the meeting to discuss a merge with his forked KOrganizer version with ours. The KO/Pi-project is a multiplatform PIM suite for Linux, Windows the Zaurus PDA. Thanks to Qt, it's quite easy to port an application to platforms like these. The software includes more features and bugfixes, and is optimized to sync perfectly with the Zaurus. Now, it's time to merge some of these new features back into KOrganizer.
A short summary:
KPilot work concentrated on finding and fixing two bugs that had snuck into the code recently -- just before the KDE 3.4.0 release. These bugs were off-by-one bugs in buffer code, and were found after much harrowing examination of that buffer code. Patches were released and incorporated into KDE 3.4.0.
The KDE PIM website was updated a bit to reflect the new focus on people and development for PIM. This continues the trend of splitting the information about PIM into two sections: the user information about applications and how to use them is on kontact.org while developer information -- architectures, API documentation, developer histories and a who-is-who listing -- is on pim.kde.org.
A much bigger undertaking was the redesign of the kontact.org. The current site looks somewhat dated, and is a purely tables-based design which can be hard to navigate. A mockup was produced by some artists and this mockup was implemented with CSS and some additional PHP code. The new Kontact website is viewed by many as "much prettier", but it has not gone live yet.
Another point of attention for the Kontact website is the text content available on it. The current wording of many sections is developer-oriented, while the site is intended for users. Work continues in this area, but will require some attention from a PR person.
Developers agree: this was a good place to get hacking done. Small-scale hacking works best -- you need to be able to get three to five developers in a secluded spot to get some real design work and decision making done; you need to be able to sit apart and really hack at a single bug; the whole group needs to be able to get together to talk about large-scale issues like the roadmap. In each of these respects the Annahoeve ws an excellent fit. With wireless covering most of the lawn outside, excellent weather (it can't be arranged for everyone though) and several rooms inside -- upstairs, the dining room, the bar -- available for single or group hacking, it was possible to be really productive all the time we were there.
Another part of good hacking is good food -- not only that, but good food supplied at the right time. With all the basic necessities (of course we need French bread and crab salad) taken care of, with enough coffee to start the brain cells in the morning, and beer to cool a fevered brow after a bug has been vanquished, the Annahoeve again showed its class. The nice thing about having everything taken care of is that you never need to lose your stride by thinking about the mundane: there is no restaurant to choose, since it sidles up to you instead. Fabrice also helped by dishing out chocolate, drop (licorice) and cookies liberally throughout the day.
It was a good place to hack.
Roadmap discussions were held on Friday evening (the mosquitoes are a bit of a distraction) and again on Saturday. Cornelius wrote the following comprehensive roadmap document.
We had a session about the roadmap for KDE PIM at the KDE PIM NL meeting. Here is what we came up with. This should serve as a starting point for a discussion. The goal is to agree on a roadmap for KDE PIM for the releases up to KDE 4. It's not set in stone, but it certainly would be very beneficial, if we can state, what our common plans and goals are. If you have comments, objections, ideas, please don't hesitate to reply.
The basic assumption of the roadmap is that we won't be able to do feature work in two different branches, while porting one branch to Qt 4, because we don't have the resources to cope with the inevitable merging hell which would result from this. So we propose to concentrate on the 3.5 release and start Qt 4 porting and KDE 4 feature work when 3.5 is basically done.