Unlikely to happen because:
- Writing a sync service from 0 is a gigantic pain
- Akonadi is incredibly powerful and handles most of what anyone would need from a sync service
- Akonadi has a sensible and easy-to-use API that apps like Kalendar can leverage
- There is no alternative that uses KDE APIs that is under active maintenance
Not saying Akonadi doesn't have big issues, but it is a good base. It just needs more love -- love it hasn't really gotten!
Most of that money goes to paying for contractors and events hosted by the community. AFAIK there are no contractors being employed to work on Akonadi. Like 99% of other KDE developers, Akonadi developers do it for free.
Paying someone to help improve the framework would be one way to help things. The other would be to try to encourage new developers to come in and help -- this is what is mostly done for other KDE projects like Plasma.
Two factors were explicitly mentioned:
- complexity of the system (yeah, no kidding);
- less-than-great way that the project reacts to criticism (with ample examples of that in that thread).
If I find that thread, I'll link it here.
I think it is important to note the human element here: an incredible amount of effort went into creating a super powerful PIM framework, and then many people piled on to criticise it -- some for better reasons than others.
It is natural for the response to sometimes be overly defensive in reaction to these things. Again, as a PIM developer myself -- Akonadi often gets more flak than it deserves, though I also agree some changes are needed.
Disrupting lives and work of hundreds of thousands of users, just because they decided that "it's ready" when it was anything but.
That is no way to treat your userbase. And yes, it's a FLOSS project, so technically users are not owed anything, but in that case the devs need to deal with the criticism.
In terms of complexity, I partly agree here, though I also think proper documentation would go a long way to making things seem less impenetrable even without any technical changes. Yet writing documentation also required manpower, which as we have established is lacking in Akonadi development right now
@claucambra @musicmatze @kde @carlschwan anyway, my apologies for butting-in and ranting about Akonadi. I do have strong feelings about it, and they are based in personal experience and observing the project for a decade.
But you didn't sign up for this, and I should have kept this as a separate thread.
In no way should that make you feel bad, I'm sorry if it did. I appreciate anyone who is contributing code and working on FLOSS.
Certainly enough people have complained about it by now for us to be aware of the fact it has issues. Unfortunately what we need is to get more people working on a solution, and from my point of view that means fixing what we have and not starting back from square one.
Unfortunately, unlike Plasma since the 4.0 days, Akonadi hasn't really seen a concerted effort to address the large issues. Hopefully that will change sooner rather than later :)
Having a fully integrated and usable Kontact suite and a way to sync configuration between multiple devices are my only two painpoints with the ecosystem 😄
@musicmatze @claucambra @rysiek The problem is funding. There haven't been developers funded on working on the internal of Kontact in years. The sponsors listed on kde.org are just barely enough to pay for the small developer meetings and a few part-time contractors working on promo and other community events.
@musicmatze @claucambra https://community.kde.org/Get_Involved/development is a good start! I personally had almost no development experience in any language other than html/css before starting contributing to KDE.
KMail/Kontact were the best PIM tools I have used in my life, hands down. And then Akonadi came along, and I had to switch to the dumpster fire that Thunderbird is.
Today, KMail/Kontact are *finally* barely not unusable.
At some point somebody needs to recognize that Akonadi is overcomplicated and overengineered for what it is trying to do.
@claucambra @musicmatze @kde @carlschwan everything is a separate process -- okay, great. But that causes inevitable coordination problems, which I run into all the time. Two IMAP processes, one Mail Filtering Agent, and if stuff happens in the wrong order, the whole thing just locks up good. Need to kill it and restart it.
Even when it is not locking up, I have to be mindful when I do things. I literally check if there is no back-end task running before I re-run filters on my mailbox.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!