16:01:18 #startmeeting fpc 16:01:18 Meeting started Thu Jul 23 16:01:18 2020 UTC. 16:01:18 This meeting is logged and archived in a public location. 16:01:18 The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:18 The meeting name has been set to 'fpc' 16:01:19 #meetingname fpc 16:01:19 #topic Roll Call 16:01:19 The meeting name has been set to 'fpc' 16:01:24 Thanks siddharthvipul 16:01:49 Hey. 16:01:52 hello ö/ 16:01:54 hi 16:02:06 * limburgher here 16:02:10 #chair tibbs 16:02:10 Current chairs: geppetto tibbs 16:02:12 #chair mhroncok 16:02:12 Current chairs: geppetto mhroncok tibbs 16:02:15 #chair limburgher 16:02:15 Current chairs: geppetto limburgher mhroncok tibbs 16:02:26 #chair decathorpe 16:02:26 Current chairs: decathorpe geppetto limburgher mhroncok tibbs 16:03:04 .hello ngompa 16:03:06 King_InuYasha: ngompa 'Neal Gompa' 16:04:04 hey Neal o/ have you officially joined us? ;) 16:05:03 * geppetto quickly assigns all the tickets to neal 16:06:26 oh dear 16:06:34 I dunno, but I figure I'd show up 16:06:57 * limburgher locks the door 16:07:23 the meeting won't end until we solve all the tickets, right? 16:07:30 * King_InuYasha looks worried 16:07:30 :D 16:07:46 hahaha 16:08:25 #topic Schedule 16:08:29 #link https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/47AODIXTYLCTQPUTH6IB6GWIPN3DLUNN/ 16:08:42 #topic #1007 Golang pkg review exception to update a lot of packages 16:08:45 .fpc 1007 16:08:49 geppetto: Issue #1007: Golang package review exception to update a lot of packages - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/1007 16:09:26 eclipseo: hey 16:09:41 hi 16:09:54 in principle, I'm fine with this. I know Go packaging is a bit of a mess and they make new dependencies like rabbits make little rabbits 16:10:22 I'm okay with it too 16:10:30 as a Go SIG member, I approve of this too 16:10:30 though it would be nice to have a list of new packages (even a WIP list) that the exception applies to. 16:10:35 yeah 16:11:00 * mhroncok would feel more comfortable having the bunch of spec files to inspect rather than giving a blanket exception 16:11:05 Yeh, I was +1 with it but then mhroncok was worrid enough to want a list 16:11:07 I have posted 6 that are waiting on my last comment, they are the one I have for the 90 packages I have tested so far 16:11:09 but I can acks this as well if that is unrealistic 16:11:22 The only issue with a blanket exception is the bit about licenses being autodetected. 16:12:02 I use askalono-cli which is a tool dev by Amazon to detect license files 16:12:23 tibbs: this isn't like the old days though … now developer upload to github and github sees what the licesnes is, or bugs the developer about it until it finds out 16:12:36 I mean, I don't have many things to do this week, I can be on standby to ACK package reviews and manually check licenses. 16:12:52 And does legal trust those processes and tools? 16:12:53 ef there is no license files then I bother upstream of course 16:12:57 eclipseo: Does that check github, or just the data? 16:13:01 decathorpe: I can imagine time better spent :) 16:13:11 .hello2 16:13:11 ignatenkobrain: ignatenkobrain 'Igor Raits' 16:13:13 that check all the files in the repo 16:13:16 sorry for being late 16:13:19 mhroncok: sure ... I could fix more Java packages 16:13:23 #chair ignatenkobrain 16:13:23 Current chairs: decathorpe geppetto ignatenkobrain limburgher mhroncok tibbs 16:13:25 decathorpe: exactly :D 16:13:44 Really, legal review is the sole reason package review is necessary in many cases where packaging is autogenerated. 16:14:21 OTOH I bet many package reviews don't do better job than askalono 16:14:26 So if legal is OK with us bypassing things, then I would be happy to consider expedited process for whole classes of autogenerated packages. 16:14:52 one of these days, I'll get cavil working... 16:15:04 King_InuYasha: once everyhting else is done :D 16:15:08 :D 16:15:22 you know it! 16:16:00 eclipseo: is it unreasonable to generate them all and past for sanity check? I don't know how you operate 16:17:31 generate them all? I'm not sure I follow, I can't know what I will need right now 16:17:46 Oh, Go, never change. 16:18:11 * King_InuYasha sighs 16:18:11 basically the problem is that when you start packaging A, then you have to package B and C and thousands of deps for them :) 16:18:19 There is very complex dependency graph, some app have chain of deps that goes to 800 packages 16:18:27 I'll fire off a message to fedora-legal and see if we can get an answer. 16:18:39 eclipseo: somebody said k8s? 16:18:50 +1 to review exception assuming legal is OK with this 16:19:40 k8s is tricky 16:19:40 but less than docker 16:19:44 docker use pinned repository and trivial forks 16:20:02 +1 same as mhroncok (and otherwise I think I can spare a few minutes to check some packages manually every day) 16:20:17 #action tibbs to Make sure fedora-legal are ok with this 16:20:24 *cough*terraform*cough* 16:20:30 But, yeh, I'm fine with it all in theory 16:20:32 uhh, does anyone one know *who* fe-legal is now? 16:20:49 spot & rfontana? 16:20:56 Still see messages from spot and Ruchard Fontana in the mailing list. 16:20:57 not spot 16:21:11 Though that list is pretty low traffic. 16:21:28 so still same black box :) 16:21:38 Pretty much. 16:22:15 I mean, a decision could just be made and then someone could come along and say it was a bad idea after the fact. 16:22:44 should I ask myself to legal? 16:23:31 Well if you prefer; I was typing the message already but I can stop. 16:23:39 no it's ok 16:24:01 Just precise that I do check the license files manually too 16:26:11 #topic #pr-988 Don't obsolete debuginfo packages 16:26:11 https://pagure.io/packaging-committee/pull-request/988 16:26:37 Seems like a trivial +1 16:27:07 * mhroncok was +1 in the ticket 16:27:11 Agreed, +1 16:27:31 +1 from me too, ideally dnf would just automagically remove them, but oh well 16:27:55 this is fine 16:28:03 To be clear: there's no automated process that adds these obsoletes, it's all done manually by a misguided maintainers? 16:28:14 tibbs: yes 16:28:41 I mean, dmlite still uses %defattrand has conditionsls for %fedora >= 17, so.... 16:29:40 +1 16:30:05 Though to be nitpicky, the PR needs sembreaks and a lint for grammar. 16:30:54 +1 16:32:05 (my +1 is for the rule, not for merging immediatelly as is.) 16:32:29 #action Don't obsolete debuginfo packages (+1:5, 0:0, -1:0) 16:32:45 #topic #pr-1006 Update CMake guidelines 16:32:45 https://pagure.io/packaging-committee/pull-request/1006 16:33:06 * mhroncok hasn't read this yet 16:33:56 this is fine (and already deployed in rawhide?) 16:34:08 yes, and backported to f31/f32 16:34:26 should have done it long ago, but did not have time :/ 16:34:40 diff is small and looks good, +1 16:34:47 Looks ok to me. Wish I'd seen it before one of my packages hit it but that's on me. :) 16:34:50 +1 16:34:59 yeh, adding a param. doesn't seem like a big deal :) 16:35:04 +1 16:35:46 +1 in general, haven't checked the syntax etc. 16:36:11 So what happens if packages still use %make_build and %make_install instead of %cmake_*? 16:36:34 make != cmake … so they are fine? 16:36:42 tibbs: in f33, they have to add use `-C %{_vpath_builddir}` or `%global __cmake_in_source_build 1` 16:36:51 that is basically change: https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds 16:37:38 I wonder how many things that breaks. Using %make_build with cmake has been the norm for basically forever. 16:37:49 it breaks a lot fo packages 16:38:00 but it already has 16:38:26 tibbs: we've already managed to fix around 1k packages out of 1.8k 16:38:29 Having this in the guidelines would help people fix it faster. 16:38:34 yes 16:39:07 I don't disagree; just trying to understand the issue. The decision to make the underlying change was already done (and I would argue is a mistake, but that's not up to us). 16:39:40 +1 16:39:59 well, this PR for the Packaging Guidelines only aligns them with the new reality 16:40:09 Yes, of course. 16:40:48 #action Update CMake guidelines (+1:5, 0:0, -1:0) 16:41:23 #topic #pr-938 Add Package Review Process page. 16:41:23 https://pagure.io/packaging-committee/pull-request/938 16:41:43 I didn't think the guidelines were the place for this. 16:42:53 I am fine either way 16:43:32 well, we should verify that the content is actually still the same 16:43:54 If so, i'm on board. 16:44:30 tibbs: where did you want to put it? 16:44:49 The wiki seems a reasonable place for a community-maintained document. 16:44:55 tibbs: Just have it as a normal wiki page that anyone can change? 16:45:09 I guess I'm fine with that 16:45:09 Hasn't it always been that way? 16:45:16 * geppetto has no idea 16:45:57 I think it is not a bad idea to have such documents in one place, maintained by same people and with a same dialect of source code 16:46:23 Depends on what you mean by "such documents". 16:46:46 It seems a bit weird to me that the actual Guidelines are all together but the document that outlines what to do with them doesnt 16:46:50 There is a rather big difference between something the community is welcome to edit and something that is protected by committee process. 16:47:45 I don't see this document as telling you how to apply the packaging guidelines at all. 16:48:49 This a about bugzilla states and blocker tickets. 16:49:26 The ReviewGuidelines page is more abuit applying the guidelines, and it is under the Packaging: hierarchy. I don't know if it ever got moved or cleaned up in the new system. 16:52:30 * decathorpe shrugs 16:53:41 tibbs: You want to move it to the right place in the wiki? 16:53:59 What place would be better than where it is now? 16:54:40 I wasn't sure if it needed to be moved 16:55:01 So I guess we just close it and tell them to alter it directly? 16:55:37 I'm fine with that 16:56:10 Well, I mean, I'm just one person with an opinion. If others feel confident moving the thing to be under the umbrella of the guidelines then that's fine. 16:56:22 #info No need for FPC to own this document, can leave it being commnuity maintained. Feel free to do any changes directly 16:56:27 I feel like the wiki to docs transition is still a bit messy 16:56:41 I would think this belong to docs, but I'm not arguing about it 16:56:43 That's an understatement. 16:57:02 yeah :sad face: 16:57:06 tibbs: I didn't want to sound harsh, it is a total mess :D 16:57:15 I've heard King_InuYasha will fix it 16:57:21 wait what?! 16:57:24 :D 16:57:26 Sounds good 16:57:30 oh no 16:57:33 * King_InuYasha dies 16:57:37 Well the automated conversion simply wasn't remotely as good as what was sold to us. 16:57:37 *action King_InuYasha will fix it 16:58:01 oh no 16:58:05 I can't fix this :( 16:58:16 though it should really be in docs system instead of wiki 16:58:44 #topic Open Floor 16:58:53 But how do you have a community maintained document in the docs system? 16:58:59 ... PRs? 16:59:17 well, if somebody reviews thaem, maybe :P 16:59:22 That's kind of the opposite of community maintained. 16:59:33 I guess we didn't talk about 977 … I guess that's done now, unless King_InuYasha wants to volunteer after the fact 16:59:37 someone is the steward of the package review process docs? 16:59:39 .fpc 977 16:59:40 geppetto: Issue #977: Get new members? - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/977 16:59:50 I'm happy to join fpc if wanted 16:59:59 I'd also volunteer carlwgeorge too :P 17:00:01 I would think the community would be the steward of things. 17:00:23 Would have been cool to apply in the tiny 2 month window ;) 17:00:33 Maybe that's comically utopian and wikis are just not the way things are done any more. 17:00:45 🔥 17:01:23 geppetto: I didn't know :o 17:01:24 * bcotton peeks in the window 17:01:40 oh no, it's 2020 out there 17:01:41 geppetto: well, do we want to turn away volunteers when we're short-handed anyway? 17:01:46 it only kinda showed up because mhroncok pointed it out to me :P 17:01:53 * decathorpe waves at bcotton 17:01:56 * limburgher pulls blinds 17:01:57 me? no way 17:02:20 tibbs: The new new thing is git + hugo … so I assume we'll all be porting to that rsn. 17:02:39 sustainability ftw! 17:03:08 huh ... that's almost what I wanted them to do in the first place :O 17:03:32 (though Jekyll actually has an official asciidoc plugin) 17:04:45 * bcotton glares in i-have-this-room-reserved-now :-) 17:04:59 bcotton: deal with it, FPC is slow :D 17:05:09 bcotton: We also started late … so blame infra ;) 17:05:16 bcotton: want to join? there was a window 17:05:16 I'm done. Will finish up that message to legal and add my comments to 938. 17:05:37 I'm done as well 17:05:39 yeah, let's end 17:05:42 bcotton: what is the meeting baout? 17:05:47 *about 17:05:54 Council meeting 17:05:54 * dgilmore looks at bcotton 17:05:55 Anyway … we should be nice. I'll end it now. 17:06:02 #endmeeting