16:00:08 #startmeeting fpc 16:00:08 Meeting started Thu Oct 22 16:00:08 2020 UTC. 16:00:08 This meeting is logged and archived in a public location. 16:00:08 The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:08 The meeting name has been set to 'fpc' 16:00:08 #meetingname fpc 16:00:08 The meeting name has been set to 'fpc' 16:00:08 #topic Roll Call 16:00:22 Hey. 16:00:27 .hello2 16:00:28 #chair tibbs 16:00:28 Current chairs: geppetto tibbs 16:00:28 decathorpe: decathorpe 'Fabio Valentini' 16:00:31 #chair decathorpe 16:00:31 Current chairs: decathorpe geppetto tibbs 16:00:38 #chair King_InuYasha 16:00:38 Current chairs: King_InuYasha decathorpe geppetto tibbs 16:01:01 hi there 16:01:08 #chair mhroncok 16:01:08 Current chairs: King_InuYasha decathorpe geppetto mhroncok tibbs 16:03:13 I know carlwgeorge is around 16:03:33 howdy everyone 16:03:33 maybe grabbing a drink or something, back to back meetings are the best etc. :) 16:03:43 #chair carlwgeorge 16:03:43 Current chairs: King_InuYasha carlwgeorge decathorpe geppetto mhroncok tibbs 16:05:07 #topic Schedule 16:05:08 https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/APCEJN2Y6IHEDINPD4G7UUECSRYK4QXY/ 16:05:43 Same schedule as last week … which means not much to do unless anyone has antyhing to talk about, or something has moved and not been updated? 16:07:06 Not really. I started going over some old tickets last night and taking notes on how to deal with them. I will tag them with meeting if there is anything we need to talk about. 16:07:17 ok, cool 16:07:18 Otherwise, I note that we haven't made any kind of guidelines change announcement in ages. 16:08:13 It all gets kind of complicated with PRs and tickets and keeping track of what needs announcing. I kind of wish I could pull announcement text from the git commit log somehow. 16:08:17 yeh, probably worth doing that 16:08:46 I still owe the update for the Rust Packaging Guidelines, I need to write a PR for changes with fedora 34 16:10:33 tibbs: There's no way to see PR merges? 16:11:59 decathorpe: Yeh, I'd thought about keeping some kind of running #action item's on the schedule too … but I wasn't sure if that would feel like me being a giant 💩 16:12:18 There is, but what you get isn't usually something that can just get pasted into an email. 16:12:19 #topic Open Floor 16:12:28 tibbs: Ahh, yeh 16:12:40 Honestly I would have no problem being reminded about what I promised to do but haven't done yet. 16:13:04 keepign track of things is hard 16:13:07 I mean, I still need to figure out where all of the pagure notification emails are going. Lost in the torrent. 16:13:08 yeah that would be fine :) sometimes I forgot to write those things down and then forget completely :( 16:13:23 * geppetto nods 16:13:53 #action geppetto to keep list of #action items in weekly Schedule. 16:14:29 I'm afraid my list would be quite long. But reminding me would help to shorten it. 16:14:50 Ok, unless there's something else ya'll want to talk about I'm going to close and give you all 45 minutes back. 16:15:06 tibbs: You asked for it, don't blame the messenger ;) 16:15:41 We could also reassign things too 16:15:56 yeah that would help 16:16:29 There aren't all that many issues assigned to me; mostly what I need to do is figure out what actually needs to happen for each of them. 16:17:23 tibbs: don't keep all the good stuff for yourself :) 16:17:33 what is the next step for my review exception pull request? 16:17:35 Oh, there's plenty to go around. 16:18:13 carlwgeorge: Merge it, I suppose. 16:18:16 https://pagure.io/packaging-committee/pull-request/1025 16:18:41 yeah. merge it before somebody creates merge conflicts! 16:18:45 It's weird because we voted without having the wording, so it sort of goes into limbo because it's not clear if we need to vote again. 16:19:51 We don't have any kind of restriction on merging your own PRs, and I'm not sure we would want one. 16:20:37 So since you got some acks, I think you should go ahead and merge. (Though I haven't actually looked myself.) 16:20:47 I'd say that, yes 16:20:51 the spirit has been voted 16:20:56 the text has been reviewed 16:20:57 merge 16:21:12 +1 16:21:14 as far as I can tell, the text matches closely what we voted on, and is well written, so I'd say it's fine to merge 16:21:20 it can always be fixed after merging if somebody says "but this is not what was agreed" 16:24:42 excellent, merged 16:24:50 Cool, on that note 16:24:54 #endmeeting