17:06:12 #startmeeting FESCo (2022-07-26) 17:06:12 Meeting started Tue Jul 26 17:06:12 2022 UTC. 17:06:12 This meeting is logged and archived in a public location. 17:06:12 The chair is sgallagh. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:06:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:06:12 The meeting name has been set to 'fesco_(2022-07-26)' 17:06:18 #meetingname fesco 17:06:18 The meeting name has been set to 'fesco' 17:06:27 #topic Init Process 17:06:32 .hi 17:06:33 sgallagh: sgallagh 'Stephen Gallagher' 17:06:49 morning 17:07:23 .hello churchyard 17:07:24 mhroncok: churchyard 'Miro Hrončok' 17:07:43 .hello2 17:07:44 bcotton: bcotton 'Ben Cotton' 17:07:57 .hello2 17:07:58 decathorpe: decathorpe 'Fabio Valentini' 17:08:26 .hi 17:08:27 salimma: salimma 'Michel Alexandre Salim' 17:08:33 Hmm, maybe we won’t hit quorum :-) 17:08:46 we can summon Neal 17:09:07 .hello ngompa 17:09:08 Eighth_Doctor: ngompa 'Neal Gompa' 17:09:08 I’m short on salt for the circle 17:09:15 I'm half dead, but I'm here 17:10:19 Okay, I got tied up this morning and didn’t have a chance to do the ticket scrub, so I’m basically just going to do this as an Open Floor meeting and folks can suggest tickets as needed. 17:10:31 I’ll handle the secretary work after the meeting. 17:10:39 #topic Open Floor 17:11:15 What needs the most urgent discussion? 17:11:30 * mhroncok goes to check 17:12:08 I wnated to see what folks think about https://pagure.io/fesco/issue/2842 but it is not urgent (any more) 17:12:16 (Sorry, also shoveling lunch down while I type) 17:12:18 Ah right 17:12:47 * nirik is fine with it whenever. 17:13:22 My thoughts here are that it’s fine to allow post-mass rebuild since we’ve been running it this way in ELN for a long time now. 17:13:34 but ELN doe snot include everything, does it? 17:13:40 s/doe/does/, s/snot/not/ 17:13:40 True 17:13:41 Remind me, how many packages are in ELN, and how many packages are in Fedora? 17:13:59 (same argument for RHEL 8/9( 17:14:02 Roughly 5000 packages in ELN currently 17:14:09 I don'T wan tto deal with random stuff suddenyl failing on me when i need to ship a CVE fix 17:14:13 Fair 17:14:25 * I don't want to deal with random stuff suddenly failing on me when I need to ship a CVE fix 17:14:38 I don’t object to deferring it. But I’m also on board if a majority just says “go ahead”. 17:14:48 same 17:14:59 also, ELN is an even higher baseline, innit? 17:15:12 Hmm, actually yeah. It’s z14 17:16:05 ELN has -march=z14 -mtune=z15 17:16:12 this has -march=z13 -mtune=z14 17:16:26 I don't know if ELN ever had -march=z13 -mtune=z14 for an extended period or not 17:16:27 * nirik wonders why. 17:16:32 wait, so we're downgrading march? 17:16:36 no 17:16:46 Fedora Rawhide now has -march=zEC12 -mtune=z13 17:16:54 See https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/207#request_diff 17:17:25 yeah, I find it hard to think that people with older mainframes would be using lots of fedora when rhel doesn't work there already... 17:17:44 ELN was updated 5 months ago, https://src.fedoraproject.org/rpms/redhat-rpm-config/c/04be20e64b522956b90d40e9973957aa4c190690 17:17:52 It had what this proposal has before 17:18:44 dropping support for older mainframes doe snot really concern me at all. a mass rebuild has no effect on this, we either do it in f37 or f38, no difference 17:18:53 s/doe/does/, s/snot/not/ 17:19:16 random subtle buggy behavior in a random package here and there is what I am afraid of 17:20:09 anyway, we can vote asynchronously, it's tagged with meeting only because it has negative votes 17:20:20 True. After all, none of the packages in Fedora have other bugs. :-P 17:21:33 And to be realistic, I highly doubt that more than a few dozen mainframes exist that run Fedora. 17:23:00 meh, I'm fine with updating the s390x/Z system baseline 17:23:34 #chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, music, mhayden, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 17:23:34 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mhayden mhroncok music nirik sgallagh zbyszek 17:23:44 (Forgot to do that earlier) 17:23:51 👋 17:24:45 OK, I think we can take this to the ticket now. 17:24:56 Does anyone want to discuss the RPi 4 topic? 17:25:14 Or just wait for pbrobinson to update the wiki? 17:26:06 I'm not sure whats still unclear here... we are adding accelerated graphics and some net support... so that it's all around supported by fedora... 17:26:26 sgallagh: That does not make build issues go away :( 17:26:48 Stephen Gallagher: I don't care about the RPi 4 topic beyond just approving it 17:26:53 it's purely a marketing Change 17:27:00 since we're getting it as part of a kernel rebase 17:27:08 nirik: It's not clear to me at all. What does "offical support" even mean? How does that impact release criteria? 17:27:34 Right, the main open question is whether RPi4 issues are blocking on the release 17:27:39 And if so, on which media? 17:27:39 it means Peter will hopefully stop being rude to people who ask about Raspberry Pi support in Fedora ARM channels 17:27:46 It means "all the various parts work now" and no, it doesn't affect release critera other than adding that device as a device we test? 17:27:51 because we'll have a document for him to point to 17:28:22 Eighth_Doctor: I've NEVER been rude actually, please don't lie and make false claims 17:28:26 Conan Kudo: Please don't editorialize. 17:28:40 I respectfully disagree 17:28:49 I completely utterly disagree 17:29:08 people, this is unnecessarily off-topic :( 17:29:23 mhroncok: you're not even on the arm channel 17:29:25 the reason why this Change is happening is because Fedora does not historically support RPi4 17:29:32 and people keep asking about it 17:29:48 Please drop this topic or take it elsewhere. 17:29:52 otherwise it wouldn't be Change worthy 17:30:03 and we don't support it because the core deliverable of Workstation doesn't properly work 17:30:08 It's not conducive to making a decision or to remaining civil 17:30:36 (Meaning the parts not relevant to the Change, of course) 17:31:04 right, with accelerated graphics, the workstation arm release blocking deliverable will be testable/doable. 17:31:08 so, hopefully this brings us back on topic -- if we approve this change for the rpi4, what are the potential bad outcomes? delayed release because tests fail? more support burden? 17:31:19 pbrobinson: Can you answer the question about blocking media? 17:31:19 the only open question is a consolidation of the declared supported ARM devices 17:31:20 That's all I need to know for a +1 17:31:21 that is, where people find out what is supported 17:32:05 sgallagh: I did actually answer that, it makes it the same status as the other arm blocking devices 17:32:18 and QE has a process around that (I don't remember it off hand) 17:32:29 OK, so it does affect the blocker criteria 17:32:49 which is not describe din the proposal 17:32:53 s/describe/described/, s/din/in/ 17:32:54 Right, they have a matrix of install media and hardware that is blocking to the release. 17:32:58 it doesn't change the critera any, it adds a new device to be tested against that critera 17:33:11 not the critera but the criterea will be applied to the rpi4 when previously they weren't 17:33:15 So if this is adding one or more entries onto that matrix, we need to add it. 17:34:12 OK, so it's just being treated like different x64 hardware. 17:34:34 It isn't necessarily blocking unless a large subset of aarch64 hardware is affected. 17:34:42 Do I have that right? 17:35:31 yep 17:35:42 OK 17:36:12 Sorry for so many questions, but I'm just trying to make sure the request is clear. 17:36:18 so the big question is that the documentation on supported hardware is confusing 17:36:26 people can't figure out what is and isn't supported 17:36:32 That's not exclusive to RPi 4 though 17:36:41 I'd suggest we open that as its own issue 17:36:46 no, but the Raspberry Pis come up way more than anything else 17:36:57 frankly, most people don't care about the rest as much 17:37:24 so a Change that markets that we support this should also cover us actually documenting this 17:37:38 since that's the only real effort required for this Change 17:37:58 so when and where is that happening? 17:38:11 pbrobinson: Would you have a problem if we made acceptance contingent on updating the support documentation to be more clear? 17:38:13 sorry, I need to drop 17:39:04 Eighth_Doctor: that's COMPLETELY not true actually 17:39:33 there's been like a whole bunches of patches that I got upstream and a lot of other work 17:40:03 and there is a point on documentation in the change too about movigng the rpi docs to docs.fo.o 17:40:41 If I remember correctly, one problem that was previously mentioned is that there's multiple different Wiki and docs pages about Fedora on ARM and they list different hardware as supported? 17:41:05 the patches are already done though, this is a post facto change 17:41:20 as the Change is written, it's announcing things that are already done 17:41:21 Conan Kudo: Please desist from this line of conversation. 17:41:44 It is becoming unnecessarily hostile. 17:42:07 Stephen Gallagher: look, the change, as written, indicates the code work is done 17:42:28 so what are we accepting? 17:42:29 decathorpe: yes, the plan is to merge all of that overr to docs 17:42:34 That's not unique to this Change by any stretch of the imagination 17:42:53 Many Changes come to us as fait accompli for marketing purposes. 17:42:54 This is fine. 17:43:02 Eighth_Doctor: I had to do specific 5.19 PR for Fedora that will land once this is approved 17:43:04 * Eighth_Doctor grumbles 17:43:12 Eighth_Doctor: so again you are incorrect 17:43:13 fine whatever 17:43:35 Stephen Gallagher: fait accompli changes generally get a finger wag 17:43:44 pbrobinson: Please desist from that line of conversation as well. 17:44:10 sgallagh: fair enough, but I'm just replying to accusations 17:44:21 OK, so let me propose a solution here: 17:45:14 Proposal: As indicated in the Change, the owners will perform necessary documentation updates and convergence onto docs.fp.o. The Change is approved, contingent upon those doc updates being made by Beta release. 17:45:41 that was already in the change so sure 17:45:56 (If the doc updates are not made, we will simply delist this as a Change, not remove the features) 17:45:57 Stephen Gallagher: +1 17:46:12 meh, +1 17:46:12 sure, still +1 :) 17:46:49 mhayden: ? 17:47:05 I'm a +1 on it 17:47:30 #agreed As indicated in the Change, the owners will perform necessary documentation updates and convergence onto docs.fp.o. The Change is approved, contingent upon those doc updates being made by Beta release. (+5, 0, -0) 17:47:48 pbrobinson: Thank you for taking the time to answer our questions. I appreciate it. 17:48:00 pbrobinson: 🫂 17:48:39 As an aside, I recently got my hands on a Raspberry Pi 400 and stuck Fedora IoT on it; I'd be happy to help with testing if desired. 17:49:59 will the endless open floor just taper off now? 17:50:09 I'm starting to get hungry 17:50:25 #topic Next Week's Chair 17:51:12 Anyone? 17:51:48 I guess we'll all be busy with preparing for Nest next week? 17:52:04 hmm 17:52:54 OK, do we want to plan on skipping? 17:53:41 I'd be fine with that. I don't think there's any urgent tickets ... but I can volunteer to run the meeting if we end up needing it. 17:54:28 #action decathorpe to chair next week meeting if we don't cancel due to Nest 17:54:34 Thanks for coming, all. 17:54:41 Sorry for the chaos at the start. 17:55:10 #endmeeting