17:00:01 #startmeeting IRC Support SIG (2012-09-27) 17:00:01 Meeting started Thu Sep 27 17:00:01 2012 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:01 #meetingname irc-support-sig 17:00:01 The meeting name has been set to 'irc-support-sig' 17:00:02 #topic init process 17:00:13 * N3LRX 17:00:15 hey folks. Who's around for a quick irc support sig meeting? ;) 17:00:20 * Discordian is 17:00:24 bikedude880: everyone is welcome... 17:00:30 Thanks nirik 17:00:57 * BobJensen 17:01:32 okey dokey, lets go ahead and get started then I guess... 17:01:34 #topic Week in review 17:01:34 http://fedora.theglaserfamily.org/ircstats/fedora-weekly.html 17:01:53 anyone have items from the previous week to note? common bugs or issues or the like? 17:02:12 bikedude880: you are number 1. ;) 17:02:27 There's the clangg issue in F17 17:02:28 I don't understand that honestly... 17:02:32 clang 17:02:35 seems like it was a pretty quiet week. I have been busy, so not as active as normal. 17:02:38 Except for my IR remote issue which seems to have fixed itself 17:02:56 bikedude880: really? cool... glad it's working. 17:02:57 Looked like a USB controller bug, but that's enough on that 17:03:14 libstdc++ is out of step on i686 and x86_64 17:03:37 Discordian: it's not, it's other things that are depending on it... like clang. ;) 17:04:09 Well whatever it's been bothering a few folk including me 17:04:48 yeah, it's clang in updates needs the old gcc/libstdc++... so yum tries to find it, and finds the old 32bit one in the base repo and boom. 17:05:13 ok, anything else to note from the week? or shall we move on? 17:05:22 (hopefully clang in updates-testing will go out soon and fix that issue) 17:05:33 * Discordian nods 17:05:39 The only things I can note will get updated in F18 17:06:24 ok, on to tickets. 17:06:26 #topic ticket 128 - Community helped fix a nvidia module 17:06:27 https://fedorahosted.org/irc-support-sig/ticket/128 17:06:47 this is some kudos to some folks. 17:06:57 always nice to see people happy their issue was solved well. 17:07:07 Yep +1 17:07:16 Nice work :) 17:08:02 yep. 17:08:22 next ticket... 17:08:23 #topic ticket 127 - Hey why am i being treated like an idiot for asking? 17:08:24 https://fedorahosted.org/irc-support-sig/ticket/127 17:08:53 I think the reporter here was being oversensitive and taking offense where none was offered. 17:08:55 I'm afraid there seems to have been a communication issue 17:08:56 Just saw that, quite a bit of reading in that one 17:09:13 and yes they over-reacted 17:09:33 First few lines... I agree 17:09:46 I don't see where the user was treated like an idiot. But I am commonly blind to people's image of themselves. 17:10:09 I can see where it would be misinterpreted 17:10:29 * nirik fixes the log, reload for more readable version 17:10:31 When a user fails to provide more information than the error message, it's hard to want to help 17:10:39 I also don't think fenrus02 treated them like an idiot 17:11:21 lots of context missing for sure. 17:11:32 I'm afraid I would have handled them... much more abrasively... 17:11:35 so, what can we learn from this/do? 17:12:15 I guess it might have helped to get more info from the user... but unclear 17:12:19 No matter how hard we try we can't please everyone 17:12:21 * Sonar_Gal sneaks in 17:12:28 yeah. 17:12:30 We can only try 17:12:46 Been around Android long enough to know that some people can't express their issue in English 17:13:03 Or they don't know how to find out the root cause of it 17:13:32 This user seemed to have a lot of problems that may have been self inflicted in the days that followed the ticket also. 17:14:12 yeah, I recall talking with them briefly and they were much more interested in ranting about things than providing info or working on a solution to issues. ;( 17:14:25 Did not seem to really want to own up to some of the errors in judgment or help people that would try to work with them to resolve the issues. 17:14:42 anyhow, I guess we thank them for feedback, and just try and do better at gathering info or pointing people to other support resources. 17:14:45 I'd say the best thing to ask is if it's a clean install 17:15:15 Yeah button it up. Hope they sorted it all out. 17:15:53 bikedude880: yeah, that would be good info to know... along with: what log was the error in, lines around it for context, and a lot of other things. ;) 17:16:07 Definitely 17:16:35 I'm sure 'fpaste --sysinfo' could provide most of the basic info 17:16:44 anyhow, thats the tickets this week... would anyone like to step up to close them out politely with the info from this meeting? 17:16:56 nirik: I'll do it 17:17:05 BobJensen: thanks. 17:17:08 #topic Open Floor 17:17:22 any items for open floor? suggestions / ideas / bacon? 17:18:24 I know I'm constantly looking for what's getting updated next, already familiar with the 'bodhi' command... is there any place where the information is posted publicly? 17:19:09 bikedude880: if you want a firehose of info... #fedora-fedmsg shows all the messages from the internal message bus... including when updates are created, etc. There are also bodhi rss feeds. 17:20:31 Nice, good info to know 17:20:44 ok, any other open floor items? or shall we call it a meeting? 17:21:47 Call it what you like... 17:21:53 I'll call it... 17:21:54 Closed the tickets. 17:21:56 bacon. :) 17:22:01 Thanks for coming everyone! 17:22:01 Mmmmm Bacon 17:22:05 #endmeeting