[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] KDE PIM roadmap
From:       Mark Bucciarelli <mark () easymailings ! com>
Date:       2005-06-30 13:06:43
Message-ID: 20050630130643.GH1280 () rabbit
[Download RAW message or body]

On Sat, May 28, 2005 at 05:19:58PM +0200, Cornelius Schumacher wrote:

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

Seems I am the only one with comments.  ;)

Am I the only one concerned about the quality of 3.4 KDEPIM?  Speaking
for myself, karm 3.4 was a poor release and I have been getting bug
reports from frustrated users.  Traffic on the list suggest that for
some users, other pim apps are not up to their usual high standards.

So I would like to suggest another goal for KDE PIM 4:

  - Improved quality by writing automated functional tests for an agreed
    upon set of functions.

Thorsten and I have been working on automated functional testing in
karm, and it is becoming mature.  We use a combination of dcop,
xautomation, and things like a local Perl Webdav server and a local
Python HTTP server that supports PUT.  We have a C++ wrapper that runs
all scripts it finds in the test directory so adding a new test is as
simple as saving a Perl or Python or Bash or PHP script to that
directory, make check finds it and runs it.

From watching cvs, I know that Reinhold has been working hard building
unit tests for libkcal.  To ensure quality I think we to start building
automated functional tests as well.

m

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]