17:00:04 #startmeeting FESCO (2012-09-26) 17:00:04 Meeting started Wed Sep 26 17:00:04 2012 UTC. The chair is jwb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:10 #meetingname fesco 17:00:10 The meeting name has been set to 'fesco' 17:00:10 #chair notting nirik mjg59 mmaslano t8m pjones mitr limburgher jwb 17:00:10 Current chairs: jwb limburgher mitr mjg59 mmaslano nirik notting pjones t8m 17:00:12 #topic init process 17:00:20 morning everyone. 17:00:20 hello. 17:00:25 should be a short meeting today 17:00:37 * limburgher here, busy 17:00:52 * notting is vaguely here 17:00:55 mitr said he wouldn't make it 17:00:56 will do my best 17:01:01 hi all 17:01:09 mjg59? 17:01:20 mmaslano won't make it either 17:01:26 t8m, ok, thanks 17:01:55 well, we'll move on. mjg59 will show up eventually 17:01:59 t8m: hm, i just saw her... (she may have something else scheduled) 17:02:05 notting, yep 17:02:39 #topic Followups 17:02:45 .fesco 932 17:02:47 jwb: #932 (F18 Features - progress at Feature Freeze) – FESCo - https://fedorahosted.org/fesco/ticket/932 17:03:08 we don't really need to evaluate this until next week, but I thought i would add it quickly in case someone had something urgent on it 17:03:21 Here 17:03:29 Sorry, iwlwifi 17:04:24 ok, so no comments. good. 17:04:30 * nirik has nothing off hand. 17:04:42 anyone have any other follow ups before we move on to the one thing we have to discuss today? 17:05:17 #topic New Business 17:05:50 #topic #952 become co-maintainer on gradle 17:06:00 .fesco 952 17:06:02 jwb: #952 (become co-maintainer on gradle) – FESCo - https://fedorahosted.org/fesco/ticket/952 17:06:42 mitr said he was 0 on this. it seems this is sort of a case of rushed non-responsive maintainer 17:06:47 hm, lkundrak. have we had non-responsive maintainer issues with him before? 17:07:03 yeah, and he popped up on the devel list when pinged. 17:07:09 * nirik isn't sure how urgent this is. 17:07:17 notting, i don't recall having issues before 17:07:29 hi, what did I miss 17:07:41 mmaslano, nothing really. we're on ticket 952 now 17:07:42 notting: he used to be the grub2 package maintainer and just sortof disappeared 17:08:02 in like 2009 17:08:17 grub2 in 2009? i would have disappeared too. 17:08:29 Well, it wasn't my idea ;) 17:08:42 so, I'm a slight +1 to this, as it seems his missing/busy, so might as well add co-maintainer. 17:08:54 the reason he's asking for co-maint is to do an upgrade 17:09:02 the upgrade wouldn't land in f18, i think 17:09:13 if I may chime in, getting the maintainer for the gradle package sorted out is pretty important since Fedora has really be lagging here getting proper Gradle support 17:09:25 so doesn't seem like it would be time critical. but i'm not *against* it 17:09:38 notting, but if it's not going to land in f18, why can't it wait for the full NRM process? 17:09:57 Agreed with jwb 17:09:59 it doesn't seem to be critical, so I would prefer standart process 17:10:00 i may be overstating it, but we are potentially going to miss an opportunity w/ java developers if we let this go much longer 17:10:39 http://lists.fedoraproject.org/pipermail/devel/2012-March/164253.html 17:10:53 hrm 17:11:01 To me it looks like the standard process should have been followed by gil for some time already and we wouldn't be in this situation now. 17:11:06 https://bugzilla.redhat.com/show_bug.cgi?id=746391 17:11:23 yeah, I think he has already been non responsive for a while. 17:11:36 He;s sort of hot and cold. 17:11:37 * nirik also thinks our process is too difficult to trac for people, so they give up. 17:11:55 nirik, possibly, yeah 17:12:06 ok. i'm kinda leaning towards +1 here too 17:12:23 he said he's sent lkundrak e-mail, and he's posted on the list on sunday. 17:12:46 as far as I can see the post in march never got a reply either. 17:13:31 I'm leaning towards +1 on adding him as a co-maintainer. 17:13:49 reboot 17:14:14 sorry, you're not authorized to reboot the meeting 17:14:19 I am +0 and keep following the nonresponsive maintainer process 17:14:25 ok, should we take a formal vote? 17:14:42 proposal: addi gil as a gradel co-maintainer 17:14:47 s/addi/add 17:15:02 +1 17:15:06 mitr was 0 17:15:18 +1 for pragmatism, but mostly meh 17:15:29 meh. 0 this week. ask again next week. 17:15:32 +0 17:15:46 +1 17:15:50 marek goldmann is not present, but I'm pretty confident he would +1 here since he's been mentoring/assisting gil 17:15:52 +0 17:15:57 If we're not going to do it this week, then we may as well go with what t8m said. 17:16:05 mojavelinux: he's not a person who gets a vote. 17:16:09 i think by the normal policy, next week is when the normal process would expire 17:16:10 oh 17:16:14 I wasn't sure 17:16:33 at least by a best-fit line of the nonresponsive policy to what gil has done already 17:16:49 notting: fair enough. 17:17:08 notting, yep, and he would become owner, not a comaintainer 17:17:20 (bug filed on 09-07, re-ping later, mail to devel list on 09-23) 17:17:40 * nirik notes that he owns a lot of packages. 17:17:44 proposal: continue non-responsive maintainer policy - will revisit next week if no suitable response 17:17:52 notting: +1 17:17:55 +1 17:18:01 yeah, +1 to following the policy at this point. It's not too far out. 17:18:03 sure, why not. +1 17:18:06 * notting is +1 17:18:15 that's 5. 17:18:16 ok, that's 5 17:18:16 * nirik is ok with that too I guess. 17:18:31 +1 17:18:58 +1 to that, then 17:19:19 #agreed continue non-responsive maintainer policy - will revisit next week if no suitable response 17:20:04 #topic Open Floor 17:20:10 oops 17:20:12 #undo 17:20:12 Removing item from minutes: 17:20:27 sigh. i suck at driving zodbot 17:20:34 did i just undo the agreed? 17:20:42 I think so, yeah. 17:20:44 no, the last command... 17:20:44 so the topic 17:20:45 no, you undid the open floor topic 17:20:47 oh. 17:20:51 well, that's better. 17:20:58 ok good. that's what i wanted 17:21:09 #topic Next week's chair 17:21:21 ok, so clearly i could use more practice 17:21:31 i'd be willing to chair again if nobody else is really itching to do it 17:21:32 * limburgher whistles. . . 17:21:36 I can 17:21:51 ok mmaslano. 17:22:02 #action mmaslano to chair next week 17:22:09 #topic Open Floor 17:22:14 ok. now on to open floor 17:22:18 anyone have anything? 17:22:35 Not here. 17:22:45 i have a brief thing 17:22:58 the existing ticket for refining the Feature process 17:23:20 i haven't forgotten about it, but i'm holding off for a bit. i might start with just proposing a new Feature page template 17:23:37 to try and get rid of some of the duplication, etc 17:23:45 anyway, just an FYI 17:23:47 jwb, afaik jreznik started working on it but the work stalled 17:24:04 yeah, seems a common theme with that whole area :) 17:24:14 jwb, due to being busy with the alpha release 17:24:35 yep, sorry it was quite difficult during alpha and I did not have mood to start working on it :( 17:24:54 but I think we collected a lot of ideas with t8m, mitr and marcela 17:25:05 jreznik, will you be able to do it before beta? 17:25:55 t8m: I hope so... I'll be travelling the next week but I really like to make it before beta 17:26:21 ok, great. 17:26:39 more open floor topics? 17:26:56 if not, i'll end the meeting in 4 min 17:27:02 hi 17:27:16 hi gil_ 17:27:25 * nirik has nothing. 17:28:03 gil_, hi, can you please follow the formal process https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers 17:28:49 gil_, we agreed that you're somewhere at the point 3 or 4 - so it would be easy to finish it 17:29:31 yes did ... or not? 17:30:43 ah ok thanks 17:31:51 gil_, you'll also become owner of the package, not comaintainer 17:32:12 Unless you want others to be owners. 17:32:13 ah ok 17:33:50 ok, i think that about does it for the meeting 17:34:01 next week should be a bit longer as we have the features to work through again 17:34:15 and i think jreznik would like a review of the f18 upgrade stuff 17:34:36 thanks for attending everyone 17:34:38 #endmeeting