14:00:25 #startmeeting FESCO (2020-09-16) 14:00:25 Meeting started Wed Sep 16 14:00:25 2020 UTC. 14:00:25 This meeting is logged and archived in a public location. 14:00:25 The chair is cverna. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:25 The meeting name has been set to 'fesco_(2020-09-16)' 14:00:31 #meetingname fesco 14:00:31 The meeting name has been set to 'fesco' 14:00:35 .hello2 14:00:35 #chair nirik, ignatenkobrain, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, cverna, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 14:00:35 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku cverna dcantrell decathorpe ignatenkobrain mhroncok nirik sgallagh zbyszek 14:00:35 sgallagh: sgallagh 'Stephen Gallagher' 14:00:38 .hello2 14:00:39 dcantrell: dcantrell 'David Cantrell' 14:00:42 .hello churchyard 14:00:43 mhroncok: churchyard 'Miro Hrončok' 14:00:43 #topic init process 14:00:50 hello everyone 14:00:57 morning 14:01:03 .hello kevin 14:01:04 nirik: kevin 'Kevin Fenzi' 14:01:13 .hello2 14:01:14 bcotton: bcotton 'Ben Cotton' 14:01:25 .hello ngompa 14:01:26 King_InuYasha: ngompa 'Neal Gompa' 14:01:36 * King_InuYasha just got back from getting flu shot 14:01:52 oh I should get one of those 14:01:54 So we did not have any ticket tagged with meeting 14:02:13 .hello2 14:02:14 decathorpe: decathorpe 'Fabio Valentini' 14:02:18 but we have couple of old tickets still open 14:02:29 do we want to look at these ? 14:02:34 .hello2 14:02:34 dcantrell: I love modern medicine, as long as I don't look at it :D 14:02:34 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 14:02:40 * King_InuYasha twitches over needles 14:02:53 I am the same way. I hate getting shots, though it's never as bad as I think 14:03:18 but worse than that is getting blood drawn. I always pass out. and it's because I look at it and see it happening and then boom, I'm on the floor 14:03:35 yeah... 14:03:36 but it's only ever for myself, I don't do that if I see other people having it done....go figure 14:03:47 I get queasy when I see blood drawn directly 14:04:24 cverna: What tickets are you referring to? 14:04:24 you get used to it :D 14:04:25 cverna: good idea 14:04:37 .fesco 2441 14:04:38 cverna: Issue #2441: F34 System-Wide Change: RPM-level auto release and changelog bumping - fesco - Pagure.io - https://pagure.io/fesco/issue/2441 14:04:42 when I had Lyme disease last year (not recommended), they took A LOT of blood multiple times and wow, they asked me to remind them of the fact that I'll end up on the floor because they want to give me the big recliner and have OJ ready to go 14:04:46 dcantrell: omg, me too 14:04:48 dcantrell: Don't they make you sit down? Your phlebotomist might be trolling you 14:04:59 last comment was 2 months ago 14:05:07 mbooth: I fall out of that chair 14:05:17 unless they lock me in to all 25,000 Pyramid style 14:05:21 cverna: I appreciate you try stay on topic :D 14:05:33 mhroncok: trying hard :P 14:05:35 mhroncok: sorry.... 14:05:55 dcantrell: haha no worries 14:06:09 https://fedoraproject.org/w/index.php?title=Changes/rpm_level_auto_release_and_changelog_bumping&action=history 14:06:16 no change what so ever 14:06:27 if we want to get rid of the ticket, we can say to resubmit once ready 14:06:30 I remain in favor of eliminating %changelog entirely, but whatever 14:06:48 didn't we say it depends on 2440? 14:07:08 we did 14:07:11 yeah, it depends on that other one 14:07:22 did something happen to it or is it in limbo? 14:07:25 which... nim has not done anything so far 14:07:32 do we want to close the ticket and ask to reopen when 2440 was implemented 14:07:33 I assume because he's been on vacation 14:07:43 * nirik hasn't seen him around on irc lately. :( 14:08:04 iirc, he's on a long vacation right now 14:08:26 proposal : close 2441 and ask to reopen once 2440 is implemented 14:08:44 cverna: +1 14:08:45 * cverna is not a fan of ticket staying open forever 14:08:45 I agree with sgallagh on changelogs, but that aside I don't really have a problem with these changes if it's optional for packagers (which it appears to be). I don't think this is something that will work for all packages, but for those that want to use it...sure? 14:08:58 cverna: yeah, I'm ok with that too +1 14:09:00 cverna: +1 14:09:12 cverna: +1 14:09:14 dcantrell: Last we checked in on this, didn't we determine that the implementation would require infra work that no one wanted to implement? 14:09:18 yes 14:09:19 cverna: sure, but I think I am not in favor of the change... but we can discuss that down the road 14:09:26 cverna: +1 14:09:27 sgallagh: yes 14:09:30 sgallagh: yeah, that's still the case 14:09:58 #action cverna to close #2441 asking to reopen once #2440 is implemented 14:10:35 .fesco 2418 14:10:36 cverna: Issue #2418: Formalize updated policies for what spins can change without asking (and what can be changed with FESCo clearance) - fesco - Pagure.io - https://pagure.io/fesco/issue/2418 14:10:51 Hmm, I would prefer to keep the ticket open while it's being worked on. 14:11:00 Closing and reopening doesn't make much sense. 14:11:11 (I stepped away to take a phone call, sorry.) 14:11:20 zbyszek: mark as "stalled" and ignore it until something changes? 14:11:29 yeah, I feel this one is more stalled than anything 14:11:36 Yes. We did that with many other tickets. 14:11:39 stalled tickets tend to be stalled forever, until they are closed 14:11:41 I think closing acts as sort of a poke to see if there's still interest 14:11:42 zbyszek: no problem, it is just so that we know we don't have to care about that ticket for now 14:11:51 mhroncok++ 14:12:11 note that they can't reopen the ticket 14:12:16 only project admins can 14:12:36 (or people with ticket privileges) 14:12:49 they can just open a new one 14:13:01 we can ask them to add a comment to the ticket for it to be reopen in that case 14:13:18 Yeah, but then we have two tickets on the same subject, history becomes messy. 14:13:38 I don't have a strong opinion on that one 14:13:49 stalled is fine 14:13:55 this ticket is still an F34 ticket 14:13:57 so we can leave it open 14:14:03 #undo 14:14:03 Removing item from minutes: ACTION by cverna at 14:09:58 : cverna to close #2441 asking to reopen once #2440 is implemented 14:14:05 we closed the F33 ticket with guidance 14:14:24 #action cverna to tagged #2441 as stalled 14:14:24 we can ask him to resubmit that for F34 14:14:35 cverna: thanks 14:14:45 and we (bcotton) will do the needful :) 14:15:37 so next 14:15:37 #action bcotton to do the needful 14:15:41 .fesco 2418 14:15:42 cverna: Issue #2418: Formalize updated policies for what spins can change without asking (and what can be changed with FESCo clearance) - fesco - Pagure.io - https://pagure.io/fesco/issue/2418 14:16:11 blech 14:16:12 I have not followed that ticket much but it does not seems super active anymore 14:16:33 I think really the only thing we need to do is purge references to the Spins SIG and remove the spins/labs split 14:16:51 pretty much everything else winds up being a case-by-case thing we have to evaluate as a Change anyway 14:17:01 Well, I think a fair bit of this was triggered by questions around ELN 14:17:14 King_InuYasha: that was my thinking 14:17:17 ah yes, the amorphous blob :D 14:17:20 there's the question of some guidence, but I guess we could punt that... 14:17:57 I think we could just say introducing new flavors/variants/spins/etc requires a System-Wide Change no matter what 14:18:02 that's pretty simple guidance 14:18:14 Or resurrecting a long-dormant one, maybe 14:18:14 that works for me 14:18:33 i'd say self-contained is more appropriate, but it doesn't matter too much either way 14:18:46 there's a lot of moving pieces for introducing or removing flavors, and system-wide changes tend to capture that better, imho 14:19:04 releng, kickstart, comps, pungi, etc. 14:19:17 well, the main help would be to save people time if they propose something too 'off fedora', but it's really hard to say what that might be comprised of. 14:19:38 Fedora: Smart Fridge Edition! 14:19:43 hah 14:19:51 I could see someone making a Home Assistant flavor 14:19:56 ... 14:19:59 err Smart Home flavor 14:20:05 sgallagh: you make one that works and I'll install it my kitchen immediately 14:20:16 nirik: i think the trademark guidelines cover that fairly well...but it's probably worth making the docs easy to find from one place 14:20:16 sgallagh: no joke, I would too 14:20:23 so less a creation of new docs and more a curation of existing 14:20:24 ... 14:20:25 * King_InuYasha mourns his crappy fridge 14:20:45 fwiw, my Taiga Board of Shame has a card for improving the spins process docs because the current ones are....largely lies 14:20:50 are you guys kidding? no software in my kitchen. I've seen software. We work on that stuff 14:20:53 I mean if someone submits a thing that uses sysvinit is that approvable? apparmour? how about .debs? freebsd kernel? 14:20:55 bcotton: yay lies :D 14:20:56 Ok, but "works" in my definition may include solving the problem of food shortage in the fridge by elimination of the consuming entities... 14:21:10 nirik: oh boy... 14:21:23 nirik: so that was my concern, but more about using the Fedora brand 14:21:31 I think those have to be case by case 14:21:35 yup 14:21:39 yeah. I mean... go for it! but it's not really fedora. 14:21:47 I think the System-Wide Change process captures these kinds of things pretty well 14:21:47 * nirik nods. 14:21:55 That's definitely the point at which it should be a Fedora Remix 14:21:56 and forces it to be relatively descriptive and involve all the stakeholders early 14:22:09 definitely 14:22:57 I don't think we are able to draw a line 14:23:14 this is not sortable 14:23:18 the mechanics of making a new flavor probably need to be better defined, but the process of adding and removing flavors should just be System-Wide Changes, IMO 14:23:23 yeah, the line is fuzzy. But I guess we will see what we get. :) 14:24:00 I am all in favor of: start a discussion on devel, see if people like the idea, do a change proposal 14:24:09 mhroncok: +1 14:24:13 based on the examples nirik mentioned, some of those ideas wouldn't even be able to use current infrastructure while others could. 14:24:18 mhroncok: +1 14:24:26 mhroncok: +1 14:24:32 so to summarize introducing new or bringing back to live a flavors/variants/spins/etc requires a System-Wide Change 14:24:50 cverna: likewise so for removing flavors 14:24:56 sure. Happy to talk about even the craziest of ideas. :) 14:25:06 King_InuYasha: could you add that proposal to the ticket and we can vote there ? 14:25:07 Should i prepare a draft based on https://pagure.io/fesco/issue/2418#comment-667545? Or do we want to start with a different angle? 14:25:38 nirik: ehhh, I think there's a limit. I wouldn't even entertain "Fedora: Enhanced Interrogation Edition" as a proposal... 14:25:44 zbyszek: that looks good to me 14:26:08 sgallagh: I would talk about it for long enough to say no. ;) 14:26:21 cverna: I think what zbyszek has sufficies, just adding a word to mention removing them does require a System-Wide Change too 14:26:21 nirik: fair 14:26:34 King_InuYasha: ack 14:26:38 the whole point of doing so is just to make sure everyone knows 14:26:41 King_InuYasha: agreed 14:26:48 and the process goes without a hitch (if approved) 14:26:52 agreed 14:27:06 ehhh 14:27:09 and system-wide changes also give an opportunity for others to participate (either in taking over or helping with new stuff) 14:27:15 otherwise, nobody knows 14:27:18 not sure i'm on board with requiring a change proposal to remove them 14:27:21 well, the orig ask is a bit more detailed tho 14:27:33 like are we going to force people to keep doing it if they don't want to 14:27:34 e.g. nobody knew that the scientific kde flavor disappeared in F31 14:27:46 bcotton: no, it's more of an alert of all the things that need to be reaped 14:27:56 and if someone wants to take over instead of letting it go, we can do that 14:27:58 who would file that? how do we know? 14:27:59 also, the spins keepalive is later in the schedule in the system-wide change proposal deadline 14:28:07 hmm 14:28:18 not that we can't change that milestone around 14:28:30 but it doesn't really fit the change proposal model 14:28:37 the problem I want to solve is to give interested parties an opportunity to take over an orphaned flavor 14:29:00 right now, I don't know of a way for us to do that beyond Change proposals 14:29:18 yeah, that can just be a devel-announce post after the keepalive with a "here are the spins that will be removed because nobody is apparently around for it" 14:29:35 I'm fine with that as well 14:29:35 it's more like a non-responsive maintainer process than a change process 14:29:39 True. So maybe bcotton should announce when a spin doesn't pass the keepalive check, and ask for volunteers to pick it up, and if that doesn't happen, we'll announce the removal of the spin along with other hcanges. 14:29:41 hmm fair 14:29:48 more like the orphaned package process. 14:29:48 that works for me 14:30:00 +1 14:30:07 so zbyszek, could you incorporate that into your thing? 14:30:29 King_InuYasha: yep 14:30:30 but I think that covers all the bases 14:30:37 so... +1 with all that :D 14:31:23 so looking at the orig ask in the ticket... it seems like we should just say "all the things other solutions are doing you can do, if you diverge from fedora thats fine, but we need to discuss it in a change and approve it." 14:31:45 proposal: zbyszek to draft spins/flavors/variants policy based on https://pagure.io/fesco/issue/2418#comment-667545 with announce notices for orphaned spins/flavors/variants similar to orphaned packages 14:31:46 #action zbyszek to prepare a draft proposal for #2418 14:31:47 really this is docs for the spin process. 14:32:00 #undo 14:32:00 Removing item from minutes: ACTION by cverna at 14:31:46 : zbyszek to prepare a draft proposal for #2418 14:32:06 King_InuYasha: yours is better :) 14:32:12 King_InuYasha: +1 14:32:32 nirik: hmm, I can imagine a case where somebody says "I'll do kde-spin2, that is the same but uses a different clipboard mechanism", and I think we'd reject that because it's not *different* enough 14:32:50 what are flavors and variants again? flavors makes me think of openstack... ;) 14:32:55 zbyszek: good point. 14:33:24 flavors makes me think of ice creams 14:33:29 :P 14:33:36 or koolaid 14:33:45 instant ramen 14:33:58 downloading the spin / drinking the koolaid 14:34:23 #action zbyszek to draft spins/flavors/variants policy based on https://pagure.io/fesco/issue/2418#comment-667545 with announce notices for orphaned spins/flavors/variants similar to orphaned packages 14:34:41 sounds like we have a way forward for this ticket 14:35:02 zbyszek++ for working on the draft 14:35:02 cverna: Karma for zbyszek changed to 8 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:36:29 .fesco 2409 14:36:34 cverna: Issue #2409: F34 System-Wide Change: CompilerPolicy Change - fesco - Pagure.io - https://pagure.io/fesco/issue/2409 14:36:40 This is stalled too 14:37:31 Let's mark it as stalled too, I'm sure law will return to it at some point. 14:37:34 though the mass rebuild and gcc 11 / LTO issues have 99% been dealt with, so probably law has time now :) 14:38:01 yeah, might ping law in the ticket and ask for an update? 14:38:46 #action cverna to tag #2409 stalled 14:38:47 +1 14:39:05 nirik: yeah will do when I tag the ticket 14:39:43 +1 14:40:25 ok any other tickets we want to look at ? 14:40:30 https://pagure.io/fesco/issues 14:40:36 firefox? 14:41:03 .fesco 2020 14:41:07 cverna: Issue #2020: Firefox is switching from gcc to clang/llvm - fesco - Pagure.io - https://pagure.io/fesco/issue/2020 14:41:38 I think this is now moot 14:41:39 Man, I get PTSD just from the ticket number 14:41:45 ha 14:42:00 ugh 14:42:06 that ticket represents 2020 so well 14:42:14 lol 14:42:26 It was filed in 2018, prescience 14:42:45 anyhow, I am pretty sure the gcc bug was found, worked around and it's using gcc again. 14:42:59 yup 14:43:05 we can just close this ticket (again) 14:43:41 sounds good to me, I ll close it after the meeting 14:43:42 firefox still doesn't build in rawhide BTW 14:43:57 #action cverna to close #2020 14:44:16 closing 2020 sounds good 14:44:26 * mhroncok hopes 2021 will be better 14:44:33 :) 14:44:36 yeah, looks like it's hitting various problems... but the maintainer is on it. 14:44:39 ERROR: Package 'nss' has version '3.55.0', required version is '>= 3.56' 14:44:50 Not the compiler definitively. 14:45:20 Too many crypto libraries: we have a different ticket for that ;) 14:46:23 ok going to move to the next topic :) 14:46:33 #topic Next week's chair 14:47:30 I'll do it 14:48:44 #action mhroncok to chair next meeting 14:48:47 thanks mhroncok 14:48:51 #topic Open Floor 14:49:13 dcantrell: anything at council level we should know about? 14:50:28 Oh, " 14:50:51 #324 3rd party repo policy updated" was opened and closed. 14:51:20 (The council was given a fyi about the policy change we approved, just in case.) 14:53:48 nice :) 14:56:17 ok going to close the meeting 14:56:21 :) 14:56:22 thanks everyone for joining 14:56:25 thanks all! 14:56:31 #endmeeting