KF6 meeting notes 2021-05-01

[Luigi Toscano]

Hi all,

as suggested it would be wise to send some reminders before the meeting.
Also, it has been pointed out not everyone may attend on Saturday - but on the
other hand it may be difficult to find another slot.

Anyway, here are the notes:

---

- https://phabricator.kde.org/T12542 "Fix circular dependency of
applications.menu in KService and plasma-workspace"

Problem: where to move the applications.menu file to remove the dependency
Probably David F. will discuss with David E. about this (clear problem, yet
unclear solution).


- https://phabricator.kde.org/T12056 "KBookmarks"

Why is it still in needinput?
Most of the major tasks done, maybe some minor cleanup is possible.
Should we split it between a core and widget library? Maybe it makes sense
only if some QML stuff is going to use it.
Does it need a rewrite? Probably just an internal implementation problem
(apart from protected some virtual methods which affects the API).
-> waiting for branching


- Question about https://phabricator.kde.org/T12256 "Phase out
KonqPopupMenu/Plugin service type".

It seems KServiceTypeTrader may be still useful.
Related XDG discussion on standard dbus interface to open a terminal and run
commands. This brings the issue on how to select the implementation. The
proposed solution (for now called "intents") looks similar to the idea of
service types.
This will bring something akin to KServiceTypeTraders.
We may just still deprecate it and port it to an intent, which may be
KDE-specific, but still.

(and then discussion delved into porting implementation details, including
https://invent.kde.org/frameworks/kio/-/merge_requests/429 )


- https://phabricator.kde.org/T12214 "Move KIOWorkers into a thread of the
calling application instead of separate process"

It would require changes of the scheduler, the question is whether this can be
done later/anytime or it would impact the API.
People pointed out there may be a risk of crashing the entire application if
something misbehaves. Maybe not a big increase in performance.
The main use case is bundled deployment (Android, Windows) where you are not
supposed to launch additional processes or there is troubles.
On Windows it work if you run the other processes as subprocesses, but not on
Android.
This is of course a problem with other type of processes too, for example the
password server - without a separate process for the password server you would
be prompted again for a password when running another process. But you could
store that in QtKeychain, but that doesn't work if the password doesn't need
or want to be stored permanently on file.
It needs more investigation.


A question was asked on how to contribute a bug fix for
https://bugs.kde.org/show_bug.cgi?id=433804. This is about file system
detection in ksysguard (so Plasma), but actually it may be interesting for
Frameworks too as there is some (duplicate?) code to detect the file system
type. So maybe there is space for some cleanup.


Ciao
-- 
Luigi