15:06:02 #startmeeting bugzappers 2010-07-13 15:06:02 Meeting started Tue Jul 13 15:06:02 2010 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:06:09 #meetingname bugzappers 15:06:09 The meeting name has been set to 'bugzappers' 15:06:17 #topic gathering 15:07:01 alright, hi everyone... 15:07:09 hi 15:07:17 * jraber is present, but only about 15% so. $dayjob is killer this week. 15:07:26 * poelcat here 15:07:56 * fenrus02 15:09:09 okey dokey 15:09:41 don't really have anything agenda-wise today. unless there was anything sent to the list? 15:09:50 we can do a quick: 15:09:57 #topic triage metrics update 15:10:12 from me on this one, i was supposed to send a first stats report to the list with discussion about the format and stuff 15:10:20 which i totally didn't get around to yet, sorry for that :/ 15:10:26 i'll do it this week instead 15:11:33 ok. I have no update regarding the triage metrics. 15:11:50 I still need to move them from my talk page to the bugZappers/Metrics page 15:12:00 ok 15:12:09 so, no news is bad news there =) 15:12:38 (I am updating my talk page with the latest metrics, but they don't seem to have changed much in the last week. 15:12:57 i dont really have any input, ill just listen in for n ow 15:13:15 tbonito88: yup, that's fine 15:13:29 alrighty 15:13:35 #agreed adamw sucks and will do the mail shot next week 15:13:44 #info jraber has little to report this week 15:14:00 i don't have anything else on the agenda, is there any big topic i'm missing? 15:14:06 yes :) 15:14:18 https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora14#Rawhide_Rebase_Warning_to_Package_Maintainers 15:14:37 in particular needs to be done today 15:15:04 poelcat: I didn't forget... Just waiting for the open discussion at the end. ;) 15:15:05 I also need help updating the content on the entire page... much of it is a copy/paste from f13 15:15:09 oh, sorry 15:15:31 Don't worry, I think we are already at that point.. 15:16:24 I did edit poelcats message on the wiki. It is pretty generic, but conveys the message. 15:16:30 durn it 15:16:41 I wanted to have someone else look at it before I sent the message today 15:16:49 #topic housekeeping help 15:17:07 #topic housekeeping help 15:17:14 keep talking =) 15:17:27 #link https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora14 15:18:14 is everyone in agreement w/ the email warning about the rawhide rebase/ 15:18:21 ? 15:18:45 +1 15:18:52 +1 15:19:49 ok, the rest of the wiki needs to be reviewed and edited as necessary to ensure that it is relevant to F14. I don't mind taking that task. 15:20:00 It looks mostly updated to me. 15:20:10 +1 (just that "I hope everyone is well." in the start of the message makes me feel about Nigeria ...) 15:20:46 jraber: yeah, it just needs to be gone over really carefully, particularly creating new query links 15:21:07 mcepl: it could say, "dearly beloved" and talk about needing bank account information ;-) 15:23:55 "free pony" is always a good addition too. 15:24:21 mcepl: I am not opposed to removing it. poelcat's version felt less 'machine generated'. 15:24:45 jraber: it wasn't mine... it was a roll-forward of tk009's version from f13 :) 15:25:34 jraber: I was just kidding .. people will at leat laugh over this 15:27:22 i guess we can go ahead with that mailshot then 15:27:30 #agreed rawhide rebase warning email looks good 15:28:50 anything else on this topic? 15:30:08 nothing from me. 15:30:33 jraber: thanks for your help 15:31:52 okey dokey 15:31:55 #topic open floor 15:32:03 anyone have anything for open floor this week? 15:32:31 I had a question regarding a commonbug 15:33:52 go for it 15:33:56 bug 586236 is a commonbug, but normally I would close it as a dup of bug 595924 15:33:59 #topic open floor - jraber commonbug question 15:34:40 should I mark 595924 as a dup, or the other way round? 15:35:30 i'd say mark 595924 as the dup 15:35:43 595924 is longer, but 586236 came first and they both have the essential info 15:35:50 ok, I didn't want to close a bug marked as a commonbug, without checking the etiquette. 15:35:51 the bug simply is that compiz-on-i8xx-no-worky 15:36:12 generally speaking that's not really a problem, it's best to then update the commonbugs page to change the bug number there 15:36:22 but in this case i think we can safely avoid it 15:36:49 are these bugs actual problems with the components, or a problem with the components integrating into fedora 15:37:30 i dont understand how its our problem if a certain program/package doesnt work. isnt that up to the writer of the program to make it work with fedora? 15:38:24 the answer to that is 'erm. sorta. it depends.' =) 15:38:56 it seems like 3/4 of the bugs are for a specific program, not fedora itself. 15:39:06 its like blaming windows if photoshop screws up 15:39:14 particularly for X stuff, we like to have bugs open downstream - in fedora / rh bugzilla - because rh employs half the x developers anyway 15:39:15 bad example but you know what i mean 15:39:37 ah 15:39:37 yes. it's not something bugzappers is hugely concerned with. mostly we consider the choice of whether to move bugs upstream to be the maintainer's 15:39:39 they're down to only half? 15:39:49 fenrus02: intel keeps hiring our intel devs 15:39:57 doesnt rhat still employ most of the gcc developers too? 15:40:12 dunno. probably. our tentacles go everywhere. muahahaha... 15:40:12 like for instance, i had a bug where my screen flickered, on instinct i blamed fedora, later i found out it was compiz's fault 15:40:13 adamw: *nod* _A_ went, but he was the last one i saw 15:40:52 tbonito88, screen flicker is often a driver conflict 15:41:09 i was able to narrow down the problem 15:41:17 my computer works fine without compiz enabled 15:41:18 tbonito88: anyway, it's a sensible problem, and in this case indeed the bug likely exists in upstream intel driver. you're definitely not wrong. but in practice we usually accept such reports, especially for core components. 15:41:24 s/problem/question/ 15:42:28 (and hiring all our devs Intel produces code which is unbelievable ... :'( ) 15:42:33 * mcepl cannot resist 15:42:40 heh 15:42:47 okay, so, that's the q answered anyway 15:42:52 any more open floor topics? questions etc? 15:42:57 it seems like a frustrating job for linux developers to make all these 3rd party programs work together seemlessly, its impossible really, with all the variables, gnome/kde, kernel version, personal settings, etc. 15:43:16 tbonito88: nah, it's easy, the developers all leave work at 10am every day. on their unicorns 15:43:25 =) 15:43:31 thats what i do 15:45:09 okey dokey...i guess that's all? 15:45:16 closing the meeting in one minute 15:49:11 [You suddenly realize it is unnaturally quiet] 15:50:25 #endmeeting