17:12:05 <brainycmurf> #startmeeting Workstation WG (2023-01-31)
17:12:05 <zodbot> Meeting started Tue Jan 31 17:12:05 2023 UTC.
17:12:05 <zodbot> This meeting is logged and archived in a public location.
17:12:05 <zodbot> The chair is brainycmurf. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
17:12:05 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:12:05 <zodbot> The meeting name has been set to 'workstation_wg_(2023-01-31)'
17:12:05 <brainycmurf> #meetingname workstation
17:12:05 <brainycmurf> #chair Michael
17:12:05 <zodbot> The meeting name has been set to 'workstation'
17:12:05 <zodbot> Current chairs: Michael brainycmurf
17:12:17 <brainycmurf> #info Present members: Michael, Owen, Kalev, Allan, Chris, Neal
17:12:17 <brainycmurf> #info Guests: Jonathan, Justin
17:12:17 <brainycmurf> #info Regrets: Matthias, Jens, Tomas
17:12:17 <brainycmurf> #info Secretary: Owen
17:12:17 <brainycmurf> #topic Fedora doesn't have kernel parameters for enabling IOMMU
17:12:18 <brainycmurf> #link https://pagure.io/fedora-workstation/issue/346
17:12:20 <brainycmurf> - If not enabled, thunderbolt devices can overwrite any memory
17:12:22 <brainycmurf> - On older hardware, enabling this causes breakage
17:12:24 <brainycmurf> - mcantanza Can we detect broken hardware and create a deny lists
17:12:26 <brainycmurf> - otaylor Can we base off age of hardware?
17:12:28 <brainycmurf> - Justin: either requires research and getting hardware upstream
17:12:30 <brainycmurf> - Seems to be o for *some* intel machines even when CONFIG_INTEL_IIOMU_DEFAULT_ON is false
17:12:34 <brainycmurf> - what is the user interface when you plug in a thunderbolt device? Could it be malicious without us noticing?
17:12:37 <brainycmurf> - mcantanzaro: proposes we close the issue, since we aren't going to do the work to fix it - no objections
17:12:40 <brainycmurf> #topic Reconsider scope of Fedora Flatpaks
17:12:42 <brainycmurf> #link https://pagure.io/fedora-workstation/issue/352
17:12:44 <brainycmurf> - owen: we should keep it going because we strongly believe in Flatpaks as the path going forward, and given current constraints, we don't have a story for Fedora contributors about how they can keep maintaining their applications if the only source of Flatpaks is Flathub..
17:12:48 <brainycmurf> - mcantanzaro: situation has changed in his perspective because  of the existence of the Fedora Flatpaks sig
17:12:51 <brainycmurf> - aday: if there are issues with Fedora Flatpaks - in terms of quality - we should keep track of those issue - we need a place
17:12:54 <brainycmurf> - owen: we can have a place to track Fedora flatpak for a) WG b) Flatpak SIG but can't expect end-uses to report issues there
17:12:57 <brainycmurf> - action: close ticket that we're not going to reconsider the scope, but will encourage Flatpak SIG to track issues better
17:13:00 <brainycmurf> #topic Mouse acceleration options are unavailable
17:13:04 <brainycmurf> #link https://pagure.io/fedora-workstation/issue/354
17:13:06 <brainycmurf> - aday: think this can be done upstream possibly even by the next release - there is an upstream PR that aday doesn't object to in principle. UI freeze is in about a week
17:13:09 <brainycmurf> #topic Announcements and status updates
17:13:11 <brainycmurf> Some progress has been made on the next boot design
17:13:13 <brainycmurf> #link https://pagure.io/fedora-workstation/issue/278
17:13:15 <brainycmurf> #info The minutes from the previous meeting have been posted.
17:13:17 <brainycmurf> #link https://meetbot.fedoraproject.org/fedora-meeting-2/2023-01-30/workstation.2023-01-30-20.00.log.html
17:13:20 <brainycmurf> #endmeeting