• boredsquirrel
    7·
    3 days ago

    Hey, I am really excited about this!

    A few questions:

    1. Will this be developed in parallel to #Kontact, are the same devs working on it, is only the UI changing and background things kept the same? Will it replace Kontact some time, swapping out, or getting the name?
    2. Is #CalDAV support possible currently, in the past or planned? It is a major dealbreaker for me currently.
    3. Are CalDAV features supported by #DAVx5 planned? Like journals?
    4. The #Flatpak is kinda bundled in the “Kontact” Flatpak. Will this change?
    • Carl Schwan :kde:@floss.social
      6·
      3 days ago

      @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.

      1. CalDAV is definitively supported

      2. 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.

      • boredsquirrel
        2·
        3 days ago

        Thanks! And does Merkuro use the same backend things as the older Kontact suite?

        And if CalDAV is supported, where is it added? On Fedora Kinoite I have no support, only Nextcloud etc. I woule file a bug at the correct place.

      • Carl Schwan :kde:@floss.social
        1·
        3 days ago

        @boredsquirrel @kde

        1. 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.