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

[Pablo Sanchez]

*** Please do not email me directly.  Email the list. ***

Below is your message.

If you feel strongly about something, do.

I cannot change that you misunderstood my initial response.  I am done with 
this thread as it is devolving.
---
pablo on my mobile device

--- Original message ---
From: Alexander Zhigalin <alexander at zhigalin.tk>
Sent: March 16, 2018 22:41:24
To: Pablo Sanchez <pablo at blueoakdb.com>
Subject: Re: kde-pim dev needed, for a sponsored open source effort, to 
remove akonadi

Because they don't want to admit akonadi was, is and will be a mistake?

17.03.2018, 03:30, "Pablo Sanchez" <pablo at blueoakdb.com>:
.. and now I get why devs don't like to post.
---
pablo on my mobile device

--- Original message ---
From: Alexander Zhigalin <alexander at zhigalin.tk>
Sent: March 16, 2018 22:27:32
To: Pablo Sanchez <pablo at blueoakdb.com>
CC: KDEPim Users ML <kdepim-users at kde.org>
Subject: Re: kde-pim dev needed, for a sponsored open source effort, to 
remove akonadi

Hi Pablo,

That is, to make it performant I don't think there is much effort.  That is 
what we were talking about.  I think you misunderstood something.
I think you misunderstood something, because we were not speaking of 
performance.
We were speaking of cutting out akonadi because it have so many bugs that 
it's literally a cancer.
As with Open Source, contributions are always welcomed.   I am sure if you 
want to help your contributions would be invaluable.
Well, I would like to contribute, at least to fix caldav/carddav but 
akonadi is just too complex for me.
If Paul initiative of removing it will success (I really hope it will 
because kontact is unusable now) than I might be able to contribute...

15.03.2018, 17:31, "Pablo Sanchez" <pablo at blueoakdb.com>:

Based on my experience with these types of problems, I don't think
there's much. I found an egregious issue. That's a good thing
because that means once it is resolved, it'll solve a lot of the
problems I've read about: fans going crazy, etc.17.03.2018, 00:56, 
"Alexander Zhigalin" <alexander at zhigalin.tk>:
You don't think there is much? Really?
In the last 6 months:
"Unable to start akonadi" randomly.
Random crashes when trying to interact with kleopatra.
Mail setup wizard completed without errors but no mail account is being added.
Deleting a contact break carddav sync.
Now carddav and caldav are both not syncing, and the agent show no errors.
The second event with the same title in the same day not displayed with 
google calendar. [ happening right now ]
Create an all-day event in korganizer and it won't be synced to google, but 
if you create it with web interface akonadi will sync it. [ happening right 
now ]
Kmail columns set to minimal width, column size not being remembered, 
automatic alignment is available but only manual. [ happening right now ]
Akregator suddenly lost all the feeds with no motivation, 3 times
Notes randomly not displayed. [ happening right now ]
Notes randomly being deleted.
If you have 3 events which intersect at some point, the first event will be 
displayed twice as wide as it should and the right half of it will "blink". 
[ happening right now ]
Notes folders randomly being hidden. [ happening right now ]
All the notes was lost at some point.
If you close kontact while being on the akregator section the next time you 
open it akregator will crash.
kontact just randomly crashes sometimes (roughly 3 times a month).
kalarm randomly creates akonadi_kalarm_resource_* agents each one of them 
is creating 6 000 calendar files (6000!) in it's ~/.local/share folder and 
eats up to 200 mb of RAM. [ happening right now ]
so right now i have 13 kalarm agents totaling 85 000 calendar files with 
only one active daily alarm and only one expired alarm.
all of these 13 agents have "status: Online, Broken" and "status message: 
unable to start" but my only active daily alarm is being started regularly 
in spite of this.
Each time I power on my PC i should run "killall akonadi_kalarm_resource" 
before they kill my RAM
I should run "killall akonadi_kalarm_resource" 3 times because the first 2 
times I kill them they resurrect.
Removing all the kalarm agents from akonadi console is not helping
I'm not even going to list all the minor glitches I'have seen.
You still don't think there is much?

17.03.2018, 03:08, "Pablo Sanchez" <pablo at blueoakdb.com>:
Hi Alexander,

Ignoring the sarcasm, yes really.   That is, to make it performant I don't 
think there is much effort.  That is what we were talking about.  I think 
you misunderstood something.

As with Open Source, contributions are always welcomed.  This is why I am 
helping on the database front.   I am sure if you want to help your 
contributions would be invaluable.

Cheers,
-pablo


--
Alexander Zhigalin — Developer Operations
Consulenze & servizi informatici
———————————————————————————————————————————
Email: alexander at zhigalin.tk
Cell: +39 380 593 0050
Tel:  +39 019 294 0240
Fax:  +39 019 924 1167

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20180316/8bf7c04f/attachment.html>