* https://phabricator.kde.org/T13056: Technically not a KF task, and solved itself by moving away from KAboutData.
* https://phabricator.kde.org/T14564: There are a number of good reasons to consistently use JSON files, desktop files for editing might be nicer, but those files are rarely edited and mainly contain scripty generated content. * https://invent.kde.org/network/kio-extras/-/merge_requests/114#note_278244 (thumbnailer configuration): Use-cases of the existing settings seem dubious to begin with (see e.g. https://bugs.kde.org/show_bug.cgi?id=238618 ) Reading the config should be kept for now, but the GUI options can be removed. * https://phabricator.kde.org/T14330: Do we need a dedicated KCM launcher job? Mostly a UX problem and needing input from UX people. * Do we still need to install the service type files for KCMs? Those are needed for KServiceTypeTrader use, but that's only relevant for 3rd parties at this point, if at all. * https://phabricator.kde.org/T12180, https://phabricator.kde.org/T12191: Duplicates, widget dependency removal can only be done for KF6, KHotKeys removal is a Plasma rather than a KF6 task.
signature.asc
Description: This is a digitally signed message part.
