16:00:05 #startmeeting IRC Support SIG (2010-06-03) 16:00:05 Meeting started Thu Jun 3 16:00:05 2010 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:05 #meetingname irc-support-sig 16:00:05 The meeting name has been set to 'irc-support-sig' 16:00:05 #topic init process 16:00:15 who all is around for an irc support sig meeting? 16:00:34 * zcat 16:01:29 * Southern_Gentlem 16:02:45 * nirik will wait a few more for more folks to wander in. 16:04:34 ok, we have a few things on the agenda today, so I guess we should start in... 16:04:51 #topic Week in review 16:05:08 first the typical week in review... 16:05:10 http://fedora.theglaserfamily.org/ircstats/fedora-weekly.html 16:05:37 The nss-softokn stuff has been all too common... 16:05:43 hopefully that will be fixed very soon. 16:06:41 ok, if nothing else... moving on. 16:07:02 * dcr226 here 16:07:07 #topic fedora-social guidelines 16:07:20 There were some questions last week about #fedora-social and it's guidelines... 16:07:40 I made an initial FAQ like we are using for the main channel now: https://fedoraproject.org/wiki/Fedora_Social_Channel_FAQ 16:07:57 thats my understanding of the channel, but we may want to adjust or modify that stance. 16:08:02 or ask social folks for input. 16:08:47 looks good 16:08:50 any thoughts or comments on that? 16:08:56 Heh. bacon 16:09:02 nirik, would writing the actual channel name on that guide help? 16:09:05 bacon? 16:09:14 looks like i got here just in time 16:09:23 plarsen: where? 16:09:23 mock, https://fedoraproject.org/wiki/Fedora_Social_Channel_FAQ you see anything wrong with that as far as -social is concerned 16:09:38 * nirik isn't sure how mediawiki treats #'s 16:09:40 looking... 16:09:48 nirik, like the title: #fedora-social FAQ instead of "Fedora Social Channel FAQ" ? 16:10:38 might a specification be put in for vim/emacs and gnome/kde wars? maybe in the religion/politics section? 16:10:52 or are those allowed in there, as long as they kept civilized? 16:10:55 plarsen: I don't think you can put #'s in titles. 16:11:08 I can look into it tho. 16:11:12 nirik: Good idea, that page 16:11:16 mock you are more a person to tell us that 16:11:19 +1 to "try" to avoid religion/politics. :) 16:11:26 Southern_Gentlem: :) 16:11:38 thanks. I think we need to make sure people know what to expect... 16:11:50 * stickster notes that standard Freenode guidelines still say, zero tolerance for racial or religious slurs or any other discrimination. 16:11:51 probably s/fedora-social/#fedora-social <- my only comment 16:11:53 * mock knows he loves a good friendly gnome/kde rumble with others occasionally ;) 16:12:17 nirik, i posted a link to it in -social and asked for feedback thus the influx of new nicks 16:12:24 ah, cool. 16:12:32 Fedora enjoys the support of the Freenode staff and therefore we will observe the rules of their highway too. 16:12:41 well, I would say perhaps we gather feedback over the next week or so and see if it looks good next week? 16:13:10 i will add it to the social topic 16:13:32 stickster: indeed. The link in the above points to that freenode guideline. 16:13:35 * mock is glad for the spotlight on bacon in that faq 16:14:32 any other comments on it? Or should we gather feedback and see next week? or do we think it's ok as is? 16:15:53 next week give the users of the channel time for feedback 16:16:00 Southern_Gentlem +1 16:16:08 and to be here next meeting 16:16:20 ok, sounds good to me. 16:16:40 #topic greivance process 16:16:59 So, we have had a pretty informal process for people to notify us of issues/bad behavior. 16:17:19 Consisting of letting us know in #fedora-ops and/or mailing the alias the various ops are on. 16:17:28 Do we need a more formal process? 16:17:46 nein 16:17:48 nirik, I thought !ops nick issue was also active? 16:17:56 nirik: maybe we need to document our informal process on our wiki page 16:17:57 i really dont think so 16:18:11 plarsen: nope... there's not bot avenue. 16:18:11 that would work 16:19:05 well, there are drawbacks to our current setup... but honestly it doesn't get used much. 16:19:17 add to the wiki page to inform us in #fedora-ops 16:19:30 nirik, is that because it's not known how to, or because people don't need it? 16:19:45 plarsen: good question. Perhaps some of both. 16:19:57 ummm, I think you might get a recursive problem letting everyone know the existence of -ops fwiw 16:20:01 usually there is an op person in the channel that handles it fairly quickly 16:20:34 wiki page with the nick's of ops for the various channels, otherwise you (imo) will get a flood of non-ops in -ops 16:20:35 but i am sure there are times we are busy with other stuff 16:21:01 "popped in to complain, stuck around to watch" 16:21:07 dcr226, or give the /cs access list command 16:21:30 I think freenode has a policy of not discussing klines on network at all... only email. 16:21:44 personally, I think -ops should be the only channel that has an acl, but thats imo 16:21:57 * dcr226 sees the hypocracy 16:22:18 well, at the very least we should document the current policy... 16:22:28 but I think we might be able to adjust it so it works better. 16:22:30 nirik, +1, and a contact strategy 16:22:52 Southern_Gentlem, that works 16:23:01 honestly I think email would be better for talking to folks who had been banned than letting them go into ops and rant 16:23:25 for noting problems, email is slower... so might not catch a bad activity when it's happening. 16:23:39 exactly 16:23:51 * dcr226 /cs acces list wfm 16:24:14 well, the problem with access list is that someone will just pick someone out... 16:24:14 that way, you find an active op - when its needed 16:24:25 they may be gone, not active, not able to look, etc. 16:24:57 and then also the issue goes to private message most likely, which means only the person and the op can see it. 16:24:59 what is -ops normally used for, other than raising complaints? 16:25:03 * nirik would prefer things to be transparent. 16:25:08 ops meetings? 16:25:11 nirik, how about an alisa - which ping's ops? @complain for example 16:25:16 It's been my experience that coming in after the fact rarely is helpful. If there's an ongoing issue, it's important to be able to call in an active op to "referree" 16:25:29 * dcr226 gah my spelling sucks today 16:25:46 mock: discussion of channel activity, ops from some channels letting others know about problem users, etc 16:26:09 plarsen: +1 16:26:16 nirik: so, is ops the best place for normal users to bring matters up? what about another channel for it? 16:26:26 dcr226: I would fear it would get misused... and/or doesn't have a way to know who's active. ;) 16:26:37 #fedora-customer-service 16:26:59 #fedora-support-customer-service 16:27:01 nirik, yeah, but if it announces in -ops, then thats as good as visiting ops, without the inherant danger maybe? 16:27:03 mock: well, we could do that, but it has all the same disadvantages, IMHO. 16:27:12 if they take the time to type it out, their complaint would be worth listening to 16:27:54 yeah, we definitely want to hear issues... even if we can only learn from them after the fact. 16:28:23 i was just thinking of keeping ops for ops and not for not public 16:28:34 example : - pm the bot, complain blah blah blah - announces in -ops as to the complaint 16:28:38 mock, +1 16:28:48 but i fear i know not enough about ops procedures to really talk about that smartly 16:28:54 dcr226, that's what I thought was already the case ;) 16:28:56 I can see if there is a way to do that... I don't know off hand. 16:29:10 plarsen, it wont be if its location is advertised on the wiki 16:29:42 * dcr226 is a -ops occupying hypocrit 16:29:44 well, it's already mentioned on the wiki... 16:29:51 oh, ok then :) 16:30:02 but our policiies around it are not noted anywhere I know of. 16:30:30 So, I guess I need a Fedora_Ops_FAQ ? (whee... we can put them all in a fedora-irc-channels category) 16:31:25 ok, I can look at documenting and we can all brainstorm ways to do things better in this. 16:31:51 any other thoughts on this before we move on? 16:32:23 ok, moving along. 16:32:26 #topic irc-support-operators group questions 16:32:43 I orig setup the irc-support-operators fedora group to contain people who were ops in #fedora. 16:32:59 Over time I added a few more active ops in other #fedora-* channels. 16:33:19 Do we want to keep this group to just #fedora ops? or any #fedora-* or does it even matter? 16:33:42 the only way this enters into things is that it's an alias people can send complaints to and get to all the folks in the group. 16:34:56 we could just setup a proper mailing list for people interested in irc support, but then complaints to there might be a bad idea as it would be public and have public archives, etc. 16:35:54 * zcat is more content to just be a low-level grunt op in #fedora. this admin stuff makes me all dilbert-y 16:36:15 heh 16:36:15 so, any thoughts there? or does it all tie into any changes in the process? 16:36:22 zcat: agreed. Can't we all get along? :) 16:36:31 +1000 on just getting along 16:36:37 nirik, it's been my experience that mailing lists are very bad at handling "ad-hoc" situations 16:36:52 nirik, why not have two ops channels? A public and a private? 16:37:07 that gets wiggy 16:37:18 I think that would just add to confusion... 16:37:24 plarsen, most of us are in TOOOO many channels as is 16:37:31 erm, i'm in plenty of channels already 16:37:33 Southern_Gentlem, tell me about it :( 16:37:57 Well, if you want a dialog with the person that is having issues, you really don't have many options then? 16:38:04 nirik, cant @say #fedora-ops be squished into an alias @{something}? 16:38:07 if need be we can always set -ops to invite only and kick everyone else out 16:38:13 plarsen: right. 16:38:31 well, we could make ops invite only... then invite anyone who wished to note an issue... 16:38:39 Personally, I call "ops" when there's a situation at hand like flooding that needs to be dealt with immediately. Anything else I would most likely just pm an op about 16:38:53 #fedora-waiting-room 16:39:05 take complaints there ^^ 16:39:05 dcr226: nope... say requires you to have privs on the bot... ;( 16:39:14 So a bot or similar to call attention to a situation would suffice. 16:39:15 Southern_Gentlem, imho, that will only make matters worse / more combative 16:39:26 but yeah, we could possibly do an alias... 16:39:36 nirik, another bot? specifically for the purpose? 16:39:41 fenris02, i said if need be 16:40:01 dcr226: I think I could make an alias that lets someone ping something in ops... if we decide thats usefull. 16:40:14 I think that works fwiw 16:41:16 makes for a simple procedure on the faq/wiki 16:41:17 so, really we just need a documentable way to let people notify us of issues that are currently happening/urgent... 16:41:37 and another procedure (email ?) for non currently happening/less urgent issues. 16:42:01 #fedora-parents 16:42:09 "i'm telling..." 16:42:13 "@911 no-one will help with my $other_os kernel re-build" 16:42:33 ok, I can look at cooking up a bot alias. 16:42:54 nirik: @judge 16:42:55 nirik, yup - I think it should be that "simple" 16:43:07 Now, after the complaint/issue is noted... how do we act on it? Currently it's just a rough consensus... 16:43:07 or @judge_n_jury 16:43:23 nirik, use the fight alias ;-) 16:43:33 lol 16:43:39 there was mention of some kind of panel/council who would review issues. Do we want something like that? 16:43:41 * mock almost spit his water out 16:44:09 wow - what kind of issues demand that kind of bureaucracy ? 16:44:15 nirik: i would think the matter, once raised, would be noted in -ops? 16:44:15 nirik, to repeat, a panel of *uninvolved* parties to mom the -ops 16:44:39 nirik, if that happens, you can kiss any amount of order good bye 16:44:59 * nirik was just bringing up the idea. ;) 16:45:02 nirik i think thats what this meeting is for 16:45:09 afterall, who is left to mother them? 16:45:35 well, the problem with this meeting is that it's logged and public... and people may not want to drag specific issues out to the public... 16:45:45 email then 16:46:03 email has the advantage of attaching logfiles if they so desiren 16:46:07 why not, if the problem is _that_ bad, go by vote on active ops in -ops at that time - surely they will be best placed to judge? 16:46:13 * dcr226 braces for impact 16:46:17 Aren't we talking about two different things? OP actions in the channel and "policy" issues about what should be allowed? 16:46:18 and what type of issue gets regulated to that 16:46:51 plarsen: yeah, theres a number of things here... I was talking about complaints specifically. 16:47:42 i would hate to think anytime an op did anything in the channel we had to go through all of this 16:47:56 nirik, Policy/rules talk is a completely different animal. An op to me is "all powerful" in channel. And when he puts his hat on, and say jump - you jump or find another channel. 16:48:08 plarsen, +1 16:48:10 nirik, that should be the way it is. 16:48:18 ops are nominated with good reason 16:48:40 ok, so. I will document our current setup, try and get a bot command to note issues to ops, and we can revisit next week and see if we can improve anything. 16:49:16 anything else we need to do now? any further thoughts before we move on? 16:49:23 move on 16:50:02 #topic Open Floor 16:50:10 ok, thats all I had. Any issues for open floor? 16:51:11 we have 2 indivuals i want to nominate for limited bot use in #fedora for 30 days as Trail ops 16:51:31 plarsen and dcr226 16:52:25 * nirik would be ok just nominating them as ops personally. 16:52:26 what would 'Trial ops' include? 16:53:12 +1 16:53:13 Thanks Southern_Gentlem. What does that entail? 16:53:26 fenris02, give us time to evaluate them and see if they will be good ops 16:53:44 Southern_Gentlem, sure, i mean is that a bot-op, or a +o ? 16:53:45 plarsen: the bot is opped there, so you can kick/ban/change topic, etc... via the bot. 16:53:49 but i will say we go nirik way as well 16:54:02 nirik, ohhhhhh 16:54:11 * dcr226 is happy with probation - and to be notminated, thanks 16:54:41 but we said a while back that all new ops would be bot ops on a trail basis before coming +o ops 16:55:05 +2, in this case - one for each 16:55:05 I was going to bring up a problem in Social of not having ops in there or ops that won't kick people. EvilBob Has things going on and hasn't been online much gwerra has things going on and I am sorry he will not kick people. 16:55:08 plarsen / dcr226: so our procedure here is that some op nominates you and the pool of existing ops vote... 16:55:31 Sonar_Gal: did you see the draft faq? 16:55:31 * dcr226 nods 16:55:41 Southern_Gentlem, not a problem. I have no problems with being "evaluated". I've spend a lot of time on IRC avoiding being an OP though ;) 16:55:41 Sonar_Gal, afaik, -social has no additional rules beyond the freenode ones 16:55:42 https://fedoraproject.org/wiki/Fedora_Social_Channel_FAQ 16:56:06 If someone breaks those rules, I would be happy to clear them out... 16:56:17 Sonar_Gal, if you're talking about a certain "hacker dood", he hasn't hit my kick threshhold - sorry 16:56:39 ok 16:56:44 Thanks 16:57:06 nirik, i know how to solve this problem in social as well 16:57:29 lets let the lady really swing the frying pan 16:57:35 Southern_Gentlem, +1 16:57:39 +1 16:58:03 * dcr226 thinks thats a great excuse for @pan alias 16:58:04 Sonar_Gal, you want +o in social or just bot op 16:58:21 i haven't read the faq yet for -social, but maybe we should nominate Sonar_gal as an op there, 16:58:24 dcr226 +1 16:58:38 sure... thats ok with me. I'm sure she would go a fine job. 16:58:38 Southern_Gentlem, No I am fine. I said last week if it couldn't get resolved I would not stay in that channel 16:58:48 Southern_Gentlem: +1 16:59:13 Sonar_Gal: feel free to ping me or ops when/if an issue comes up... (until I get a pesky '@shiny-red-button' alias for the bot) 16:59:29 +1 +o for Sonar_Gal in -social 16:59:30 * dcr226 thinks Sonar_Gal would do a great job 16:59:59 Southern_Gentlem: +1 17:00:17 I've only ever seen you make well placed comments about bad conduct Sonar_Gal 17:00:34 fwiw 17:00:56 * mock has full confidence in Sonar_Gal to wield the frying pan effectively 17:01:24 dcr226, I normally don't have an issue. Only twice have I asked for someone to be kicked since the day that channel started 17:02:01 Sonar_Gal, I saw 1 occassion that you are referring to, and I think you were justified totally 17:02:22 well, sounds like if you want ops there it's yours Sonar_Gal. ;) Otherwise we can try harder to police if there are issues. 17:03:11 Anyone have any additional issues to bring up? 17:03:14 nirik, like I said I have only had a few issues in there most of the time it's fine in there 17:04:35 Sonar_Gal, no harm in +o then ;-) 17:05:00 Sonar_Gal: c'mon, everyone's doing it! 17:05:06 dcr226, nirik That's fine 17:05:16 * dcr226 yeeeeeeyy 17:06:48 ok, will close out the meeting in a minute here if nothing else comes up. 17:07:06 * mock holds his breath... 17:07:37 * mock turns blue... 17:07:40 thanks for coming everyone 17:07:43 #endmeeting