A few months ago, @ngraham announced the creation of the "Sponsored Work" category for trying to fund efforts to fix bugs and implement features on his blog.
While Fedora KDE does not have any money to give organizationally to KDE to fix issues, individual members of the SIG may have money to spare. In that respect, we should try to identify gaps to close that we'd like to fund, then come up with a pool of money for this and make offers accordingly.
cc: @mattdm
As an example, I've personally thrown money into the pot for mouse/trackpad/touchscreen gesture support for Plasma Wayland.
I donate directly to KDE to support them generally. I'm not sure that I have the kind of funds to dedicate to specific issues that generally require a larger sum to get the attention of a developer to fix.
I do as well, but we do have a fair number of members in the SIG and if we can collect some issues we would like to have KDE upstream prioritize, we can come up with a way to fund that.
Ah OK sounds good.
As the Sig discusses what it would look like to become a Personal Systems Working Group, it seems like restarting this discussion would be valuable for the items that need to be punted upstream for development work.
The logistics of how to pool funds still needs to be discussed. It sounds like for this to function, there would need to be a treasurer of some sort in the KDE Sig and probably a 2-person sign off for disbursement. It could potentially be done with a LiberaPay but something more akin to OpenCollective would provide more transparency.
Funding development work for Plasma Mobile would help with usability gap closures. Would the Sig still like to pursue this?
cc: @ngompa
Based on my first look at OpenCollective, it would make sense to create a Fedora KDE Community Collective. This would allow for continuity in the event that someone needs to step down in the Sig or treasurer positions need to change. The ideal thing would be to have either Red Hat or Fedora create a Fiscal Host that other Fedora Sigs could be collectives under. Fedora Mindshare would probably be best equipped to handle that.
I haven't been able to determine if the community collective is required to have a fiscal host or not. If it isn't required, then this would probably be a better option over LiberaPay. LiberaPay distributes immediately to individuals as a part of a team so it doesn't actually pool funds together. This would create a bus factor issue and potential opportunities for abuse. If a community collective does require a fiscal host, the best thing would be to petition Fedora Council for creating a Fiscal host on OpenCollective with Red Hat's approval.
There are multiple Red Hat organizations on Open Collective which is a bit weird. My guess is that each organization has been created as needed by individuals at Red Hat for distributing funds to open source projects. This, in my opinion, is sub-optimal. There should probably be a singular Red Hat organization that distribution is funneled through. Perhaps that would be something for @mattdm or @jflory7 to look at or bring up to Red Hat?
If that part isn't feasible, attempting to get squared away as an Open Source Adjacent Community with Open Source Collective as a Fiscal Host might be possible.
Open Source Adjacent Community
Metadata Update from @ngompa: - Issue tagged with: meeting
This was discussed in Sig meeting on 05/20/2024. @ngompa stated that there are some things moving in the background that are vaguely positive but that can't be discussed at the moment. In the meantime, this ticket will be used to aggregate desired upstream development efforts from the sig members.
One of the items discussed by @marcdeop @farchord and @ngompa is Group Policy Objects which would be of use to enterprise desktop customers. This would be useful for the eventual Cloud VDI Edition proposed as a part of the Personal Systems Working Group.
Another feature I'd really like us to push through is OEM mode for KDE.
To clarify for those who don't know what that is, think the "After setup" wizard gnome gets in Fedora Workstation, where you create your user and setup your interface for first use.
In the Windows world, they call that an OOBE (Out Of Box Experience).
I trudged through the open issues on here to see what previously mentioned upstream work was needed. These are probably lower hanging fruit than the larger funding efforts:
kvkbd
org.freedesktop.locale1
maliit-keyboard
Adding this as another thing to potentially fund:
I'd also suggest the following: - Neochat - Adding Jitsi Support or Element Call / Voip support since this currently requires switching to Element for some Fedora Meetings
That would be nice, though everytime I try Neochat, I get stung. Something always just goes badly that makes me go back to element
Metadata Update from @ngompa: - Issue untagged with: meeting
firewalld
plasma-firewall
https://pagure.io/fedora-kde/SIG/issue/501 porting of maliit-keyboard to qt6
there were discussions on KDE mailing lists about developing an alternative QtVirtualKeyboard, not sure if it's relevant but https://mail.kde.org/pipermail/plasma-devel/2024-June/123435.html