<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi all,</div>
<div> </div>
<div>here are the notes from the KF6 weekly.</div>
<div> </div>
<div>Regards<br/>
Alexander</div>
<div> </div>
<div>https://phabricator.kde.org/T12176:</div>
<div>If a usecase comes up one could think if implementing a cross-platform autostart API. In its current state & the current usages it should be deprecated. The needed logic should be imported in plasma-workspace; where the actual autostarting is done and the autostart KCM is.</div>
<div><br/>
https://phabricator.kde.org/T14314:</div>
<div>Question about how logging should be handled: KCoreAddons should provide both translated and untranslated error strings for the API users. Like the KJob error handling with the errorString and errorText.</div>
<div>The critical error should also be logged by kcoreaddons.</div>
<div>See https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/106 for the Merge Request.</div>
<div> </div>
<div>https://phabricator.kde.org/T14744:</div>
<div>The keyword stuff is not really needed and should be deprecated. Multiple plugins can be loaded without it being involved, if the classes are different. That is in most of the current usages the case. The KCMs in kinfocenter should be ported to KPluginMetaData and will not need the keyword stuff afterwards. See https://phabricator.kde.org/T14517.</div>
<div>The X-KDE-KCM-Args property might help with the KWin usages. But it needs to be read from the plugin which has the config modules, not the config module itself. </div>
<div><br/>
Frederik has been working on the API documentation, https://phabricator.kde.org/T12004. See https://invent.kde.org/frameworks/kapidox/-/merge_requests/20 for a draft MR about making kapidox run in a docker container.</div>
<div> </div>
<div> </div></div></body></html>