16:01:51 #startmeeting fpc 16:01:51 Meeting started Thu May 7 16:01:51 2015 UTC. The chair is geppetto. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:51 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:51 #meetingname fpc 16:01:51 The meeting name has been set to 'fpc' 16:01:51 #topic Roll Call 16:02:00 geppetto limburgher mbooth orionp racor Rathann SmootherFr0gZ tibbs|w tomspur: FPC ping 16:02:09 Hello 16:02:14 #chair mbooth 16:02:14 Current chairs: geppetto mbooth 16:02:15 Morning 16:02:32 #chair orionp 16:02:32 Current chairs: geppetto mbooth orionp 16:02:54 hello 16:03:02 dwmw2: hey … was just about to ping you too :) 16:05:02 #chair tibbs|w 16:05:02 Current chairs: geppetto mbooth orionp tibbs|w 16:05:06 Howdy. 16:05:11 hey 16:07:07 So, holding at 4? 16:07:12 yeh, atm :( 16:07:28 I assume Rathann or tomspur will turn up 16:07:56 They are both on IRC, just not here atm. 16:08:51 hi 16:09:13 #chair Rathann|Mobile 16:09:13 Current chairs: Rathann|Mobile geppetto mbooth orionp tibbs|w 16:09:16 hey :) 16:09:20 And then there were 5 :) 16:09:31 #topic Schedule 16:09:36 https://lists.fedoraproject.org/pipermail/packaging/2015-May/010638.html 16:09:58 Ok, dwmw2 you want to go first? 16:10:04 #topic #480 Packaging guidelines for consistent PKCS#11 usage 16:10:04 .fpc 480 16:10:04 https://fedorahosted.org/fpc/ticket/480 16:10:05 geppetto: #480 (Packaging guidelines for consistent PKCS#11 usage) – fpc - https://fedorahosted.org/fpc/ticket/480 16:10:05 er, ok 16:10:30 as noted in the ticket, I've tried to make the draft more readable and I've provided some examples 16:11:34 " If your application can certificate" :) 16:12:10 fixed :) 16:17:04 ok, seems fine to me 16:17:35 likewise, +1 from me 16:17:41 Yeah, +1. 16:18:17 If I were prone to bikeshedding, I'd suggest giving bug 1173546 a useful alias so people didn't have to get the number right. 16:18:19 can we change the title to 'SSL Certificate' guidelines rather than 'PKCS#11' ? 16:18:31 tibbs|w: good idea. 16:18:42 "SSL Certificate Handling"? 16:18:50 dwmw2: Maybe SSL Certificate hardware support? 16:18:52 thatworks 16:18:57 no, not *hardware* 16:18:58 definitely not :) 16:19:14 'SSL Certificate' sounds like it would handle generation of certificates as well. 16:19:20 SSL Certificate usage? 16:19:23 Which is a separate proposal that's working its way through. I'd hate to confuse the two. 16:19:42 Well I think when people see "SSL Certificate" they'll assume servers 16:19:52 This is for certs with *keys*. Not just about trust. 16:20:04 "Cryptographic token handling"? 16:20:07 yeah, maybe it's best just left as PKCS#11. 16:20:25 I was after something that people didn't glance at and ignore on the basis that "my package doesn't do that" 16:20:30 when the point is that your package *should* :P) 16:20:38 Yeh 16:21:19 or "Client SSL Certficate Handling"? 16:21:25 is also for servers 16:21:32 Apache should be able to do it (I haven't looked yet if it can) 16:21:35 for example 16:21:42 oh 16:21:44 +1 on the draft, and I'd be fine with "SSL Certificate Handling" 16:21:44 ahh 16:21:47 nmav just prodded me to stop talking just about 'client' :) 16:22:30 https://bugzilla.redhat.com/showdependencytree.cgi?id=PKCS11 16:22:33 there, an alias :) 16:22:34 mbooth: just you left to vote 16:22:43 dwmw2: nice 16:29:27 mbooth: ping? 16:29:27 geppetto: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings 16:29:59 :) 16:30:05 zodbot: context is everything. 16:32:20 mbooth: are you still around? 16:33:39 geppetto: Sorry, had a visitor 16:33:41 Have to step out for a few; sorry. 16:33:42 Yes 16:34:27 +1 for me -- it mostly makes sense to my non-cryptographer eyes 16:34:33 #action Packaging guidelines for consistent PKCS#11 usage (+1:5, 0:0, -1:0) 16:34:36 Ok, cool 16:35:20 dwmw2: If you still want to rename/retitle … put the name in the ticket, and tibbs will dtrt when he moves it to live. 16:35:34 #topic #524 static UID for ceph 16:35:40 .fpc 524 16:35:40 https://fedorahosted.org/fpc/ticket/524 16:35:41 geppetto: #524 (static UID for ceph) – fpc - https://fedorahosted.org/fpc/ticket/524 16:35:42 ok, thanks. I'll go for 'SSL Certificate handling', since I think that had consensus? 16:35:57 I'm fine with either wording 16:36:11 I'm fine with most any title 16:36:53 So the ceph people really seem to want a static uid 16:38:57 Yeah, not sure what to do here. 16:39:15 We were kind of not super against it. 16:39:32 But I doubt we can get +5 today unless opinions have really changed. 16:40:22 I guess I'm a reluctant +1 … I don't think they actually need it, but they aren't arguing rationally anymore either, so meh. 16:40:25 I'm +1 as this seems to be pretty tied to filesystems 16:41:04 Rathann|Mobile: mbooth: vote? 16:41:20 I am +1 I guess too 16:41:26 * mbooth has been fence-sitting 16:41:29 +1, they did raise some valid points about chown taking long to run 16:41:55 I don't really like this, but given that they actually sort of provided info on timing, I can +1 it. 16:42:27 #action static UID for Ceph (+1:5, 0:0, -1:0) 16:42:30 ok, done 16:42:42 #topic #520 [Guidelines Draft] Per-Product Configuration Defaults v2 16:42:42 .fpc 520 16:42:42 https://fedorahosted.org/fpc/ticket/520 16:42:43 geppetto: #520 ([Guidelines Draft] Per-Product Configuration Defaults v2) – fpc - https://fedorahosted.org/fpc/ticket/520 16:42:49 sgallagh: ping, fpc 520 16:42:52 Haven't had time to work on that setup thing, but everything is in place to use it. 16:43:13 (that was for 524 in case not obvious) 16:43:25 geppetto: What's left to do for 520? 16:43:36 oh, the variant thing 16:43:46 but you just did it 16:43:48 Yeah, I just went ahead and took care of it. 16:43:51 * geppetto nods 16:43:58 No point in having a guideline that doesn't match reality. 16:44:05 true 16:44:07 #topic #513 Use python -Es in shbang 16:44:07 .fpc 513 16:44:07 https://fedorahosted.org/fpc/ticket/513 16:44:09 geppetto: #513 (Use python -Es in shbang) – fpc - https://fedorahosted.org/fpc/ticket/513 16:44:27 I haven't had a chance to touch this. Not sure if anyone else has. 16:44:32 no 16:44:49 Can move on then 16:44:50 #topic #508 New GID for openstack-neutron 16:44:50 .fpc 508 16:44:50 https://fedorahosted.org/fpc/ticket/508 16:44:51 geppetto: #508 (New GID for openstack-neutron) – fpc - https://fedorahosted.org/fpc/ticket/508 16:45:00 Is this one still churning. 16:45:02 ? 16:45:23 I mean, some of that is my setup idea, but that really isn't an FPC thing. 16:45:47 hey, I'm not sure what we (FPC) have/can do here 16:46:01 The last really on-topic comment from that ticket was https://fedorahosted.org/fpc/ticket/508#comment:3 16:46:37 I guess I'm thinking "give them an alternate way to do this" and then FPC doesn't have much to do. 16:47:00 But if it turns out that we can't give them an alternative, then FPC does have to at least say "nope" again. 16:47:24 yeh, I guess … it will be much easier to say nope if your setup thing is there :) 16:48:07 But I guess we can move on until I can get something done. 16:48:15 My current project is taking about 130% of my time. 16:48:19 * geppetto nods 16:48:49 I can see it from their POV … but on the other hand, it's really a local thing. Even more so than Ceph. 16:49:22 So it seems a lot better to allow users to configure their local uid/gids how they want than to statically allocate them at the distro level 16:49:24 blah 16:49:26 anyway … 16:49:35 #topic #281 New Python Macros for Easier Packaging 16:49:35 .fpc 281 16:49:35 https://fedorahosted.org/fpc/ticket/281 16:49:36 That's my opinion as well. 16:49:37 geppetto: #281 (New Python Macros for Easier Packaging) – fpc - https://fedorahosted.org/fpc/ticket/281 16:49:52 This is the last one … and I'm not sure what we have to do here either ?:-o 16:49:53 This is really another python thing that needs more buy in from the python folks. 16:50:06 I'm all for simplifying packaging in any way possible. 16:50:41 But I don't think we can just forge ahead without some assent from the python folks, and I haven't had the time to try and stir up more discussion with them. 16:50:53 I'm also still not on the right mailing lists, I think. 16:51:10 A good metric would be, "by how many lines will the python guidelines shrink?" 16:51:28 If it's even a few characters, I'm for it. 16:51:51 I suspect several folks here are far more into python than I am. 16:51:57 python guidelines are quite the mess atm 16:52:03 I agree. 16:52:12 But it's the 2/3 split that makes them really bad. 16:52:19 That and el5/6 support. 16:52:24 Really need a standard spec template 16:53:04 Given all of the 2/3 differences and the lack of modules supporting both, I'm not sure that's feasible. 16:53:25 And honestly in the Fedora guidelines I would prefer to excise all old EL support just to keep them cleaner. 16:55:47 Well in a year or so we could maybe drop all py2 from the Fedora guidlines 16:55:48 I mean, I guess if I get the time I can just go over the current guideline with a chainsaw and see if I can make it less horrible. 16:56:07 BTW, do we have a mandate that things which can work with py3 be built with py3? 16:56:25 I can't recall, but I'm running into that issue with some of the stuff I'm writing. 16:56:41 IIRC the guideline says if upstream supports it 16:57:41 Actually they say you can, but only if upstream supports it. 16:58:28 Which I think should really be "you must if upstream supports it" given that we actually do want to have py3 by default at some point. 16:59:27 isn't it default in f22? 16:59:37 Not as far as I recall. 16:59:54 https://fedoraproject.org/wiki/Changes/Python_3_as_Default 16:59:57 says F23. 17:00:01 I thought it was going to be, got stopped, and then went back to py3 as default 17:00:43 BTW, is there general support for "must build for py3 if supported"? I can make a proposal later. 17:00:58 I mean, I'd +1 it as it seems kind of obvious. 17:01:09 Unless I really can't read and it's already in there. 17:01:53 well half my system wants to go with it if I try to remove it :) 17:03:02 There's no doubt we use it. 17:03:49 yeh, dnf doesn't seem to use it … which I thought it did 17:03:52 I didn't really learn python2; I just started doing "real" coding using python3. 17:04:11 but the desktop is def. broken if you try to remove it … so joy, worst of all possible worlds for f22 17:04:12 I think it can, but they were trying to keep only one python interpreter in the minimal install. 17:04:30 * geppetto nods 17:04:32 Well, I think the rule for desktop is "disk is cheap enough". 17:04:41 yeh, dnf was built for py3 at various points 17:04:47 lol :) 17:04:51 When minimal can go all the way over, then I think it will. I guess check rawhide. 17:05:40 Yeah, in rawhide it wants py3. 17:05:48 itshappening.gif 17:06:42 * geppetto nods 17:07:07 So I'll keep a couple of drafts open for cleaning up/gutting/splitting the current python guidelines. 17:07:26 ok 17:07:33 Hmm, I am on the python-devel list. 17:07:33 #topic Open Floor 17:07:38 It just doesn't have any traffic. 17:07:50 nothing from me and I have to drop off now 17:07:53 We were kind of in open floor anyway … but anything anyone wants to bring up? 17:07:58 sorry and thanks 17:08:01 no problem 17:08:10 and thanks for making 5 Rathann|Mobile :) 17:08:20 We're really getting the ticket count down. 17:08:36 Sorry folks, wasn't around earlier. Were there any questions for me about 520? 17:08:37 I have zero clue at all about the scintilla thing at this point. 17:08:53 sgallagh: I took care of the changes you needed. 17:09:10 tibbs|w: OK, thanks 17:09:15 There was one question at the end of the ticket.... 17:09:23 Not anything you have to answer now, though. 17:10:07 Ah, right. I'll have to think on that. 17:10:29 But scintilla, I mean, someone's going to have to own an actual scintilla package if we want it unbundled. 17:10:34 Though I'm probably okay with not worrying about it until and unless we hit it. 17:10:51 sgallagh: Someone did ask the question on one of the lists; I'm not sure if you saw it. 17:10:52 tibbs: yeh 17:10:57 Might be worth some discussion. 17:11:14 geppetto: The alternative is to just approve scintilla as a copylib and get on with life. 17:11:23 tibbs|w: I didn't see it 17:11:33 sgallagh: I'll try to figure out where it was. 17:11:42 Thanks 17:11:49 scintilla is really way too big to be a copylib, though. 17:12:10 And it almost certainly edits random things that come from the 'net. 17:13:09 And something's bundling like a ten year old version of it. 17:13:27 of course 17:13:45 And I'm sure if we looked harder we'd find something else that bundles it. 17:13:52 At least it's all tracked properly now. 17:14:07 that's what bundling is for … it's like the I installed Fedora 7 and just never turned it off method of maintenance 17:14:32 But I don't think that's sufficient to just get rid of the ticket, and I'm not the one to either package the unbundled scintilla or fix the packages to use it. 17:14:53 Might be able to twist rdieter's arm a bit. 17:15:15 Also nobody seems to want to do the work to determine how their bundled copies have been modified. 17:15:49 We don't really have any power unless we want to just decide we can force things to be pulled from the distro. 17:16:08 * geppetto gets out the cabal decider stamp 17:16:10 I mean, between us we certainly have enough access to do that. 17:16:33 But I would really hate to think we'd get to that point over some editing library that's not had a known security issue. 17:16:50 Which leaves us at, uh, pretty much where we're at. 17:17:03 tibbs|w I could look at it someday, been meaning to really, just lots of other higher priority stuff to do 17:17:12 rdieter: You're not the only one. 17:17:29 Do you know if qscintilla is modifying its bundled copy? 17:17:38 next kid-at-home-sickday, I'm all over it 17:17:39 It's almost up to date, so I'd think it's pretty close. 17:17:50 tibbs|w: i don't know 17:18:06 I guess that's the next step. 17:18:07 I would guess no, or minimally 17:18:16 they rebase semi-frequently 17:18:47 It's certainly not supposed to work as a shared lib. Static would be OK with me, I guess. 17:18:58 But if it would work, that would be doubly awesome. 17:20:19 Anyway, I'm sure everyone has work to do. 17:20:32 yeh 17:20:48 See ya all next week 17:21:03 #endmeeting