16:02:42 #startmeeting Fedora Sway SIG (2023-01-16) 16:02:42 Meeting started Mon Jan 16 16:02:42 2023 UTC. 16:02:42 This meeting is logged and archived in a public location. 16:02:42 The chair is alebastr[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:02:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:42 The meeting name has been set to 'fedora_sway_sig_(2023-01-16)' 16:03:44 oh. there's a huge lag on the irc bridge, so bot responses will be delayed 16:03:44 .hello jkonecny 16:03:45 jkonecny[m]: Something blew up, please try again 16:03:48 jkonecny[m]: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:03:49 .hello alebastr 16:03:52 .hello anthr76 16:03:54 alebastr[m]: Something blew up, please try again 16:03:57 alebastr[m]: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:04:00 anthr76[m]: Something blew up, please try again 16:04:02 .hello fale 16:04:04 anthr76[m]: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:04:07 Fale[m]: Something blew up, please try again 16:04:09 Fale[m]: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:06:27 #topic Spin development progress 16:07:01 the bot is not healthy, but there's nothing we can fix :) 16:07:32 #info comps Pr is merged: https://pagure.io/fedora-comps/pull-request/781 16:07:54 #info KS PR is merged: https://pagure.io/fedora-kickstarts/pull-request/924 16:07:54 This is awesome news! 16:08:04 so we got everything except workstation-ostree-config merged. I'll ping travier about that later :) 16:08:21 after checking if it builds on rawhide 16:08:31 alebastr[m]: Is anything actionable on our side? Besides maybe CI in the future? 16:08:50 we still need to also work on documentation 16:08:59 and tests 16:09:07 * Fale[m] will try next weekend to work on the documentation 16:09:12 and actually test the stuff :) 16:09:24 By tests do you mean openQA? 16:09:46 * alebastr[m] still suspects that the live images will get a broken installation because of missing xorg drivers and sddm-x11 16:10:04 WIP: https://pagure.io/fedora-kickstarts/pull-request/932# 16:10:20 some small change is required 16:10:30 anthr76[m]: yep, openqa 16:11:34 alebastr: how this is handled. Do Fedora QE helps with the tests or it's on us to implement them? 16:13:13 I'm sure Adam will be able to help with some stuff. I don't think QA has a lot of free time to implement our tests though 16:15:44 I think looking to see how it's done with i3 and trying to adapt is a decent start 16:16:17 definitely 16:16:37 BTW do we already have an Fedora builds? 16:16:47 if not I'm not sure the OpenQA will work 16:17:00 not sure how much it's linked to the fedora repositories only 16:17:05 s/repositories/infra/ 16:17:05 I think we should if KS was merged.. 16:17:26 Actually, I don't see any spins running in openqa: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20230114.n.0&groupid=1 16:17:50 I see "Flavor: KDE-live-iso" 16:18:07 Maybe it's optional? 16:18:44 oh. kde is a spin. 16:19:56 asking Adam for details 16:20:02 is the change in kickstart enough to have the nightly built? or do we have to do some other changes somewhere else? 16:20:18 we don't have fedora builds, but it's about time to ask releng 16:20:29 at least for classic live installer images 16:20:51 definitely 16:21:08 however, I would be interested also about Sericea 16:21:32 I think we should progress the spin and sericea as parallels tracks 16:22:02 +1 16:22:20 if the spin is going more quickly than sericea, let's continue working on both. Sooner we have an official build (either iso or sericea) sooner we can start to test it more simply 16:22:34 obviously the goal is to have asap both 16:24:09 I guess the pungi work is required from us to support Sericea. Do I remember correctly alebastr ? 16:24:52 is pungi change also requested for the spin? 16:25:17 yes. I'm not sure what else is required, releng should know 16:26:08 alebastr: will you contact releng or someone else should take that to find out 16:26:08 should we update https://pagure.io/releng/issue/11152? 16:26:08 That is correct but IIRC that was possibly changing with changes travier was proposing 16:26:08 seems like the first step to me now 🙂 16:26:21 I can folloup on releng#11152 16:27:56 #action Fale will follow up on releng#11152 16:29:38 I've noticed https://todo.sr.ht/~exec64/imv/20 yesterday and I have a question 16:29:38 Does anyone here run configuration with output scale? 16:29:49 I do 16:30:15 On my laptop screen 16:30:15 Do things crash a lot for you? :) 16:30:43 mmmm not really but I honestly don't use the laptop a ton 16:31:01 I mean I've been using it clamshell mode for the past week or so given the move and it's been stable 16:31:22 It seems to be a thing with Sway 1.8 which implements stricter checks for scaled surface size 16:31:23 * a ton (rather then docked) 16:32:18 I have had a mouse cursor the size of a dust particle but I believe it's only isolated to chrome and electron 16:33:43 alebastr[m]: I will poke a bit tonight to see if I can get anything to break IIRC I scale at 1.7 16:34:41 I don't have any HiDPI displays to test stuff, unfortunately. Well, fortunately for me as I knew there will be issues with these. 16:35:30 Indeed it's always fun fractional scaling 16:35:59 but it seems that running a setup with scale 2 is a must to be able to see all these bugs before it affects our users. 16:41:28 do we have other topics? 16:43:01 I'm aware of my tasks from last meeting and will be putting an honest effort in as time permits 16:43:34 #link https://gitlab.com/fedora/sigs/sway/SIG/-/issues/17 16:45:33 It would be appreciated if anyone could take a look at the imv bug. I think it's happening somewhere in src/viewport.c where one of the paths returns unscaled size. 16:46:39 But there's also which may mean we need a new default 16:47:24 what was the reason for using imv instead of feh? 16:47:32 wayland support 16:48:06 uh, right 16:50:01 1y+ with no commits, is not a good sign https://git.sr.ht/~exec64/imv 16:52:49 Well, the author does not have time to actively develop it right now. And nobody attempted to fix the scaling issue so far. 16:53:42 @alebastr if the project is maintained by a single person, imho is already concerning 16:54:46 Fale: there's a lot of wayland stuff maintained by a single person :( 16:55:01 yeah, that is the sad part around wayland 16:55:45 even foot has a few regular contributors but only one maintainer 16:57:31 but I think that's already off-topic for the meeting 16:58:00 do we have anything else or it's time to close the meeting? 16:58:06 Im good here 17:02:11 #endmeeting