New framework: KContacts

[Volker Krause]

On Saturday, 6 April 2019 18:01:09 CEST Volker Krause wrote:
> Hi,
> 
> I'd like to propose KContacts for review to move from KDE PIM to KF5.
> 
> KContacts is essentially an implementation of the vCard standard, covering
> the data model as well as parsing and creating of vCard files. As the
> recent CI issue showed it's used outside of KDE PIM as well, therefore we
> would particularly benefit from the KF5 stability guarantees.
> 
> KContacts depends on KConfig, KCodecs, KCoreAddons and KI18n, making it a
> Tier 2 functional framework.
> 
> KContacts used to be part of kdelibs during the 2 and 3 era under the name
> "kabc", and part of kdepimlibs in the 4 era, so it's very well prepared for
> complying with the API and ABI guarantees.
> 
> To have a smooth as possible transition the proposed timeline would be:
> - complete the review and possibly required adjustments before the 19.08
> freeze
> - do one final release as part of KDE PIM with 19.08, with the final ABI and
> library name for KF5
> - after 19.08 (so Sep or Oct 2019), release it with KF5, which will then be
> a drop-in replacement for the KDE PIM release.
> 
> This approach has already successfully been used for KHolidays and
> Syndication.
> 
> We did a review at the currently ongoing PIM sprint, which resulted in
> removal of some ancient unused cruft (D20270, D20273, D20274, D20275,
> D20276) which did technically change the ABI, therefore the transition
> after 19.08 rather than 19.04.

With the 19.08 deadline approaching I'd also like to raise this again for a 
decision :)

I'm not aware of any unaddressed feedback, main changes in the meantime:
- a number of duplicated or string-based code in applications using this was 
upstreamed into KContacts with proper API
- several types got Q_GADGET/Q_PROPERTY annotations for direct use in QML or 
Grantlee (now used directly by KAddressBook's display and printing code)
- custom fields for messaging addresses are now converted to standard Impp 
fields, improving e.g. compatibility with Nextcloud and removing error-prone 
application code

Thanks,
Volker

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20190716/c96d4fbe/attachment.sig>