16:16:55 #startmeeting Fedora i3 (2021-02-23) 16:16:55 Meeting started Tue Feb 23 16:16:55 2021 UTC. 16:16:55 This meeting is logged and archived in a public location. 16:16:55 The chair is x3mboy. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:16:55 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:16:55 The meeting name has been set to 'fedora_i3_(2021-02-23)' 16:17:10 We need to check who will be at the maintainers.toml file 16:17:40 I got nothing, sorry 16:17:42 #chair O​dilhao @O​dilhao @jwflory jwf defolos 16:17:42 Current chairs: @O​dilhao @jwflory O​dilhao defolos jwf x3mboy 16:17:59 wanted to take a look at i3-expo, but didn't get to it 16:18:05 #topic Quick meeting to check status of things 16:18:06 x3mboy: Thanks 16:18:08 and the openqa stuff is all still pending 16:18:38 * x3mboy sent an issue to pungi to get a nightly build in qa 16:18:50 @Odilhao Ah. But looks like an easyfix task right? 16:18:57 x3mboy++ 16:19:12 #link https://pagure.io/pungi-fedora/issue/1009 16:20:25 #action O​dilhao to push a missing file into fedora-kickstarts 16:20:31 I think all of us 16:20:33 yes, it is, we just need to see who will be there 16:20:47 I dont know we have a limit, I'll ask in the issue 16:20:49 You can put several 16:21:19 The one with most have 4 16:22:38 If 4, I candidate myself to be out of the list 16:22:49 If more, everyone: Dan, Justin, Odilon, Nasir and Eduard 16:24:47 We have a logo!!!! 16:25:34 #link https://pagure.io/design/issue/709#comment-716471 16:26:28 It looks like it needs an approval from the design team, but our feedback in general is quite good 16:27:49 And pretty optimistic about we launching the spin in F34 16:27:51 Woot! 16:27:53 But the roadmap doesn't look good 16:27:54 #link https://pagure.io/i3-sig/Fedora-i3-Spin/roadmap 16:30:33 What's the status of https://pagure.io/i3-sig/Fedora-i3-Spin/issue/26 ??? 16:31:59 There is new discussion there I am behind on 16:32:40 I thought we were going to use xdg-user-dirs-update but looks like some chatter about systemd oneshot service 16:33:19 I suggested that 16:33:30 but to use a systemd service to launch xdg-user-dirs-update 16:34:59 Got it 16:35:10 Well, today is the F34 100% code completion deadline. 16:35:23 Do we push to get this done, or defer to F35? 16:35:59 Unfortunately I have zero capacity until March :/ 16:36:45 We already have the comps package in place, we could defer to F35 and use F34 as Beta 16:37:13 Makes sense 16:37:58 I was thinking about that too, maybe making F34 i3 Spin a soft launch, collecting feedback, then making a bigger splash for F35. But this is a side-bar 16:37:59 i3 can be hard to get into, if we don't have a nice experience would be hard to get traction later 16:38:04 +1 16:38:27 For issue #26, I will move it to the F35 roadmap milestone 16:38:56 Defer +1 16:39:09 can't we modify the kickstart after beta? 16:39:17 Not sure 16:40:00 I think not for Fedora Infra because of the Beta Freeze 16:40:17 Of course, we can update our own kickstarts to resubmit for F35 16:40:32 But it will be local changes, not in official composes 16:40:36 Well, let's put it like this: keep it until Beta and if we can, modify to GA, if not, defer to F35 16:40:39 wdyt? 16:41:44 I think it has to be possibñe 16:41:47 We should confirm with bcotton or CPE team to confirm how late we can push changes to kickstarts 16:41:58 sounds good 16:42:08 The whole point of having a Beta it's to be able to improve and fix for GA 16:42:12 jwf: and by cpe you mean releng? 16:42:25 errr, yes probably defolos 16:42:35 👌 16:42:42 x3mboy: true. 16:43:00 #agreed keep #26 it until Beta and if we can, modify to GA, if not, defer to F35 16:43:11 Six years in Fedora, and this is all new to me :D 17:04:51 Ooops 17:04:58 I think I need to close the meetins 17:05:00 * I think I need to close the meeting 17:05:04 #endmeeting