This week in Kalendar development: v0.3.0 coming this week, bringing improved stability, efficiency, accessibility... and a Windows version??
Read all about the big changes that have taken over the past two weeks:
@claucambra @kde @carlschwan awww, but it's also Akonadi-based right?
*sigh*
@rysiek @claucambra @kde @carlschwan is there any alternative? 😆
@musicmatze @rysiek @kde @carlschwan
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!
@claucambra @rysiek @kde @carlschwan
So why isn't there more love? Isn't there a fairly long list (from what I read on kde.org) of Patreons? Can't be a funding problem, is it?
@musicmatze @claucambra @kde @carlschwan I've seen some threads on KDE mailing list that suggested that there is a serious problem with finding and *retaining* contributors.
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.
@rysiek @musicmatze @kde @carlschwan
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 and it's lacking for reasons that have not changed for a decade. 🤷♀️
@rysiek @musicmatze @kde @carlschwan
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 :)
@claucambra @musicmatze @kde @carlschwan I remain hopeful, and I do use KDE as my main environment. In general, it's great.
@rysiek @claucambra @kde @carlschwan same here! Am using KDE Plasma for about a year now (came from XFCE and before that sway and i3) and I never been happier with my desktop.
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 😄
@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.