Plasma Mobile BoF recap at Akademy

[Devin]

Summary of BoF:

Plasma Mobile Gear
- Some applications can possibly be moved to KDE Gear (ex. Calindori,
Kongress) since they are not changing very much
- Appstream release information can just link to the blog post rather
than messing with an actual changelog for each project
- Bhushan create a gitlab issue for every release, so we can help out
with tasks left to do

QtFeedback
- Not maintained, Jonah forked it a while ago and had some work in
porting it to Qt 6
- Does the QtFeedback API make sense for KDE apps to use directly, it
probably should be in KNotifications/included in the style
- If non-Qt apps wanted to do vibrations, they'd need to communicate
directly to hfd-service (QtFeedback is a Qt library)
- Moving to feedbackd backend from hfd-service? Haptics backend would
be shared with GNOME and includes support for per-device
configurations, LED + sound theme integration;
    - While consensus was reached in-person, it was hard to hear
between online and in-person attendees, possibly needs further meeting
due to opposition

kirigami-addons
- Not in KDEReview anymore, hurray!
- Not scalable to keep alongside Plasma Mobile Gear release schedule
- Do big release changes for KF6, not within KF5 period

Plasma 6 (Plasma Mobile 6)
- Plan is one last release of Plasma (5.27), before branches are made
for Plasma 6
- No large changes anticipated, testing can begin once Plasma 5.27 is
released and we can run the QML conversion script

Hardware Vendors
- SHIFTphones and Fairphone can run pmOS with Plasma Mobile, perhaps
we can open communication channels with them?
- Manjaro was working with 2 tablet (?) vendors, they have positive
reception and had a few suggestions