18:01:33 #startmeeting FESCO (2014-01-08) 18:01:33 Meeting started Wed Jan 8 18:01:33 2014 UTC. The chair is t8m. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:34 #meetingname fesco 18:01:34 The meeting name has been set to 'fesco' 18:01:34 #chair abadger1999 mattdm mitr mmaslano notting nirik pjones t8m sgallagh 18:01:34 #topic init process 18:01:34 Current chairs: abadger1999 mattdm mitr mmaslano nirik notting pjones sgallagh t8m 18:01:42 Hello all 18:01:43 hi 18:01:43 morning everyone. 18:01:45 hello1 18:01:46 .hellomynameis sgallagh 18:01:48 sgallagh: sgallagh 'Stephen Gallagher' 18:01:54 happy new year, everybody 18:02:03 I'm splitting my attention with Server PRD planning, so apologies if I'm slow to respond 18:02:06 * notting is here 18:02:15 Yep, happy new year to everyone 18:02:49 I hope this time the meeting will be quite short 18:03:05 hahahah. 18:03:09 i mean yes 18:03:13 :) 18:03:47 abadger1999, mitr, around? 18:03:55 Hello 18:03:58 let's start then 18:04:05 * abadger1999 here but extricating from other discussions 18:04:10 #topic #1132 libtool + %global _hardened_build 1 = no full hardening 18:04:14 .fesco 1132 18:04:16 t8m: #1132 (libtool + %global _hardened_build 1 = no full hardening) – FESCo - https://fedorahosted.org/fesco/ticket/1132 18:05:07 So any volunteer to apply the new %configure hack? 18:05:44 or do we need to vote first whether it should be applied? 18:05:47 * nirik looks to see where we were. 18:07:25 ok, yeah, sounds like we were ready to try the latest patch in rawhide. 18:07:34 * mattdm nods 18:07:48 #proposal Apply the %configure hack (with possible opt-out) as of https://bugzilla.redhat.com/attachment.cgi?id=838954 18:08:01 +1 18:08:04 +1 18:08:07 +1 18:08:09 +1 18:08:10 +1 18:08:11 +1 18:08:20 +1, please announce on fedora-devel 18:08:54 so, who wants to apply and announce? ;) 18:09:31 * nirik listens to crickets, guess that means me. 18:09:34 #agreed Apply the %configure hack (with possible opt-out) as of https://bugzilla.redhat.com/attachment.cgi?id=838954 (+7, 0, 0) 18:09:42 heh :) 18:09:53 not sure how fast I will get to it, but can try 18:09:56 nirik, thanks for volunteering 18:10:07 (for the record, +1) 18:10:25 #action nirik will apply the patch and announce it on fedora-devel 18:11:02 #topic #1198 Possible changes to Fedora EOL bug procedure 18:11:07 .fesco 1198 18:11:08 t8m: #1198 (Possible changes to Fedora EOL bug procedure) – FESCo - https://fedorahosted.org/fesco/ticket/1198 18:11:32 I'm going to look through bugs closed as wontfix this cycle 18:11:38 and contact some of the users affected 18:11:42 and see if they can reopen 18:11:59 i would like to leave the ticket open but take it off the agenda 18:12:04 until i can do that project 18:12:15 OK 18:12:23 thanks, mattdm 18:12:26 next topic 18:12:43 #topic #1213 Please process commit access requests for spampd 18:12:49 .fesco 1213 18:12:50 t8m: #1213 (Please process commit access requests for spampd) – FESCo - https://fedorahosted.org/fesco/ticket/1213 18:13:16 oddly, I saw an email on another list from him today... 18:13:42 So I am not sure the nonresponsive maintainers policy was followed completely 18:14:11 the process is pretty long and unweidly sadly. 18:14:24 yep 18:15:00 Yeah, that process really seems to be weighted towards lazy owners rather than willing maintainers. 18:15:39 I think that's a conclusion unsupported by data 18:15:49 I could see some improvement or fasttrack process if the maintainer was not appearing anywhere for a long time. 18:15:58 t8m: that might be a good idea 18:16:03 for EOL - we have one week left 18:16:05 it's difficult, because the world isn't black and white. 18:16:14 nirik: that's right 18:16:18 +1 nirik 18:16:24 dure 18:16:29 sure that is 18:16:43 the biggest assumption our current process makes is that the current maintainer probably has the most domain experience with the package 18:16:50 which may or may not be true, but often is 18:17:05 has anyone attempted to contact mattias in other channels? 18:17:07 and so it's weighted heavily towards keeping the incumbent in unless there's a good reason not to 18:17:52 mattdm: I just sent him email 18:18:04 I see the posts to the devel list didn't cc him (as I think the policy asks) 18:18:08 nirik okay so i won't press send on the one i was writing. heh 18:18:49 policy doesn't seem to ask that, but it seems to imply other attempts at contacting the maintainer 18:18:54 #proposal Wait a week for eventual response to direct mail from Matthias 18:18:56 I guess the other big assumption it makes is that when people say they're following the process, they are 18:19:08 pjones: right, it's pretty free form 18:19:16 t8m: +1 18:19:20 which maybe we could provide a checkbox-list form for the reporter to fill out for the ticket? 18:19:22 pjones: which is not much different than the rest of our discretionary policies 18:19:36 part of the process is "all reasonable efforts to contact the maintainer have failed", and that's open to a lot of interpretation 18:19:38 [ ] the owner has been contacted directly 18:19:48 pjones: but yes, automation / acutal *processing* good 18:19:49 [ ] the owner has been contacted on f-d-l and was on the cc list 18:20:11 [ ] I have feelings and deserve dignity which I will demand by doing a good job at this checkybox form 18:20:14 #proposal note that nirik sent an email, revisit next week 18:20:19 +1 18:20:28 lol pjones 18:20:48 pjones: per the theoretical process we shouldn't even be getting a ticket, but reacting on fedora-devel 18:20:50 we did have a proposal a long time ago to do a timeout on acl requests. 18:21:02 mitr: that's true, and occasionally it even works that way 18:21:22 ie, you ask for commit on a package, if the maintainer doesn't say yes or no after X time, it autoapproves you and you can work on the package 18:21:27 mitr: I suspect the timing of this request in terms of holidays is to its detriment. 18:21:41 proposal? (Really not sure) After step 5 of http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers, add "File a FESCo ticket to get an ack" 18:21:43 +1 to myself or mattdm's proposal as it is basically the same 18:21:57 nirik: ... which works a lot better in february than in august if the maintainer is, for example, in france... 18:21:57 +1 to mattdm 18:22:13 pjones: yeah, depending on how long X is. 18:22:52 * mattdm did not see t8m's earlier proposal. i agree that they're basically the same. 18:23:15 mitr: in practice thats what seems to usually happen anyhow. ;) 18:23:47 Please vote :) 18:24:13 t8m +1 to yours too if that helps :) 18:24:40 oh, for 'wait for a week'? +1 18:24:51 mattdm: +1 18:25:54 #agreed Nirik sent direct e-mail, we will revisit next week (+7, 0, 0) 18:26:01 (with some sloppy counting) 18:26:19 #topic #1216 Requesting input on FESCo Badge concept 18:26:24 .fesco 1216 18:26:25 t8m: #1216 (Requesting input on FESCo Badge concept) – FESCo - https://fedorahosted.org/fesco/ticket/1216 18:27:41 I think it should say "Ultima Ratio Regum" on it some place. 18:27:48 ha 18:27:50 So I don't really have any idea what should be on FESCo ex-member badge 18:27:53 * nirik doesn't too much care. 18:28:08 the badges artwork has been outstanding so far. :) 18:28:24 maybe just a picture of the sierra madres. 18:28:25 * mitr has nothing to add 18:28:44 I liked vondruch proposal in ticket 18:28:47 "I know the treasure is here somewhere!" ? :) 18:28:52 rubber stamp seems fine, as long as it that stays a caricature and not reality :) 18:29:13 the steering wheel is good too 18:29:18 adminral "it's a trap!" akbar 18:29:47 notting: wee don't need no steenking BADges? 18:30:19 No one likes the Eye of Providence? ;-) 18:30:37 mattdm: as long as you can read it (maybe backwards) and it says "rejected" or "your idea is bad and you should feel bad" or "ultima ratio regum" ;) 18:31:07 sgallagh no that one needs to be reserved for members of the fedora cabal 18:31:22 I like the "ultima ratio regum" as it is funnily ironic in many ways 18:31:39 that plus the rubber stamp. done. 18:31:40 mattdm: So only Red Hat members of FESCo <.< >.> 18:31:54 sgallagh: I think that's all of us right now... 18:32:03 pjones: is the latin in the badge on an actual cannon? 18:32:19 notting: it's correct latin, if that's what you are asking 18:32:22 notting: a cannon that says that would be perfectly fine by me ;) 18:32:47 OK, I'll add to the ticket that the author of the badge should read this meeting log for ideas :) 18:33:16 #topic Next week's chair 18:33:53 anybody volunteers? 18:33:58 mattdm: We should have a cabal badge that's never awarded ;-) 18:34:06 abadger1999: +1 18:34:36 abadger1999: don't tempt me to root the badge system ;) 18:35:03 abadger1999 nice :) 18:36:35 abadger1999 it should be awarded to no actual people but the badge page should say that it was awarded 13 times 18:36:43 t8m: ok, I'll do it 18:36:59 #action mmaslano will be the next week's chair 18:37:01 mmaslano: +13 ;-) 18:37:08 ;) 18:37:12 abadger1999: I opt out ;-) 18:37:27 #topic Open Floor 18:37:38 Anything? 18:37:49 except for more cabal badges proposals? 18:37:49 So, I'm pretty sure cloud WG prd is not going to be as good as it could be by the deadline 18:37:58 we made some good progress but it needs more work 18:38:16 I'd like to request a 1-week extension 18:38:24 from our arbitrary deadline 18:38:31 well, theres still the later part of this week and early next week, no? 18:38:50 btw. I was getting quite a lot questions about F21 release schedule - so it's now on planet.fpo... 18:39:19 mattdm: i'd be ok with that 18:39:24 mattdm, go ahead with #proposal 18:39:35 I'm not sure with env and stacks prd too 18:39:47 one week could be beneficial 18:40:27 I'd prefer to see next week what still needs more time. 18:40:47 previous deadline was the 15th, right? 18:41:13 I'm okay with still trying to hit that but giving the warning that we might ask for an extension at that point 18:41:25 no wait it was the 13th 18:41:30 eg monday. 18:41:40 I'd somewhat prefer that (just for the psychological effect) 18:41:46 I thought it was 15th... 18:41:56 nirik https://fedorahosted.org/fesco/ticket/1196 18:42:03 mattdm: yeah so 15th would be better for us 18:42:14 okay, so: 18:42:21 but we've also been thinking it's >13th 18:42:35 #proposal bump PRD deadline by 2 days to the 15th to align with FESCo meeting 18:42:54 +1 18:43:10 and we'll see where we are there. hopefully done. :) 18:43:16 well fesco should have some time to study it shouldn't? 18:43:31 The purpose of the 13th was to give FESCo two days to read it and formulate thoughts 18:43:38 t8m that might have been the original intention of giving extra days, yeah. 18:43:39 sgallagh, +1 18:43:47 Actually, were these being submitted to FESCo or the Board? 18:43:57 fesco, IMHO 18:44:07 i think we agreed that fesco would review them and pass on to board with recommendation 18:44:15 mattdm: Right, thanks 18:44:55 so, different proposal? +7 days, so fesco has time to review those prds? 18:45:08 mmaslano, +1 18:45:24 mmaslano +1 18:45:34 sure, still +1 18:45:56 sigh, ok. 18:45:59 and of course if some are done earlier that's just fine. i think workstation is about ready, for example 18:45:59 +1 18:45:59 +1 to my proposal 18:46:01 mmaslano, do you vote for yourself? 18:46:08 0. I understand the necessity for Cloud, but I don't really like forcing the date out since we're waiting for these to start scheduling. 18:46:27 mmaslano: +1 18:46:50 0 18:47:00 +1; we still need a Server<->Cloud conversation to happen AFAICS and that will take some back-and-forth 18:47:17 sgallagh: yeah, this is all still too abstract for me to know really what we are producing, which worries me. The longer we take to actually figure out what we need to change the less time we have 18:47:21 * abadger1999 thinks that starting the review, feedback cycle next week might still be beneficial 18:47:28 #agreed PRD deadline bumped by 7 days to the 20th (+7, -0, 0:2) 18:47:29 mitr yeah that's one of our blank sections. 18:47:35 even if some of the prds were still work in progress 18:47:54 sgallagh attempted to get that conversation started I think but we aren't ready. 18:47:56 weren't 18:48:02 i think it's much more ready now, actually 18:48:22 #info feel free to submit even unfinished PRDs for comments earlier 18:48:37 heh i was just typing that info t8m :) 18:49:29 t8m: Submit where? 18:49:35 devel@ 18:49:36 ? 18:49:52 sgallagh, I suppose so 18:49:53 post to devel-announce, maybe file fesco ticket? 18:50:19 (we probably want a ticket for each of 'em anyway.) 18:50:27 #undo 18:50:27 Removing item from minutes: 18:50:50 #info feel free to submit even unfinished PRDs for comments to devel-announce@ and open a FESCo ticket earlier 18:52:12 Anything else for Open Floor? 18:52:28 just heard back from thias... ;) 18:52:55 he's going to try and add folks as co-maintainers, as his life has been very busy of late. 18:53:04 aweome 18:53:06 some 18:53:07 good 18:53:12 this keyboard ucks 18:54:13 I will close the meeting in a minute if nobody has anything else. 18:55:34 #endmeeting