carlschwan

@kde @mykolak @kde@lemmy.kde.social It's a bit more complicated than that. There has been many bug reports about this already and it's a conflict prone subject even between KMail contibutors...

@TheGhostHybrid @palitu I probably should update the readme... This is a bit outdated

@louis_sch @m4m4m4m4 Thanks :)

@Strit @m4m4m4m4 Thanks!

@boredsquirrel Yes Merkuro uses the same backend. And we (Merkuro dev) are contributing to improve it which benefit all the Kontact users.

@boredsquirrel @kde

4. We indeed need to figure out a good flatpak strategy for Merkuro. The advantage of putting everything in the Kontact flatpak is that it allows us to share the Akonadi engine with e.g. KMail. This might change when Merkuro Mail is mature enough.

@boredsquirrel @kde 1. While some devs (like me) works on both Kontact and Merkuro devs, other are only working on one of them. I don't see Kontact disappearing anytime soon.

2. CalDAV is definitively supported

3. Journals works in KOrganizer. It's quite unlikely I will add that to Merkuro mail any time soon as I have no real use for them and I don't want to makes the UI more complex.

@alfajet @kde @kde@lemmy.kde.social BMW is using a bunch of our frameworks already and do occasionally some contributions: https://invent.kde.org/frameworks/bluez-qt/-/commit/1a5660ab1547236c7bc0f883bbbb039889489a22

@QuazarOmega https://en.wikipedia.org/wiki/KIO

@QuazarOmega @G020B The power of KIO!

@Strit @leopold It takes a lot of time to port to KF6 and it is good that a release sooner than later even if it is still based on KF5.

@blackfire @thisweekinkde kubuntu 24.04 won't include plasma 6 but a not so well maintained plasma 5 session unfortunately