16:01:22 #startmeeting fpc 16:01:22 Meeting started Thu Apr 20 16:01:22 2023 UTC. 16:01:22 This meeting is logged and archived in a public location. 16:01:22 The chair is geppetto. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:01:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:22 The meeting name has been set to 'fpc' 16:01:22 #meetingname fpc 16:01:22 The meeting name has been set to 'fpc' 16:01:22 #topic Roll Call 16:01:34 Blah … late and unprepared, let's go. 16:01:51 let's-a-goo 16:02:05 #chair decathorpe 16:02:05 Current chairs: decathorpe geppetto 16:03:01 it's-a-me, Fabio 16:03:23 haha 16:03:27 .whatever 16:03:36 :D 16:03:44 #chair GwynCieslasheher 16:03:44 Current chairs: GwynCieslasheher decathorpe geppetto 16:03:50 I....guess I'm in another castle? 16:05:25 mamma mia 16:05:31 is it only us three? 16:05:49 Unless I'm very bad at counting 16:08:04 If so you're compensating pretty well, life-wise. 16:09:15 I can get to ten using my fingers, unfortunately they are AI generated so who knows what base that's in. 16:09:53 #topic Open Floor 16:10:26 Nothing much is happening AFAICS, anything anyone wants to talk about? 16:10:45 nothing in particular 16:12:02 i'd love some feedback for my mingw packaging guidelines proposal 16:12:15 https://pagure.io/packaging-committee/pull-request/1260 16:13:45 (and i'm still kinda fuzzy on the process for officially getting changes on the FPC meeting agenda for discussion) 16:14:25 .fpc 1259 16:14:26 geppetto: Issue #1259: Update mingw guidelines to document integrated packaging approach - packaging-committee - Pagure.io - https://pagure.io/packaging-committee/issue/1259 16:14:43 I think explicitly getting it onto the meeting agenda would be "tag the ticket with `meeting`"? 16:14:44 I tagged the issue and PR with meeting, so it'll show up prominently 16:14:55 AFAIK, i have no ability to tag tickets 16:15:10 meh 16:15:12 Yeh, only FPC people can do it. 16:15:30 bit of a chicken + egg scenario :-) 16:16:06 In theory we go through the open tickets and see which ones are ready to be discussed at the meeting … but in practice you probably want to ping someone. 16:16:29 so as far as I can tell the PR is just about documenting new best practices? 16:16:38 I'm not personally super experienced with mingw; are there plans for a large scale migrations hinging on these changes? 16:16:40 Anyway, it's there now … and it looks okish … hopefully can get it merged soon. 16:16:42 anyway, if anyone wants to add comments on the PR, i'd be grateful 16:17:11 I've never done mingw packaging, so I'd kind of trust you on the details, but I'll look at the text for anything non-domain-specific :) 16:17:16 there's no proposal to force / mass migrate packages -it is at the discretion of the existing maintainers 16:18:21 what's possibly most interesting for FPC input is the impact the new guidelines have on native package maintainers 16:19:12 👀 16:19:16 because its steering towards having mingw be a sub-rpm which obviously requires buy-in from the existing native maintainer 16:19:38 we want to push towards that model reasonably strongly as we believe it reduces the maint burden for fedora as a whole 16:20:02 I assume you generally cooperate a lot with the native package maintainer? 16:20:10 but at same time don't want to force this unconditionally onto native maintainers if they're not comfortable 16:20:56 some packages have the same person owning both native + mingw, so that's an easy case where this is a clear win 16:21:30 in cases where there are separate maintainers for native and mingw, they've typically worked fairly independantly 16:22:10 which is what has resulted in mingw packages often being behind native 16:22:51 lines 22 -> 86 talk about this problem and the recommended practices https://pagure.io/fork/berrange/packaging-committee/c/f7a9312ccc8a6cf1f959473ca47a76f9be6971a3 16:23:40 and line 62-86 are where FPC might have some particular opinions 16:25:21 * geppetto nods … seemsmostly fine to me 16:25:45 But def. need quorum 16:25:55 Same and yes. 16:26:55 ok, i've got to address the comments from ferdnyc on it too, but good to know it looks broadly ok 16:27:26 Ok, cool … Anyone have anything else? 16:30:18 Ok, enjoy your free 30 minutes 16:30:20 #endmeeting