16:30:54 #startmeeting fedora_coreos_meeting 16:30:54 Meeting started Wed Jan 6 16:30:54 2021 UTC. 16:30:54 This meeting is logged and archived in a public location. 16:30:54 The chair is jlebon. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:30:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:30:54 The meeting name has been set to 'fedora_coreos_meeting' 16:31:00 #topic roll call 16:31:05 .hello2 16:31:06 cyberpear: cyberpear 'James Cassell' 16:31:20 #chair cyberpear 16:31:20 Current chairs: cyberpear jlebon 16:31:34 .hello2 16:31:35 lorbus: lorbus 'Christian Glombek' 16:31:37 .hello jasonbrooks 16:31:37 jbrooks: jasonbrooks 'Jason Brooks' 16:31:52 let's see how many people show up or if we're still recovering from the holidays :) 16:31:57 #chair lorbus jbrooks 16:31:57 Current chairs: cyberpear jbrooks jlebon lorbus 16:32:26 .hello2 16:32:27 lucab: lucab 'Luca Bruno' 16:33:11 #chair lucab 16:33:11 Current chairs: cyberpear jbrooks jlebon lorbus lucab 16:33:43 happy new-ish year 16:34:02 happy new year all :) 16:35:04 happy new year!! :) 16:35:13 o/ 16:35:50 hmm ok, looks like no one else is showing up 16:36:14 cool 16:36:14 let's see... 16:36:17 #topic Action items from last meeting 16:36:27 red_beard to investigate forklifting FCOS artifacts into OVH to see if they work red_beard to open a ticket to strategize on FCOS RH summit presence 16:36:40 ahh that was supposed to be on two lines 16:36:57 red_beard is not here. i'll re-action for now 16:37:07 #action red_beard to investigate forklifting FCOS artifacts into OVH to see if they work 16:37:07 .hello2 16:37:07 davdunc: davdunc 'David Duncan' 16:37:12 #action red_beard to open a ticket to strategize on FCOS RH summit presence 16:37:18 #chair davdunc 16:37:18 Current chairs: cyberpear davdunc jbrooks jlebon lorbus lucab 16:37:57 there isn't a lot for this meeting. one thing i wanted to discuss was: 16:38:02 #topic tracker: Fedora 34 rebase work 16:38:06 #link https://github.com/coreos/fedora-coreos-tracker/issues/704 16:38:48 so with f33, we started a bit late tracking the changes that happened there, and it was a lot of pain (to us and to various maintainers) to get bugs sorted out 16:39:09 for f34, we're trying to be ahead this time 16:39:26 we currently have a rawhide stream which has been merrily building and passing tests so far 16:39:47 i've noticed only a few minor issues which i've already reported to maintainers 16:39:52 thanks for setting up rawhide, jlebon++ 16:40:26 a major thing we should do though is keep a close eye on all the f34 change proposals and evaluate how they affect FCOS 16:40:47 i wrote up some from a glance at the list in https://github.com/coreos/fedora-coreos-tracker/issues/704#issue-772426769 16:40:51 jlebon++ 16:40:53 jbrooks: Karma for jlebon changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:41:10 but i invite folks to take a look themselves as well and pick up anything else that's relevant 16:41:30 the earlier we catch these, the easier it'll be to deal with it 16:41:46 anyway, that's all i had to say on the subject :) 16:42:16 :) 16:42:24 Sounds good 16:42:26 anyone wants to add anything on this before moving on? 16:42:37 I left a comment on https://bugzilla.redhat.com/show_bug.cgi?id=1792468 for the service restart triggers 16:43:18 lucab: nice, thanks lucab 16:44:20 ok, next item: 16:44:29 #topic 16:44:34 #topic 2021-01-06: gather status update for Fedora Council 16:44:39 #link https://github.com/coreos/fedora-coreos-tracker/issues/690 16:45:04 i've just created https://hackmd.io/e6uqIVaSSAqfWmpdKE784g 16:46:06 please add anything we did during December worth mentioning there 16:46:12 since we're a bit thin today, i'll share this with others after the meeting as well 16:47:24 * jlebon checks what releases we've done recently 16:49:03 I don't think there was much movement in December 16:49:40 yeah, agreed 16:50:17 added a couple things i found 16:50:22 we can finish that up outside this meeting 16:50:50 so that's more or less all we had scheduled for this meeting. anyone have any topics they want to bring up before open floor? 16:51:43 nothing from my side 16:51:51 #topic open floor 16:51:57 https://pagure.io/fedora-kickstarts/pull-request/737 16:52:26 addressing issue-319 16:52:26 davdunc: ahh sorry, moved to open floor just before -- but we can discuss it here :) 16:52:47 I left it to open jlebon 16:52:55 since I didn't add it to the agenda. 16:53:18 davdunc: this is for the cloud SIG right? 16:53:30 oh. jlebon It is. 16:53:36 I just got confused. 16:53:50 sorry. split-brain. 16:54:10 np. good to know what's happening there anyway 16:55:03 one thing i'll mention is that lucab did a redesign of the build browser: https://builds.coreos.fedoraproject.org/browser 16:55:27 same information, just more styling :) 16:55:41 meh, it was more of a quick CSS pass 16:55:42 nice layout. very easy to understand. 16:55:48 there's some tweaks we'd like to do there 16:56:06 looks nice 16:56:18 great job 16:56:27 ok, closing out the meeting in 60s if no other topics 16:56:49 I'm doing some web (React) experiment to make the "tweak rollouts" step of releng a bit more human-friendly 16:57:13 lucab++ 16:57:13 davdunc: Karma for lucab changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:57:21 lucab: can you expand on that? 16:57:33 lucab++ 16:57:33 jbrooks: Karma for lucab changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:57:34 I'm not sure if we want to have a single panel with also the release browser inside 16:58:35 jlebon: basically a webUI to load the JSON from github, tweak the details live (while watching the graph update) and then PR back to GH 16:59:04 lucab: ahh gotcha 16:59:18 (I'm still very far from that) 16:59:47 what would also be really cool is a big red button we can press and it stops whatever rollouts are in progress (via PR to GH) 17:00:25 I'm not planning to embed the existing browsers into it, but there is some overlap in scope 17:00:27 the requirement being that it's faster than it'd take an engineer to type up the equivalent PR manually :) 17:00:58 right yeah 17:01:12 ah yes, I remember there was some discussion about a deadman knob 17:01:32 anyway, it was mostly FYI 17:01:44 we had to do that recently and when you're doing it in a hurry, it's easy to mess up 17:02:14 (restarting 60s countdown after every last msg -- excluding this one :) ) 17:02:44 #endmeeting