/srv/irclogs.ubuntu.com/2010/04/25/#ubuntu-meeting.txt

Smexnite folks.03:32
=== Ursinha_ is now known as Ursinha
=== alsroot_ is now known as alsroot
=== yofel_ is now known as yofel
abbra_kadabbraany forum council members happen to be on?17:54
abbra_kadabbraI sent a mail to the mailing list but the spam blocker quarantined it.  I just want to know if it finally went through17:55
abbra_kadabbraping18:07
persiaThis channel generally only has traffic for scheduled meetings.  You'd do better to find a more specific channel (e.g. #ubuntuforums), or wait for the folks you want to have their scheduled meeting.18:13
abbra_kadabbrathanks18:16
* Pici yawns19:00
jussio/19:00
topylihi19:00
jussihave we a tsimpson?19:01
guntbertthats infectious Pici19:01
topylitsimpson was doubtful yesterday19:01
jussishall we start in any case? we have 3 of us...19:01
jussi#startmeeting19:02
MootBotMeeting started at 13:02. The chair is jussi.19:02
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:02
jussi[link] https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda19:02
MootBotLINK received:  https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda19:02
jussi[topic] #ubuntu-release-party access list19:03
MootBotNew Topic:  #ubuntu-release-party access list19:03
jussiikonia: about?19:03
PiciI don't think he needs to be here for this one.19:03
jussiright, so someone want to summarise for the record?19:04
PiciThere are a large number of people on the access list in u-r-p, it was crazy last time around.19:05
jussiSo remove the @ubuntu/member access?19:05
PiciIts open to ubuntu/member/* right now.  Lots of those people are not normally operators19:06
Pici(laggin here)19:06
persiaWas there significant abuse of that right, or just a crazy number of operators?19:06
Pici"The last party channel was a very rowdy channel and a strong portition of the ubuntu member cloak holders where not mature enough to manage the channel without playing silly games. I understand the channel is supposed to be a fun place but kicking people for fun and placing bans in a channel is not part of that fun. I would suggest adding the core channel operators to the list and removing the membership cloak access."19:06
Pici* from the agenda proposal page.19:07
topylitsimpson suggested restricting it to core channel ops, since we have no core ops yet19:07
jussi[idea]I would suggest adding the core channel operators to the list and removing the membership cloak access (ikonia)19:07
MootBotIDEA received: I would suggest adding the core channel operators to the list and removing the membership cloak access (ikonia)19:07
jussiI think thats a good idea, basically replicating the -ops +v list with +o instead.19:08
topyliah, same suggestion :)19:08
topylinhandler said he has a script to copy an access list from one channel to another. this would help if we decide to go that way19:08
jussitopyli: yes, and then make sure that everyone is op, not just +v.19:09
PiciSounds good to me.19:10
topyliyeah19:10
jussiok, lets vote on that...19:10
topyliquestion19:11
Picianswer.19:11
topylii haven't been to the channel in a few years, too old19:11
topyliis that enough ops for the channel?19:11
jussitopyli: I think so.19:11
jussiif its not, we can revisit the idea.19:12
DavieyI'm actually more concerned about the point that Ubuntu Members haven't been acting in a proper way previously.19:12
topylijussi, ok, i'm going to believe you :)19:12
PiciI think we should allow for common sense when adding ops on-the-fly19:12
jussi[vote] add the core channel operators to the list (#ubuntu-ops +V list) and removing the membership cloak access19:12
MootBotPlease vote on:  add the core channel operators to the list (#ubuntu-ops +V list) and removing the membership cloak access.19:12
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot19:12
MootBotE.g. /msg MootBot +1 #ubuntu-meeting19:12
PiciDaviey: Its more that they're not used to operator duties.19:12
Piciand the problems that come along with that.19:13
Pici+119:13
MootBot+1 received from Pici. 1 for, 0 against. 0 have abstained. Count is now 119:13
jussi+119:13
topyli+119:13
MootBot+1 received from jussi. 2 for, 0 against. 0 have abstained. Count is now 219:13
MootBot+1 received from topyli. 3 for, 0 against. 0 have abstained. Count is now 319:13
jussi[endvote]19:13
MootBotFinal result is 3 for, 0 against. 0 abstained. Total: 319:13
ikoniajussi: yes19:13
jussiawesome. now then:19:13
jussi[topic] Consider deactivating/re-purposing the ~ubuntu-irc team on launchpad19:14
MootBotNew Topic:  Consider deactivating/re-purposing the ~ubuntu-irc team on launchpad19:14
jussi[idea] As for ~ubuntu-irc, I haven't seen any good ideas on how to re-purpose it right now, so I would propose removing all members, making it restricted, and adjusting the description to "disable" it for now (nhandler)19:14
MootBotIDEA received:  As for ~ubuntu-irc, I haven't seen any good ideas on how to re-purpose it right now, so I would propose removing all members, making it restricted, and adjusting the description to "disable" it for now (nhandler)19:14
topylii have heard anyone come up with a viable use for it so far19:15
jussiso, thoughts on this?19:15
=== j_ack_ is now known as j_ack
topylihave not, even19:15
ikoniacould it not be used for irc related dicussion ?19:15
jussiikonia: the LP group?19:15
ikoniaoh, sorry the actual group, miss-read19:16
jussi:)19:16
jussiIm with nhandler here.19:16
PiciI'd like to see it eventually turn into our irc-community participants group. Since we currently don't have any way of quantifying that.19:16
ikoniaPici: could you expand on that a little for me please ?19:16
jussiI dont think we need to come up with exactly what it needs to become in the future, but just that for now it should be disabled.19:17
Piciikonia: Its a bit vauge, but we don't have a group right now that includes people in our communtiy that partipate that are not operators.19:17
persiaPici: So a container for the polity that e.g. votes to confirm IRCC?19:17
ikoniaPici: perfect, thank you19:18
jussiYeah, we are working on the membership thing, but that still excludes a lot.19:18
Picipersia: yes.19:18
Picijussi: Yes, but its a start.  We have nothing now.19:18
topyliPici, i like that19:18
PiciBesides operators.19:18
jussiyes19:18
persiaYou might just set to be a moderated team, disable anyone not in ~ubuntumembers, and process the join requests e.g. weekly based on membership in ~ubuntumembers.19:19
jussiok, so the thought is that we disable it for now and think about what it should become, perhaps with some public discussion on the list?19:19
persiaBut I'd recommend checking with the CC about polity definition: there may be reasons to poll the entirety of ~ubuntumembers, even though some folk are rarely on IRC.19:19
jussipersia: the CC dont want us polling all of them19:20
PiciI don't see value in closing it and deactivating its members.19:20
* persia stops attempting to get folk to repeat history19:21
jussiPici: why?19:21
persiaFor what it's worth, I agree with Pici: I think that's needlessly disruptive if the purpose remains undefined.19:21
PiciAgreed.19:21
jussithing is, for me, we need to create a clean slate. Its currently confusing to people - I had someone PM just yesterday (ne op in a loco) asking if they should join it.19:22
Picijussi: Everyone who is in it right now should be in it if we turn it into a 'community users' group.19:23
topylii guess the current members of the group would be included in any larger group we imagine19:23
PiciIf we aren't sure what to do with it at this juncture, then I suggest that we change it's description to say that.19:24
jussiok, so perhaps not cleaning it out, but putting something in the description?19:24
jussilol19:24
Pici:)19:24
jussigreat minds19:24
jussiok, Id agree with that.19:24
topyli"Ubuntu IRC thingy"19:25
jussi[vote] Change the description of ~ubuntu-irc to reflect its current state of disuse, think about the future use of it.19:25
MootBotPlease vote on:  Change the description of ~ubuntu-irc to reflect its current state of disuse, think about the future use of it..19:25
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot19:25
MootBotE.g. /msg MootBot +1 #ubuntu-meeting19:25
jussi+119:25
MootBot+1 received from jussi. 1 for, 0 against. 0 have abstained. Count is now 119:25
Pici+119:25
MootBot+1 received from Pici. 2 for, 0 against. 0 have abstained. Count is now 219:25
topyli+119:25
MootBot+1 received from topyli. 3 for, 0 against. 0 have abstained. Count is now 319:25
jussi[endvote]19:26
MootBotFinal result is 3 for, 0 against. 0 abstained. Total: 319:26
jussiok, great. next item:19:26
jussi[topic] Create policy on external logging of channels (ircanswers.com)19:26
MootBotNew Topic:  Create policy on external logging of channels (ircanswers.com)19:26
PiciCan anyone give some backstory on what this is.  I only caught part of the conversation in u-irc.19:27
jussiSo, I think as long as a party requests it and is not malicious, there is no reason to say no.19:27
jussiPici: go look at the url ;)19:27
Picijussi: It looks like a metabot-like thing.19:28
Picibut on a website19:28
jussiPici: it basically is metabot transcribed to the web19:28
jussi:D19:28
Picijussi: stop that!19:28
jussihehe19:28
topylithe ircanswers.com owner/maintainer realised he should ask permission to use our logs, and did so19:28
jussiyes, because freenode klined him19:29
Picioh?19:29
ikoniawhy should we allow 3rd party bots to log in #ubuntu channels ?19:29
topyliwe have a precedent from 2007, when irseek was discussed19:29
jussiikonia: why not?19:29
ikoniajussi: because ubuntu logs the channels publicly, those logs are available, why invite others19:29
ikoniathose are the official logs - use them or do not, but having more and more bots to log channels opens the door19:30
ikoniawhy would we allow some, and not others19:30
jussithe thing is, whether they pull from own logs or the web logs makes no difference, except a bit of server loat, no?19:30
topyliikonia, for arguments aready used in a similar matter, see https://wiki.ubuntu.com/IRC/IrcTeam/IRSeekDiscussion19:30
ikoniawe provide official logs - they are there for public use19:30
ikoniaok - so I disagree with that argument totally19:30
Piciikonia: why?19:31
ikoniaPici: why can they not use the logs we provide, why do they have to hav a bot19:31
ikoniahave even19:31
ikoniathe precidence is set, if we allow ircseek we have to allow others19:31
ikoniawhat makes them special19:31
topylii guess their bot parses the logs nicely for their use. who knows, that's their business19:32
ikoniaI thought one of the reason we provide logs is to stop this sort of argument19:32
topyliikonia, we will allow others19:32
ikoniatopyli: I have no issue with them parsing the logs, but not running a bot19:32
ikoniatopyli: why ?19:32
jussiikonia: we want to advance ubuntu, not hold it back. I dont see anything about this that is bad for our community?19:32
ikoniatopyli: where it the line, how many ?19:32
ikoniajussi: why would this not advance ubuntu,19:32
ikoniawhy would the policy of use the official logs be a holding back of ubuntu ?19:32
ikoniafrom trusted sources19:33
Piciikonia: Why is having other people log #ubuntu an issue?19:33
* persia notes that sometimes the official logbots miss a couple days in one channel or another19:33
topylia trusted source is no guarantee of the integrity of the service. whether they use our logs or their own makes no difference19:33
ikoniaPici: because you could end up with a channel of bots19:34
ikoniaPici: there is a no unofficial bot policy in ubuntu, and it works well19:34
jussiThe fact is, that we can say, yes, you can have your bot there, as long as you ask nicely and promise not to be nasty, or the person can go grab logs from canonical and eat bandwidth. this way, we know who is doing it.19:34
ikoniaPici: how do you know what these bots that log do apart from log ?19:34
ikoniajussi: no you don't know who's doing it or what else it's doing19:34
Picijussi: +119:34
ikoniajussi: the canonical logs are there to BE parsed19:35
jussiikonia: as long as the bot/irssi+script/whatever is silent, how does that harm us? if we do it this way, we know which bots are logging and we can keep an eye on them19:36
ikoniajussi: I disagree, but I'm not going to die if you impliment this. It just seems to go %100 turn around on the no official bots policy to "all silent bots welcome"19:37
jussiwe also find out more about different ubuntu sites, and we make it easier for people to spread ubuntu.19:37
ikoniahow are we interested in different ubuntu sites19:37
ikoniathat's nothing to do with irc council19:37
jussiikonia: no, silent bots welcome with permission.19:37
Piciikonia: no, its "silent bots welcome as long as we know about them"19:37
jussilol19:37
Picio...19:37
ikoniahow are these bots to be tracked ?19:38
jussiWe can use the wiki for a list of approved logging bots.19:38
guntbertI'm more comfortable with ikonia's approach -- everybody can parse the official logs19:38
ikoniaI assume we'll need a tracking page, with bot owner contact details and rules such as must be authenticated against freenode ?19:38
Piciguntbert: But that way we don't know who is parsing those logs.  This way we do.19:39
jussiikonia: we already have such a page for official bots19:39
jussiikonia: so replicating that for extrnal logging bots wont be too hard.19:39
ikoniajussi: yes, but I'm talking about making that more official, with rules such as must be authenticated against freenode, must have an active email account etc, crterial19:39
jussior even just adding a section19:39
ikoniacritera19:39
ikonia jussi the current approved bots are trusted, these new ones will not be, hence why I'm suggesting rules and guidelines19:40
jussiikonia: yes, thats what I was thinking also. this is about creating the poolicy for that.19:40
guntbertPici: yes, but what good wolud that knowledge do? is there man/womanpower to check and recheck and look at the outcomes?19:40
guntbert*would19:41
topyliwe can deal with someone asking permission, checking what they're doing, making sure they satisfy freenode's guidelines and saying 'ok'19:42
jussiI think we need to specify that any logs taken need to go into the public domain.19:42
ikoniawhy ?19:43
PiciThere isn't any manpower being wasted on the bots that we do know about.19:43
ikoniawhat is the point of allowing bots to log and then put in the public domain the same as the offical logs?  once they log the data they can do what they want with it19:43
jussiand we need to of course run this by canonicals legal dept19:43
ikoniaagain - why ? we make the logs public19:44
PiciI don't see any reason to say anything about the logs themselves.  They are already in the public domain.19:44
ikoniaexactly, suggesting I have to public logs when I may want them for a private application development test is wrong19:44
Picijussi: They're public domain, that means that anyone can do with them as they please. They are not being released under a license with specific terms.19:45
jussiright19:45
topyliwe can't demand anything regarding the logs19:45
PiciSo we cannot tell Joe Botowner that he needs to release his logs under the public-domain as well.19:45
AmaranthWhat channels will they be allowed to log?19:46
PiciAmaranth: good question.19:46
PiciI say only the core support channels.19:46
AmaranthEverything? Everything but -offtopic? Only #ubuntu? etc19:46
jussiI say the same conditions as irseek19:46
PiciPlus #ubuntu-meeting19:46
Picis/meeting/classroom/19:47
topyliAmaranth, the irseek decision page says: 1) channels with 'UbuntuIrcCouncil as contact, 2) already publically logged19:47
Amaranthirseek was only allowed to log channels ubuntubot is in then, right?19:47
jussiThis initial permission extends only to channels satisfying the following conditions:19:47
jussiChannel has 'ubuntuirccouncil' as contact with chanserv.19:47
jussiChannel is already logged at irclogs.ubuntu.com by 'ubuntulog'19:47
jussiThe IRSeek bot must also satisfy the freenode guidelines, mainly it should not be torified and should be easily identifiable by nickname.19:47
jussiAmaranth: correct19:47
topyliok now you're doing it to me too19:47
Picigag19:47
Picier, hah19:47
Amaranthhehe19:47
Picior gag too, thats fitting.19:47
ScottKIRC logs are not public domain.19:48
AmaranthDon't we delay the logs though?19:48
ScottKAt least in the US.19:48
ikoniaScottK: how can they not be, ubuntu posts them on a public website with no terms of use?19:48
persiaI believe they are protected as public speech in most jurisdictions, which typically allows arbitrary use of content if the speaker was aware they were being recorded.19:49
Amaranthikonia: That makes them "All rights reserved"19:49
PiciThey aren't posted to a website in the US...19:49
* persia could be mistaken19:49
ikoniaPici: ahh, so the domain location is key19:49
* Pici shrugs19:49
ScottKHard to say, but in the US it's almost impossible for something created since Mickey Mouse to be public domain.19:49
PiciI am not a lawyer./19:49
ScottKIt really just applies to a narrow category of works created by the government.19:49
persiaPici: The only places that don't default to "All Rights Reserved" are Nicaragua and Honduras, and they default to "Most Rights Reserved".19:50
topylithere's an extensive literature on public mailing lists, forum posts and irc logs, which i don't encourage anyone to read. in a nutshell, the consensus is those are public domain19:50
jussibut in anycase, we can consult canonical's legal eagles before actioning anything if need be.19:50
persiatopyli: The consensus is that the are publically available on open fora.  Avoid saying "public domain" as it has a specific meaning which may not apply.19:51
ScottKtopyli: What persia said.19:51
AmaranthSo what if they put up logs faster than ubuntulog?19:51
ScottKI don't see that ubuntulog has any more or less rights to what I say on IRC than anyone else.19:52
jussiAmaranth: is there an issue there? do we delay the logs for any reason but practicality?19:52
Amaranthjussi: I don't know, that's my question, really19:52
ScottKIf it's OK for ubuntulog to publish logs of what I say on IRC, then it's OK for anyone to do so.19:52
jussiAmaranth: afaik, its just that the cron job is hourly.19:53
ikoniamaybe council should vote on concpet, then make rules later19:53
topyliso we take down our logs and start asking users to sign an agreement before publishing logs on ubuntulogs.org?19:53
PiciNo19:53
topylii didn't think so19:53
persiatopyli: Check the ToS of freenode: I expect it covers the implicit agreement that comments may be logged.19:53
jussiyeah, the motd has something iirc19:54
persia(if it doesn't, that's a flaw, as lots of things that pretend to be humans log)19:54
ScottKBut once again, ubuntulog doesn't have any special rights over any other logger19:54
PiciI say we replace the entrymsg with something that says that your logs may be published by the entities listed at $SOMEURL19:54
jussiScottK: freenode says that people cant log unless they ask permission first19:54
ScottKjussi: That isn't what I said.19:55
PiciAnd at $SOMEURL, we list the people that have asked and have been granted permission.19:55
jussiScottK: so yes, it does, it has permission.19:55
ScottKMostly what I said is that the specific term public domain doesn't apply.19:55
jussiPici: that makes sense.19:55
ScottKPici: What gives you the right to give permission on my behalf?19:56
ikoniacouncil, how about beyond logging bots, bots that are silent, such as the bridge bots of late, that have bridged #ubuntu to other irc networks ?19:56
topyliScottK, i'll use another term once i think of one :)19:56
ScottKtopyli: Good.19:56
PiciScottK: If you can come up with a better idea, I'd love to hear it.19:57
Picifreenode's motd states that users should be informed of public logging by a channel entry message or channel topic.  I'm assuming (perhaps incorrectly) that this says that we are allowed to publically log channels.19:58
ScottKPici: Mostly I think that if you try to come up with rules about who can log and what a log bot is, it's a minefield.19:58
ScottKPici: Sounds like as long as such an entry message is present.19:58
ikoniaScottK: that was part of my point, easier to say, no bpts19:58
ikoniabots19:58
ScottKOf course that's just taking the logs.19:59
ikoniajust maintain official bots19:59
ScottKThe matter of publishing them and redistributing them is another question.19:59
ikoniaI am interested to see views on the bots that do more than log, such as the bridge bots ?19:59
ScottKikonia: So when I'm not connected to my quassel core, is it a bot?19:59
jussi- By connecting to freenode you indicate that you have read19:59
jussi- and agree to adhere to our policies and procedures as per19:59
jussi- the website (http://freenode.net). We would like to remind19:59
jussi- you that unauthorized public logging of channels on the19:59
jussi- network is prohibited. Public channel logging should only19:59
jussi- take place where the channel owner(s) has requested this19:59
jussi- and users of the channel are all made aware (if you are19:59
jussi- publically logging your channel, you may wish to keep a19:59
jussi- notice in topic and perhaps as a on-join message).19:59
ikoniaScottK: no more less than my /away log19:59
jussiSorry for the paste, but its useful.19:59
jussiScottK: its about publishing the logs.20:00
ScottKRight, so how is a bot different?20:00
persiaThat's the bit that protects freenode in jurisdictions that grant protection to public speech.  As noted, it's best practice to indicate a channel is logged, if the logs are to be published, as the lack of informed consent makes it unacceptable in most jurisdictions.20:00
ikoniaScottK: bots can do more, such as the bridge bots I'm refercing to20:01
ikoniaScottK: I have no issue with logging, it's public anyway, I'm more intereted in control of the bots and what "else" they do20:01
Piciikonia: you're the only one discussing that though...20:01
ScottKOK.20:01
persiaSo, technically, it's essential to have notice in every channel in which the log bot is that it's logging each user.20:01
persia(in many places)20:01
ikoniaPici: if it's a non-valid point, I can leave it20:01
persiaubuntulog may not currently comply as much as one would like.20:01
Picipersia: Those should already be in place.20:01
jussiyes, if they you nice one that isnt, please let us know.20:02
jussipersia: remember the xubuntu is logged factoid request? ;)20:02
persiaPici: I know of counter-cases, but yes, *should*.  Point stands, that there should be a documented place that lists the loggers, which then gives them the special rights that ScottK asks about.  Other loggers souldn't be there.20:02
Picipersia: I agree, we should create that.20:02
jussipersia: exactly what we said 20 mins ago :)20:03
persiaYes.20:03
jussiok, so a vote?20:04
ikoniajussi: before you vote, I'd like to know if this is just for logging bots, or any silent bot20:05
Picier, this has always been about logging.20:05
jussi[vote] Public log bots be allowed with a set of conditions and list of bots documented on a wiki page20:05
MootBotPlease vote on:  Public log bots be allowed with a set of conditions and list of bots documented on a wiki page.20:05
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot20:05
MootBotE.g. /msg MootBot +1 #ubuntu-meeting20:05
ikoniaok, thank you20:05
Pici+120:06
MootBot+1 received from Pici. 1 for, 0 against. 0 have abstained. Count is now 120:06
jussi+120:06
MootBot+1 received from jussi. 2 for, 0 against. 0 have abstained. Count is now 220:06
topyli+120:06
MootBot+1 received from topyli. 3 for, 0 against. 0 have abstained. Count is now 320:06
jussi[endvote]20:06
MootBotFinal result is 3 for, 0 against. 0 abstained. Total: 320:06
jussiright, so who wants to get at least the bareboes of such a wiki page up?20:06
topylicould copy a skeleton from the irseek discussion page20:07
jussiyeah20:08
persiaMight I suggest one additional rule: that channel operators are responsible for ensuring that public notice is provided if they allow the logbots (including ubuntulog) to enter their channels?20:08
topylimaking sure the topic includes "channel is logged" would be good20:09
Picipersia: I believe that is already present on the wiki page regarding creating new channels.20:09
PiciWe should double check though20:09
jussiyeah, i think Pici is right20:09
persiaPici: Yes, but it's not part of the logbot request process, which is the gap.20:09
jussiok, anything else?20:09
* persia knows lots of folk who created channels in the namespace who have only a passing famliarity with the guide20:09
PiciWho is doing the u-r-p stuff? That channel should probably be opened soon/now.20:10
PiciI've already heard a few questions about when it is supposed to open20:10
jussiPici: you volunteering? or did nhandler say he could do it?20:10
Picijussi: I'd be happy to do it in nhandler's absense./20:10
gnomefreakIRCC meeting?20:11
nhandlerI can do it Pici20:11
nhandlerSorry for missing the meeting20:11
jussignomefreak: almost done20:11
Picignomefreak: just finishing.20:11
jussilol20:11
Pici. . .20:11
topylinhandler, just in time for volunteering for tasks!20:11
nhandler:)20:12
jussiI need to go. so Ill end the meeting, but feel free to sort stuff as needed20:12
nhandlerI also noticed no action for updating ~ubuntu-irc. I can do that if nobody wants20:12
Picinhandler: We had discussed copying the access list from -ops (those with +v) to u-r-p but to +o20:12
nhandlerI saw20:12
jussi[endmeeting]20:12
Picinhandler: Will your script do that? if not I'll do it manually.20:12
nhandlerI can script that to save time20:12
Piciokay :)20:12
nhandlerPici: With a slight modification it should20:12
jussi#endmeeting20:12
MootBotMeeting finished at 14:12.20:12
jussilaters all20:13
gnomefreakwhile i have everyone here. any chance we can keep +1 open or at least open it when toolchain lands?20:13
topylithanks gusy20:13
ikoniagnomefreak: yes please20:13
nhandler[action] nhandler to update release party access list20:13
jussioh +1 to re-open when toolchain lands.20:13
PiciI say make it +im until the toolchain lands on... the 6th is it?20:13
jussiPici: +1. now im gone20:13
Picik :)20:14
nhandlerI am fine with that Pici20:14
gnomefreakits win 3 for me and i know first 20 channels so it screws me uup :(20:14
nhandlerWho wants the ~ubuntu-irc action?20:14
Picinhandler: do you need to clear out the current access list, or will your script take care of that?20:14
Picirather, need me to clear it out.20:14
nhandlerPici: I can take care of that20:14
Piciokay :)20:14
topylii'll create the bot wiki thingy20:15
topyliwe'll then hack it to pieces and remove my big fat "DRAFT" header20:16
nhandlertopyli: Maybe just add a section to the already existing bot page20:16
nhandler[action] topyli to make bot list on wiki20:16
topylinhandler, good idea, it's not that big20:16
nhandler[action] nhandler to update ~ubuntu-irc20:16
nhandlerWho is doing minutes/updating wiki? jussi ?20:16
PiciI suppose.20:17
topylitraditionally, perks of the chair isn't it?20:19
=== arand is now known as fakeubot
=== fakeubot is now known as arand

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!