#title #ubuntu-meeting: IRC team Meeting started by AlanBell at 18:58:14 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-02-18.58.log.html . == Meeting summary == ''LINK:'' https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda (AlanBell, 19:03:01) *Review last meetings action items *people to provide feedback on the ubottu-fr trial on bug 892500 (AlanBell, 19:04:08) ''LINK:'' http://nicolas.coevoet.fr (niko, 19:26:23) *Open items in the IRCC tracker *Review Bugs related to the Ubuntu IRC Council *bug 788503 IRC Guidelines too #ubuntu centric - tsimpson (AlanBell, 19:27:49) ''LINK:'' https://wiki.ubuntu.com/IRC/Guidelines has been updated (AlanBell, 19:28:37) *bug 884671 Ubuntu IRC operator recruitment is slow and ungainly - jussi (AlanBell, 19:29:52) *bug 892500 eir is still not fit for purpose in #ubuntu -ikonia (AlanBell, 19:35:14) *bug 913541 there are a number of people with Ubuntu IRC cloaks who have expired from the ubuntumembers group (AlanBell, 19:36:09) *bug 916247 devel wiki on ubottu.com needs some attention (AlanBell, 19:37:25) *end of the induction/probation period for the current intake of operators ''LINK:'' https://launchpad.net/~irc-lubuntu-ops/+members#active (AlanBell, 19:43:53) *Calling for new operators ''ACTION:'' AlanBell to sort out a call for ops (AlanBell, 19:52:57) *alignment of launchpad teams and channel access lists ''LINK:'' https://docs.google.com/spreadsheet/ccc?key=0Ankl5FhsdSiZdGZVV2ZuLVRwa2c5M3pqX3BEaUhXMFE (AlanBell, 19:57:29) *UDS blueprint ''ACTION:'' AlanBell to schedule UDS session (AlanBell, 20:08:07) *setting up an election of another council member *set up #ubuntu-discuss for on-topic non-support discussion and ramblings ''LINK:'' http://paste.ubuntu.com/963188/ (AlanBell, 20:38:01) *Any Other Business Meeting ended at 20:48:42 UTC. == Votes == == Action items == * AlanBell to sort out a call for ops * AlanBell to schedule UDS session == Action items, by person == * AlanBell ** AlanBell to sort out a call for ops ** AlanBell to schedule UDS session == People present (lines said) == * AlanBell (165) * ikonia (71) * topyli (67) * Myrtti (31) * oCean (29) * Sidewinder (20) * funkyHat (19) * LjL (17) * Resistance (8) * ubottu (7) * meetingology` (5) * guntbert (5) * niko (5) * tsimpson (4) * dax (4) * Unit193 (3) * EvilResistance (3) * jussi (1) == Full Log == 18:58:14 #startmeeting IRC team 18:58:14 Meeting started Wed May 2 18:58:14 2012 UTC. The chair is AlanBell. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 18:58:14 18:58:14 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 18:58:25 hi all, who is here for the IRCC meeting? 18:59:02 present 18:59:04 _o/ 18:59:05 yessir 19:00:03 lets give it a few minutes for others to pop along 19:02:03 hi funkyHat and topyli 19:02:15 o/ 19:02:53 Hi ô/ 19:03:01 https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda 19:03:24 ok, lets get started 19:03:53 we don't have to clear out in a hurry at the end of the hour, but lets try and get through it by then anyhow 19:04:05 #topic Review last meetings action items 19:04:08 #progress people to provide feedback on the ubottu-fr trial on bug 892500 19:04:10 Launchpad bug 892500 in ubuntu-community "eir is still not fit for purpose in #ubuntu" [Undecided,In progress] https://launchpad.net/bugs/892500 19:04:31 do we have any? 19:04:35 only a little bit of feedback provided, anyone got anything else to add about ubottu-fr 19:05:23 Have not really been able to actually test it 19:05:44 Or more honestly, Ignored it, since it's confusing to have to work with multiple bots 19:06:26 And I still think that the list with bugs filed for eir is valid for any bot handling our bans/mutes 19:06:36 I've fed back on ubuntu-fr, I think it's the way to go 19:06:40 um, ok, but that doesn't help us to get to the goal of not having multiple bots 19:06:48 it needs trimming down though 19:06:57 but you can only do that once you've picked a direction to develop 19:07:55 Can we assume, with little feedback there is, others have ignored it too? 19:07:55 ok, I like the idea of using the ubottu-fr code too 19:08:37 that seems likely 19:08:51 yeah 19:09:11 I think that is because we are not sure which way we're going 19:09:27 yes, pick a path and lets go ! 19:09:30 get behind it like it or not 19:09:38 I'll even shut up about eir if that's the way you want to go 19:09:42 but lets get stuck in 19:09:59 I definitely agree 19:10:27 at least there has been discussion this time 19:10:30 thought/testing behind it 19:10:35 get some opinions etc, 19:10:46 it is something we can maintain as well 19:11:12 AlanBell: the work niko has done makes it pretty much "too good" out of the box, so we should be able to trim it back 19:11:13 i think we can do trials, but either we all say "ok, we're trialling ubottu-fr, so let's ONLY use ubottu-fr for a month [or whatever] and nothing else", or otherwise we'll all continue using what we're used to 19:11:15 rather than develop it 19:11:29 LjL: yeah, the dual bot thing has confused me a bit 19:11:36 ok, lets move on for now, we will come back to the eir bug in a second 19:11:39 lets wade in, one way or another 19:11:58 that is a fair point about not using multiple bots, thats why we moved eir out of the way 19:12:03 has it gone ? 19:12:09 so that it would still process expiries 19:12:12 I thought we where still supposed to be using it 19:12:27 it was still in #ubuntu picking up bans the other day 19:12:29 it is in #ubuntu-ops-monitor 19:12:34 we just moved the control channel 19:12:42 AlanBell: yeah, but it's still picking up bans in #ubuntu, so it's not going to be phased out 19:12:47 it's just not spamming #ubuntu-ops-team any more 19:12:56 right 19:12:58 well it will pick them up if it is there 19:13:08 but it is mainly there so that it will remove bans 19:13:08 can we dump it out of ubuntu for a while ? 19:13:24 Sure, most of us are still using eir 19:13:33 oCean: that's why LjL's point is valid 19:13:38 yep 19:14:02 if someone has a ban set to expire in 30 days or so and we remove eir altogether then that removal won't get processed 19:14:12 could the council have a little think please and knock up a draft plan ? 19:14:25 it makes sense to use code that already fits with supybot if we are aiming for a single bot solution 19:14:28 AlanBell: could we not say "we'll work it out manually for a while" 19:14:45 just to phase it out, we can always phase it back in if it's decided eir is the way forward 19:15:17 i don't think eir needs to be removed, just for it to be made clear that it's not the one to be used (if it's decided so) 19:15:28 one way or another we'll have to deal with those bans 19:15:28 LjL: but it picks up every ban 19:15:40 it will still have it in the database and the default nag of 2 days option (or whatever it is) 19:15:45 AlanBell: I can still update the overview on somedom, so we can see which ban has expired 19:15:48 then remove manually 19:16:02 is there a way to put it into read only mode 19:16:06 so it doesn't pickup anything new ? 19:16:18 probably not 19:16:22 Also, I think eir can still remind us of exired bans even when eir is not in #u 19:16:25 not without affecting other channels 19:16:33 ahhh of course 19:16:37 didn't think of the other channels 19:16:54 How many bans are likely to be in eir? Would it be feasible to move them manually to ubotu-fr after disabling eir in #u? 19:17:16 funkyHat: currently 107 19:17:21 Or script it if we can get a detailed enough output from eir 19:17:28 funkyHat: oCean 's script run weekly until they are phased out would probable work simpler 19:17:31 just review on a sunday or something for a month or two 19:17:36 Ok 19:17:38 hell, I'll take an action to do it if needed 19:17:42 sounds good 19:17:45 exactly 19:18:17 i'd be fine with that 19:18:34 it's not exactly a long term issue, and probably just a simple way of phasing it out 19:18:45 Yep, sounds good 19:18:51 what is the overlap between ubottu and ubottu-fr? Can we put bits of ubottu-fr into ubottu easily? 19:19:28 as I recall niko basically did a modular hot swap 19:19:30 so you can swap in / out what you want 19:19:38 ubottu-fr was just a snapshot of ubottu's later code from what I recall 19:19:38 ikonia: I am only a bot, please don't think I'm intelligent :) 19:19:44 do we want to phase it out before we know whether ubottu-fr is "good enough", though? do most of us currently know anything about ubuntu-fr? i'm still leaning towards something like yelling at every op "use ubottu-fr instead of eir for a month!", but without killing eir immediately 19:20:01 that depends on how ubottu-fr works, ubottu is a regular supybot with plugins. so as long as all the code is external to supybot, it should be fine 19:20:05 ikonia: no, i don't think it is just that. it has been modified (the supybot core, that is) to my knowledge 19:20:30 the good news, i seem to recall, is that the modifications are being pushed upstream (to supybot)... don't quote me on that, it's what i seem to recall hearing 19:20:31 LjL: I don't know, so I'm not stating anything factually 19:20:51 ok, we need to have a chat with niko about this 19:21:03 heh, good luck getting anything upstream in supybot 19:21:16 there is some core changes in ubotu-fr, that means, you can't use channel plugin of ubotu-fr without the full bot, but that means too that you can load any kind of ubottu plugin into ubotu-fr 19:22:02 oh that sounds fine then 19:22:05 niko: yeah, it's inconvenient, though, to rely on a non-standard supybot. should we need to put a bot up quickly, we can't just apt-get supybot or whatever 19:22:36 But LjL has a point, with so little review/trials done on ubotu-fr, how much do we trust it, to replace eir, and actually remove eir from #u 19:22:41 so we can load all the ubottu plugins into an ubotu-fr clone and bring it up as ubottu 19:22:42 wget the tar files, sudo python setup.py install, and that's all 19:23:12 So what are the issues with getting ubotu-fr code into supybot? 19:23:33 tsimpson: I'm guessing you've had a tough time getting anything upstream ? 19:23:39 ubotu-fr code is dedicaced for ircd-seven, that's the big point 19:23:46 ikonia: upstream seem dead 19:23:49 ahh 19:23:53 so very hard then 19:24:03 aren't we getting a little ahead with discussing merges etc? 19:24:08 niko: would it be possible to make that part a "module" rather than part of the code base 19:24:11 oCean: sorry, yes 19:24:28 I got excited 19:24:39 why not fork it properly then, if upstream is not maintaining the original? 19:24:40 ikonia: not really, too much stuff need to be done in core files, due to how supybot was written 19:24:50 topyli: because the code is both insane, and ugly 19:25:00 ok :) 19:25:02 if we trust current ubotu-fr enough, I say remove eir, bring ubotu-fr in, and run,test,file bugs, etc 19:25:10 I have the impression tsimpson may not have had a good time 19:25:29 yeah, I think we need to jump in with both feet here 19:26:06 we also need to get through this meeting :) 19:26:11 Is there a manual/usage wikipage of some sorts on ubotu-fr usage? 19:26:23 http://nicolas.coevoet.fr 19:26:55 I will mail the list with a plan to set up an ubottu-fr clone with the ubottu plugins loaded and get it to replace ubottu 19:27:11 niko: I see very few lines under usage :) 19:27:12 we can discuss on the mailing list and at UDS for those going or attending remotely 19:27:21 OK 19:27:27 lets crack on with the agenda now 19:27:33 #topic Open items in the IRCC tracker 19:27:38 there are none \o/ 19:27:43 #topic Review Bugs related to the Ubuntu IRC Council 19:27:46 yay! 19:27:49 #subtopic bug 788503 IRC Guidelines too #ubuntu centric - tsimpson 19:27:51 Launchpad bug 788503 in ubuntu-community "IRC Guidelines too #ubuntu centric" [Undecided,In progress] https://launchpad.net/bugs/788503 19:28:04 ok, I put the text we had on the wiki 19:28:17 yeah, thanks for that 19:28:37 https://wiki.ubuntu.com/IRC/Guidelines has been updated 19:28:52 it is improved 19:28:58 I think it is better than it was, if there are further improvements to be made then great, we can make them on the wiki 19:29:09 yes 19:29:16 So is this done? ⢁) 19:29:16 I will close that bug now 19:29:29 fix released 19:29:52 #subtopic bug 884671 Ubuntu IRC operator recruitment is slow and ungainly - jussi 19:29:53 Launchpad bug 884671 in ubuntu-community "Ubuntu IRC operator recruitment is slow and ungainly" [Undecided,In progress] https://launchpad.net/bugs/884671 19:30:32 so for this one we have a new procedure of processing applications from existing core ops as fast as we can conveniently do it 19:30:42 this is streamlined a bit with the fast approval of "old" ops 19:30:44 yes 19:31:04 I think we have one to do from a couple of days ago, but generally we are responsive on this now 19:31:44 I also want to do a big call for ops for lots of channels and process all the queues to do an intake of operators for the Quantal cycle 19:31:59 and generally have an intake at the start of each development cycle 19:32:21 I think that makes operator recruitment regular and quite gainly 19:32:29 so I think that bug is fixed :) 19:32:57 we could compile a list of channels and simply send out a call for ops. it's been a while 19:33:11 yup, and it is the start of the cycle 19:33:18 yes 19:34:30 Just for the record: I still think you should have a "procedure" (or lack of one, whatever makes it happen) for appointing ops outside of a semestral recruitment process or whatever. And I'm not sure I see how a new release makes new ops automatically needed, on the other hand. But this has been discussed a lot before, so I'm just saying this for the logs, basically. 19:34:30 we can close the bug 19:34:45 fix released 19:35:01 noted LJL 19:35:14 #subtopic bug 892500 eir is still not fit for purpose in #ubuntu -ikonia 19:35:15 Launchpad bug 892500 in ubuntu-community "eir is still not fit for purpose in #ubuntu" [Undecided,In progress] https://launchpad.net/bugs/892500 19:35:55 so on this one we look like going in the ubotu-fr direction, I will mail the list and get some actions together for this. 19:36:09 #subtopic bug 913541 there are a number of people with Ubuntu IRC cloaks who have expired from the ubuntumembers group 19:36:10 yeah, the ubottu-fr plan covers this 19:36:11 Launchpad bug 913541 in ubuntu-community "there are a number of people with Ubuntu IRC cloaks who have expired from the ubuntumembers group" [Undecided,In progress] https://launchpad.net/bugs/913541 19:36:22 Pici: did you get anywhere with this one? 19:37:09 um, pici hasn't said anything, maybe he is indisposed 19:37:15 lets move on 19:37:25 #subtopic bug 916247 devel wiki on ubottu.com needs some attention 19:37:27 Launchpad bug 916247 in ubuntu-community "devel wiki on ubottu.com needs some attention" [Undecided,In progress] https://launchpad.net/bugs/916247 19:38:12 well this was full of spam, that got cleared up and locked down, migrating the data to wiki.ubuntu.com might be a good idea, but the formatting will need a lot of manual fixing and nobody is leaping forward to take on that rather dull task 19:38:37 I can help with it, I can't "do" it 19:38:43 the ubuntu wiki is a tough mistress 19:38:44 the bug was the spam, which has been addressed, I don't think the devel wiki in itself is a major overhead to have just sitting there 19:39:06 I am inclined at this point to just leave it and close the bug 19:39:20 moving the content is a different issue really 19:40:37 ok, commented and [C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C fix released then 19:40:42 oops 19:40:54 ok 19:40:59 right, moving on 19:41:08 #topic end of the induction/probation period for the current intake of operators 19:41:37 oh it's time is it? 19:41:37 so we have a bunch of operators from the #lubuntu area who are at the end of their 3 month intro period 19:42:24 there have been a couple of resignations from people who for various reasons decided not to continue and I think one of them never showed up at all 19:43:17 we should email them individually I think 19:43:18 remind us of the nicknames again? 19:43:29 or shhould I go check myself :-P 19:43:53 https://launchpad.net/~irc-lubuntu-ops/+members#active 19:44:06 i haven't noticed any serious worries with the lubuntu ops. those who are not active are another story 19:45:09 * AlanBell tidies up a couple 19:46:17 * Myrtti nods 19:46:37 anyone know m0hi? 19:47:02 not me 19:47:10 AlanBell: IAmNotThatGuy 19:47:25 oh, I have seen that nick 19:48:12 IAm... is currently in #ubuntuforums 19:48:35 Shall I ask him to join here? 19:48:42 Sidewinder: that would be great 19:48:45 is he active in #lubuntu ? 19:48:47 K 19:48:51 he's on the channel 19:49:02 there hasn't been that much need for ops there... 19:49:32 then again I can't remember if he was on the lesson at -classroom either, and I don't know if he needs it 19:49:41 oh maybe i should apply there myself, i like that kind of channels 19:49:58 yeah, I don't have any concerns really, as an Ubuntu Member 19:50:49 AlanBell, I politely paged IAmNot ThatGuy 19:51:11 ok, thats fine, will chat later, I don't have any concerns really 19:51:19 idle 29minutes 19:51:25 (There is no meeting directly after this) 19:51:41 ok, lets move on 19:51:43 #topic Calling for new operators 19:51:53 ok, new cycle new intake of operators 19:52:00 yes let's just do it 19:52:18 Yep 19:52:21 I will update my list of everyone in the queue and do a call for ops 19:52:44 then we can process the queues and get a new group in 19:52:54 ok 19:52:57 #action AlanBell to sort out a call for ops 19:52:57 * meetingology` AlanBell to sort out a call for ops 19:52:57 which channels are we looking for? 19:53:05 and do you want me to redo my classroom? 19:53:45 pretty much all the core channels and yes please Myrtti 19:54:09 and I want to get a few more classroom sessions scheduled too 19:54:19 you did have a good subject which you might do every now and then if you have the energy 19:54:21 may I suggest a specific call for certain timezones? 19:54:43 good point, what times are in need of coverage? 19:55:22 I think nighttime Europe is always in need 19:55:33 few extra eyes wouldn't be bad 19:55:56 so, pacific america? 19:55:58 ok, kind of 00:00 to 08:00 UTC 19:56:15 topyli: or au/nz/jp 19:56:17 doesn't really matter where people actually are, just what time they are on IRC 19:56:22 depends on the viewpoint 19:56:25 exactly 19:56:38 yeah :) 19:56:46 ok, I will put something about that in the call for ops 19:56:48 ok, moving on 19:56:57 #topic alignment of launchpad teams and channel access lists 19:57:17 right now the access lists and launchpad teams are in approximate agreement at best 19:57:29 https://docs.google.com/spreadsheet/ccc?key=0Ankl5FhsdSiZdGZVV2ZuLVRwa2c5M3pqX3BEaUhXMFE 19:57:38 is all the access lists 19:57:51 someone was helping with this, no? 19:57:58 anyone who pms me an email address can have edit access to thi 19:58:24 knome was helping to identify some issues 19:59:12 I was thinking of doing a bit of automation to get the launchpad groups and the access lists in the spreadsheet side by side 19:59:19 then we can make them all match up 19:59:29 hasn't Pici done work on this before 19:59:31 maybe worth checking 19:59:37 AlanBell: i see one flaw there, though: not every nickname that patches on Launchpad is up-to-date here on Freenode 20:00:13 s/patches/is/ 20:00:13 EvilResistance: that is a good point, but everyone in the core ops team does have a nick on their launchpad page (I checked) 20:00:38 if any don't tie up I will be asking them to change the launchpad nick to their account name 20:00:39 indeed, just wanted to point that out, you'd need to make sure the nicks are kept up to date ;) 20:00:45 it is done on account names rather than nicks 20:00:46 isn't it a requirement in the first place, so you can be an op? :) 20:01:20 account : Resistance 20:01:35 :P 20:01:58 ok, don't need to go through the spreadsheet line by line right now 20:02:01 oh, one thing 20:02:24 VotiA or VotriA or something else as the default? should it be the same over all channels? 20:02:36 and should people have founder flags? 20:03:50 some channels have a wide assortment of flags for operators, it looks a bit messy but I guess it works fine 20:03:55 AlanBell: from an ITSec point of view, i think that only members of IRCC should have the founder flag, anyone else who has founder flag has sort of a god power over a channel. 20:04:00 i think we've just done VotiA, but i'm far from clueful in this 20:04:34 ok, we will have a bit of a think about this and work out some conventions I think 20:04:39 yeah i agree, ops don't need founder flags 20:04:43 bit of a pici question 20:04:52 #topic UDS blueprint 20:05:00 so UDS is coming up next week 20:05:10 I am going in person, anyone else going to be there? 20:05:46 Resistance +1 20:06:14 just remote lurking. i'll probably be semi-actively following the community track 20:06:25 wasn't sponsored, so not going 20:06:53 would you like to have an IRCC session set up so we can have a chat over the audio streaming thingie? 20:07:23 why not, if we have something to chat about :) 20:07:56 ok, I will set one up then, I will try to get a morning slot for it 20:08:07 #action AlanBell to schedule UDS session 20:08:07 * meetingology` AlanBell to schedule UDS session 20:08:14 #topic setting up an election of another council member 20:08:33 there are 4 people on the IRCC, there should be 5 according to our charter 20:08:43 yeah 20:09:06 we deferred fixing that into the Q cycle but I think we are now in a much better position to go ahead with it 20:09:30 And we are now in the Q cycle ⢁D 20:09:42 we need to feel around for candidates 20:09:50 I'm happy I'm practically unelectable \o/ 20:09:56 \o/ 20:10:06 I can continue to heckle from the peanut gallery 20:10:23 mmm peanuts 20:10:42 Yep, we can toss the peanuts at them. :D 20:10:42 I know of one potential candidate, and I remember someone else being mentioned too 20:10:56 ok, not much more to say on this one, just wanted to announce it and get started on it 20:11:05 we will talk to the CC about the process 20:11:24 final item now 20:11:27 #topic set up #ubuntu-discuss for on-topic non-support discussion and ramblings 20:11:57 we have had Canonical sending people into #ubuntu to join the discussion about ubuntu 20:12:05 people who don't have an active support problem 20:12:20 #ubuntu-project 20:12:22 this isn't ideal so we talked to canonical about this issue and got it fixed 20:12:41 but it would be nice to have an area for on-topic talk about ubuntu that isn't support 20:12:50 and isn't what -offtopic is 20:12:56 that was always my dream for -offtopic 20:13:35 you can kill #ubuntu-offtopic, or you can talk about interesting things there and make it better, your call i guess 20:13:51 option 2 is always my preference 20:13:57 i'd use -ot 20:14:23 or *continue* to use -ot, rather 20:14:28 I would if you could have a discussion in there 20:14:45 It is quite possible to have a discussion in -ot 20:15:19 well right now it is being used for a perfectly nice conversation about films 20:15:20 Unless you want to create an #ubuntu-offtopic-offtopic, which I wouldn't recommend. 20:15:35 Sidewinder: more of an #ubuntu-ontopic 20:16:03 Not a bad idea; just non-support.. 20:16:03 I don't want to remove #ubuntu-offtopic 20:16:04 so you want a channel for support, a channel for Ubuntu discussions that are not support, and a channel strictly for discussions that are not about Ubuntu 20:16:06 seems overkill to me 20:16:19 and a good way to kill either or both the "secondary" channels 20:16:43 There is that. 20:17:06 i think -ot is just fine for any ubuntu-related discussion. you're not required to talk about flashlights there. it's just for whatever is not support 20:17:08 it is possible that it won't be a viable channel long term, I don't know without trying it 20:17:10 I don't feel that ot is overly busy. 20:17:28 maybe make it more obvious in -ot that is is intended for discussion about ubuntu - not just a general "anything goes" 20:17:39 I don't see much issue with encouraging more ubuntu-related discussion in -ot. At the moment it's not a terribly busy channel 20:17:40 guntbert: well but it's not. it's for both things 20:18:11 guntbert: well it is a general channel too 20:18:16 LjL: ok, (I said 'not just' :-) 20:18:24 If it ain't broke, don't fix it. IMHO 20:19:05 it's not broken. sure, we could always tend to it better, but that's not the channel's fault as such 20:19:05 "Join the discussions in #ubuntu on Freenode" is what the canonical stuff said 20:19:13 I see one problem: quality discussion just don't happen there - do they? 20:19:24 "Join the discussions in #ubuntu-offtopic on Freenode" would be a strange thing for them to say to customers 20:19:35 quality discussion does happen in -ot. just not all the time 20:19:51 so the issue is the channel name? 20:19:53 AlanBell: that's true 20:20:01 guntbert, I think they do; it's not just limited to that. 20:20:54 LjL, I think the name's fine, but that's just me. 20:20:56 LjL: partly, yes, and partly because someone arriving in a totally off-topic discussion might be confusing 20:21:19 canonical could say "join #ubuntu for support and #ubuntu-offtopic for general discussion" 20:21:31 I think arriving to see an off topic discussion is better than joining a dead channel 20:21:33 AlanBell: make #ubuntu-chat or #ubuntu-discuss or whatever and redirect it to #ubuntu-offtopic if the issue is the channel name in "marketing", i don't think that's an issue. if the problem is the content, well i don't think it's an issue either, but i guess it might be 20:21:36 how about doing it the freenode way? #help = #freenode so #ubuntu-offtopic = #ubuntu-discuss 20:21:44 topyli, I think that's THE answer. 20:21:56 i think topyli has the right idea there 20:21:58 Maybe if -ot gets too crowded we could rethink having a -discuss or -project channel 20:22:32 (assuming some of the crowd is actually project related ;) 20:23:29 I too like topyli's proposal 20:24:05 Yep 20:24:34 how much of the crowd at the moment is made up of people who are developers on the project in some way? 20:24:56 pretty much zero 20:25:05 what ikonia said, at the most maybe 1% 20:25:08 in -ot? not too many 20:25:28 offtopic has nothing to do with ubuntu in any way 20:25:30 even community 20:25:32 people don't user/support/discuss ubuntu, it's just another defocus 20:25:37 most of the time it feels like -uk is better for that discussion ;-) 20:25:42 Myrtti: it is 20:25:45 yup 20:26:00 i'm always talking about ubuntu or linux in -ot 20:26:01 s/that// 20:26:14 except when i'm talking about something else :) 20:26:24 Heh,. 20:26:27 topyli: yes, your a rarer beast, as is ljl and a few others 20:26:27 but a lot of the users have no "ubuntu" reason to be there 20:27:15 and lots of people who do some contribution to ubuntu in some context don't really want to be there 20:27:15 there are a lot of people there who don't even use ubuntu anymore, but used to at some point and just like the people 20:27:37 topyli: I don't think you have to use it, but have an interest in it, follow it, be aware of it so you can actually participate 20:27:48 be "involved" in someway 20:27:52 both are fine, I don't want to go shutting down -offtopic as a kind of defocusy chatter place 20:28:11 ikonia: it would be more "ubuntu" that way for sure 20:28:15 a lot of loco teams don't have active channels so -offtopic kind of takes that role a bit 20:28:30 Currently it's just less strict. 20:28:35 topyli: at the moment there is no "ubuntu" community to that channel, beyond the fact that it has the ubuntu coc 20:28:57 it's not made up of members/users/interested parties etc, its just people 20:29:27 you could chnge the channel name to offtopic and it would not have any difference to the users/content 20:29:56 If memory serves, the top three people in that channel don't use Ubuntu; topyli breaks the trend by being in 4th place :P 20:30:11 I don't think using it is a requirement 20:30:13 topyli: have you moved back to Ubuntu now? 20:30:15 :-P 20:30:20 i'm back on ubuntu yes :) 20:30:22 but being part of the community, following it's disucssion/development etc 20:30:30 being able to join in with it in some way 20:30:54 I will refrain from discussing my opinions on whether AtomicSpark is part of the Ubuntu community, but I don't think I (#2) am :P 20:31:31 ok, so how do we draw this item to a conclusion? 20:31:52 yeah you're an example of someone who *was* a part of the community for a long time and now just hang in there with old friends :) 20:32:15 AlanBell: well, frankly i'd do nothing but tell canonical to clarify their message 20:32:19 Homeostasis? 20:32:30 topyli, +1 20:33:02 I'm not on the Council, but I think that, at the least, telling Canonical to clarify their message is the first step, but that more in-depth research and discussion on this topic needs to be done to determine whether an Ubuntu discussion channel needs to exist separate from -offtopic 20:33:04 If we were voting, that is.. 20:33:05 maybe it will improve -ot if canonical starts sending people there, who are actually interested in discussing ubuntu 20:33:08 I agree. And if we want to have more ubuntu related discussion in -ot we need to just have more ubuntu related discussion 20:33:12 Yes 20:33:12 well I did that, and Mark said 20:33:14 * if there is a better IRC channel for general "hello, I'm interested in X with Ubuntu, where should I go?", then let me know and I'll update the team to use that for the cases where they do judge the audience to be developer or at least highly technical in nature. 20:33:30 the other option is that canonical don't send people to IRC 20:33:43 and send them to askubuntu.com or something instead 20:33:50 AlanBell: that'd be cutting out one of the big support communities, there. 20:33:58 well the latter one does not sound very good 20:35:06 i think IRC is better for real-time support, askubuntu.com and ubuntuforums.org take some time to actually get decent responses, and to be honest, there's more people on IRC who really know what they're talking about 20:35:12 (at least, in comparison to askubuntu.com) 20:35:19 it isn't about support 20:35:22 also, it's not *so* terrible to come to the main channel, it's natural. it's just that people will use their energy to guide these people to the correct channels like -ot or -server or whatever 20:35:41 i don't know how big this problem is for #ubuntu 20:35:58 this was about their communications around ubuntu for android 20:36:31 is there *any* channel where people talk about ubuntu for android? 20:36:41 does it even have anything to do with the community? 20:36:47 ^ 20:37:23 maybe the problem is that Canonical and its developers should interact with the community, not "send" people to IRC when there's no way anyone can have a clue about the product 20:37:33 Does it have publicly accessible source-code anywhere? 20:37:48 (because if not, it's not an Ubuntu community project, it's a Canonical project using Ubuntu branding) 20:38:01 http://paste.ubuntu.com/963188/ 20:38:21 silly pastbin with no wrapping 20:38:28 ubuntu one has nicely settled on its own channel, it's not bothering us too much i think 20:38:36 at least that's how it used to be 20:39:18 so yes, there should be more canonical developers involved, but no they are not going to all join #ubuntu-offtopic and stay there 20:39:39 probably not. they have jobs :) 20:40:45 this might be something that could be discussed in UDS... 20:40:58 that is a good point 20:41:09 get some more canonical opinions on the matter too 20:41:36 yes. the devs will be there 20:41:36 indeed 20:41:50 ok I will put it on the agenda of the UDS meeting 20:41:50 AlanBell, What's wrong with them joining #u? I for one have noticed some questions asked there that were not answered and I could not. 20:42:29 Sidewinder: there is nothing to support 20:42:39 Sidewinder: because they don't have a support question and the general feeling at the time was nobody wanted people turning up in #u wanting to "join the conversation" 20:42:40 Sidewinder: that Ubuntu's policy has always (to my knowledge) been that it's a technical support channel only, not for opinions, information about products, discussion, etc - if we opened *that* door, a lot of stuff would come in 20:42:41 Sidewinder: so it doesn't fit on a support channel at the moment 20:43:02 anyhow, lets discuss that more next week 20:43:02 OIC. 20:43:05 #topic Any Other Business 20:43:13 anything else to discuss now? 20:43:18 AlanBell: #ubuntu+1 20:43:23 (see -ops) 20:43:32 ah right, shall we open it again? 20:43:43 if Q is open, why not? 20:43:52 can't see any particular reason no to, the toolchain is open 20:43:56 LjL, I agree. 20:44:07 lets do it 20:44:12 yeah 20:44:18 ok, anything else 20:44:19 AlanBell: One more thing, since you skipped quite quickly through the "eir not fit for purpose" 20:44:29 Recently I removed a lot of bans/mutes. Most of those had no comments at all, so I had to go through logs etc to see if they could be removed 20:44:49 Because I don't really want to go through all that again, and we don't want to do that if we're weekly reviewing which bans can be removed, I suggested changing eir's config (or for any new bot) to autoremove-after-expire. 20:45:01 ok, I think if people are not commenting on bans they are fair game for removal 20:45:06 So if you want a ban/mute to stay, just make sure you btset it with an expire date and/or comment, or after 2 days it is gone and so preventing all these undocumented bans 20:45:42 we can agree, but others should be aware of it 20:45:55 since even after a couple of days, we have lots of expired and uncommented bans again 20:46:18 sounds good to me. an email to the list should handle the communication 20:46:32 yup 20:46:48 oCean: are you volunteering to compose this email? :) 20:47:04 sure, but it would not go out before the weekend 20:47:09 because you would know what you're talking about, unlike me 20:47:13 don t think we're in a hurry though 20:47:33 ok 20:48:17 fine 20:48:22 anything else to discuss? 20:48:42 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)