[06:19] hello [06:19] rww, IdleOne, elky, Unit193, welcome to #ubuntu-irc, the land of ubuntu IRC discussion. [06:21] So. There's been a lot of discussion about what's broken with the IRC Core Team (i.e., the folks that op #ubuntu, #ubuntu-offtopic, #ubuntu-ops, etc.) recently. [06:22] And we have a few venues like ubuntu-irc mailing list, and #ubuntu-ops-team, and #ubuntu-ops to discuss this, but they all -- frankly -- suck. [06:22] So Unit193 proposed, and phunyguy and I agree, that talking about it in here may make the discussion improve without making this channel suck too. [06:23] before we segued onto that topic, my last statement was along the lines of: [06:24] I think a lot of people have lost faith in the IRC Council as an institution because various iterations of it have chosen inaction in important situations. I'm tempted to say that they should stick with ban appeals and let us govern ourselves for the rest of it, but consensus has so far being a crap way of managing the team because it's too large. [06:24] So we need some respected process for us to make decisions that will lead people who disagree with the end result to be happy that they were heard and respect the conclusion. The IRC Council establishment is not that. Which is not a slight against the people currently on the IRCC, but against the institution of it. Having some sort of batcrap crazy chaos is also not that. So I don't know what *is* that. [06:25] I like this idea. Too tired to want to talk about anything specific right now, but I think this more open forum will allow people to contribute and maybe help the team of ops deal with some of the issues it has had for a long time now. [06:26] ^ [06:26] same about the tired. [06:26] I'm pretty out of it too, but I wanted to get the above out there and see if anyone had any thoughts. [06:26] Good idea [06:26] the other elephant in the room, is the human aspect of IRC has gone a way a bit. [06:27] we have to make sure that is out there as a discussion topic as well. [06:27] (and an aside: some of the issues with the IRC team are also issues with Ubuntu in general, but we can't fix Ubuntu in general right now, and we can (hopefully) fix this team) [06:29] I am just as guilty of this, but we have a nasty habit of enforcing rules "too much", and it drives people away. I made this point the other day, but I will make it public here. When I first started using #ubuntu for support, I will not mention any names, I made an offtopic remark or two, because I didn't know about the offtopic channel, but I got the nasty "Stop with the offtopic outbursts, or you will be removed from the channel". [06:30] THAT can't happen. [06:30] Agreed. I think this is where we started wandering off into talking about factiods the other week too. [06:30] I am now an op here, so I must be a decent human being, yet I was treated like garbage. [06:30] because a lot of that overly-snappy behavior is reinforced by us having cookie-cutter responses to "offtopic" etc. comments. [06:32] yes, you are correct. [06:32] or me recently with the "We don't support Google Chrome here" in #ubuntu. [06:32] I will take the hit on that one. [06:33] the other aspect I don't agree with is "You aren't experienced enough in this, so i recommend you stop doing it" [06:34] phunyguy: as in saying that to a user who's trying to do something advanced/unsupported? [06:35] no, just something advanced. [06:35] okay [06:35] unsupported maybe, but resetting a mysql root password because a coworker who did a terrible job got fired [06:36] and being told that you aren't experienced enough and shouldn't be doing it for a living is just flat out wrong. [06:36] good example, and I agree with you on that sort of thing [06:36] especially if you are picking up slack. [06:36] (I think our attitude towards unsupported behavior needs to get less harsher, but we can discuss that later) [06:40] are people still flipping out about eulas? [06:40] elky: hrm? [06:41] i tried to convince some people a few years ago that flipping out when someone wants to install osx in a VM is hilariously silly since it's a contractual matter not a legal issue [06:42] this is of course applicable to other scenarios [06:44] well, on a personal note, I think support in #ubuntu is not well managed. the only couple times I went there for support, people ended up saying 'you don't collaborate, go find help somewhere else' [06:44] Since SCaLE, I've been pondering how to turn #ubuntu into a functional support avenue like AskUbuntu seems to be. [06:45] And perhaps it's just pessimism from bashing my head against #ubuntu so much, but I think IRC is structurally a bad system for this. [06:45] Way too many people in one place is going to be extremely difficult to manage. We make it worse, but even if we were perfect it would still be a mess. [06:45] the ability to delete stupid things that were said from everyone's scrollback makes management infinitely difficult. [06:46] inability*, and yes, that's one huge advantage of stack [06:46] anyway, my back is cramping, i need to go move around before i start crying [06:46] you edit the questions/answers until they're good reference, and then point people at them [06:47] but while some of the issue with #ubuntu is structural, we are very, very, very far off doing the best we can to manage it [06:47] I think that the fact that there's more people looking for support nowadays than it was a couple years ago has made it a non-viable method of support [06:47] (and this focuses on #ubuntu, when the IRC Team itself has issues independent of any channel) [06:48] or, in other words, we need a brainstorm board for "let's fix the IRC team", and a brainstorm board for "let's fix #ubuntu" with an entry "fix the IRC team" on the latter [06:48] ^ [06:48] and how can that be done? [06:49] that remains to be seen. [06:49] well actually, no it doesn't.. I think I spelled it out pretty good above. [06:50] kinda tired of dancing around it :( [06:53] I think a meeting can be summoned, and during/after that we can note down ideas on an etherpad [06:56] pad.ubuntu.com requires indirect membership in https://launchpad.net/~ubuntu-etherpad still, right? [06:56] :( [06:57] if so, one of the IRC LP teams needs to get added to that [06:57] well, membership to ~ubuntu-etherpad is practically open [06:57] just request it and popey will approve you within minutes, if he's awake [06:58] *nod* [06:58] still, less hoops and all that [06:58] anyway [06:58] etherpad: very yes [06:58] ^ yes [06:58] meeting: i'd prefer to mention here during a regular IRCC meeting and on the mailing list, and have ongoing discussion [06:59] ^ yes also [07:00] ok ladies and germs... time for me to go to bed. [07:00] thanks for listening. :) [07:01] thanks for not disappearing because of me being argumentative ;) [07:01] i put you on the spot earlier tonight, this is what I wanted to happen :) [07:03] :) [07:03] bai [09:38] hello all [12:28] EITAZORRAZZFF is in #ubuntu-br spamming user's nicknames for attention. [12:28] (for the sake of being annoying) [12:29] And now there are two of them. [14:40] #ubuntu-br is getting DDoS'd again. [15:40] Daekdroom: was it sorted? [15:40] MooDoo, yes. I hadn't noticed at the time but niko is still at the channel and took care of it. [15:40] groovy :) [17:01] IdleOne: cprofitt, AlanBell, et all, can we discuss in here? [17:02] yup [17:02] Just seems more appropriate [17:02] old habit of going in there is hard to break [17:03] maybe that needs to be added to an ubuntu-irc@ post [17:03] maybe it will be my first ever mailing list post on any list! [17:04] cprofitt: so you get where I was going with that. [17:08] yes, we can disuss here [17:09] I think one thing to keep in mind -- to assume - is that everyone wants what is best for the team... there may be differences in opinion on what to do to get there, but one should not assume ill intent [17:10] yes. I can agree with that. [17:11] With that said, what are the recommendations to get the team back to a healthy state... then work on improving how the team operates? [17:13] IdleOne do you have some specific issues? [17:15] I stated my issues twice now. The whole treating people with respect no matter how new they are, or whatever crummy position at work they were dumped in. [17:15] if they need help, they need help. [17:16] phunyguy - respect is a two way street though... I assume you want IRC ops to show some restraint and take things on a case by case basis? [17:16] cprofitt: That is the thing. I don't think there are any specific issues. I think that many if not all the issues stem from personal interpretation of the CoC and channel guidelines. Some people are more strict in enforcing those documents then others. [17:17] That creates a sense of resentment on both sides of the isle? [17:17] cprofitt: that is a start. The mentality of "This is my playground, so whatever I say, goes" is not a good way to do business. [17:17] This is what I am getting from what I have heard from people so far [17:17] So, IdleOne you are saying that by not having set rules we have issues with things being taken 'personally' vs. 'by the rule'. [17:18] so to be clear do we have issues with -ops playing favorites? or being too harsh? [17:18] cprofitt: yes. [17:18] Is it differences between -op 1 and -op 2 or is it the same -op acting differently towards different people? [17:18] I think so. There has long been complaints from many users that the !guidelines are not specific enough and allow ops to use them for personal vendettas. I don't believe that has been the case, but I do understand how a vague set of rules can be hard to enforce. [17:19] * cprofitt nods [17:20] Is there an issue with 'protect your own' in which operators take the side of operators when there has been a dispute? [17:20] yes, hard to enforce, but some do enforce, and it is to the point of, "I can say what I want, because I am the op, and you are terrible at what you do, so maybe you should try something else." [17:20] some ops such as LjL have long said that the ops team (or many of us) are to literal in the interpretation. letter of the law vs spirit of the law [17:21] being an op, doesn't mean you can be a bully. [17:21] phunyguy: I agree - not good to have bullies [17:22] There is a correction I need to make there: I am not an op. [17:22] hi LjL :) [17:22] LjL: right, former ops* [17:22] I think the problem is one that is hard to fix... but steps can be taken to make things better... [17:22] but LjL I would like, if you want, to be a part of this discussion also. I think you still have a lot to offer to it. [17:22] though past history may make the issue thorny [17:23] I would like LjL to have a voice as well, but I would like to ensure that we all take time to prevent emotions for running high [17:24] absolutely agree and this is why I think it was a great idea to move the discussion to this channel, where it is logged and open to all to contribute. [17:24] * cprofitt nods [17:25] so currently how does -op behavior get reviewed? [17:26] The only thing I'm willing to offer this so-called team at the present moment and in the present situation is my middle finger. [17:26] good question. [17:26] LjL :( [17:26] wow [17:27] LjL: take offtopic discussions to #ubuntu-offt... oh wait. [17:27] I think we should definitely keep from making any jokes or sarcastic comments. [17:28] This is a serious issue for the ops team and the irc community and we need to stay on the right track. [17:28] yes, apologies. [17:28] I need coffee. brb [17:29] as an outsider, who is interested this is very interesting [also sorry for buttin in] ;) [17:30] MooDoo: no worries... we are having this discussion here to get more opions... just like yours [17:30] thanks [17:32] As someone who is looking in from the outside you probably will be able to see things we don't or chose not to. [17:32] So feel free to jump in and help if you think you can [17:32] lets get back to the question, how is operatore status reviewed? [17:33] I don't really think it is. [17:34] you can never write rules that are specific enough, people will always find open leaks. The more you try, the more complicated they will get, and people will stop reading them. So a short, simple set or rules is better. If an operator actually did abuse the power or was a bully, then there are enough groups that can review this, starting at the council which people are free to contact in that case [17:34] Fuchs++ [17:34] I mean, there is https://wiki.ubuntu.com/IRC/AppealProcess [17:34] But I think the issue is the fact that the IRCC hasn't been. [17:35] hasn't been what? [17:35] with the ircc is there a poc like the loco teams or is everyone equal? [17:35] Fuchs: reviewing, or not taking any action. [17:35] that is the impression I got anyway [17:35] ah, yeah, that would defeat the purpose slightly. But then there still is https://wiki.ubuntu.com/IRC/AppealProcess point 5, the community council [17:36] MooDoo: the point of contact for the IRCC would be the chair which was me up until last night. [17:36] Fuchs: that raises a question for me... does behavior only get reviewed in an appeal? [17:36] cprofitt: typically, yes. [17:36] cprofitt: I don't know about core channels, I am only a op in a local channel. But I do assume so, yes. [17:36] * cprofitt nods [17:36] is there any health check done for irc ops on a by channel basis [17:37] (and personally I don't see a point in periodic reviews. If you hear nothing, things are fine. If there are more and more IRCC / CC appeals concerning a specific op, then maybe a review is due) [17:37] ^ yes [17:37] not like a review or inqusition, but like "hey, how are you guys feeling?" everyone still feeling good? [17:37] I was thinking about this a little earlier. I think a big problem is that we are trying to govern this giant country and not letting each city do it's own thing. [17:37] Fuchs: some channels can really push operators... no news is not always good news if we have people in the process of burning out [17:38] cprofitt: then why don't these people report that? [17:38] maybe they do in private and (semi-)informally and get ignored all the time [17:38] Fuchs: it is hard to see that you are burning out... when you are burning out. [17:38] anyway. We (the german speaking ones) have regular meetings where such concerns can/could be addressed. Based on experience: rarely up to never used [17:38] surprise [17:39] cprofitt: well, then I wonder if they'd notice if they are asked "are you feeling okay?". I doubt it. If people _around_ an op notice that he/she is burning out, then it's their duty to report. Not due to this being IRC or ubuntu, but rather common sense. [17:39] Fuchs: the people themselves may not... [17:39] but perhaps their fellow ops would [17:39] I don't want to sound overly pessimistic, but I don't really think there is an administrative works-everytime solution for this problem. [17:40] well, yes, then they should report it, really :) [17:40] and if there was a set time to discuss it would not feel so much like ratting out a friend [17:40] Fuchs: reporting it only works if it doesn't fall on deaf ears right? [17:40] yes, we have to not have deaf ears as well [17:41] MooDoo: well, yes, obviously. But there you also have quite a big set of ears (starting with your fellow ops, then the IRCC, then the CC), so if all of them are deaf, then there is a huge problem [17:41] Has it been the case that operators report burn out and do not get listened too? [17:41] Fuchs cprofitt: people have gone to the ircc and suggested that an op should maybe take a break, but there hasn't been (that I have seen) any real way of mandating an op take time off. [17:41] short of removing +o from the channels [17:42] of course it's not like a "forced break" is anything that can be considered a "break" but in bureaucratic terms [17:42] which is not the best way [17:42] IdleOne: do you think that is because 'time off' is seen as a punishment rather than a well earned vacation? [17:42] IdleOne: it's the only way. [17:42] cprofitt: I think so, yes. [17:43] I think taking flags of should be really the last possible measure, as indeed it can be taken wrongly by the affected person. Talking to them is way more important, and trying to solve it without having to alter actual privileges. However, if it doesn't work, then I'd say that is still better than a burnout, really [17:43] is there resistence to rotating channels? In other words... ops rotate through channels so everyone gets a turn in the stressful and non-stressful channels? [17:44] maybe the "punishment" sense can be lowered a bit when people keep other things (e.g. launchpad memberships or whatnot), so they still feel as part of the team, just not on duty [17:44] I would not want to have all rookies in stressful channels mind you... [17:44] Fuchs: do you think not allowing for leeway after removing flags is going to be helpful against getting both? [17:44] I think channel culture will make rotating ops difficult [17:44] IdleOne: agree. [17:45] LjL: I'd say depends on the case, I wouldn't give a general statement here. It certainly has to be well thought of and done carefully. I am not really aware of the current case, but you seem to be very unhappy [17:45] LjL: if you want to talk to someone "external" about it, feel free to poke me [17:45] I agree IdleOne, but if we keep people familiar with the channel culture in with those that are not potentially we can help have more people exposed [17:45] LjL: but as for the general solution and not "your" case: see above, depends, really. [17:45] not external enough i'm afraid [17:46] I would think the start of rotation might be difficult, but eventually it would level out [17:46] LjL: well, let me know if I can do something for you or organize someone, then :) [17:46] cprofitt: I am slightly against rotation. Knowing a couple of different ubuntu channels: the culture really is that different that an op not used to it might very well start upsetting people, [17:46] cprofitt: I am not OK with that. [17:46] cprofitt: wouldn't that just annoy people rotating? [17:47] From starting my ops process, can't you just have some process in place for putting ops on review? [17:47] e.g. if a specific topic or behaviour was so far okay in channel #ubuntu-xy, now the new op comes in and kicks people due to it, then things are quite sure to go downwards from there on [17:47] we all have the channels we are most comfortable in. [17:47] Fuchs: see isn't that where people need to be approacing ircc and reporting it? [17:47] I'd rather say have more ops in the "difficult" channels (and yes, I know how hard it is, former staff, #defocus) [17:48] rotating could annoy people... I was just brain storming a way to get people time away from stress with out removing op status [17:48] or having it be a punishment [17:48] MooDoo: well, yes, but actually I'd rather if stuff like that would not happen in the first place :) But yes, that would be where to go from there (if talking to ops doesn't already work) [17:48] MooDoo: i think it's where people, especially long-time channel regulars, should probably tell the rookie concerned "get the fuck out of our channel now" [17:49] in a slightly friendlier tone, and maybe giving him/her the chance to adapt first [17:49] unfortunately, the way I see it, stress is part of the job you applied for. Maybe removing op status from that channel is not the best idea. But there should be some sort of system in place for "Ok you have been reported 4 times now for being a jerk in #ubuntu, let's talk and see where your head is at" [17:50] maybe try to guide the operator into a different behavior [17:50] thids doesn't need to be too incredibly difficult. [17:50] hang on shouldn't the op guide themselves,? [17:50] not if they are pissing people off. [17:50] MooDoo: technically yes, but assuming you do have a rotation (which I think is not a good idea), then this might be hard [17:50] MooDoo: yes, but ops are human and sometimes humans don't see how they are acting until it is too late [17:50] what should happen though, regardless of whether you do have a rotation or not, is that other (more senior) ops do guide you [17:51] so if you really do introduce an op rotation (which I still see as a bad idea), then maybe have the new op take a couple of days in there first without actual opping, so he/she sees how things are done [17:51] Fuchs: oh, is that why rww was appointed as my mentor in 2012 or whenever it was? i had never seen that under that light [17:52] We need to try and keep this as non personal as possible. This discussion is not about one person or one channel. [17:52] LjL: again, I am afraid that I do not know your specific case, sorry. I do think that mentoring is a good thing, though. Whether rww is a good choice or not is up to debate, I can't really decide whether that was sarcasm from you there or not (sorry, downside of text only communication) [17:53] Fuchs: it was sarcasm, since in 2012, i had merely taken what you'd call a "break" or "hiatus" from opping, since i had actually been an op starting in 2006 [17:53] Fuchs: and in fact, rww only started being an op after i was [17:53] (and I think it would be better to keep this debate here generic, so that future cases can be solved as well) [17:54] ah, yeah, as said, wasn't aware of the specifics. But then maybe this should have been solved back then, I am afraid that no matter what is done or decided or discussed here today changes what happened in 2012 :( [17:54] ^ [17:54] however, I do think that, if everybody tries to keep emotions out of this and be pragmatic, this here could lead to past errors not happening again, and improve the situation for the future [17:54] Fuchs: yet, rww has only started being an op *again* recently, end of 2013 i believe? [17:55] was he assigned a mentor? [17:55] now while that doesn't solve your case, I am afraid that whatever might have happened already did happen, so it is too late anyway. So lets make the best out of it at least, right? :) [17:55] no [17:55] well, I don't know, but if there is rule that people should have a mentor and he fell under that and didn't get one: that would be something that should be addressed. Then there we'd have a point that could be improved [17:56] Do you feel ops that have been doing it awhile and who come back require mentors? [17:57] to be somewhat blunt (hoping you accept that from me): whatever happened that made you made: unfortunately it did happen and can't be changed. But we could try to improve things for the future, so this doesn't happen to others. That would be nice, wouldn't it? (Well, you wouldn't directly benefit from it. But neither would you from anything else, hence the "unfortunately already too late") [17:57] Yep, man this is a great discussion so far. [17:57] MooDoo: I do not. [17:58] Fuchs: nice? no, i wouldn't find it nice [17:58] LjL: right. What would you find nice? [17:58] LjL: there was strong opposition back then to giving you back +o and that is why the IRCC at the time decided to assign a mentor. I agree with Fuchs that there is nothing that can be done now to change how things happened then. How do we make things better now is the question. [17:58] IdleOne: how do you happen to know that, given that last time we talked about that in #ubuntu-irc-council, the general response seemed to be that you didn't know / remember? [17:59] LjL: so from what I've been seeing, you've been aggreived somehow....I don't know the ins and outs of it, but let me ask. What are you actually wanting right now [sorry if that sounded aggressive?] [17:59] MooDoo: what i'm wanting is only my concern [17:59] LjL: because I spoke to members of the IRCC at the time after the discussion we had in the council channel and learned this [17:59] Fuchs: getting laid, other things [17:59] this is getting off track [17:59] sorry [18:00] LjL: right. Let me rephrase: what would you like here / from the CC / from the ops team to be done? [18:00] LjL: This is still an ubuntu channel, please keep it clean and within the channel guidelines please. [18:00] IdleOne: eat shit [18:00] * MooDoo is just totally lost lol.... [18:00] LjL: because I really suggest that either we all try to keep this pragmatic and actual helpful or, if not possible, let the situation cool down first until it is possible. [18:00] * chu sighs [18:00] hell chu [18:01] hello* [18:01] oops [18:01] Hey phunyguy. [18:01] sorry guys I just don't get it, he doesn't want anything, he doesn't want anything resolved, but he won't tell us why? I'm missing something pyes i'm a noob] ;) [18:01] MooDoo: it's a long story. [18:02] MooDoo: reading the ubuntu-irc mailing list has lots of good info. [18:02] phunyguy: yeah sorry for interferring....just wondering why he keeps coming in moaning... [18:02] MooDoo: no worries [18:02] * MooDoo shuts up lol [18:04] MooDoo: your input is valued... and you guys are correct that to get to a better place we can not rehash what happened in 2012 on a personal level... generic with suggestions to get better.... sure [18:05] :) I agree to the point that there needs to be some way of policing the ops though, but do people feel scared approaching the IRCC in the first place? [18:06] MooDoo: I doubt it [18:06] phunyguy: doubt or know? [18:07] I doubt folks are afraid to approach the IRCC, but I cannot speak for everyone [18:07] it's not like it is public info unless they make it public. [18:08] I thik we have two issues [18:09] it sounds to me that people who go into #ubuntu for example, just as a generic user who doesn't know ubuntu well wouldn't kow what to do if an ops became abusive or was bullying them [18:09] 1) Operators who made a bad decision on a particular case -- the case needs to be reviewed [18:09] MooDoo, are you talking about "people" in general or other ops? [18:09] 2) Bad operators - either due to burn out or other [18:09] Daekdroom: in this case generaly people sorry think i've gone off track [18:09] I'm not the generic #ubuntu visitor and I have no idea how to contact IRCC (although I don't think I'd have trouble finding out how) [18:10] well if you get banned from #ubuntu, you can go to -ops to discuss, and they will give you the appeals link [18:10] generally. [18:11] Yes. Sometimes they even include 'https://wiki.ubuntu.com/IRC/AppealProcess?action=show&redirect=IrcTeam%2FAppealProcess" in the ban. [18:11] as a percentage [ish random guess] how many of these appeals followed through, is there a ticketing system or such like? [18:12] I have a sneaky suspicion most appeals are rubbish. [18:12] chu: that would be an issue as well... we need to have people think appeals are valid [18:12] s/sneaky/sneaking/ [18:13] well if it's all done without no history / logs, then that's not very good :S [18:13] maybe a ticket system isn't a half bad idea [18:13] though we also have to have a system that disallows people who are tossed for good reason gumming up the works repeatedly with appeals [18:13] Note that I am in no way involved with the IRCC though, just the most common case (well, of the cases I see) of someone requesting an appeal are troll users. [18:13] chu: I'm not either, but I want to be one day lol [18:14] cprofitt: you'd have to have it that the owner of the ticket isn't the op being complained about...but they can have input on it [18:14] MooDoo: the issue with compaints is that they usually have these features: [18:15] 1) A person booted from a channel usually gets more angry and acts poorly for a period of time befor calming down [18:15] 2) a person booted usually makes allegations they were being picked on in another channel or that it is a long standing fued [18:16] 3) People have bad days [18:16] eehhh.... starting to retract my statement about it being a decent idea [18:16] seems like am admin nightmare [18:16] Of all the requests I have seen, they are usually of the form: "I don't like ikonia; he banned me. Remove my ban now or I will call Mark Shuttleworth and complain." [18:17] MooDoo: the way the system is currently setip -- I think is that the the IRCC members are not -ops while serving on the IRCC [18:17] phunyguy: what other historical medium do you have? or is it all done on the fly? [18:17] chu: exactly [18:17] I don't understand the question [18:17] most complaints about bans are overly aggressive [18:17] cprofitt: ah! [18:18] phunyguy: do you log op complaints any where? [18:18] phunyguy: I might totally not be making sense here, just trying to get a feel for how it all works, [18:18] I think there is a broader issue of behavior that does not result in boots [18:18] MooDoo: not that I am aeware of [18:18] aware* [18:18] I am not aware of one either [18:18] hmmm interesting [18:19] MY assumption though would be an email sent to the IRCC [18:19] that would be in a mailing list [18:19] No I think that would be a bad idea [18:19] thta probably becomes public info [18:19] that* [18:19] There is an irc-council channel, no? [18:19] phunyguy: not all email lists are public [18:19] this is also true. [18:19] there is a channel [18:20] couldn't you have a channel where the aggrieved parties could come for a meeting with an senior op? [18:20] private email list only seen by irc-council and perhaps the cc would likely keep things more private [18:20] MooDoo: then you have an issue with what if it was a senior op who did the kick-ban [18:21] it is an administrative nightmare, but I would think you have to go outside of the -op group to complain [18:21] though to be honest I think if most people back away from a kick-ban... sleep on it and then come back and talk to the -op who booted them that things would likely go fairly well [18:22] especially if they offered an apology for the poor behavior [18:22] you guys rock, it's all so complicated lol [18:23] * MooDoo makes a mental note, you really want to get involved with this ;) lol [18:23] being an -op is not an easy thing [18:24] at least not in the high traffic low experience channels [18:24] cprofitt: now he tells me seeing as I've applied to be one lol [18:24] MooDoo: I am glad you did... I think the more people that -op the more likely this problem becomes a bit easier to deal with [18:25] I agree. [18:25] more -ops mean people can take a break from a rough channel... feel less pressure that they have to be there [18:25] and more eyeballs on bad -ops [18:25] bad -ops decisions [18:25] etc [18:25] why do you keep adding a dash? [18:25] -ops [18:25] habbit I guess [18:25] and an extra b [18:25] :) [18:26] and the groups you apply to are devel-ops etc ubuntu-ops ? [18:26] yeah... had hobbit on my mind [18:26] One problem with certain users is that the second you invoke your op "powers" you essentially escalate the problem and the user is now set in some irrational tirade against *you*, so that for certain users it's really about catalyzing *without* showing that you're an op. Now this is time and effort which some ops just don't have to spend, so, how do you deal with it? [18:26] chu, well said [18:27] if there is no time to spend being an op... then whey are they doing it? [18:27] there is a saying behaviour breeds behaviour, sholdn't you only use ops when it's the last resourt? [18:28] MooDoo, it is the reason FreeNode asks channel ops to only have +o when necessary. [18:29] :) [18:29] chu: I think it also depends on the behavior [18:29] hence chanserv, and flags [18:29] When someone has +o, the dynamic changes. [18:30] swearing in an official ubuntu channel is different than making a racial comment attacking a person [18:30] both require just a warning surely [18:30] some behavior needs a private discussion other behavior needs a boot to the head [18:31] MooDoo: hence some of the difference in ops... if I saw someone attack a person with racial attacks I would boot them [18:31] but I realize that might just be me. [18:31] I have a low tolerance for that [18:32] perfectly acceptable, but we are allowed to act how we feel is best for the channel [18:32] use of a racially charged word without the personal attack would be a warning from me [18:32] +1 phunyguy [18:32] there will always be someone that disagrees. [18:33] which is why, and I hate to say this, the IRCC probably doesn't do much when approached. How would you fix it? [18:33] phunyguy -- well if there was a pattern of inconsistent operator behavior [18:33] right [18:34] but insonsistent according to whom? [18:34] say op 1 kicks person A for swearing, but then allows person B a long time Ubuntu personality to swear up a storm... that would be a problem [18:34] so why don't ircc do much, you need to change this [18:34] I don't like drawing attention to some things, because it then just attracts certain observers - they now know what's a "key" to firing off the ops. And in the end, it's that response they're looking for, some form of "validation" perhaps. I'll often let something slide - without a warning - and if it continues, then it becomes something I deal with. [18:37] I hope everyone thinks this has been a valuable discussion [18:38] of course it has [18:38] I would encourage further discussion [18:38] but we need to keep it calm and not dredge up old wounds [18:38] it's been enlightening :) [18:38] that only makes trying to move forward difficult [18:39] so perhaps you can make points from the logs and raise it at the next ircc meeting? does this happen? [18:39] wow i'm so interferring ;) [18:39] MooDoo: anyone can likely add an item to the agenda [18:39] everyone might want to read this: [18:39] http://www.mindtools.com/pages/article/newLDR_86.htm [18:40] or any other information on the stages of team development [18:40] to help identify what is taking place with the team [18:41] I am also willing to have anyone contact me and discuss things [18:44] thanks all, it's been fun, speak soon, taking son to bed :D [18:45] ok sir. [18:48] thanks MooDoo [18:50] phunyguy: is there any particular behavior from last night or today that you find troubling? [18:50] cprofitt: we hashed that out last night [18:50] all is well. [18:50] * cprofitt nods [18:51] what about today - this discussion? [18:52] I don't understand the question, and why are you singling me out? [18:53] did not mean to single you out, but MooDoo went to put his son to bed [18:53] and I knew you were still here [18:53] this is a heated topic... so I wanted to make sure how the discussion went was acceptable... to see if I could have guided it any better [18:53] I think this was a great discussion today. [18:53] 17:47:25 < Fuchs> e.g. if a specific topic or behaviour was so far okay in channel #ubuntu-xy, now the new op comes in and kicks people due to it, then things are quite sure to go downwards from there on [18:54] Oh deary deary deary dear that makes me crnige. [18:54] Cringe even. [18:54] hm? [18:54] Although I came into this conversation late, I think something which came up was about accountability of operators. But I have no idea what a nice solution to this problem would be. [18:54] chu: that is indeed a big issue that has no clear resolution [18:55] Fuchs: You seem to be implying that there would be a problem with the op choosing to take action because of there being a bad topic. I don't really want to get in on that discussion. [18:55] chu: but I don't feel it is impossible to resolve. [18:55] Pricey: read the whole backlog. [18:55] Fuchs: What narks me off is that you suggest straight away that the new op would kick people due to it... and that's what narks me off. [18:55] nark nark nark [18:55] Fuchs: I have been. [18:55] Pricey: no, the discussion was whether ops should be rotated between different channels, [18:55] Fuchs: I'm ignoring that discussion. [18:56] apparently. [18:56] Pricey: and so it could happen that an operator who does not know that culture might act based on what he is used to, which might not work in that culture [18:56] Pricey: that was in reference to my asking about rotating ops through difference channels [18:56] Fuchs: Sure, whatever, that's fine. [18:56] You're missing the point. [18:56] Pricey: maybe that is not the best idea, then ;) [18:56] more of a worry about an op not knowing the culture of a channel [18:56] Can we please just stop kicking everyone? [18:56] The example I gave before was a counter-example to that rotation policy; for the reasons I gave, I would be a terrible op in #ubuntu, but I can op the more "social" channels (well, I believe so, maybe others see differently, no qualms against that) [18:56] Pricey: err, you got that completely wrong, neither I nor anyone else suggested or even supported a new op kicking anyone [18:56] If there's a disruption in a channel, kicking and banning is a bad idea. [18:57] Fuchs: "if a specific topic or behaviour was so far okay in channel #ubuntu-xy, now the new op comes in and kicks people due to it" [18:57] Pricey: it was an example of what could go wrong, not a suggestion [18:57] [05:54] If there's a disruption in a channel, kicking and banning is a bad idea. +1 [18:57] This is making me itch. [18:57] You could have written "... now the new op comes in and starts trying to tackle the problem, taking people aside etc. etc." [18:57] yes, which is a hypothetical situation in case of op rotation (which I, three times at least, said is a bad idea), not what I suggest happens [18:57] Pricey: sorry for being direct and blunt, but really, do read the backlog again [18:58] I was _at no single point_ suggesting that people should be kicked. [18:58] Thank you :) [18:58] Fuchs: I don't mean to say that you're a bad example, always kicking people etc. et. etc. [18:58] But I feel that that *does* happen. [18:58] yes it does happen, and is my exact beef. [18:58] pricey I think we agree that kicking people is a last resort [18:58] And I think that using examples like that to make your point is a subconscious pointer to a real problem. [18:58] at least I do. [18:58] Pricey++ [18:59] I think IdleOne's kick of LjL above is a good example. [18:59] Pricey: again, sorry, please do read it again. You are currently attacking me based on false assumptions, which is highly unfair. [18:59] Yep, that's my only complaint, that's a very large factor in LjL's bigger issue too, not that I want to take the discussion back there. [19:00] Pricey: I saw a +q not a kick [19:00] did I miss something? [19:00] no, you didn't. [19:00] there was no kick and no suggestion to kick either. [19:00] how is +q any different in this case? [19:00] Fuchs: I believe I understand the context... rotation would mean uneven application of policies, causing unnecessary friction etc. etc. ? [19:00] if anything it is worse than a kick [19:01] Pricey: correct, which is why I brought up a possible bad situation that could happen from rotation. After mentioning at least three times that rotation is, in my opinion, a bad idea. [19:01] Fuchs: Cool, I agree :) [19:01] at least with a kick, you can come back. With a +q, you are essentially banned, but can still see the conversation [19:01] Good. Thank you. [19:02] Fuchs: I hope no op would do that though... see a bad conversation and kick for it. That's my point. It's a bad solution to a perhaps non-problem. [19:02] (Sure, this is all oversimplifying and no doubt there'll be no end of intricacies in any real-world situation.) [19:03] Pricey: well, I took the worst possible case to show why it is a bad idea. Substitute the kick with either a quiet or even catalyzing and it still is bad [19:03] Fuchs: Far less bad and disruptive though :) [19:03] yes, but still bad and unneeded, so why go for "less bad" if you can have "good" instead? [19:04] I would agree that any administrative action would potentially escalate the situation, but if a person is causing significant problems for a channel something must be done [19:04] is there an issue with different ops not taking 'ideal' action in such cases? [19:05] Fuchs: The example is grounded in the fact that the action is "bad". I agree that rotation is a silly idea. [19:06] Pricey: to give you some background it has been suggested that some operators might need to take a 'break' - I was spitballing ideas to make such breaks seem less like a punishment and more like an earned vacation [19:06] 1. Maaan, you create a lot of backlog to read... 2. I think this has been sidetracked. [19:07] cprofitt: I believe I'm up to date. [19:07] Unit193: Sidetracked *from*? [19:07] no, forced breaks are probably not the solution. [19:07] that just creates more tension [19:07] chu: Getting caught in the details of an example. [19:07] forced breaks would produce tension... [19:07] I agree [19:07] any kind of forced action should absolutely be a last resort. [19:07] chu: Getting back on now. [19:08] that includes op rotation. [19:08] but we likely have to find a way for people to de-stress... [19:08] even when they do not realize the need themselves [19:08] it would be best if fellow ops, friends, could handle that [19:08] didn't help that I was rabbiting on as well Unit193 ;) [19:08] so, corner them? [19:09] no, not corner -- that is why I said friends [19:09] still seems that it would cause them to put up a wall. [19:09] it has to be received as something from a friend not someone who is going to increase the tension [19:09] that will be hard to do in a public forum [19:09] that is a very difficult fine line -- as anyone with brothers, sisters or spouses can attest [19:10] Yep [19:10] phunyguy: I would say such advice should be handled in private not in public [19:11] ok, so here is the problem with that, it starts organizing "pacts" of a few ops against one person [19:11] I see a simulairty in a parent over reacting in a punishment with a child... the other parent needs to support the spouse, but has to ensure the over reaction is realized by the other parent [19:12] phunyguy do you think it is a non-issue or do we need to try and find a good way to deal with these issues? [19:13] I think it is an issue 100% [19:13] BUT [19:13] Maybe we need to play good cop/bad cop. If you get a complaint about op X, find an op you know they are friends with, and an op you know they don't get along with. Get them both to talk up about it. [19:13] how can that be dealt with? [19:14] chu: that could be very time consuming [19:14] chu wouldn't that cause the person to react to the bad cop? [19:14] MooDoo: Yeah, unfortunately. [19:15] time consuming, but would it be worth it? [19:15] can't it just be simple as , x complains about op and ircc council member approach X see if it's a valid complaint then they talk to op ? [19:15] cprofitt: I would rather hope it goes the other way, and having both sides of the cube, the person could reason it themselves. [19:15] I do not have a lot of experience with good cop v bad cop so I am not sure [19:17] I don't either, but much experience playing the devil's advocate, and I take that position to help people reason things out for themselves (not *just* 'cause I'm an ass ;P). [19:17] lol [19:18] Pricey: any thought, I respect your experience... would love for you to weigh in [19:20] There are enough processes and procedures. [19:21] Pricey: is there an issue with operator behavior? [19:21] cprofitt: We all make mistakes. [19:22] true... I would not consider occassional mistakes an issue overall [19:23] Given a couple of hours together at a UDS (shame it's now virtual...) I doubt any of us would refuse to buy anyone else in this channel a drink. Things really do get silly over text sometimes. [19:23] +1 [19:23] I agree with that. [19:24] I miss physical UDSs [19:24] I have made the suggestion that we have a physical UDS once every LTS [19:24] cprofitt: Awesome, are you financing it? [19:24] get this chat on a google+ hangout ;) [19:25] Google :( [19:25] :( [19:25] the only issue with that is you'd probably see some real middle fingers :) [19:25] Pricey: I could try to finance it, but I doubt that I can run a debt as far as a government [19:27] actually I can't finance it :-) [19:27] cprofitt: well that's a bit selfish ;) [19:27] true [19:27] can't you sweet talk jono or mark? [19:27] ;) [19:28] I appreciate that he checked his financial statement first. [19:28] with three kids I have very little money [19:28] I will try sweet talking both jono and Mark [19:28] tell me about it, cprofitt my son is minecraft mad at the moment. [19:28] not sure it will work though [19:33] changing the subject a bit, can someone takea look at this - https://wiki.ubuntu.com/IRC/AppealProcess?action=show&redirect=IrcTeam%2FAppealProcess [19:34] is this right? - [19:34] ubottu? [19:34] MooDoo: not sure [19:34] ubottu.com is correct I think [19:35] ok i'll shut up :) [19:35] no need to shutup .. it was a fair question [19:35] MooDoo: https://wiki.ubuntu.com/IRC/AppealProcess?action=diff&rev1=7&rev2=8 jussi added it so i'd assume it was probably correct. [19:36] okey cokey.... [19:42] hi all [19:42] hey AlanBell [19:43] hello [19:44] * AlanBell reads back lots and lots of stuffs [19:44] yes, lots of stuff. [19:45] AlanBell: it'll give you a head ache ;) [19:53] MooDoo: yeah, it will [19:53] :) [19:54] ok, first thing that I can actually answer :) is the address that creates a ticket in http://ubottu.com/tickets/scp/login.php [19:54] so, for appeals, we get a ticket to track [19:54] oh, good [19:54] ah there is a ticketing system [19:55] mostly appeals are of the nature of someone who got abusive, got kicked out, appeals to the IRCC to overturn the decision [19:55] Did kind of wonder about < IdleOne> I was thinking about this a little earlier. I think a big problem is that we are trying to govern this giant country and not letting each city do it's own thing. [19:55] we then spend a ridiculous amount of time and effort that nobody knows about, discussing the matter with the user and *almost* always backing up and supporting the decision of the operator [19:55] because the IRCC is there to support and back up the operators [19:56] (We have a "review IRCC tickets on the agenda for every meeting, didn't everyone know it existed? :/ ) [19:56] which is what I may have mentioned in the reply I did to the open letter . . . [19:56] AlanBell: Is that the point of the IRCC? [19:56] we are *not* here to regularly review and discipline the operators [19:56] Pricey: it is one of our functions, yes [19:56] IRCC not being IA is a good thing™ [19:57] Unit193: IA? [19:57] internal affairs [19:57] ? [19:59] so one of the things that I have been doing is trying to make sure that regular problem users have a ban history from multiple operators, so they can't claim a vendetta from one operator for example [20:00] Pricey: I didn't kick LjL earlier I simply muted him. My intention is not to keep anyone from expressing their opinion on this very heated topic, but I will not let someone blatantly break the CoC and channel guidelines that are currently in place. Especially from someone who helped to create those guidelines and knows better. [20:00] there has been quite a lot of conflicting opinion recently on what the IRCC should be doing [20:01] I am coming to the conclusion that I don't know enough about the IRCC to make any real recommendations here. [20:01] some have suggested that the IRCC should personally interview all the operators in turn, to find out what their opinions on life are or something. Not really something I want to do tbh [20:02] we are always available, but proactively going round everyone isn't really what it is about [20:02] I also would appreciate that before you go around pointing fingers at me or anyone else, make sure you know what you are talking about. I respect that you have been a long time user and contributor to this community. I know you were one of the original IRCC members. [20:02] AlanBell: Yeah... I do not feel that is possible given the time it would take... and the chance for positive results would be low anyway [20:03] we really don't do an awful lot apart from protecting ops from appeals, and the occasional channel management decision where one has to be done [20:03] IdleOne: what are you talking about? [20:03] AlanBell: That's a bit sad. [20:04] cprofitt: think that was addressed to Pricey [20:04] Pricey: in what way? [20:04] * cprofitt nods to AlanBell [20:04] so some people think the IRCC should do less, or not exist [20:04] ok.. misread that [20:04] cprofitt: I don't appreciate having my actions questioned when I know from experience that there was no other choice. [20:04] IdleOne: I agree with that. [20:05] I am up for making changes, really I am [20:05] All I am saying is that in this particular case maybe Pricey is not aware of all the history. [20:06] so after the main part of the recent drama, we were discussing factoid over-use, and someone suggested doing a bit of a collaborative review of them, and how we use them [20:06] AlanBell: the problem I see is that many of the potential solutions bring with them other issues [20:06] this was the *first* actionable suggestion I had seen, so I figured it would be good to get on with it, but there was resistance to it that I don't really understand [20:07] I thought the general consensus was, factoids should be for technical things only, not op issues. [20:07] like !grub vs !language [20:07] maybe I misunderstood? [20:07] we have no idea what the general concensus is [20:08] ok. [20:08] well that is how I see it. So there's that. [20:08] some people suggested reviewing it, so we started to do so [20:08] it was an easy way to get people to work together again [20:08] it is possible that we will delete every non-technical factoid, or some of them, or none of them [20:08] Not sure why there would be resistence to a review of it either AlanBell [20:08] but I am not going to autocratically decide [20:08] and maybe start to rebuild some semblance of a team [20:09] * cprofitt nods to IdleOne [20:09] Factoids like !ru, !es etc, are useful to redirect people, tho, specially when they don't know English well (or at all) [20:09] I can agree there [20:09] http://pad.ubuntu.com/factoids [20:09] some people saw it as an attempt to sweep things under the rug [20:09] Daekdroom: that's understandable [20:09] IdleOne: i don't agree with them. [20:09] so that is the list we started to put together, but then we got stomped on for reasons I don't think were sufficiently well explained to me [20:10] "Either you have not been granted access to this resource or your entitlement has timed out. Please try again." [20:10] :( [20:11] popey: can you give phunyguy access to the etherpad please [20:11] I already requested it on LP [20:11] just needs to be approved [20:11] IdleOne: sure [20:11] thank you [20:11] yes, thank you [20:11] phunyguy: approved [20:12] ah didn't know AlanBell could do it too [20:12] yeah, I was somewhat involved in etherpad use for UDS [20:13] yeah, there's a few admins [20:13] AlanBell: maybe adding the various ops teams would be good? [20:14] sure, adding teams is a touch non-trivial as it sometimes emails every team member, but the ops teams I can do [20:14] done [20:16] yeah, you know I don't mind so much getting a few extra emails. easy to delete what is not important and move on with my life :) [20:16] yeah, just a bit scary when you do it to ~locoteams or whatever [20:18] looks like a good document to work on as a team. [20:18] from my perspective having some warning factoids -- that everyone agrees with the wording on might be helpful [20:19] I'm no team building expert or anything but it seems to me that a team is only a team if they work together on a real concrete, tangible?, project. [20:19] phunyguy: you can offer a suggested alternate to any of the factoids on there. [20:19] IdleOne: I agree [20:19] I am adding my notes. [20:19] gentleman... I need to go cook dinner for the family, but I will be back [20:20] that is great phunyguy :) [20:20] cprofitt: I'd far prefer to see nice human to human conversation than "warning factoids" used at every possible opportunity. I'm pretty sure !coc was almost a meme at one point. [20:21] !coc [20:21] The Ubuntu Code of Conduct is the document that spells out etiquette in the Ubuntu community | http://www.ubuntu.com/project/about-ubuntu/conduct | For information on how to electronically sign the CoC, see https://help.ubuntu.com/community/SigningCodeofConduct | Watch http://static.screencasts.ubuntu.com/videos/2010/12/22/004-SigningCoC.ogv [20:21] * AlanBell adds to the list [20:22] hmm, it actually has helpful information in it now [20:22] it was along with a few others. That is actually what brought on the discussion of over use of factoids by ops and users. that eventually turned into improving some of the factoids but the idea of using them less was not put aside. [20:23] the idea is that we improve some, ditch some, decide to keep some [20:23] but we decide together, not by IRCC dictat, because we don't really do that [20:23] As ops we can start setting the example by not using them as much or at all if possible and also improve/delete what factoids we have. [20:24] and we can use that review to start more of a wider conversation about how we use them in a human kinda way [20:25] This btw was one of the things that many ops and former ops had issue with. We are not human enough. [20:26] turing test for all operators [20:27] Sure this factoid thing is most definitely not the start point to solving all the issues we have, but we have to start somewhere. I doubt there will ever be consensus on *the* starting point. [20:28] I don't have another starting point really [20:28] neither do I [20:28] I know rww and others think that it is wandering off and failing to address the real issues . . . [20:28] but without knowing what the real issues are in an addressable way, I have nowhere else to start [20:29] if someone wants to suggest another starting point (apart from the individual interviews with operators to decide if they are human enough, because that isn't going to happen) [20:30] phunyguy has mentioned a couple but I think the solution to what he said boils down to we aren't human enough. [20:30] Do I have to save these changes on the etherpad, or does it just do it on its own? [20:31] auto saves [20:31] ok good. [20:32] multiplayer notepad, it saves every keystroke [20:34] good. I have made my edits. [20:34] I hope I did it right [20:36] looks good to me, the plan is/was to gather general opinions from more people, and have a team meeting on wednesday 19th march where we would make a final decision about each one [20:37] we have had a general principal of discussing things at any time, but deciding things at a booked time [20:38] setting a date for a final decision to be made gives people a deadline to get things worked on. [20:38] that way people don't miss the end of the discussion and the decision if they don't want to, they can arrange to be there [20:38] without a deadline you never get things done. Least that is how I am. [20:38] ^ [20:39] I've been meaning to build a shed for the past 20 years [20:39] silly example I know [20:39] we could all decide what colour to paint it [20:50] aurbegine ;) [20:51] I'm not a fan off eggplant [20:51] of* [20:53] #dd4814 [20:53] sky blue is a good colour for a shed [20:54] note to self: remove this channel from auto-attach [20:55] glad I run irssi in a ssh session, i'm never leaving [21:38] * rww yawns [21:39] tired? bored? [21:39] just woke up [21:40] lol 21:40 pm for me [21:40] it's past 2pm here, but it's a weekend, and daylight saving time just kicked in, so i get a free pass [21:40] * rww reads scrollback [21:52] AlanBell: yeah, I was pondering that opinion last night, and I retract my objection to factoid review, it's a reasonable start to one of the multitude of issues we have [21:52] thanks rww [21:52] and as far as op rotation: there are some ops that are good at opping some particular channel(s) and would be a bad fit for other channel(s), which would make that challenging [21:53] oh, yeah, op rotation is another actionable suggestion I suppose, I am personally unconvinced it is a workable one, but I should acknowledge it as a suggestion [21:54] i feel a bit useless right now in that I can see some things that are wrong but don't have suggestions for improvement for whatever reason, so i am talking less than usual (which perhaps means that i am talking the same as a normal person, i dunno) [21:55] if ops are comfortable in one channel and you rotate them, surley they would leave and you'd be in a worse state that you are now? [21:55] they'd be unhappy, and the users of the channel would probably be unhappy [21:56] yeah, ops generally op the channels they participate in [21:56] you can't just be assigned #kubuntu for a week and be expected to sit there waiting for something to happen [21:56] e.g. I have ops in #ubuntu-devel and have zero interest in actually reading that channel or opping it, I'm just there to deal with blatant spam. If someone decided to rotate me from #ubuntu to #ubuntu-devel, I would be unhappy. [21:56] however, that is a suggestion for change that has been made [21:57] ditto #ubuntu to #lubuntu ;) [21:57] can't you have a ops section that is a group for ops that don't mind being shuffled around? [21:57] * AlanBell is off to watch telly for a bit o/ [21:57] laters [21:58] Since we're throwing suggestions out there, I just had a thought. I haven't eaten yet today so it's probably a bad one tho. Stop having an IRC Council and formal IRC Team, and make an #ubuntu team, an #ubuntu-offtopic team, etc., work by consensus in those teams, and have here or #ubuntu-ops as a collaboration space much like one of #ubuntu-irc's functions was supposed to be collaboration between non-core ops [22:06] well, we can also see ops rotation as enforced time off -- op 1 takes a leave, op 2 comes in [22:07] it is something to look at for sure but i don't see it as an option that we can apply quickly [22:07] could be a good thing to implement with new ops [22:11] and opt-in with existing ops [22:11] yup [22:13] I do think that very strict set of guidelines to how this rotation will happen and when is needed before anything gets started [22:14] exactly how much time before an op is rotated? which channels do we go to and from? all these things need to be clear before hand [22:15] What? [22:15] no! [22:15] I am not OK with this [22:15] a priori, I think that 2 years would be a good span. [22:15] 2 years on, 2 years off? [22:15] 2 years in, enforced vacation for -- say 6 months [22:15] rww: no [22:17] phunyguy: you are no longer a new op :) [22:17] anything that starts would start after your arrival [22:17] one of the issues I have seen here since I came is turf. King of the Hill. Whatever you want to name it. Rotating ops this way might alleviate it, and might as well help in spreading the culture of a channel [22:17] still not OK with it [22:17] as a new op I wouldn't be either [22:18] phunyguy: sorry, wouldn't be either what? [22:18] I wouldn't be OK with it. I probably need to read the backlog though [22:18] not giving it my full attention, but the initiall thing I just read about rotating ops through channels, doesn't sit well with me [22:18] phunyguy: also, please note that these are *options* we are all putting up. Which ones make sense, or not, are to be found via this discussion [22:19] hence me discussing. :) [22:19] but I personally expect something more detailed than "I am not OK" ;-) [22:20] yes, I apologize. I can't give this my full attention at the moment [22:21] no problem, take your time [22:21] nothing is being decided, we are all just brain storming [22:22] phunyguy: no problems. Keep it in the backburner, and omment on it later on. Remember, these are *options*, probably mal-formed ideas. Perhaps some -- like mine -- deserve nothing better than being shot down as fast as possible. But, still, if we do not put them (ideas) up for discussion, nothing will happen. [22:23] I think one rule the IRCC should make (not now) is to make all final decision during meetings. [22:24] this is something that can be voted on at the next meeting maybe [22:24] IdleOne: We should decide that at a meeting first. [22:25] does this include decisions that aren't usually up for public vote? e.g. ban appeals? [22:25] Pricey: lol :) [22:25] rww: I'm not sure really [22:26] again, still brain storming stuff [22:31] the best thing I am seeing today is discussion... [22:31] it is starting to move things forward [22:32] and all it took was me setting fire to the house [22:32] * IdleOne stops kidding [22:32] lol [22:33] I agree. I like that we are talking about all these things. [22:44] 22:23 < IdleOne> I think one rule the IRCC should make (not now) is to make all final decision during meetings. [22:44] we kinda do [22:44] except, that no decisions are final ;) [22:44] true [22:45] Maybe what I am saying is that it would be nice to be able to speak in a public channel about something without it being assumed it is the "official" position [22:46] just because I might say rww smells weird on thursday doesn't mean the entire ircc thinks so [22:51] they do though ;( [22:51] i feel like that's been more of a thing with this IRCC than previous ones, for some reason, especially w.r.t. chairperson saying things [22:51] well yeah. ok, bad example [22:52] rww: so it isn't just me who feels this [22:52] ? [22:52] probably because it got given to the loudest IRCC member :3 [22:52] well I'm glad you said it [22:52] I am rather loud [22:52] well, so am I [22:53] a little, but I like that about you. [22:53] there is no uncertainty with you, least not for me. [22:54] rww: I think it is a lot less with this IRCC actually [22:54] I was much more kinda spokespersonish last IRCC, this time so far we have all been speaking quite a bit [22:55] but I think you sort of missed a couple of years :( [22:55] true [23:01] maybe what the ircc should do is more like what the loco council does. They let each loco do their own thing and check in now and then to see how everything is going. [23:01] I think this is basically what rww said also [23:02] that sounds like a reasonable suggestion IdleOne [23:02] IdleOne: yeah, I was drawing off of the LoCo Council there [23:03] as a LoCo team lead, my perception is that the LC doesn't get involved in day to day LoCo stuff unless we go chat with them, or there are complaints, or there's a health check [23:03] which is probably a saner position to be in than the cat herding that IRCC tries to do right now [23:03] * AlanBell wonders what cat herding we have been trying to do [23:04] "An idiomatic saying that refers to an attempt to control or organize a class of entities which are uncontrollable or chaotic. Implies a task that is extremely difficult or impossible to do, primarily due to chaotic factors." [23:04] that sounds like the entire job description of IRCC to me [23:04] really, meetings have been like this [23:04] https://wiki.ubuntu.com/MeetingLogs/IRCC/20131027 [23:05] action packed [23:05] i'm not talking about meetings, i'm talking about the 99% of your recent job that's been outside of them [23:05] anyways, this is tangential [23:06] so yeah, there has been some firefighting recently, but we have absolutely not been micromanaging channels [23:17] oh dear LjL isn't happy [23:17] rww: the loco team does have to get involved in some day to day things for some teams [23:18] cprofitt: after complaints and such, yes [23:18] no, not just after complaints [23:18] if there is a team that is struggling they will step in to help [23:18] okays, add that to the exceptions above, then [23:18] most things are reactive, but some are proactive