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
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.
@claucambra @musicmatze @kde @carlschwan okay, but the flipside of this is that the KDE project decided to force Akonadi (in the state it was 10 years ago) down users throats.
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.