=== mc44_ is now known as mc44 [10:00] nobuto_mobile, waiting for Asia/Oceania Meeting? [10:04] elky? [10:07] persia, lifeless: freeflying? [10:09] i can't do anything on my own :( [10:20] udienz, sorry, it's not looking like happening tonight [10:21] elky, okay no problem i'll try next meeting === oubiwann is now known as oubiwann_ === ian_brasil__ is now known as ian_brasil === oubiwann_ is now known as oubiwann === oubiwann is now known as oubiwann_ === fader_ is now known as fader === yofel_ is now known as yofel === oubiwann is now known as oubiwann_ === cking_ is now known as cking === dgjones is now known as DJones === Moot2 is now known as MootBot === oubiwann is now known as oubiwann_ === ian_brasil__ is now known as ian_brasil === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === kirkland_ is now known as kirkland [15:56] hi [15:57] \o/ [15:58] \o [15:59] jolly good morning, all. [16:00] o/ [16:00] Afternoon all.... [16:00] \o [16:00] o/ [16:01] o/ [16:01] \o [16:01] no sombreros this morning? no hunting caps? [16:01] Alright, lets begin [16:01] settle down there, SpamapS [16:01] #startmeeting [16:01] Meeting started at 10:01. The chair is hallyn. [16:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:01] *\o/* gooooo rally! [16:01] hallyn: err, ok you can do it if you want. ;) [16:02] [TOPIC] Review ACTION points from previous meeting [16:02] New Topic: Review ACTION points from previous meeting [16:02] ALL: please check the SRU tracker for 'needs-verification' bugs [16:02] http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html [16:02] LINK received: http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html [16:02] everyone rais your hands if you're NOT guilty [16:03] That one should, I think, roll forward for a bit longer so we remember that its important. [16:03] at least until 10.04.2 [16:03] [ACTION] ALL: please check the SRU tracker for 'needs-verification' bugs [16:03] ACTION received: ALL: please check the SRU tracker for 'needs-verification' bugs [16:03] SpamapS: sounds good, i'll try to remember to keep the link in with the action when i carry over [16:04] robbiew to review ServerTeam wiki [carried over] [16:04] i thought that was done? [16:04] hm, is robbiew in? [16:04] I recall him claiming he'd done it as well. [16:04] o/ [16:04] hm, didn't get updated on the meeting page... [16:05] robbiew: ^ ServerTeam wiki all reviewed and uptodate? [16:05] yeah i totally missed the boat on the server page [16:06] yup...at least the external one [16:06] zul: meaning action items aren't updated? in that case let me search the logs for the real ction items [16:07] Hi everyone! [16:09] ShootEmUp: welcome! [16:09] glad to be here [16:10] feh, there, jan 4 [16:10] yay, there ARE no actions from the jan 4 meeting [16:11] \o/ [16:11] so, barring objections (i.e. if i'm mistaken), i'll move on [16:11] none? what do they do in those meetings? [16:11] [TOPIC] Natty Development [16:11] New Topic: Natty Development [16:11] ShootEmUp: play duke nukem [16:11] robbiew: ^ over to you [16:11] hallyn, what? [16:12] * robbiew wonders why he covers the one topic he doesn't do :P [16:12] heh [16:12] so we made great progress on work items [16:12] charlie-tca! [16:12] lots of Done's, Postpones, and dropped [16:12] all goodness [16:12] I haven't checked bugs yet [16:13] but I usually know of the serious ones...from the irc pings and email [16:13] that's it! [16:13] Thanks Mr. Narwhal! [16:13] I have a topic to debate [16:13] [TOPIC] Weekly Updates & Questions for the QA Team (hggdh) [16:13] New Topic: Weekly Updates & Questions for the QA Team (hggdh) [16:13] ShootEmUp: if its not related to the current topic please hold it until Open Discussion [16:13] ShootEmUp: wait till the end of the meeting for Open Discussion :) [16:13] okay [16:14] didn't actually see hggdh today, is he around? [16:14] guess not, moving on, i know smb is here :) [16:14] [TOPIC] Weekly Updates & Questions for the Kernel Team (smb) [16:14] New Topic: Weekly Updates & Questions for the Kernel Team (smb) [16:15] So I did some little stuff last week but have no paper records, hence I am not sure anymore what that was [16:15] Currently working on bug 686692 [16:15] Launchpad bug 686692 in linux (Ubuntu Natty) "natty kernel does not boot on ec2 t1.micro" [High,Confirmed] https://launchpad.net/bugs/686692 [16:16] which I can locally reproduce but not yet found a final solution [16:16] smb, Is that the bug that only happend on t1.micro i386's? [16:16] just that it would boot if the mem= is a multiple of 4 [16:16] Daviey, t1.micro but I believe both i386 and x86_64 [16:16] ah [16:17] They are doing something different with memory layout too. Just not sure this is just something that happens too or related [16:17] any questions for smb? [16:18] Other thing I pushed for SRU in lucid is the paper over approach for bug 614853 [16:18] Launchpad bug 614853 in linux-ec2 (Ubuntu) "kernel panic divide error: 0000 [#1] SMP" [Medium,Confirmed] https://launchpad.net/bugs/614853 [16:18] To keep until we found/got a real solution [16:19] smb, What nasty effects does it have? [16:19] The current patch just avoids the divide by zero. While the variable in question is supposed to never be zero in the first place [16:20] So I sent two patches for sru, the one preventing the divide and one sort of debug patch to yell when the variable is set/left zero [16:21] smoser, Are you arround? [16:21] o/ [16:21] yeah, smb, i agree with that. [16:22] Just saw your bug 704022 [16:22] Launchpad bug 704022 in linux (Ubuntu) "xen_emul_unplug=unnecessary on kernel cmdline is required in ec2 hvm" [Medium,Confirmed] https://launchpad.net/bugs/704022 [16:22] one thing i had considered would have been to just add the debugging bit, and let it crash [16:22] Though I am a bit confused by the logs as the ones which say with option and working seem to contain drops into busybox as well [16:22] even with info like "if you see this message, please add to bug at https://launcpad.net/..." [16:23] smb i may have uploaded incorrect (un-trimmed) logs [16:23] but it does fail [16:23] smoser, What made me rethink a bit is that those affected people seem to run production severs with that and so maybe a avoid and complain is preferable [16:24] yeah, so the reboot with argument i sjust not trimmed [16:24] so it contains the previous boot log (thats why the busybox in the middle of it) [16:24] http://launchpadlibrarian.net/62372677/restart-with-unplug-arg.txt [16:24] LINK received: http://launchpadlibrarian.net/62372677/restart-with-unplug-arg.txt [16:24] smoser, Ah ok. That xvd* does not show up without the option is ok. Though one would think the sd* devices should always [16:25] smb, yeah, i agree, getting people actually fixed is good, but if you fix the problem you'll never get debug info [16:25] they wont send it becuase they wont know they have a problem [16:25] so do you want it changed? (let's either make a decision, or move offline?) [16:25] * SpamapS wonders if this couldn't be discussed further offline? [16:26] * SpamapS apologizes for smashing hallyn's toes [16:26] i can defer to smb's decision. [16:26] grrr [16:26] ok - any other questions for smb? [16:26] (or from) [16:26] if not, [16:26] I am done [16:26] thanks, smb [16:26] [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer) [16:26] New Topic: Weekly Updates & Questions for the Documentation Team (sommer) [16:27] sommer is not around [16:27] :( [16:27] yup [16:27] [TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0) [16:27] New Topic: Weekly Updates & Questions for the Ubuntu Community Team (kim0) [16:27] kim0 is also not around [16:27] and so, we move on to [16:27] [TOPIC] Open Discussion [16:27] New Topic: Open Discussion [16:28] ShootEmUp: your turn [16:28] should ubuntu try to look like windows or Mac or neither? [16:28] lol [16:29] ShootEmUp: you may want to ask that in #ubuntu [16:29] like my old palm V [16:29] ShootEmUp: indeed. This is the Server team meeting [16:29] lol [16:29] okay [16:29] SpamapS: for some reason i thougth there was something you wanted to discuss? [16:30] why does everybody always assume I want to TALK? ;) [16:30] no I'm good [16:30] :) [16:30] wow, first time for everything! :) [16:30] anybody? going once... [16:30] SpamapS: because you are a chatty cathy [16:30] zul: whatever you nervous nelly [16:30] going twice... [16:31] SpamapS: i know what you are but what am i? [16:31] [TOPIC] Announce next meeting date and time [16:31] New Topic: Announce next meeting date and time [16:31] hm, the meeting page says feb 1 [16:31] i dont' think that's right [16:31] I would have assumed: [16:31] 25th [16:31] Tuesday, January 25 2011 16:00 UTC [16:32] ok, another almost action-free meeting. [16:32] thanks all [16:32] #endmeeting [16:32] Meeting finished at 10:32. [16:32] \o/ === kamal is now known as kamal-afk [16:59] o/ [16:59] \o [16:59] \o yes I'm here [16:59] \o [16:59] * tgardner waves [17:00] * ara waves [17:00] \o [17:01] * smb looks expectingly at bjf [17:02] not a US holiday today too? [17:02] 09:59 by my clock [17:02] #startmeeting [17:02] Meeting started at 11:02. The chair is bjf. [17:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:02] [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting [17:02] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty [17:02] LINK received: https://wiki.ubuntu.com/KernelTeam/Meeting [17:02] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty [17:02] # [17:02] # NOTE: '..' indicates that you are finished with your input. [17:02] # [17:02] [TOPIC] ARM Status (bjf) [17:02] New Topic: ARM Status (bjf) [17:03] Nothing new [17:03] .. [17:03] [TOPIC] Release Metrics (JFo) [17:03] New Topic: Release Metrics (JFo) [17:03] no JFo today? [17:04] guess not, moving on [17:04] [TOPIC] Blueprints: Kernel Configuration Review (apw) [17:04] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review [17:04] New Topic: Blueprints: Kernel Configuration Review (apw) [17:04] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review [17:04] o/ [17:04] Nothing to report here. [17:04] .. [17:04] [TOPIC] Blueprints: Enhancements to the firmware test suite (cking) [17:04] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements [17:04] New Topic: Blueprints: Enhancements to the firmware test suite (cking) [17:04] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements [17:05] Changes to fwts (natty development branch): [17:05] * 0.21.0 now in Natty universe. [17:05] * wmi test: handle table not found error more gracefully. [17:05] * report off by one error on month in date. [17:05] * add --disassemble-aml. [17:05] * fix null pointer segfault. [17:05] * syntaxcheck test: add 40 advice lines on specific error output. [17:05] .. [17:05] [TOPIC] Blueprints: Handling of Deviations from Standard Kernels (smb) [17:05] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance [17:05] New Topic: Blueprints: Handling of Deviations from Standard Kernels (smb) [17:05] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance [17:05] Done. [17:05] [ACTION] bjf remove from agenda [17:05] .. [17:05] i'll remove from agenda [17:05] [TOPIC] Blueprints: Review of the Stable Maintenance Process (sconklin / bjf) [17:05] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review [17:05] New Topic: Blueprints: Review of the Stable Maintenance Process (sconklin / bjf) [17:05] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review [17:06] * The kernel team will take responsibility for setting the verification-needed tags on bugs at the beginning of the verification phase [17:06] .. [17:06] [TOPIC] Status: Cert. Team (ara) [17:06] New Topic: Status: Cert. Team (ara) [17:06] o/ [17:06] Nothing to report here, we will test the -proposed kernel once the verification is done [17:07] we will report on status on the meeting next week [17:07] .. [17:07] [TOPIC] Blueprints: Ubuntu Kernel Delta Review (apw) [17:07] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-ubuntu-delta-review [17:07] New Topic: Blueprints: Ubuntu Kernel Delta Review (apw) [17:07] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-ubuntu-delta-review [17:07] 16 of the 19 personal patch reviews are now done. Some work remains on compcache which is now superceeded by zram in staging, but some userspace work is required to switch to it. Nothing else of interest occuring. [17:07] .. [17:07] [TOPIC] Blueprints: Kernel Version and Flavours (apw) [17:07] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours [17:07] New Topic: Blueprints: Kernel Version and Flavours (apw) [17:07] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours [17:07] Master kernels are now at v2.6.37 and remain stable. OMAP3 kernels now switched over to the distro master branch and being used in ARM images. ti-omap4 is a little behind the curve and being investigated. [17:07] .. [17:08] [TOPIC] Status: Ecryptfs (jj) [17:08] New Topic: Status: Ecryptfs (jj) [17:08] Currently working with light testing, if you don't mind losing your data you can play with it (it doesn't handle unexpected stuff yet) [17:08] current issues, that need to be resolved [17:08] - code cleanup [17:08] - name collisions [17:08] - actual fs name [17:08] - multiple uses of same name from different directories [17:08] - dentry tag on lookup [17:08] - could use inode tag (force verifying for all names on tagged file) [17:08] - Graceful fallback [17:08] - should fallback to shortname if xattr is missing, currently fill_dir fails [17:08] - should fallback to something that earlier versions of ecryptfs can [17:08] support (ie. a valid shortname). [17:08] - currently Fill dir, detects unencrypted names with leading // as [17:08] shortname tag [17:09] - need to expand current testing into a full regression test suite [17:09] .. [17:09] jjohansen, do you have a branch somewhere for this work? [17:09] ah yeah [17:10] make sure its on something which is backed up! :) [17:10] kernel.ubuntu.com/jj/ubuntu-natty.git [17:10] give me a sec to push the latest up [17:12] [TOPIC] Status: Natty (apw) [17:12] New Topic: Status: Natty (apw) [17:12] The main distro kernel is now at 2.6.37-12.26 (v2.6.37 final based). We are still in an extended merge window for v2.6.38-rc1, but testing of Ubuntu kernels based on this is looking ok so far. [17:12] .. [17:12] [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) [17:12] New Topic: Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) [17:12] || Package || Upd/Sec || Proposed || TiP || Verified || [17:12] || || || || || || [17:12] || dapper linux-source-2.6.15 || 2.6.15-55.90 || 2.6.15-55.91 || 0 || 0 || [17:12] || || || || || || [17:12] || hardy linux || 2.6.24-28.81 || 2.6.24-28.84 || 0 || 0 || [17:12] || || || || || || [17:12] || karmic linux-ec2 || 2.6.31-307.23 || 2.6.31-307.24 || 0 || 0 || [17:12] || --- linux || 2.6.31-22.70 || 2.6.31-22.71 || 0 || 0 || [17:12] || || || || || || [17:12] || lucid linux-ec2 || 2.6.32-311.23 || 2.6.32-312.24 || 5 || 5 || [17:12] || --- linux-meta-lts-backport-maverick || 2.6.35.22.34 || 2.6.35.23.35 || 0 || 0 || [17:12] || --- linux-lts-backport-maverick || 2.6.35-22.34~lucid1 || 2.6.35-23.41~lucid1 || 0 || 0 || [17:13] || --- linux-firmware || 1.34.1 || 1.34.3 || 2 || 2 || [17:13] || --- linux || 2.6.32-27.49 || 2.6.32-28.55 || 5 || 5 || [17:13] || --- linux-meta || 2.6.32.27.29 || 2.6.32.28.31 || 0 || 0 || [17:13] || || || || || || [17:13] || maverick linux-meta || 2.6.35.24.28 || 2.6.35.25.31 || 0 || 0 || [17:13] || --- linux-firmware || || 1.38.3 || 3 || 3 || [17:13] || --- linux || 2.6.35-24.42 || 2.6.35-25.43 || 20 || 18 || [17:13] || || || || || || [17:13] * New kernels were uploaded and published to -proposed for all supported releases. We are now in the verification phase for these kernels. [17:13] * There is a regression in Maverick proposed having to do with Radeo graphics ( bug 703553 ) that we'll be looking into. [17:13] Launchpad bug 703553 in linux (Ubuntu Maverick) "After upgrade to linux-image-2.6.35-25 graphics are broken" [High,Confirmed] https://launchpad.net/bugs/703553 [17:13] * The kernel currently in -proposed for Lucid is the one which we anticipate being released for the .2 release. [17:13] .. [17:14] o/ [17:14] apw, go [17:14] bjf is that TiP the cound that verified needs to get to [17:14] ie is that showing a very good verification percentage ? [17:15] .. [17:15] apw, yes and yes, most of the bugs were in fact fixed by upstream stable release [17:15] [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/) [17:15] New Topic: Open Discussion or Questions: Raise your hand to be recognized (o/) [17:16] what does TiP mean? [17:16] Test in Proposed? [17:17] o/ [17:17] tgardner, go [17:17] once you upload to canonical-kernel-team, do you have to annoy an archive admin to pocket copy? [17:17] tgardner, yes [17:17] as there is no queue [17:17] hmmm [17:17] .. [17:17] that is similar to the normal need to hastle an AA to source NEW the package anyhow [17:18] tgardner, yes not the best of situations [17:18] thanks everyone [17:18] #endmeeting [17:18] Meeting finished at 11:18. [17:18] OK, thanks all! [18:11] * stgraber waves [18:11] wendar: pong [18:12] stgraber: seems we're the only two [18:12] apparently [18:12] anyway, the only thing I really had for this meeting was the question about the version number [18:12] yes, we got a reply from the techboard on that [18:13] cool, so we'll be able to get at least one of the apps uploaded to extra then [18:14] that was the only thing I was waiting for to get suspended sentence uploaded [18:14] 2.5.1-0extras10.10.1 [18:14] so --extras. [18:14] where debian version is expected to be 0 [18:15] right [18:15] also, one I push that to the PPA, it's going to get synced to extra and everyone will see it [18:15] what was the magic part about the icon or something like that ? [18:15] or the screenshots [18:15] I seem to remember that we need to get a branch merged or something [18:16] it's in https://wiki.ubuntu.com/PostReleaseApps/Metadata [18:17] ok, and who do I need to ping to get the branch merged ? [18:17] because I'm going to upload the package in the next 5 minutes or so, meaning it'll appear in the next 24 hours, so we'll need the branch merged before that [18:19] he proposed the merge when he sent the application, but my guess is that the branch shouldn't be merged until we give the app a +1 [18:19] but should be merged before we upload [18:19] that I don't know (first time through the process) [18:19] I believe mvo has access [18:19] otherwise, I'd check in with stuart [18:19] (on UK timezone, though) [18:20] I see it's commercial-ppa-uploaders [18:20] checking who's in there [18:21] ah, robbiew is on there, he's online now [18:24] ok, I poked tumbleweed about one last detail, then I'll wait for someone to merge that branch and will upload to the PPA [18:30] great, thanks! [18:31] I'll send a note to the ARB on version numbers [18:31] ok [18:33] looks like we have one new application [18:34] no other progress on other applications [18:35] hey all sorry for being late [18:36] I looked into the code of the app that I said I would before christmas and its pretty big [18:36] id say they should go to universe rather than extras [18:39] that was 4dtris? [18:42] stgraber: if you're still on, 3 of us is enough to vote [18:44] wendar: yeah it was [18:45] its like 20 source files of C [18:46] fagan: ack! [18:46] so its pretty complex [18:46] I went through it and its ok though [18:46] well, it's a bit of a judgement call [18:46] there isnt anything harmful in there but I think in terms of complexity we should pass it on to universe [18:47] do you feel comfortable with the level of security review? [18:47] yes [18:47] well i didnt see anything bad [18:48] im very confident that its fine security wise [18:49] 18:14 < wendar> so --extras. [18:49] 18:14 < wendar> where debian version is expected to be 0 [18:49] should be no dash between and extras: [18:50] -extras. [18:50] kees: yah, I caught that when I reposted to ARB list [18:50] (just saw that in backscroll) [18:50] wendar: okay, cool :) [18:51] kees: the "for example" was right, I just got caught up in all the angle brackets in the detailed explanation :) [18:51] hehe [18:51] yeah [18:52] fagan: ENOSTGRABER, I think we'll have to wait until next meeting to vote on 4dtris [18:53] yeah [18:53] that sounds fair [18:53] fagan: but, it's worthwhile to post a summary of your recommendation to the ARB list [18:53] sure [18:53] that way we can talk about it between now and then [18:53] yeah I think its a judgement call if its accepted or not [18:54] depending on our view on large complex programs [18:55] yeah, we don't have a hard measure of "complexity" [18:55] (one of the things we talked about at UDS) [18:55] so, we'll make our best judgement [18:55] 20 C files is certainly a lot less than, say, the CPython interpreter [18:56] lines of code may enter into it [18:57] and dependencies (stand-alone/using system libraries/installing its own libraries) [18:58] I'll take on a task to review the new application before next meeting [18:59] call that a wrap on the ARB meeting [19:02] cool thanks wendar [19:02] fagan: do you want to be meeting chair next meeting? [19:02] wendar: sure [19:02] fagan: cool, I'll put you in the agenda [19:03] awesome === Ursinha is now known as Ursinha-afk [19:53] Hi everyone === unimix_ is now known as unimix === Ursinha-afk is now known as Ursinha === ShootEmUp_ is now known as shootemup === ShootEmUp_ is now known as ShootEmUp [20:55] sorry I'm late, guys [20:55] Oh wait, I'm not [20:55] I think this is the first meeting I've been on-time for. [20:56] paultag: you're early you special lad! [20:56] just a reflex to apologize for being late? :) [20:56] pleia2: yeah! [20:56] not sure the others may remember though.. no mail was sent out till um about 4 mins ago [20:57] thank you for the reminder czajkowski :) [20:58] not sure we actualy have a meeting tbh folks [20:58] one thing on the agenda [20:58] and that was dealt with via email [20:58] thank you for all your awesome work, loco council! :) [20:58] pleia2: :) [20:59] pleia2: :) [20:59] :) [20:59] o/ [21:00] Well, since we're all here [21:00] anyone have anything to say? [21:00] II've mailed team re re approvals [21:01] this cycle we only have a few [21:01] so we could do with picking a few from early next cycle as that list is massve [21:01] just a thought... [21:01] also paultag mentioned about coming up with some policies to help teams which would be ideal given the last few months with helping teams [21:01] yes, that's a great idea [21:02] I can formalize a few of them. Do we have any kind of RFC process for loco-contacts? [21:02] we have the guidelines page which is great [21:03] but I am noticing a good few teams having issues and I'd love to do more to help [21:03] but it'd be nice if we had something written down so we can get it translated [21:03] +1 [21:04] simple things like if you're struggling come to us we cna help, for team elections if you need mediate perhaps have 2 or 3 leaders if you cant reach a vote or if the team is small [21:04] share the roles/tasks [21:04] but some teams go the other extrme and that I do worry as it seems to end up with them in lots of hassle [21:04] aka unapproved or inhouse fighting [21:05] eveing everyone [21:05] 'lo huats [21:05] huats: just chatting, making use of this chance where we're all online [21:05] oh realy ? [21:06] the facotid in here is helping btw [21:06] *factoid [21:06] hello czajkowski === ian_brasil____ is now known as ian_brasil [21:09] leogg: paultag popey any comments? [21:09] if not I'm going to go back to dyingsick here! [21:09] czajkowski: hahaha [21:09] I have a comment -- [21:09] If I can't dance, I don't want to be part of your revolution. [21:09] nope [21:10] :) [21:10] Oh, on topic? this sounds great, and I think we should move forward with it [21:10] right love you and leave you all nn [21:11] night! I'll stay on if anyone comes about. Don't think we need logs or anything, aye? === BikerPiet_ is now known as BikerPiet