May/June in KDE PIM

Following Dan it’s my turn this time to provide you with an overview on what has happened around Kontact in the past two months. With more than 850 commits by 22 people in the KDE PIM repositories this can barely scratch the surface though.

Around email a particular focus area has been security and privacy:

Laurent also continued the work on a number of new productivity features in the email composer:

This isn’t all of course, there’s plenty of fixes and improvements all around KMail:

And fixing papercuts and general polishing wasn’t forgotten either (most changes by Laurent):

Around calendaring, most work has been related to the effort of making KCalCore part of KDE Frameworks 5, something that particularly benefits developers using KCalCore outside of KDE PIM. The changes to KCalCore also aimed at making it easier to use from QML, by turning more data types into implicitly shared value types with annotations. This work should come to a conclusion soon, so we can continue the KF5 review process.

Of course this isn’t all that happened around calendaring, there were a few noteworthy fixes for users too:

Like calendaring, contact handling also saw a number of changes related to making KContacts part of KDE Frameworks 5. Reviewing the code using KContacts lead to a number of repeated patterns being upstreamed, and to streamlining the contact handling code to make it easier to maintain. As a side-effect, a number of issues around the KContacts/Grantlee integration were fixed, solving for example limitations regarding the localization of contact display and contact printing.

There is one more step required to complete the KContacts preparation for KDE Frameworks 5, the move from legacy custom vCard entries to the IMPP element for messaging addresses.

The probably most important change in the past two months happened in Akonadi: Dan implemented an automatic recovery path for the dreaded “Multiple Merge Candidate” error (bug 338658). This is an error condition the Akonadi database state can end up in for still unknown reasons, and that so far blocked successful IMAP synchronization. Akonadi is now able to automatically recover from this state and with the next synchronization with the IMAP server put itself back into a consistent state.

This isn’t all though:

The backend connectors also saw some work:

The utility that allows to import/export the entire set of KDE PIM settings and associated data has received a large number of changes too, with Laurent fixing various import/export issues and improving the consistency and wording in the UI.

Take a look at some of the junior jobs that we have! They are simple, mostly programming tasks that don’t require any deep knowledge or understanding of Kontact, so anyone can work on them. Feel free to pick any task from the list and reach out to us! We’ll be happy to guide you and answer all your questions. Read more here…

Source: Volkerkrause.eu

Powered by NewsAPI.org

Keywords:

Kontact • It's My Turn (song) • Kontact • Kontact • Software repository • Email • Computer security • Privacy • Email • Kontact • KDE Frameworks • Kontact • QML • KDE Frameworks • Contact print • KDE Frameworks • VCard • Instant Messaging and Presence Protocol • Instant messaging • Akonadi • Software bug • Software bug • Software bug • Akonadi • Database • Internet Message Access Protocol • Synchronization • Akonadi • State (computer science) • Synchronization • Internet Message Access Protocol • Front and back ends • Kontact • Data • User interface • Computer programming • Kontact • Time management •