In https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/374#note_745927, @krop comments:

Although technically correct, I'm not particularly happy to see ui files being installed in XDG_CONFIG_DIR by default. There's nothing a system administrator should touch. I'm not convinced that's the right move.

Updated functionality:

• MR "KDE_INSTALL_KXMLGUIDIR: undocument and prepare remove for 6.0 "
• MR "Use GenericConfigLocation to read & write ui.rc files (w/ migration class)"

Found that AppConfigLocation actualy cannot be directly used, as plugins have their separate component name to use in place of the appname. So sticked with GenericConfigLocation/cpmonentName, which though is pretty the same as AppConfigLocation for apps anyway.

Thanks for the input, good to have :)

@dfaure Any chance on your "old-timer knowledge" on the question whether to keep using "kxmlgui5/APP" (i.e. GenericConfigLocation/ConfigLocation) or to instead switch to "APP/xmlgui5" (i.e. AppConfigLocation)?

Proposed implementation:

In T15987#296059, @kossebau wrote:

Anyone of you into Windows and could do the Windows trash worker variant?

@sitter @meven @nicolasfella Hi. Anyone of you into Windows and could do the Windows trash worker variant?

Created respective subtasks for it (and did some MRs for info & about)

We won't be supporting stable-kf6-qt6 until that is a thing, but kf6-qt6 can be supported.

This is the most advanced worker, it makes sense to pay extra care to it.

Why not do the same here? KF6-kio copies kioslaverc to kioworkerrc, once, if kioworkerrc doesn't exist yet. Later changes to kioslaverc (which only happen if someone is running a mixed environment) are ignored by KF6-based apps.

Looking at how this was approached for kdelibs4 parallel to KF5, I could not find any config file sync code though. Or migration code. Given kdelibs4 config files were located in the KDE-specific folders, where KF5 had switched to XDG folders, such synchronizing would have been needed.

In T16013#284330, @usta wrote:

I dont know if have any vote right but if i had my vote goes to "master"

In T16013#284327, @ngraham wrote:

switching the default branch name to "main"

Support both names

https://invent.kde.org/frameworks/baloo/-/merge_requests/99

https://bugs.kde.org/describecomponents.cgi?product=frameworks-ktexttemplate is now available.

https://invent.kde.org/frameworks/kio/-/merge_requests/1052 is up (myself will see to review this WE)

In T15976#283926, @dfaure wrote:

Oh, OK, the name will be right at some point, so, sure, call it that way.

@dfaure But meh, I would have though you are in that loop :) Seems people missed to communicate as needed?

The name seems wrong to me, it's not part of KF5.

If no-one has objections or has other ideas, would then go upcoming WE Nov 19/20 and create such product "frameworks-ktexttemplate", with the usual "general" component, using kdelibs-bugs as default assignee for the start.
IIRC I still have respective bko karma to execute such creation myself, so no other help needed :)

@sitter Any honey we can put on this to attract you? :)