[02:21] if a staffer might be kind enough to take a looksee at Gbotno's spamming ([n=nds@c-76-20-29-113.hsd1.ca.comcast.net]) [04:36] Hi. Sorry to bug you again about that issue, but ubuntulog is not logging ubuntu-motu. Is someone working on it? I reported here the issue on the 8th. Just wanted to be sure that it was the correct way to report this issue [04:41] fabrice_sp: Canonical runs the bot. We have no control over it. Check if an rt ticket has been filed at rt.ubuntu.com and file one if it hasn't [04:43] nhandler, AFAIK, I don't have a user to access rt.ubuntu.com (tried with my launchpad user) [04:43] fabrice_sp: ubuntu/ubuntu [04:44] nhandler, oh: thank you! [04:51] * fabrice_sp just created case 9017 for the missing ubuntulog in ubuntu-motu [10:05] ping Pici [13:26] Nafallo: ping! [13:26] Nafallo: antar du jobbar men jag tänkte kolla med dig om du tänkte mer på op-frågan eller om du kan tänka dig låta oss andra ops rösta igenom någon/några eventuellt nya ops till kanalen för att få nytt blod av aktiva? om du bara ger klartecken så ordnar jag rättigheter och sånt så slipper du lägga energi på det [13:27] Nafallo: något behöver nog göras i alla fall för just nu är det mer eller mindra bara 2 ops som är aktiva och håller kolla på kanalen men inte 24/7 med fördelningen [13:28] Nafallo: för har du inte tid med frågan så får du deligera den till oss andra ops :) [14:09] Philip5: +1 [14:51] AlanBell: pong [14:57] hi Pici [14:57] want to talk about factoids? [14:57] and bantrackertwo [14:59] Sure. [15:02] I hear some assistance could be used, not sure of the specifics but I am happy to help [15:03] AlanBell: Do you know anything about the current bantracker? [15:03] very little [15:04] and what I do know doesn't relate to factoids [15:05] Let me explain quickly what the bantracker does then. [15:05] ok [15:08] Bantracker is a supybot plugin that records channel events (kicks,bans,mutes,marks) into a sqlite database with about 100 lines of context. There is also a web interface, but that is just some python cgi that interacts with the sqlite database and allows operators to search and comment on those events. [15:09] ok, and version two is django based with a mysql back end [15:09] Yes. [15:11] I have been playing with writing a python based GUI IRC client with a desktopcouchdb back end [15:12] so python IRC stuff is something I have some awareness of [15:12] the bantrackertwo won't need to know anything about IRC [15:12] so bantrackertwo is the front end bit, not the IRC supybot plugin then [15:13] Yes [15:13] the supybot plugin will (probably) use some sort of API or direct database access [15:14] ok, so what needs doing on it, and what has it got to do with the factoids process? [15:14] Right now its interfacing via django objects, but I'd like to eventually use some sort of api so that we aren't forced to run the supybot on the same host as the django project. [15:15] I was thinking JSON would be a good base for the api [15:16] * AlanBell likes JSON and couchdb [15:18] What needs work is the issue tracker, a json interface to everything (actually, I have something basic for commenting, but it probably could be improved) [15:19] I'd like to discuss tsimpson and the rest of the irc team about ideas for the factoid tracker, I have some changes that I think might make managing multi-channel factoids a lot easier. [15:21] I'd be interested in any ideas on that front [15:21] so having done a bzr branch of bantrackertwo how do I run it? [15:22] you need python-django and an apache install [15:22] You actually don't need apache. [15:22] that's right, it has a small web server built-in [15:23] But you'll need python-django. I personally run from django trunk though. [15:24] ok, looks like it needs some openID stuff too [15:24] python-openid [15:24] and you'll need to run through the .py files changing the paths where appropriate [15:25] settings.py [15:25] if it's not in a directory called "ircTrack" the imports will need changing too [15:25] ./manage.py test seems to work now [15:26] * AlanBell considers changing name to bnrubin [15:28] :P [15:34] tsimpson: I put together a basic proof of concept factoid project that used tagging to define what channel a factoid could be used in. So you could have !fail tagged #ubuntu-offtopic and #kubuntu-offtopic and you woudlnt have to worry about making aliases pointing every which way [15:36] Also I thought it would be useful to also have category tagging, so that we could have some way of bringing up say.. all the video related factoids, without using the regular search [15:37] ideally, I would like to have the ability to have a "master" database and a "local" database, so loco channels could have their own database but fall back to the master one [15:40] so would you want the local database to have delegated approval? [15:40] also, ideally, I would like the ability to translate the factoids [15:40] so a loco could approve their own factoids by the team leader or whatever [15:40] AlanBell: basically the "local" database would be searched first, if no match is found the master database would be searched [15:41] ok, but both databases would be on the same server presumably [15:42] most likely [15:43] I would think a single database would be better, that way it would be easier to collect together all versions of !fail for example [15:43] we'd also need to decide if we are going to require a database server (mysql/postgresql) or use sqlite3 [15:43] oh, I thought that decision was already made as mysql [15:43] ah, you mean for the factoid database [15:43] django can handle most of the common standards. [15:45] * AlanBell thinks of couchdb with !foo as the document ID [15:47] then you could have all the translations and channel specific texts as attributes of the document [15:48] we will not use couchdb [15:48] not unless you want to write a django backend for it [15:52] ok, there are a couple of python couchdb libraries, but if that all gets abstracted away by django then any database would do [17:18] Nafallo: betyder +1 "kör på det" eller bara att du är/var där? :) === nik0 is now known as niko === uBOTu-fr` is now known as uBOTu-fr === McPeter_ is now known as McPeter === emma_ is now known as emma