Re: kde-pim dev needed, for a sponsored open source effort, to remove akonadi

Daniel Vrátil <[email protected]> Sat, 17 Mar 2018 17:41:34 +0100
Newsgroups	gmane.comp.kde.users.pim
Message-ID	<2369597.g1PxKXdIEK@baldr>
Hi,

Martin already voiced most of what I wanted to say, but I just want to point 
out, that you can't just remove Akonadi. You need to replace it with something 
else that will do the work that Akonadi is doing now. You can drive a car when 
you removed the engine from it :) From the experience I can say that designing 
and implementing a PIM storage solution is easily worth many hundreds of man-
days, not mentioning additional time to actually port Kontact to the new 
system and polish it. It's your money and I can't tell you what to do with it, 
but maybe consider supporting development of existing projects like Trojita or 
Kube, which may just be a missing a few features to make you a happy user.

Finally, I'm really sorry that your experience with KDE PIM is bad. We are not 
intentionally neglecting it. We all love the project and working on it and we 
do want to see every single one of our users happy and satisfied. But time and 
resources are limited and many issues that users have we just can't reproduce, 
so fixing them is very hard.

Cheers,
Daniel

PS: don't take those log messages too seriously. They often lack a context 
because it is known to developers and may not even mean a serious failure.

PPS: The problem with the Kolab Configuration folder looks like misconfiguration 
on your Kolab Server, or maybe a missing support for some specific configuration 
in the Kolab Resource. I do have access to some Kolab servers, I'll see if I 
can reproduce that and fix it in the Resource.

On Thursday, 15 March 2018 15:23:53 CET Paul Vixie wrote:
> hello. i've been using kmail for about a dozen years, due to its excellent
> integration with pgp. however, it has a lot of very old bugs on board, and
> not a lot of evidence that the people who know how to fix them, are
> motivated to do so. i'd like to provide that motivation.
> 
> what i want, specifically, is a version of kontact that does not use
> akonadi. i used for a time the kontact that's built by kolab systems, but
> ultimately i need something that works well inside suse tumbleweed, which
> isn't one of kolabsys' build platforms.
> 
> i can pay a reasonable fee for this. the result would be given to the KDE
> community under the same license that kde-pim has always had. if nobody but
> me adopts it and it falls behind on feature level, then i'll strongly
> consider sponsoring ongoing development to keep the non-akonadi version
> up-to-modern.
> 
> what i don't want, specifically, is to argue about whether akonadi was or is
> or could ever be a good idea, if only it had been or could be properly
> supported. i will ignore any responses on that topic.
> 
> i send this after yet again restarting akonadi server four times so far
> today, restarting kontact twice, rebooting three times, vacuuming,
> fsck'ing, and using tcpdump to find out what's not happening so that i can
> try to guess why.
> 
> if you wish to work with me on this project, please provide me some
> references, both work you've done in kde-pim in the past, and colleagues in
> the community who would vouch for your honesty, integrity, discipline,
> follow through, and technical skills.
> 
> thank you for reading this far.
> 
> > Tokenizer Warning: 8Bit character ' -61 '
> > Tokenizer Warning: 8Bit character ' -87 '
> > Tokenizer Warning: 8Bit character ' -61 '
> > Tokenizer Warning: 8Bit character ' -87 '
> > Tokenizer Warning: 8Bit character ' -61 '
> > Tokenizer Warning: 8Bit character ' -87 '
> > org.kde.pim.imapresource: Called item() while state holds multiple items!
> > 
> >  void ContactSearchJob::setQuery(Criterion criterion, const QString
> >  &value,
> >  Match match) "[email protected]">
> > 
> > void ContactSearchJob::setQuery(Criterion criterion, const QString &value,
> > Match match) "[email protected]">
> > 
> >  AFTER ::::::::::::::::::::::::::::::::::::::::
> > org.kde.pim.kolabresource: Failed to create configuration folder:  "Create
> > failed, server replied: A000368 NO Mailbox already exists "
> > org.kde.pim.kolabresource: Failed to create configuration folder:  "Create
> > failed, server replied: A000369 NO Mailbox already exists "
> > org.kde.pim.kimap: Connection to server lost  2
> > org.kde.pim.imapresource: Session login cancelled
> > QIODevice::write (KTcpSocket): device not open
> > org.kde.pim.kolabresource: Failed to create configuration folder:  "Create
> > failed, server replied: A000067 NO Mailbox already exists "
> > org.kde.pim.kolabresource: Failed to create configuration folder:  "Create
> > failed, server replied: A000068 NO Mailbox already exists "
> > qt.network.ssl:
> > QSslSocket::startClientEncryption: cannot start handshake on non-plain
> > connection org.kde.pim.kolabresource: Failed to create configuration
> > folder:  "Create failed, server replied: A000448 NO Mailbox already exists
> > " org.kde.pim.kolabresource: Failed to create configuration folder:
> > "Create failed, server replied: A000449 NO Mailbox already exists "


-- 
Daniel Vrátil
www.dvratil.cz | [email protected]
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

GPG Key: 0x4D69557AECB13683
Fingerprint: 0ABD FA55 A4E6 BEA9 9A83 EA97 4D69 557A ECB1 3683
signature.asc (application/pgp-signature, 833 B)