KDE 3.2 release cycle

[Cornelius Schumacher]

On Monday 19 May 2003 17:28, Bernhard Reiter wrote:
> On Saturday 17 May 2003 10:19, Cornelius Schumacher wrote:
> > On Friday 16 May 2003 18:18, Bernhard Reiter wrote:
> > > On Tuesday 13 May 2003 20:54, Aaron J. Seigo wrote:
> > > > the KDE PIM stuff is more important than all the other
> > > > applications you mentioned put together from the standpoint of
> > > > user benefit. this is not to put down those other apps, since i
> > > > think they are all great and strategically important. rather,
> > > > this speaks to the overwhelming importance of a solid PIM
> > > > infrastructure and application set in KDE.
> > >
> > > I can second this as many coporate users hope
> > > that KDE 3.2 will be able to natively act as a Kolab client.
> >
> > This still requires quite some work.
>
> Yes I know.
> Still the expectations seem to be there.
> I didn't raise them and this might show a bit
> of a discrepancy between KDE marketing
> (no 1 desktop, ready for the workplace)
> and what promise it actually can hold.

I'm not aware of any KDE marketing for 3.2 regarding the ability of 
kdepim to act as Kolab client.

> > If there are many corporate users which are interested in that
> > feature it might be a good idea, if they would help with that, e.g.
> > by providing developers or paying developers to do the work.
>
> True, but this is a chicken-egg problem.
> If KDE does not get many corporate users,
> chances are lower they get interested and involved.
> On the other hand, if they don't get involved they
> might never have anything they can use.

But in this case we already have a chicken, because there is a Kolab 
client and I suspect there also are some users of it, right? In order 
to secure the investion into the kroupware project it would be very 
sensible to take care that the result of the project is properly 
integrated into the main KDE development. You already did some 
important steps towards this goal, but it's still not done.

> In my original email I also explained why
> the monolithic project release structures
> makes it harder for companies to engage in
> smaller contributions to stable components.
>
> > As this
> > feature isn't that interesting for non-corporate users (and
> > developers), I suppose it's unlikely that it is implemented by the
> > "regular" KDE development process.
>
> I believe that it is interesting to non-corporate users, too.
> PIM is a high profile desktop application.

Agreed, but a Kolab client is only a small subset of PIM, which is 
targeted to a very specific group of users because it requires a Kolab 
server. The scope of KDE PIM is much broader than that and most of the 
work currently done addresses much more general needs than acting as a 
client to a special server.

-- 
Cornelius Schumacher <schumacher at kde.org>