13:06:07 #startmeeting Fedora Workstation WG 13:06:07 Meeting started Mon Aug 5 13:06:07 2019 UTC. 13:06:07 This meeting is logged and archived in a public location. 13:06:07 The chair is mcatanzaro. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:06:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:06:07 The meeting name has been set to 'fedora_workstation_wg' 13:06:11 #meetingname workstation 13:06:11 The meeting name has been set to 'workstation' 13:06:15 #topic Roll call 13:06:20 .hello catanzaro 13:06:21 mcatanzaro: catanzaro 'Michael Catanzaro' 13:06:45 .hello chrismurphy 13:06:46 cmurf: chrismurphy 'Chris Murphy' 13:07:06 #chair cmurf petersen 13:07:06 Current chairs: cmurf mcatanzaro petersen 13:07:54 hmm maybe pre-Flock meeting ambitious 13:07:56 hi 13:08:02 .hello2 13:08:03 petersen: petersen 'Jens Petersen' 13:08:11 #chair cschalle otaylor 13:08:11 Current chairs: cmurf cschalle mcatanzaro otaylor petersen 13:08:14 #chair langdon 13:08:14 Current chairs: cmurf cschalle langdon mcatanzaro otaylor petersen 13:08:19 yeah, I am in the middle of getting my stuff together before being picked up for the airport after lunch 13:08:21 sorry i'm late, my system choked on an update 13:08:58 cschalle: Want me to keep running the meeting then, if you're busy? 13:09:13 mcatanzaro, if you can that be great 13:09:35 * otaylor is here now 13:09:39 .hello2 13:09:40 otaylor: otaylor 'Owen Taylor' 13:09:51 Yay, otaylor makes quorum 13:10:17 #topic Fill open WG slot 13:10:32 So we had two proposals at the last meeting 13:11:05 The proposal we first approved was to invite a bunch of people to this meeting and consider who shows up 13:11:11 I accepted an action item to send the invites 13:11:43 .hello2 13:11:44 langdon: langdon 'Langdon White' 13:11:57 sorry i am late... i thought we had canceled this meeting 13:12:05 Not cancelled :) 13:12:19 Then at towards end of the meeting I thought it would be rather unnecessary; it would make a sort of contest out of WG membership, which didn't seem desirable. And we had two strong candidates at the meeting already, aday and Son_Goku (Neal Gompa) 13:12:41 like cschalle, ill be a bit distracted getting ready for *my* flight this afternoon 13:12:44 So I offered another proposal to just accept those two instead, but we were out of time to discuss it. 13:14:18 I'm ready to +1 the proposal to accept both aday and ngompa 13:14:31 me too 13:15:08 cschalle, petersen, otaylor: Your opinions/votes? This would bring WG membership from 8 up to 10. (We've historically been 9.) 13:15:37 cmurf: Wouldn't be a bad idea to try summoning Son_Goku, since he knew we would be meeting today ;) 13:15:53 +1 from me to, I am good with adding both 13:15:54 I sent an email just a couple minutes ago. 13:16:25 mcatanzaro: +1 13:16:36 * cmurf isn't sure about the DiscordBridge 13:16:45 Other people are always welcome to join the meetings if they are interested of course 13:16:53 Of course. 13:17:07 cmurf: That DiscordBridge didn't work last week, all his comments from Discord arrived after the end of the meeting. 13:17:38 otaylor: A vote from you would be lovely. 13:17:51 i just pinged son_goku in another channel 13:17:57 Thanks! 13:18:00 #proposal Add Allan Day and Neal Gompa to WG membership 13:18:08 In reference to Son_Goku - I think he's generally a very knowledgeable and productive member of the Fedora community, but I want to put it out there, that I consider snaps in Fedora to be a distraction to what we are trying to achieve and do not want to see that made appear fuzzy 13:18:48 +1 to the proposal 13:19:02 thanks for having me! i hope that i can be useful 13:19:18 +1 13:19:29 So I guess I'm +1, but with the note that my vote for Son_Goku should be not seen as any sort of endorsement Snap support on the Workstation 13:19:31 .hello ngompa 13:19:32 King_InuYasha: ngompa 'Neal Gompa' 13:19:41 I agree and I assume he'll not try to change the direction of the WG regarding application containerization and flatpak. 13:19:49 * King_InuYasha shrugs 13:19:54 King_InuYasha: lol 13:20:09 Heh :) 13:20:12 #chair aday King_InuYasha 13:20:12 Current chairs: King_InuYasha aday cmurf cschalle langdon mcatanzaro otaylor petersen 13:20:24 King_InuYasha: Does your IRC nick change from week to week? ;) 13:20:32 nah, it changes based on what machine I'm using 13:20:43 haha 13:20:46 I'm at home today preparing for heading to Flock, so I can use my home desktop 13:21:03 I fly out tomorrow evening US/EDT, so.. 13:21:55 Ah multiple people sending multiple +1s during a vote is confusing. :P I think we're still missing langdon 13:22:21 Oh he said "me too" 13:22:31 That counts I think :) 13:22:34 #agreed Add Allan Day and Neal Gompa to WG membership (+6, 0, -0) 13:22:38 :D 13:22:42 #action mcatanzaro to update WG membership page 13:23:05 mcatanzaro: ha.. i was waiting to "+1" for a "vote".. just indicating I was ready to vote :) 13:23:11 so.. for the record "+1" 13:23:19 #topic New quorum size 13:23:37 ah good. that was going to be my next question :) 13:23:38 So is our quorum still 5 or will we require 6 now? Any preferences? 13:24:37 I think it needs to be 6, practically speaking 13:24:52 but also I think proxy votes should be possible 13:25:26 I think it needs to be 6 ... votes on tickets can be counted ,of course, not sure about proxy votes :-) 13:25:52 So better to increase to 11 hehe 13:25:54 I'd consider a vote in ticket to be a kind of proxy. 13:26:05 We have 8/10 members here atm which is quite good for us historically. In the past, we've had a lot of trouble meeting quorum. So please just try to attend whenever possible so we can hit 6! 13:26:25 Yes 13:26:44 note that 9am US/ET is early for me, so if someone just pings me, I can make sure to get in 13:27:00 I mean we'd want more than 3-4 votes in favor of something no matter what. 13:27:09 sure 13:27:16 that's of course, in case I forget to actually be here already ;) 13:27:16 aday, King_InuYasha: If you have user pages on the Fedora wiki, please let me know so I can link to it from https://fedoraproject.org/wiki/Workstation 13:27:34 mcatanzaro: https://fedoraproject.org/wiki/User:Ngompa 13:27:55 mcatanzaro: i'll add one 13:27:56 it's not as fancy as some of the other folks... 13:27:57 FWIW I set my alarm on Mondays since otherwise I too would often miss 13:28:06 mcatanzaro: that's a good idea 13:28:50 OK, going down the issue list 13:29:05 #agreed Quorum size is increased to 6 13:29:08 #topic Better interactivity in low-memory situations 13:29:12 cmurf: Your show 13:29:46 Updates are in the ticket for now. There's not much new to report on this. 13:30:22 The systemd upstream rust based swap on zram generator is broken, so I need to go on a recruitment drive perhaps. 13:30:36 Find someone who wants to dabble in rust and systemd generators. 13:30:46 oh 13:30:50 so it is not going to make F31? 13:31:32 rust is not fun :( 13:31:41 petersen: unlikely 13:32:14 King_InuYasha: depends on your definition of fun :) 13:32:18 But in the ticket we discussed pushing this to Fedora 32 anyway, because it touches enough things that we probably should go through the change process. 13:32:26 okay 13:32:30 And we're past changes for Fedora 31. 13:32:40 petersen: beating my head into the ground with a language that has not good ergonomics sucks 13:32:40 cmurf: Remove meeting tag for now? 13:33:06 mcatanzaro: yes please 13:33:28 cmurf: OK to move on to next topic? 13:33:31 yes 13:34:04 cmurf: i assume some coordination between relevant parties would need to happen if/when you've found someone to work on it? 13:34:27 aday: correct, including a discussion on how to handle upgrades 13:34:51 lotsa little ducks to put in a row 13:35:02 zeenix likes rust :) 13:35:14 hey, so does aruiz 13:35:51 Worst case, rewriting in C seems plausible if there's not enough interest from Rust devs? 13:35:53 I'll inquire 13:36:01 Anyway 13:36:16 #topic Automatically install the OpenH264 codecs 13:36:17 mcatanzaro: systemd devs weren't in favor of using C for any generators going forward is my (possibly flawed) understanding 13:36:59 cschalle are you still around to give an update on this? Last update we have from kalev (missing today) is that the package is blocked on Fedora releng 13:38:54 I think cschalle is probably running to his plane :) 13:39:05 Last topic for today: 13:39:11 #topic LUKS by default 13:40:14 So our last action item here was for otaylor to form a WG subgroup to look into this issue and report back to the main WG... last December. I understand that hasn't quite happened. :) 13:40:40 I'll join that subgroup, I'm familiar with most of the issues. 13:40:48 there's no subgroup :-) 13:40:58 there's two :-D 13:42:27 I think two is sufficient to report back to the WG with a recommendation 13:42:42 does LUKS by default mean Fedora does FDE by default? 13:42:46 That's the goal 13:42:47 err Workstation 13:42:52 King_InuYasha: multiple possibilities 13:43:14 could mean FDE, could mean /home only, could mean per user ext4 based file system encryption using the VFS interface 13:43:16 blah blah blah 13:43:43 i agree with aruiz that the goal is "better protect user data" rather than a specific technological solution 13:43:52 yep 13:43:59 my understanding was that the subgroup was going to evaluate the options and report back 13:44:05 Well that goal is only plausibly going to be met by LUKS, of course 13:44:14 cmurf: genrerally, talk to aruiz about what he thinks the path forward should be - I'm a bit skeptical but since he leads the team that does our early boot, need to coordinate with him :-) 13:44:42 otaylor: which part are you skeptical about? 13:44:44 I am not necessarily claiming to know what the final solution should be 13:44:45 There was back and forth about this, pjones for sure, maybe aruiz, on one of the lists. 13:44:46 I do think that the subgroup purpose was intended to be "figure out how to protect data by default" 13:45:00 Their work was predicated on LUKS2 which itself requires TPM 2.0 13:45:16 I am mostly against the password by default because I've seen how much damage that setup makes to users in real life deployments 13:45:30 and also how people actually disable it because of how inconvenient it is 13:45:43 Agreed 13:45:51 aday: I am skeptical about making all home directories loopback mounts - a developer basically needs a large home directory which is the most performance sensitive thing, and a thin OS around it 13:45:53 having a list of these common issues would be a good thing to have 13:46:01 things like keyboard layout mismatches between vconsole.conf and the graphical session, having to remember two passwords, handling a recovery.... 13:46:04 if we could have a design page or document... 13:46:36 Fortunately this conversation is being recorded... ;-) 13:46:36 otaylor, ah i see. thanks 13:46:39 my take is that we should encrypt just /home/user for now using ext4 and then explore more generic options 13:47:10 I have personal experience with how bad loopback mounts everywhere are 13:47:18 aruiz: that does come with several advantages, easy to undo, easy to ugprade in place, easy to do for installations 13:47:28 after developing many systems that abused loops, I don't really think they're a good system for anything 13:47:40 King_InuYasha, I am not necessarily saying with loopback mounts, I mean online ext4 encryption 13:47:41 King_InuYasha: great for testing! 13:47:47 My original expectation when the WG originally approved LUKS by default was that we'd just flip the default value of the checkbox in anaconda and move on. I wasn't expecting it to be controversial. But the objection from aruiz is input methods are not available in plymouth for typing likely passwords in non-Latin locales. I don't see how doing LUKS without any password at all would be beneficial, and we already have it hooked up to skip gdm 13:47:50 so two passwords shouldn't be an issue, can just use the same password for both. But there are many warts here, many stars have to align for this to work as we desire (e.g. user enters exactly the same password in both anaconda and gnome-initial-setup and then never changes keyboard layout later...) so I certainly agree there are many warts here.... 13:47:54 Oops, that was long 13:48:05 aday: I'm also skeptical about the LUKS2 / TPM 2.0 stuff - busted motherboard should not cause data loss, IMO 13:48:22 Also aruiz joined halfway through my writing that essay :D 13:48:25 oh yay, busted motherboards, I didn't even think of that 13:48:30 otaylor, I have my issues with that too 13:48:32 that would be horrifying 13:48:46 aday: So i don't think you can encrypt passwordless without having a recovery password and some mechanism where the user actually will have the recovery password when they need it 13:48:59 otaylor, that was more of a compromise if we really wanted to encrypt the whole of "/" 13:49:19 i'm not sure we're going to solve this here with 10 minutes to go :) 13:49:41 aday: We're not, but there's nothing else on the agenda ;) 13:49:50 but we have the subgroup! 13:50:09 cmurf: can you provide details of that? 13:50:10 otaylor: cmurf: aruiz: aday: 13:50:34 i would like to clarify that I am confused about the meeting schedule.. i thought we were off today .. so if we want to touch on that topic briefly before the end... 13:51:19 langdon: the change was voted on end of last minute and the calendar updated; to bypass conflicts with Flock and something else I can't remember. 13:51:26 So we're off next week. 13:51:40 langdon: Last week we agreed to shift the usual meeting schedule forward by one week. So yes, off next week, next meeting Aug 19 13:51:43 hmm .. ok.. weird.. i usually update my calendar and seem to have the the opposite 13:52:04 alright.. ill just chalk it up to i am bad at calendars 13:52:19 cmurf: guadec 13:52:27 https://apps.fedoraproject.org/calendar/workstation/ is updated 13:52:29 I don't think the Fedora calendar automatically updates e.g. Google calendar, at least mine didn't 13:52:37 perhaps we should focus on the process for figuring this out? do we need to set up a call between the interested parties? 13:52:43 i'm not sure that it's a URL based calendar rather than having to manually import the .ics 13:52:46 Mine did 13:53:19 yeah.. i have never had the ics update gcal.. but maybe it got better? 13:53:42 "perhaps we should focus on the process for figuring this out?" indeed, having a subgroup still sounds like a good idea to me. 13:54:09 aday: +1 13:54:21 Volunteers to join cmurf? (aday? aruiz? otaylor?) 13:54:35 i'd be interested from a ux perspective 13:54:41 I am up to cotribute as well as involving other people, namely gicmo and hansdg 13:54:57 I'll do a summary/organize the issues and points and concerns in this meeting, post to desktop@ 13:54:58 I don't think we need to decide in the next 5m how you'll meet, we can just agree that you will coordinate among yourselves to schedule some meetings somehow and discuss 13:55:00 My main interest is the keyboard layouts issue 13:55:05 aruiz: sounds great 13:55:08 cmurf: I can join, but not lead, but the caveat on that is that I'm out from mid-august to mid-september, and I'd suggest just proceeding without me while I'm gone 13:55:11 refine that, then setup a live voice meeting 13:55:13 gicmo, I was not aware of my summoning powers 13:55:13 Keyboard layouts seem like the biggest problem 13:55:21 Been meaning to discuss that with aruiz for some time 13:55:34 aruiz: heh ;) 13:55:39 mcatanzaro: it'd be good to have someone take the lead, at least in organising the call 13:55:47 mcatanzaro: make a proposal that the subgroup has been formed and will report to the WG regularly 13:56:09 cmurf: You have the power, use #agreed :) 13:56:13 cmurf to lead subgroup... 13:57:04 #agreed cmurf to lead subgroup to explore ways of better safeguarding user data by default 13:57:24 ack nack patch? 13:57:31 petersen, o/ 13:57:32 +1 13:57:35 +1 13:57:39 +1 13:57:49 +1 13:57:56 though it says agreed hehe 13:58:14 we'll take that as a combined proposal and agreed I guess :D 13:58:22 yes 13:58:23 cmurf: I'd be interested in attending at least the first meeting as well 13:58:57 sort out the details on desktop@ and fedora-workstation? 13:59:16 Sounds good 13:59:48 I can also update the ticket 14:00:05 This is a tricky problem of balancing security and usability and it's important that we get the balance to the best point we practically can. That might have to mean some difficult compromises.... 14:00:22 Anyway, that's time 14:00:30 Next meeting: Aug 19 14:00:37 Thanks cmurf for leading! 14:00:39 #endmeeting