12:22 p.m.
=============================================
#fedora-meeting: IRC Support SIG (2012-09-27)
=============================================
Meeting started by nirik at 17:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2012-09-27/irc-support-si...
.
Meeting summary
---------------
* init process (nirik, 17:00:02)
* Week in review (nirik, 17:01:34)
* LINK: http://fedora.theglaserfamily.org/ircstats/fedora-weekly.html
(nirik, 17:01:34)
* ticket 128 - Community helped fix a nvidia module (nirik, 17:06:26)
* LINK: https://fedorahosted.org/irc-support-sig/ticket/128 (nirik,
17:06:27)
* ticket 127 - Hey why am i being treated like an idiot for asking?
(nirik, 17:08:23)
* LINK: https://fedorahosted.org/irc-support-sig/ticket/127 (nirik,
17:08:24)
* Open Floor (nirik, 17:17:08)
Meeting ended at 17:22:05 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (44)
* bikedude880 (17)
* BobJensen (12)
* Discordian (10)
* zodbot (3)
* N3LRX (1)
* Sonar_Gal (1)
--
17:00:01 <nirik> #startmeeting IRC Support SIG (2012-09-27)
17:00:01 <zodbot> 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 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:01 <nirik> #meetingname irc-support-sig
17:00:01 <zodbot> The meeting name has been set to 'irc-support-sig'
17:00:02 <nirik> #topic init process
17:00:13 * N3LRX
17:00:15 <nirik> hey folks. Who's around for a quick irc support sig meeting?
;)
17:00:20 * Discordian is
17:00:24 <nirik> bikedude880: everyone is welcome...
17:00:30 <bikedude880> Thanks nirik
17:00:57 * BobJensen
17:01:32 <nirik> okey dokey, lets go ahead and get started then I guess...
17:01:34 <nirik> #topic Week in review
17:01:34 <nirik> http://fedora.theglaserfamily.org/ircstats/fedora-weekly.html
17:01:53 <nirik> anyone have items from the previous week to note? common bugs or
issues or the like?
17:02:12 <nirik> bikedude880: you are number 1. ;)
17:02:27 <Discordian> There's the clangg issue in F17
17:02:28 <bikedude880> I don't understand that honestly...
17:02:32 <Discordian> clang
17:02:35 <nirik> seems like it was a pretty quiet week. I have been busy, so not as
active as normal.
17:02:38 <bikedude880> Except for my IR remote issue which seems to have fixed
itself
17:02:56 <nirik> bikedude880: really? cool... glad it's working.
17:02:57 <bikedude880> Looked like a USB controller bug, but that's enough on
that
17:03:14 <Discordian> libstdc++ is out of step on i686 and x86_64
17:03:37 <nirik> Discordian: it's not, it's other things that are depending
on it... like clang. ;)
17:04:09 <Discordian> Well whatever it's been bothering a few folk including me
17:04:48 <nirik> 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 <nirik> ok, anything else to note from the week? or shall we move on?
17:05:22 <nirik> (hopefully clang in updates-testing will go out soon and fix that
issue)
17:05:33 * Discordian nods
17:05:39 <bikedude880> The only things I can note will get updated in F18
17:06:24 <nirik> ok, on to tickets.
17:06:26 <nirik> #topic ticket 128 - Community helped fix a nvidia module
17:06:27 <nirik> https://fedorahosted.org/irc-support-sig/ticket/128
17:06:47 <nirik> this is some kudos to some folks.
17:06:57 <nirik> always nice to see people happy their issue was solved well.
17:07:07 <Discordian> Yep +1
17:07:16 <bikedude880> Nice work :)
17:08:02 <nirik> yep.
17:08:22 <nirik> next ticket...
17:08:23 <nirik> #topic ticket 127 - Hey why am i being treated like an idiot for
asking?
17:08:24 <nirik> https://fedorahosted.org/irc-support-sig/ticket/127
17:08:53 <nirik> I think the reporter here was being oversensitive and taking
offense where none was offered.
17:08:55 <Discordian> I'm afraid there seems to have been a communication issue
17:08:56 <bikedude880> Just saw that, quite a bit of reading in that one
17:09:13 <Discordian> and yes they over-reacted
17:09:33 <bikedude880> First few lines... I agree
17:09:46 <BobJensen> 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 <bikedude880> I can see where it would be misinterpreted
17:10:29 * nirik fixes the log, reload for more readable version
17:10:31 <bikedude880> When a user fails to provide more information than the error
message, it's hard to want to help
17:10:39 <Discordian> I also don't think fenrus02 treated them like an idiot
17:11:21 <nirik> lots of context missing for sure.
17:11:32 <BobJensen> I'm afraid I would have handled them... much more
abrasively...
17:11:35 <nirik> so, what can we learn from this/do?
17:12:15 <nirik> I guess it might have helped to get more info from the user... but
unclear
17:12:19 <BobJensen> No matter how hard we try we can't please everyone
17:12:21 * Sonar_Gal sneaks in
17:12:28 <nirik> yeah.
17:12:30 <BobJensen> We can only try
17:12:46 <bikedude880> Been around Android long enough to know that some people
can't express their issue in English
17:13:03 <bikedude880> Or they don't know how to find out the root cause of it
17:13:32 <BobJensen> 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 <nirik> 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 <BobJensen> 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 <nirik> 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 <bikedude880> I'd say the best thing to ask is if it's a clean
install
17:15:15 <BobJensen> Yeah button it up. Hope they sorted it all out.
17:15:53 <nirik> 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 <bikedude880> Definitely
17:16:35 <bikedude880> I'm sure 'fpaste --sysinfo' could provide most of
the basic info
17:16:44 <nirik> 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 <BobJensen> nirik: I'll do it
17:17:05 <nirik> BobJensen: thanks.
17:17:08 <nirik> #topic Open Floor
17:17:22 <nirik> any items for open floor? suggestions / ideas / bacon?
17:18:24 <bikedude880> 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 <nirik> 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 <bikedude880> Nice, good info to know
17:20:44 <nirik> ok, any other open floor items? or shall we call it a meeting?
17:21:47 <BobJensen> Call it what you like...
17:21:53 <nirik> I'll call it...
17:21:54 <BobJensen> Closed the tickets.
17:21:56 <nirik> bacon. :)
17:22:01 <nirik> Thanks for coming everyone!
17:22:01 <BobJensen> Mmmmm Bacon
17:22:05 <nirik> #endmeeting