Kolab client integration

[Bo Thorsen]

On Monday 12 July 2004 10:19, Cornelius Schumacher wrote:
> On Monday 12 July 2004 08:45, Bo Thorsen wrote:
> > Cornelius, that's just not true! The only thing that's branched is
> > the new format stuff. Everything else is just HEAD. All our testing
> > and functionality is done in HEAD, and we don't have any secret
> > patches anywhere.
>
> Well, your last commit to KOrganizer was something like two months ago.
> Since then I had to do some pretty serious changes because of problems
> in the groupware parts, e.g. the Free/Busy stuff didn't really work.
> You tell me that my changes didn't break any Kolab-related
> functionality and that now everything works perfect? Ok, that's good.

As long as I don't get bug reports that FB lists are not working, I don't 
fix them.

> > We are doing this all the time. We have two guys in the project
> > that's do testing and documentation.
>
> Where is this documentation? The KOrganizer manual doesn't contain a
> single line from you. The Kolab functionality isn't documented at all
> and given that the text freeze for KDE 3.3 is tomorrow, I doubt that
> this will change.

This documentation is unfortunately still an OOo document :-( I did not 
know about this text freeze, or I would have done something about it 
sooner. But of course it's obvious that translators need time.

> Who are these two guys, by the way?

Michel and Tobias from KDAB (michel|tobias)@kdab.net.

> > And we do work with both the KDE bugzilla as
> > well as the kolab bug tracker.
>
> Sorry, then I must have missed the bug reports. Could you please point
> me to the KDE Bugzilla numbers?

You misunderstand me - I care about bugs in bugzilla also. But kolab 
related bugs are put in the kolab tracker. All non proko2 bugs I send to 
bugzilla.

> > > Nobody will be able to correctly set up the Kolab client
> > > functionality without a wizard. This beast is much too complex. If
> > > you don't care about usability you might say that it isn't
> > > essential, but that isn't the way KDE usually works and it
> > > certainly is something you have to integrate before you honestly
> > > can say that the Kolab client is _fully_ integrated.
> >
> > You really insist on insulting our work :-(
>
> Sorry, if you got that impression. That's not my intention. I
> appreciate the work you have done, but I think there are still some
> open issues before you can really claim that the Kolab client
> functionality is _fully_ integrated. I tried to point these issues out
> several times, but not all of them were addressed (see wizard, conflict
> resolution which were there in the kroupware branch but are not in the
> HEAD branch).

Ok, thanks for the explanation. And for what it's worth, I don't think we 
disagree on what should be implemented.

Bo.

-- 

     Bo Thorsen                 |   Praestevejen 4
     Senior Software Engineer   |   5290 Marslev
     Klarälvdalens Datakonsult  |   Denmark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20040712/0e9a4929/attachment.sig>