Roadmap discussions were held on friday evening
(the mosquitoes are a bit of a distraction)
and again on saturday. Cornelius wrote a 
comprehensive <a href="http://lists.kde.org/?l=kde-pim&m=111729365423900&w=2">roadmap document</a>.


<h2>KDE PIM Roadmap</h2>

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.

<ul>
<li>
Next release: 3.5
<ul>
<li> Feature Freeze: August 1st</li>
<li> Includes merge of KO/Pi <a href="#2">[2]</a> changes to KOrganizer</li>
<li> Includes usability improvements based on Openusability.org suggestions</li>
<li> Release with rest of KDE depending on the common 3.5 release plan</li>
</ul>
</li>

<li> Porting to Qt4
<ul>
<li> Start porting kdepim to Qt 4 at aKademy in August.</li>
<li> Reasoning: We won't be able to do the porting in parallel to doing 3.5 
stuff and aKademy is a great opportunity to start the porting while many of 
the people having experience with it are around.</li>
</ul>
</li>

<li> KDE PIM 4
<ul>
<li> Goal:  Get KDE PIM to the masses. Target large non-geek audience, not only 
developers and power-users.</li>
<li> Manage complexity by removing unnecessary functionality, moving rarely 
used functions to extensions, make user interface leaner, cleaner and more 
directly usable.</li>
<li> Focus on workflows.</li>
<li> Adapt to the user.</li>
<li> Lots of ideas and plans are already floating around, you can add them to 
the playground on pim.kde.org <a href="#3">[3]</a> if you like.</li>
<li> We will do more brainstorming.</li>
<li> Areas in the libs which need changes for kdepim: kresources, libkabc.</li>
</ul>
</li>

</ul>

<p>
<a name="2">[2]</a> http://www.0700rogowski.net/html/ko_pi.html<br/>
<a name="3">[3]</a> http://pim.kde.org/authorhelp.php#playground
</p>