15:04:59 #startmeeting FESCO (2018-07-16) 15:04:59 Meeting started Mon Jul 16 15:04:59 2018 UTC. 15:04:59 This meeting is logged and archived in a public location. 15:04:59 The chair is zbyszek. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:59 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:04:59 The meeting name has been set to 'fesco_(2018-07-16)' 15:04:59 #meetingname fesco 15:04:59 The meeting name has been set to 'fesco' 15:04:59 #chair nirik, maxamillion, jsmith, jwb, zbyszek, tyll, sgallagh, contyk, bowlofeggs 15:04:59 Current chairs: bowlofeggs contyk jsmith jwb maxamillion nirik sgallagh tyll zbyszek 15:05:02 #topic init process 15:05:06 morning 15:05:07 .hello psabata 15:05:07 .hello2 15:05:07 contyk: psabata 'Petr Šabata' 15:05:09 .hello2 15:05:10 bowlofeggs: bowlofeggs 'Randy Barlow' 15:05:13 .hello2 15:05:13 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 15:05:16 bcotton: bcotton 'Ben Cotton' 15:05:28 .hello2 15:05:30 maxamillion: maxamillion 'Adam Miller' 15:05:41 .hello2 15:05:42 sgallagh: sgallagh 'Stephen Gallagher' 15:05:47 OK, let's start with the messy one 15:05:47 #topic #1936 F29 Self Contained Change: Deprecate YUM 3 15:05:47 .fesco 1936 15:05:47 https://pagure.io/fesco/issue/1936 15:05:48 zbyszek: Issue #1936: F29 Self Contained Change: Deprecate YUM 3 - fesco - Pagure - https://pagure.io/fesco/issue/1936 15:06:26 I found out this weekend that kojid will break... so I'm -1 until more things are in place. 15:06:31 I think 15:06:49 -1 still too, until we have a clear plan and a list of things 15:06:53 yeah, pretty much that 15:07:08 -1 here as well, there's unfortunately too many things not ready for this change 15:07:17 -1 but I'd like someone to coordinate the infra/releng changes so that we can do this in f30 15:07:59 it sounds way too late for f29 15:08:02 -1 15:08:03 -1 as well, but I want this on infra/releng's priority list 15:08:18 jsmith voted -1 in the ticket 15:08:35 jwboyer voted +1 in the ticket 15:08:49 well, we don't handle these projects upstream... or have cycles to work on it I don't think. 15:09:05 koji is the big one 15:10:08 we could at least file tickets for that 15:10:11 * bcotton can handle the project management aspect 15:10:22 nirik: There's the question whether it's enough to have some parts of the stack only working on RHEL/CentOS 15:10:41 I'd like to hear your (and other's) thoughts on this 15:10:47 There is a koji ticket, but no one working on that I know of. 15:10:51 * jsmith is finally here 15:11:07 .hello2 15:11:10 jsmith: jsmith 'Jared Smith' 15:11:13 well, that would partly work for us (fedora infra), but there's others like the riscv people who are running on fedora 15:11:43 also all our builders are fedora, so kojid needing yum3 would not work here either. 15:11:56 * jsmith is still -1 for F29, but willing to defer to F30 (knowing what I know now) 15:12:14 .link https://pagure.io/koji/issue/971 15:12:20 .info https://pagure.io/koji/issue/971 15:12:37 #link https://pagure.io/koji/issue/971 15:13:58 OK, so this is clearly not happening now. What about the following: "The change is rejected for F29, but FESCo would like to see this resubmitted for F30, with a list of dependencies (tickets), that need to be solved first."? 15:14:26 zbyszek: I like that proposal :-) 15:14:35 zbyszek: +1 15:14:39 zbyszek: +1 15:14:53 +1 15:14:53 +1 ftr 15:14:55 +1 15:15:06 sure, althought I think it's just the koji and mock tickets at this point... but there is mm and some otherlyers that could be done later. 15:15:48 nirik: Agreed :-) 15:16:17 anyhow +1 to keep us moving 15:16:17 nirik: yeah, but somebody needs to go through all the discussions, compile a list of things, and either mark them as needed, or explain why they can be delayed 15:16:31 jsmith, can I count you as +1? 15:17:50 zbyszek: Yes 15:18:01 #agreed The change is rejected for F29, but FESCo would like to see this resubmitted for F30, with a list of dependencies (tickets), that need to be solved first (+7, 0, 0) 15:18:22 I'll close the tickets marked "pending ann." later today. Sorry for that. 15:18:30 = New business = 15:18:30 #topic #1940 F29 System Wide Change: Zchunk Metadata 15:18:30 .fesco 1940 15:18:30 https://pagure.io/fesco/issue/1940 15:18:31 zbyszek: Issue #1940: F29 System Wide Change: Zchunk Metadata - fesco - Pagure - https://pagure.io/fesco/issue/1940 15:19:49 so, as long as we produce the old repodata as well, I don't see a problem here 15:19:53 Is this being deferred or not? I'm confused by the comments 15:20:09 this one sounds cool, but i do want to make sure it's backwards compatible 15:20:14 sounds like it is 15:20:31 Yes, that's how I undrstand this too 15:20:33 yeah, should be fine 15:21:02 so i like the idea of generating the metadata now but waiting for F30 to have client support 15:21:15 maxamillion: I want to see the metadata creation happen so that they can test the client with real data, but I don't want to force its use until F30 15:21:22 it will require changes in pungi and possibly bodhi 15:21:33 probably any bodhi change would be small 15:21:33 +1 bowlofeggs 15:22:20 bowlofeggs: no pungi changes needed I don't think 15:22:23 it's all in createrepo_c 15:22:26 The "Scope" section has a long list of PRs to be accepted. I think it's OK to approve this, even though it's unlikely that everything gets implemented and merged 15:22:29 alright 15:22:37 +1 defer 15:23:10 Hmm, let's vote on F29 first 15:23:36 well, IMHO do whatever can be done for f29, and finish in f30 if needed. 15:23:42 +1 to F29 (and defer to F30 if it's not done by F29 deadline) 15:24:04 jsmith: what does "defer" mean? 15:24:20 well, thats just the normal contingency plan right? 15:24:30 +1 for the change 15:24:37 I think nirik's wording is better, because it does not suggest that the parts that are already done have to be disabled 15:25:02 Yes, the regular contingency plan 15:25:15 * jsmith could have been much more precise in his language, sorry 15:25:27 Could we get a clearly-worded proposal to vote on? 15:26:11 Vote to approve the change? 15:26:23 Proposal: Approve for F29. Whatever pieces aren't done by F29 are approved for F30. 15:26:30 jsmith: +1 15:26:35 +1 to that 15:26:55 Seems oddly open ended for a change that could break so many users, but alright 15:27:04 the change as worded does say "rather than xz or gzip" 15:27:17 that seems non backward compatible 15:27:30 well except that the wiki says "in addition to" 15:27:37 bowlofeggs: I think it got changed 15:27:41 ah ok 15:27:46 bowlofeggs: refresh the page 15:27:47 so the wiki is correct 15:27:51 I don't think this is any way non-backward-compatible, or could "break" a lot of users 15:28:07 At least, as I understand it 15:28:23 I guess I'm a weak +1 here 15:28:30 it is backwards compatible. If there's a problem with the new metadata on the client end, we can remove it and dnf will use the old format 15:28:40 I'd kind of like to have more runway, but I suppose realistically we won't know if it breaks until it does 15:29:28 it does seem like there's not a lot of time to get it done, but i guess i can be +1 since it's backwards compatible 15:29:50 alright, I misunderstood 15:29:53 +1 15:30:21 nirik: +1? 15:30:37 +1 15:30:51 #agreed Change is approved for F29. Whatever pieces aren't done by F29 are approved for F30 (+7, 0, 0) 15:31:15 #topic Next weeks chair 15:31:40 any takers? 15:31:43 * jsmith will likely be on the road again next week :-( 15:31:47 i haven't done it in a long time 15:32:03 can the agenda be posted on thursday instead of friday? 15:32:11 Sure :-) 15:32:12 #action bowlofeggs to chair next week's meeting 15:32:12 because i can't do that on friday, sat, or sun :) 15:32:15 hahah cool 15:32:31 bowlofeggs: you haven't done about anything in a long time... :) 15:32:38 haha it's true 15:32:49 i forgot what all these buttons on my computer are for 15:32:57 #topic Open floor 15:33:02 #1nfo bowlofeggs to be useful for a change ;-) 15:33:16 :) 15:33:33 So, on the zchunk thing, I was wondering whether we need an explicit buy-in from Infra before we set a date of shipping 15:33:36 I had one thing 15:33:51 go ahead, puiterwijk 15:34:00 Because it is going to require some infra stuff (specifically, Bodhi checks metadata contents, and this would need to be added) 15:34:18 yeah, I forgot about the bodhi part. ;( Not sure how much work that will be... 15:34:37 (but note we could enable for rawhide first) 15:34:40 (since we've had a number of times where createrepo_c generates invalid/useless metadata, so we have added checks to Bodhi to be very strict in them) 15:35:05 In addition, Bodhi boxes are f27. So we'd need to make sure that all of the build tooling is backported to f27, or we can't until we upgrade the bodhi boxes 15:35:40 yeah good points 15:35:44 i didn't think about the f27 bit 15:37:10 Who are the poeple we should ask about this? Is an infra ticket the right way? 15:37:13 The one part I'm concerned about is that fesco says "ack to f29", and then people are going to go after the infra team "You need to do this *now* because fesco said we'd have everything to deliver this in f29". 15:37:44 i wouldn't say that it's an order from fesco to infra (aka me in this case) to do it by f29 15:37:47 zbyszek: probably me and bowlofeggs are the people backing this 15:37:59 more that fesco is ok with the change, good luck getting it done in time :) 15:38:05 bowlofeggs: right. I'm not saying fesco would order us to. It's more that other people might interpret a fesco ack as that. 15:38:09 I would say we try and do it, if we don't we hit the continngency plan 15:38:29 As long as that's explicit, that's fine with me. 15:38:49 i personally do feel like it might be too ambitious to do by f29, but i'm not opposed to them trying 15:38:56 There's no urgency on this I don't think. It will be very nice to have, but it's not blocking anything... 15:39:08 i also don't know how far along they are in all the other programs 15:39:12 maybe it's further than i think 15:39:20 yeah agree with nirik 15:39:36 agreed too 15:39:38 i think it's probably pretty ambitious, but worst case it gets punted 15:40:16 #info It is understood that infra is busy, and any changes might wait before being merged 15:40:21 Okay. Then EOM 15:40:37 sgallagh? 15:41:42 sgallagh you mentioned you had something… 15:42:23 Sorry, got distracted 15:42:49 Just a minor point that came up while I was away: I think I inadvertently made one change to the new ticket policy when I codified it on the wiki 15:43:09 I'm not sure we ever *officially* agreed that a -1 vote == put it on the meeting agenda. 15:43:19 I think it's a good idea ;) 15:43:29 It seems appropriate, but I wanted to clarify that position 15:44:15 +1 to -1 means a meeting item 15:44:27 +1 to the clarification 15:44:34 Obvious +1 15:45:08 maxamillion, jsmith, jwb, tyll, contyk, bowlofeggs, vote 15:45:10 +1 to clarification - fwiw i thought that's what we had agreed to before 15:45:27 +1 :) 15:45:29 bowlofeggs: I think it may have been in the discussion, but none of the agreed proposals used that wording 15:45:38 yeah maybe that's why i thought that :) 15:45:42 So I was just being thorough 15:45:46 +1 15:46:05 OK, thanks 15:46:28 #agreed The ticket policy is clarified to mean that any -1 votes automatically put the ticket on meeting agenda (as the wiki already states) (+6, 0, 0) 15:46:46 If nobody has anything else, I'll close in one minute 15:46:58 Nothing else from me 15:47:58 * sgallagh scratches another tally mark on the "Ask forgiveness, not permission" board 15:48:12 ;) 15:48:23 python rulez 15:48:37 #endmeeting