11:53:38 #startmeeting Workstation WG (2020-03-17) 11:53:38 Meeting started Tue Mar 24 11:53:38 2020 UTC. 11:53:38 This meeting is logged and archived in a public location. 11:53:38 The chair is aday. Information about MeetBot at http://wiki.debian.org/MeetBot. 11:53:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 11:53:38 The meeting name has been set to 'workstation_wg_(2020-03-17)' 11:53:38 #meetingname workstation 11:53:38 The meeting name has been set to 'workstation' 11:53:38 #chair cmurf 11:53:38 Current chairs: aday cmurf 11:53:38 11:53:38 #topic Rollcall 11:53:38 11:53:40 #info present: Michael, Chris, Jens, Kalev, Matthias, Neal, Tomas, Langdon (joined later). Guests: Benjamin Berg, Felipe Borges, Matthew Miller 11:53:43 #info regrets: Allan 11:53:45 #info missing: 11:53:47 11:53:49 #topic Defer approval of minutes to next week 11:53:51 #link https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-03-12-18.24.html 11:53:53 11:53:55 #topic Announcements 11:53:59 11:54:01 #info Fedora 32 beta is out! 11:54:03 #info WG discusses multimedia codecs. 11:54:05 #info Kalev produced another YouTube video that has attracted some positive attention. 11:54:07 11:54:09 #topic Reconsider updates policy 11:54:11 #info https://pagure.io/fedora-workstation/issue/107 11:54:13 Michael: Summary. Weekly or bi-weekly prefered. Notification to be based on urgent severity as set in Bodhi. It applies all other available updates at the same time as urgent. Needs coordination to let maintainers know that urgent severity will cause reboot. 11:54:17 #info Regular updates every 1-2 weeks, urgent updates on demand and hopefully not often 11:54:19 Matthew: I agree. Even if there isn't a central means of deciding urgency, there should be a FESCo policy defining "urgent". 11:54:22 #info request FESCo establish a policy/definition around what is "urgent" 11:54:24 Kalev: I have ideas on how server side batching could work: two updates repositories, daily and two-week 11:54:29 Multiple persons: Can we make existing 'updates-testing' the daily, and existing 'updates' the two-week? 11:54:32 Neal: I don't think server side batching solves anything. 11:54:34 Kalev: Purpose is to QA the updates. 11:54:36 Matthew: History is QA was against it because no one has time for it. But the proposal is a step forward, perception is Fedora is unstable due to all of the updates. 11:54:39 Neal: Does merely a two week delay, that then has a ton of updates, address that perception? 11:54:41 Matthew: Yes it helps. 11:54:43 Mattias: Flatpaks also helps solve the problem, they can be update at any time without interrupting the user or requiring reboot. 11:54:46 Matthew: That's a good story too. 11:54:48 11:54:50 #topic Status update: should we enable thermald by default? 11:54:52 #info https://pagure.io/fedora-workstation/issue/71 11:54:54 Benjamin: Summary: helps mostly laptops, not much for desktops. Requires a non-free component in RPM Fusion 'dptfxtract'. Infrastructure complication whether/how to process ACPI dump to produce a configuration without 'dptfxtract'. User space daemon is more effective than depending on the kernel or firmware, it can take load into account to preemptively apply mitigation rather than waiting for temperature triggers being tripped. 11:55:01 #info dptfxtract processes raw ACPI data into a configuration file that thermald uses 11:55:03 Neal: No. Not sustainable. 11:55:05 Benjamin: Leaves ~40% of battery life on the table. 11:55:07 Chris: Difficult problem, also relates to Broadcom issue. 11:55:09 Various: And Nvidia. 11:55:11 Neal: Problem is no one cares enough to put the effort into solving it. 11:55:13 Michael: I didn't know the issues enough until now to care. 11:55:15 #info Thermald by default? WG is "no" as described, due to non-free dptfxtract, but is willing to explore alternatives 11:55:18 #action cmurf to start a discussion on 01.org 11:55:20 #action need a volunteer to start a discussion on devel@ about shipping+maintaining configuration files 11:55:23 11:55:25 #topic automatically adding new packages when upgrading 11:55:29 #info https://pagure.io/fedora-workstation/issue/138 11:55:31 cmurf: Summary. Sanity check if I'm confused, and if not is it a bigger problem in the general case? 11:55:34 Neal and Kalev: It should be possible. Sounds like a dnf bug. Workaround using weak dependencies: supplements. 11:55:37 #action cmurf to file a dnf bug 11:55:39 #action Neal to followup with Daniel Mach to confirm/deny whether this is a bug 11:55:41 11:55:43 #endmeeting