16:00:20 #startmeeting fpc 16:00:20 Meeting started Thu Oct 8 16:00:20 2015 UTC. The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:20 #meetingname fpc 16:00:20 #topic Roll Call 16:00:20 The meeting name has been set to 'fpc' 16:00:26 hello 16:00:31 * tomspur waves 16:00:44 #chair orionp 16:00:44 Current chairs: geppetto orionp 16:00:47 #chair tomspur 16:00:47 Current chairs: geppetto orionp tomspur 16:00:51 Howdy. 16:00:54 #chair tibbs 16:00:54 Current chairs: geppetto orionp tibbs tomspur 16:00:57 hey 16:01:05 #chair Rathann 16:01:05 Current chairs: Rathann geppetto orionp tibbs tomspur 16:02:12 * racor is here, too 16:02:17 #chair racor 16:02:17 Current chairs: Rathann geppetto orionp racor tibbs tomspur 16:03:38 mbooth: FPC ping ? 16:03:46 Hey 16:03:52 Was in a world of my own 16:04:09 #chair mbooth 16:04:10 Current chairs: Rathann geppetto mbooth orionp racor tibbs tomspur 16:04:18 #topic Schedule 16:04:23 https://lists.fedoraproject.org/pipermail/packaging/2015-October/011043.html 16:04:39 #topic Rant about bundling 16:04:47 Ok, might as well get it out ;) 16:04:54 I ranted in the FESCo meeting, so I'm all ranted out. 16:05:00 * geppetto nods 16:05:01 yeah, I'm good 16:05:05 I'm glad that at least one of us was there. 16:05:09 note: I think fesco would be open to changes... 16:05:26 I watched for awhile but had to leave... 16:06:20 I was trying to gather info on what FPC role could be in a more relaxed bundling world, but then the vote just went on, so... 16:06:28 I think that if FESCo as a body was interested in FPC input, it would have waited to receive some, so... 16:06:49 Anyway, I did submit a draft to implement the policy as dictated. 16:07:16 well, I think there was some of "I am tired of this, lets just do something" and also "lets do something and have people propose changes to it" 16:07:22 Ahh, https://fedorahosted.org/fpc/ticket/575 … you want to do that now? 16:07:53 It seems FPC has a very bad reputation marketing wise, which is now also solved as the FPC is not involved anymore 16:08:09 Yeh, people who say no often do 16:08:16 Indeed. 16:08:25 Esp. in Fedora where we are basically the only people who ever say no 16:08:37 * geppetto shrugs 16:08:40 We never even said no to the case which precipitated all of this. 16:08:48 Which makes it all the more hilarious. 16:08:54 Sure, but it was possible 16:09:18 I guess the possibility of us saying no to something in the next week or so was too much to bear. 16:09:22 Much better for everyone if they can just do whatever crazy thing they want and everyone else pays for it 16:09:31 Well, what's done is done. 16:09:38 Should we add to the new guidelines a kind of note, what "would be good to consider", when one bundles? 16:09:52 tomspur: FESCO having taken over the job and responsibility is the only advantage of their decision ;) 16:09:52 tomspur: Not our business any longer. 16:10:21 The policy as dictated says only that they have to ask upstream and record upstream's answer. 16:10:22 I am hoping and expecting it will back-fire at them. 16:10:30 It would still be nice to at least 'info' what we think about the policy. 16:10:45 racor: This would be one 'info' :) 16:11:09 tomspur: I don't you nor FESCO want to know what I think about this decision! 16:11:10 tomspur: I mean, if someone wants to draft an "official FPC response" or something, great. 16:11:13 At this point I think we should just try to keep the guidelines simple 16:11:24 ... don't think ... 16:11:31 But I go on vacation tomorrow and am looking forward to not worrying about this. 16:12:14 orionp: +1 … just write what FESCo voted on 16:12:29 Anything else like seems pointless. 16:12:56 It would be enough for me to say, that it is too easy to just bundle and like FESCo to reconsider. Then implement the decision from yesterday... 16:13:41 Anyway, that's what the draft I submitted does. 16:14:29 I wish I had rewritten all of the bundling stuff earlier; if it had been clearer and perhaps more concise, we might not have been in this situation. 16:14:36 doubt it 16:15:18 tibbs|w: I'm not convinced about that :-) 16:15:49 Well, there were multiple different sets of complaints and at least some of them were more about our pages than the actual policy. 16:16:21 But now we get to delete them all. So how about it? Anyone take issue with my draft in 575? 16:16:49 +1 16:17:01 No, it looks fine to me 16:17:02 +1 16:17:06 https://fedoraproject.org/wiki/User:Tibbs/BundlingDraft2 as well as "deleting" the two standalone pages on bundling. 16:17:09 +1 obviously. 16:17:11 tibbs|w: The draft doesn't say why a packager needs to "make every effort to avoid bundling". 16:18:05 tomspur: I don't think that's a thing anymore 16:18:06 +1 ... under protest! 16:18:08 tomspur: That sentence was in the original policy. I can delete it as well, but usually we don't include justification. 16:18:27 I guess my leaving it in was a bit of passive aggression. 16:18:44 But I can understand, that you want to keep it simple and wait for the "release early, release often" attitude of FESCo. 16:19:28 +1 for the record. 16:20:20 Well, +1... 16:20:35 mbooth: Rathann: vote? 16:20:51 eh 16:21:23 what if it's not possible to determine the version? 16:21:36 Anyway, I expect we'll need to refine things further and I don't think FESCo would complain as long as we don't put ourselves back in the loop. 16:21:49 Rathann: No clue; that's the exact tag FESCo told us to use. 16:22:10 At this point I didn't want to deviate materially from the language they instructed us to implement. 16:22:17 Yeah +1 16:23:07 *shrug* +1 16:23:49 #action Bundling Guidelines Overhaul (+1:7, 0:0, -1:0) 16:24:38 #info For what it's worth nobody in FPC seems to be of the opinion that this was a good change. 16:24:44 * geppetto shrugs 16:24:59 geppetto: thanks 16:25:02 #topic #567 Packaging Python 3 applications and modules for EPEL 7+ 16:25:03 .fpc 567 16:25:03 https://fedorahosted.org/fpc/ticket/567 16:25:04 geppetto: #567 (Packaging Python 3 applications and modules for EPEL 7+) – fpc - https://fedorahosted.org/fpc/ticket/567 16:25:13 And now back to python policy :) 16:26:06 So, tomspur and I have been playing with this. 16:26:36 It's not done; in particular it doesn't yet handle %files or additional dependencies for the subpackages. 16:26:54 But it's getting there. and personally I think it's kind of nice. 16:27:10 spectool-py looks nice. 16:28:27 tomspur: Yeah. Right now it doesn't download, but it at least gets the right sources and patches for me where often spectool didn't. 16:28:33 Hmm, does it make sense to have denyhosts built for several implementations? 16:28:50 tomspur: No, that's just a spec I was using to test the spectool thing. 16:29:03 Not the macros thing. 16:29:05 ok 16:29:21 Anyway, I've set out to make sure these macros don't conflict with any existing usage. 16:29:57 I need to do a mass rebuild of all python packages locally to make certain that they don't confuse anything. 16:30:46 How do you envision specifying requires looking like? 16:30:48 Anyway, more work to do on that, but if anyone has any suggestions, please let me know. 16:31:13 orionp: Probably either arguments to the subpackage section or some other macro to set them. 16:31:31 Auto-substituted for different python versions, of course 16:31:57 can you set a variable/macro in lua that can then be referenced later in another macro? 16:32:18 Yes. 16:32:25 really? 16:32:26 Look at %py_init. It sets global functions. 16:32:31 So it's the same lua instance for each package? 16:32:36 Indeed it is. 16:32:51 There's actually a whole lot you can do that nobody seems to know about. 16:33:24 in lua, everything's global anyway unless you stick local in front of it, and that global table persists. 16:36:00 Anyway, I tried to comment everything so the magic isn't quite so magical. 16:36:10 * geppetto nods 16:36:15 It's pretty nifty 16:36:24 Is there anything we want to vote on this week? 16:38:15 Unless folks want to say "please don't do this", I guess. 16:38:43 I'm basically going to throw in every convenience macro I possibly can and then if people think that hides too much then I can take that out of the package. 16:38:46 nope, I think it's looking good, thanks for working on it 16:38:57 Would it make sense to have a general fpc-macros package and not just python-macros? 16:39:14 Yeh, keep going we'll see how far the rabbit hole goes :) 16:39:33 I'll also draft the necessary guidelines changes to go with this. 16:39:59 I am actually finding this kind of fun. I'll have a set of requests to the RPM devs once I'm done, that's for sure. 16:40:08 cool 16:41:31 #topic #558 Application/Library distinction and package splitting 16:41:31 .fpc 558 16:41:32 https://fedorahosted.org/fpc/ticket/558 16:41:33 geppetto: #558 (Application/Library distinction and package splitting) – fpc - https://fedorahosted.org/fpc/ticket/558 16:41:55 So … more python stuff :) 16:42:11 I haven't messed with this. 16:42:21 Besides changing the title to make more sense. 16:43:00 not just python, this is generic 16:45:29 Anyway, I bodged up that draft but I'd really like it if someone took a pass over it. 16:45:58 * geppetto nods … although I think python is somewhat special here as it's somewhat common for a library to also contain the program bits if called as main etc. 16:46:06 * geppetto nods 16:46:33 #topic Open Floor 16:47:03 Anything anyone wants to bring up? 16:48:31 geppetto: Pretty common to most interpreted languages, really. 16:48:44 I closed all of the existing bundling tickets, so the count went down. 16:48:50 kind of 16:49:13 I feel like perl had a clearer split 16:49:39 orionp: Could you maybe test the python_provide macro etc on epel7? 16:49:40 between modules and programs … where a lot of python the "program" is just a couple of lines to run the module in program mode. 16:49:58 Maybe just me and my memory though 16:50:07 I'm about to push the latest changes of Fedora's python_provide macro there and all current macros should be out everywhere. 16:50:21 Anyway … thanks for coming! 16:50:31 tomspur - I'll try 16:50:41 #endmeeting