[04:12] JanC, popey you guys here? === rgreening_ is now known as rgreening === ShadowChild is now known as lukjad007 === ember_ is now known as ember === ejat is now known as e-jat === asac_ is now known as asac === ogra_ is now known as ogra === yofel_ is now known as yofel [15:58] o/ [15:58] o/ [15:59] * slangasek waves [15:59] Howdy [16:00] hey [16:00] * apw listens in [16:00] o/ [16:00] * lool waves [16:02] hi [16:02] yo [16:02] hi folks [16:02] * pgraner waves [16:03] slangasek: are you chairing or is it rotating? [16:03] davidm, Riddell, sbeattie, Hobbsee, ScottK: there? [16:04] slangasek: Here [16:04] cjwatson: I was planning to [16:04] #startmeeting [16:04] Meeting started at 10:04. The chair is slangasek. [16:04] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:04] slangasek, here [16:04] [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-06-19 [16:04] LINK received: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-06-19 [16:04] hi [16:05] hey [16:05] hi, folks [16:05] as mentioned in the email, the main topic today is to gather up our feature definitions for karmic [16:06] ttx has asked to go first due to time constraints [16:06] [TOPIC] Server team [16:06] New Topic: Server team [16:06] o/ [16:06] Not much progress since last week. All specs were filed, but we have too much of them... [16:07] so we are in the process of prioritizing them [16:07] ttx: when can we expect that work to be done? [16:07] slangasek: I hope on Monday. [16:07] slangasek: it's more on dendrobates hands right now [16:07] ok [16:07] There is some organizational change under way in the team but it's not complete yet. [16:08] is there a partial list of known confirmed specs that we should look at? [16:08] dendrobates: ? [16:09] I don't think any of them was formally approved yet. [16:09] ok [16:09] server-karmic-eucalyptus-in-main and server-karmic-cloud-power-management are the only two already known to be Essential [16:10] slangasek: What exactly do you need to discuss by FeatureDefinitionFreeze ? [16:10] sladen: new packages ? MIRs ? [16:11] known essential specs> noted, thanks [16:11] The spec with most impact as far as new packages is concerned is probably server-karmic-euca-javadeps-refactoring [16:11] ttx: IMHO it should cover any specs for features being added in karmic [16:12] slangasek: that means most of ours. You want to discuss all of them quickly ? Or it doesn't make sense until they are prioritized ? [16:13] let's not spend time on them right now if we don't know which ones are actually planned to be worked on this cycle [16:13] is server-karmic-euca-javadeps-refactoring a prereq for server-karmic-eucalyptus-in-main? [16:14] slangasek: not exactly. It makes an easier MIR process to have the package refactored before it's moved to main. [16:14] ok [16:14] slangasek: rather than moving a giant trashcan to main. [16:14] yes - even if it's not a prereq, please don't defer server-karmic-euca-javadeps-refactoring for too long in the cycle :) [16:15] slangasek: I'm on it already :) [16:15] what milestone is server-karmic-eucalyptus-in-main targeted for? [16:15] I have an Essential spec that depends on it, which I've currently targeted for alpha 3 [16:15] well, I suppose it isn't a hard dependency [16:16] cjwatson: we don't even know what Eucalyptus 1.6 dependencies will be yet. [16:16] ttx: the only other thing I had on the list for you guys is bug #326768 - still marked as 'in progress', but no movement since last week, is mathiaz still on this? [16:16] specifically I'm referring to foundations-karmic-cloud-setup-in-server-installer [16:16] Launchpad bug 326768 in mysql-dfsg-5.0 "mysqld_safe thinks mysqld has crashed when it hasn't" [High,In progress] https://launchpad.net/bugs/326768 [16:17] cjwatson: yes, another related spec is server-karmic-eucalyptus-fit-on-cd [16:17] both are not expected to be completed before we get upstream eucalyptus 1.6 [16:18] I'd say, not before alpha3 [16:18] so if you depend on it I'd advise retargting [16:18] well, I should start on the installer glue anyway [16:18] it'll take a while [16:19] I'll just not be able to actually deliver something testable by the general public until later - I'll note it in the whiteboard [16:19] cjwatson: I expect to complete both during the platform sprint [16:20] slangasek: about the mysql bug, mathiaz is still on it, no progress since last week. I'll make sure he updates the bug [16:20] we've been busy with blueprint finalization this week :) [16:20] I don't mean to imply he needs to update the bug if there's been no progress - I'd rather he spend his available time working on it [16:21] ttx: anything else to discuss? [16:21] slangasek: nothing from our side. I hope everything will be much clearer next week. [16:21] [TOPIC] QA team [16:21] New Topic: QA team [16:22] heno, fader, sbeattie: hi [16:22] hi [16:22] Our roadmap is all ready: https://wiki.ubuntu.com/QATeam/RoadMap Specs are written, approved and prioritised. [16:22] It's mostly bug management, test coverage and infrastructure; not much that will land in the distro - just some Checkbox enhancements [16:22] karmic-qa-increase-apport-adoption, karmic-qa-checkbox-expand-test-coverage, karmic-qa-cert-install-from-live-cd-images and karmic-qa-metrics-based-testing are Essential [16:22] ttx: sounds good, thanks [16:22] [LINK] https://wiki.ubuntu.com/QATeam/RoadMap [16:22] LINK received: https://wiki.ubuntu.com/QATeam/RoadMap [16:23] questions? [16:23] heno: well done [16:24] heno: thanks. :) Which are the ones that will land in the distro? I notice two 'checkbox' specs under 'Infrastructure', plus 'Increase Apport Coverage' which probably counts [16:24] thanks :) we did some heavy-handed prioritisation early on, before most of the drafting [16:24] slangasek: Of the checkbox ones, I think only karmic-qa-checkbox-expand-test-coverage will land in the distro [16:24] ok [16:24] It will add new tests to checkbox [16:24] slangasek: right, some checkbox tweaks and lots of aport hooks [16:25] The other one is for internal testing of the live CD which is specific to the testing environment [16:25] sounds reasonable then [16:25] do you guys have any concerns about these being delivered before feature freeze? [16:26] slangasek: ATM, no :) [16:26] okie [16:26] cr3 can give an update on live cd testing [16:26] anything to discuss regarding hardware testing this week? [16:26] slangasek: live cd tests should start trickling in on Monday [16:27] Nothing particularly new. As normal, status is here: http://people.ubuntu.com/~fader/hw-testing/current.html [16:27] As cr3 says we should start getting live cd tests soon, which is a Good Thing [16:27] ('til now we've only tested alternates) [16:27] We don't have recent test results as there doesn't appear to have been a recent alternate cd image to test [16:27] fader: I think your hwtest-breaking network kernel bug is still 'fix committed', right? [16:27] live cd changes are in and just pending review, so we're in good shape [16:27] yes, that's apparently my fault [16:27] slangasek: Correct, but we haven't had an image to test with yet [16:27] (and cjwatson fixed it this morning) [16:27] So once we get one and test it I will update the bug [16:28] fader: you've lost me - if it's 'fix committed', that implies it's in the git repo pending upload to karmic [16:28] are you saying there's doubt about the correctness of the fix? [16:29] fader: if it's worth a quick build before the end of your week, we can do one any time from about half an hour from now onward [16:29] slangasek: Ah, sorry, was thinking 'fix released' [16:29] ok [16:29] cjwatson: It would be nice to have but to be honest it will be easier to test next week once the live cd testing lands [16:29] So if we wait until Monday or Tuesday that is fine... we'll be testing a lot of images then anyway [16:30] slangasek: that's all from QA [16:30] ack, thanks [16:30] [TOPIC] Desktop team [16:30] New Topic: Desktop team [16:30] Hey [16:30] Ups, not me yet :) [16:30] 1spec definition is by and large in good shape: https://blueprints.launchpad.net/ubuntu/karmic/+specs?searchtext=desktop-karmic- [16:30] the ones that are in drafting have been reviewed by me at least once and are just needing some clarifications [16:31] the main ones that are still missing are the DX changes, we have contacted them to get them ready [16:31] but https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus should be pretty accurate now in terms of what we'll do [16:31] in Karmic [16:31] [LINK] https://blueprints.launchpad.net/ubuntu/karmic/+specs?searchtext=desktop-karmic- [16:31] LINK received: https://blueprints.launchpad.net/ubuntu/karmic/+specs?searchtext=desktop-karmic- [16:32] [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:32] LINK received: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [16:32] oops, ignore the "(specs in drafting, so don't take for granted yet):" from the wiki page [16:32] [removed now] [16:32] looks good [16:33] wrt. your next question, [16:33] can't say yet whether _all_ of this will land in karmic by FF [16:33] I'll have to spend some time fully absorbing that list later, and will get back to you with any concerns about individual specs [16:33] we were very aggressive wrt. feature goals this time, so it's likely that some low prio items won't make it [16:33] mostly because we'd rather break stuff now than in lazy lobster [16:34] presumably those low-prio ones can get cut if they miss FF, being low-prio? [16:34] my goal is to have as few structural changes as possible in LL [16:34] right [16:34] essential/high -> must have [16:34] medium -> not the end of the world, but someone would get angry [16:34] low -> target of opportunity [16:34] that's roughly how we use them [16:34] * slangasek nods [16:35] and I see the bug status report is up-to-date there as well, ok [16:35] right [16:35] anything you want to highlight/discuss further? [16:35] there hasn't been much progress on that this week unfortunately [16:35] we were mostly busy with blueprints [16:36] not from my side right now [16:37] I continue to be concerned about bug #339313 in particular; I know the focus has been on spec writing, but this bug has been something of a debacle and I'd like to be able to see it fixed soon in the cycle [16:37] Launchpad bug 339313 in ubuntu-release-notes "Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key" [Undecided,Fix released] https://launchpad.net/bugs/339313 [16:37] right, me too [16:37] we'll probably also SRU this [16:37] it can't get much worse in Karmic, so I was told [16:37] s/Karmic/Jaunty/, sorry [16:38] Isn't that the NM update we have in -proposed already? [16:38] is it? nothing indicates that on the bug [16:38] It may be a different issue. [16:38] yes it is [16:38] OK [16:38] hm, then the changelog doesn't mention this bug [16:38] mm, quite [16:38] which means it's hard to track for SRU verification [16:39] we should copy over the new version to -updates, it fixes it for some users and can't get any worse [16:39] hm, whoever processed that didn't update the bug very well [16:39] ok, let's sort this out out-of-band [16:40] I suppose we should see an update on this next week? with details about how it's been sorted? [16:40] [ACTION] slangasek, pitti, Riddell, ScottK to sort out bug #339313 status [16:40] ACTION received: slangasek, pitti, Riddell, ScottK to sort out bug #339313 status [16:40] Launchpad bug 339313 in ubuntu-release-notes "Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key" [Undecided,Fix released] https://launchpad.net/bugs/339313 [16:40] tx [16:40] rickspencer3: yes [16:41] ok, shuffling the order here again; ScottK also has a schedule conflict and asked to be bumped up [16:41] [TOPIC] MOTU [16:41] New Topic: MOTU [16:42] ScottK: hi [16:42] Still sorting out Python 2.6 stuff. [16:42] Nothing earthshattering there, but the pain isn't over. [16:42] * slangasek nods [16:42] (hmm, still need python2.5 dropped from python-defaults) [16:43] Mostly merges and new package processing on REVU for now. [16:43] There's also one or two Kubuntu related specs worth mentioning here. [16:44] Specs are mostly sorted, but the Kubuntu - Ayatana one is getting approved a bit late because it's complex. [16:44] https://blueprints.launchpad.net/ubuntu?searchtext=kubuntu+karmic is a decent list. [16:44] I'll look at that later today [16:45] https://blueprints.launchpad.net/ubuntu/+spec/kubuntu-karmic-netbook-edition will have some release management implications, but as it's meant to be mostly tech preview/proof of concept, I don't see it as a major issue. [16:45] That's all I have. [16:45] ScottK: Riddell: would it be worth dropping a link to the Kubuntu TODO list? [16:45] rickspencer3: Probably, if someone had it handy [16:46] https://wiki.kubuntu.org/Kubuntu/Todo [16:46] now burndown chat compatible I believe [16:46] chart [16:46] yes [16:46] thanks to pitti and Riddell [16:46] The good news is it looks like KDE4 integration for OOo is almost done and starting to land upstream (Go OOo) [16:47] That took some serious heavy lifting and will benifit every KDE distro. [16:47] That's all I've got. [16:47] ScottK: probably old news to you having been around for a few of these, but please make sure (collectively) that any new netbook-edition images are ready to be tested well in advance of beta [16:47] slangasek: Will do. [16:47] [LINK] https://wiki.kubuntu.org/Kubuntu/Todo [16:47] LINK received: https://wiki.kubuntu.org/Kubuntu/Todo [16:48] ScottK: ok, thanks [16:48] [TOPIC] Mobile team [16:48] New Topic: Mobile team [16:48] Our specs should be under review or pending approval and are tracked along with high prio bugs at: [16:48] lool, davidm: hi [16:48] [LINK] https://wiki.ubuntu.com/MobileTeam/Roadmap [16:48] (I wish we'd have named all specs mobile-karmic-foo like the desktop ones) [16:48] LINK received: https://wiki.ubuntu.com/MobileTeam/Roadmap [16:48] Essential specs: [16:48] - mobile-unr-karmic-seeds: cleanup seeds structure and seeds for UNR [16:48] - mobile-qa-karmic-arm: Create testplans and testcases for Ubuntu on ARM Edit title and summary.. [16:49] - mobile-unr-karmic-connman: switch UNR to connman [16:49] High priority specs: [16:49] - mobile-unr-karmic-applications: change in default apps in UNR [16:49] - mobile-karmic-general-resolution-for-touchscreen-handling: provide tools to calibrate touchscreens [16:49] - mobile-unr-karmic-application-res: improve support on low res for some apps under UNR [16:49] Alpha 3 and overall release status: [16:49] - all specs should be under review or approval (one is already implemented: moving UNR images to ISOs) [16:49] - ARM images: [16:49] - imx51: nothing new for now; Babbage 2 kernel should land for A3 (bjf? :-) and we got an early U-Boot drop which might supersede RedBoot altogether, so we'll evaluate this option after A3; we lack hardware (only 4 B2 boards available total for now) [16:49] - we plan addition of a new architecture, but are waiting for bits from a partner and his permission to publish; we have early (unstable) hardware [16:49] - ARM toolchain: we're getting late on this, we still want to build karmic with ARMv6 + VFP opts, and IS is currently benchmarking builds within qemu; we will get good ARMv7 buildd hardware, but presumably too late for that to be useful in karmic [16:49] - UNR: moved from VFAT to ISO format; no large software update, still largely jaunty's stuff; some SRUs still TBD [16:49] - 385325: I remilestoned this for beta; we continue researching this important bug, but it's not particularly a3-critical [16:49] (done) [16:49] mobile-unr-karmic-seeds> sounds like a good one to get done early, this time around - what still needs cleaned up? [16:50] look, yes, shooting babbage2 for A3 [16:50] s/look/lool/ [16:50] connman> so we'll have two different UIs to support for network connection management? [16:50] lool, issue could be when .31 drops and when we try to rebase to that [16:50] Various things, and it's in progress already; I don't know all specifics, but I think we discussed using a separate live seed, using a common gtk-desktop seed and this kind of things [16:51] lool, still working on getting babbage 1 patches into Karmic, that's a struggle right now [16:51] slangasek: StevenK does this spec and has started various changes already [16:51] slangasek: got to go now... ping dendrobates for any server-specific question. [16:51] slangasek: Yes, apparently we will have to support connman for UNR [16:51] ttx: no problem, thank you [16:51] This is a request from sabdfl [16:52] bjf: So the babbage 2 patches drop support for b1? [16:52] hmm; last I heard, connman had no plans to support half the use cases covered by NM [16:53] lool, no, I need to get babbage 1 in before I start working on babbage 2 [16:53] bjf: We don't strongly care about b1 support; if we can have it it's nice, otherwise we can continue running jaunty or just the jaunty redboot+kernel [16:53] bjf: ok [16:53] lool, babbage 2 patches are build on-top-of babbage 1 patches, they have to go in first [16:53] bjf: Ah there's a dependency, ok [16:54] lool, yes [16:54] slangasek: During the connman session, upstream explained that connman doesn't attempt to cover everything and tries to be simpler [16:54] lool, this is a forward port of both the babbage 1 and babbage 2 patches [16:54] lool: right, which sounds like a functionality regression to me :) [16:54] slangasek: It will miss features, yes [16:55] is connman a replacement for the entire nm, or just for n-m-applet? [16:55] For all of it [16:56] davidm: If you have further comments on UNR connman integration, chime in [16:56] * ScottK runs off. Enjoy the rest of the meetnig. [16:56] Pitti as I understand it it's a replacement for the entire nm stack [16:57] we will test with both [16:57] so choices can be made as appropriate. [16:58] anyone have anything else for mobile? [16:58] I think the hot things are images and toolchain [16:59] But both will happen post a3, after updates from kernel, partner, and our IS [16:59] * slangasek nods [16:59] [TOPIC] Kernel team [16:59] New Topic: Kernel team [16:59] lool, davidm: thanks [16:59] Hey everyone [16:59] We have created a Release Status page for Karmic: [16:59] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [16:59] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [16:59] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic [17:00] This is a Red/Yellow/Green Status with links to the blueprints and specs. Its updated every Tues. in our team IRC meeting. You will also find all the bugs on your agenda on the == Release Meeting Bugs == section. [17:00] On the same page [17:00] All Specs are approved, and in some form of implementation [17:01] is the next kernel upload scheduled? (seeing that half the bugs are 'fix committed') [17:01] The only one that got deferred was the "Newer Kernels on LTS" [17:01] slangasek: I don't know off hand rtg is scheduling it [17:01] slangasek: I'm still working with apw on the KMS/PAE issue [17:01] ok [17:01] what rtg said [17:02] slangasek: what rtg said [17:02] and there is also some interactons with the installer which need to be nailed down [17:02] for the flavour names [17:02] slI think we should be OK to upload if the installer and the update manager cooperate [17:02] generic will just work [17:02] cjwatson: correct [17:03] I'll have time to do the pae stuff early next week [17:03] upgrades aren't an issue, its the initial install that might cause problems. [17:03] but I'll work with cjwatson on that [17:03] not *that* much of an issue. code to check cpuinfo flags is already there, just needs to be extended. [17:03] my main worry is that we *cannot* fit >1 kernel on the CD. [17:04] then i guess most people will be staying on generic with the current mapping [17:04] my opinion at the moment is that we should have generic on the alternate/desktop CD and pae as a network option; for server, possibly pae on the cd [17:04] since that maps reasonably to what we're doing at the moment [17:04] we can perhaps just recommend they consider it? [17:04] and I'm concerned about performance claims regarding pae [17:05] cjwatson: in the past the server booted an non-pae kernel, but installed a pae kernel. is that still gonna be the case? [17:05] (for general use) [17:05] So enabling PAE at runtime is definitevely ruled out even in light of the space constraints? [17:05] lool: I asked ... [17:05] nobody has a working patch for PAE alternatives yet though. Kyle apparently started one a while back [17:05] there is no working patches to do that at th emoment [17:05] rtg: that could be changed if you reckon it's important [17:06] cjwatson: it seems like you should boot the kernel you're gonna install [17:06] the problem with the server CD is not so much that as the fact that it installs a PAE kernel unconditionally and doesn't tell you that it won't work until you reboot [17:06] rtg: I can't make that a hard guarantee; I agree it's nice when possible [17:06] cjwatson: ok [17:07] slangasek: no more kernel topics from me. [17:07] I've generally tended to think that the installer should use a fairly permissive kernel in terms of CPU requirements, so that it can be flexible about what it installs if you're not up to scratch [17:07] not that I've extended this to using the 386 kernel across the board or anything :) [17:09] slangasek: nothing else from kernel... [17:09] anyone else have questions for the kernel team? [17:09] [TOPIC] Foundations team [17:09] New Topic: Foundations team [17:09] cjwatson: heya [17:10] righto [17:10] we have the traditional big chart at https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic [17:10] traffic light colours are pending resupply from the shop but should arrive soon [17:11] [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic [17:11] LINK received: https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Karmic [17:11] https://blueprints.edge.launchpad.net/ubuntu/karmic/+specs?searchtext=foundations-karmic- is a not completely unreasonable list, but unfortunately we weren't entirely consistent about spec names so there are some things listed off that; the wiki page is more complete [17:11] s/listed/missing/ [17:11] as you can see, we have a few drafting stragglers, and a slightly greater number of reviewing stragglers [17:12] Robbie has gone through doing resource guesstimates and deferrals though, so at this point I believe we're reasonably happy with the combined workload [17:12] oh, the wiki page also includes some community-assigned specs [17:13] any questions based on those? [17:13] of the bugs you listed, one is going to be wrapped up as part of a spec currently targeted for alpha 4, and the other one I'll hoover up before EOD today [17:15] * slangasek finishes absorbing the prioritizations [17:15] looks good to me [17:15] slightly more Essentials than I'm truly happy with, but those are mostly from-above kind of things [17:17] only 4 of which are distro feature things, anyway [17:17] yes [17:17] depending on how you count usb-creator for Windows [17:17] :) [17:18] thanks - no other questions here [17:18] .oO Architecture: mingw [17:18] oh, we'll just make that spec depend on multiarch then [17:18] for great justifce [17:18] Eh [17:18] -f [17:18] [TOPIC] 8.04.3 [17:18] New Topic: 8.04.3 [17:19] wanted to talk just a bit about this today [17:19] http://people.ubuntu.com/~ubuntu-archive/pending-sru.html has the list of packages that are still waiting SRU verification for hardy; we want this list down to zero before the point release to minimize the ISO mastering hassle [17:19] LINK received: http://people.ubuntu.com/~ubuntu-archive/pending-sru.html has the list of packages that are still waiting SRU verification for hardy; we want this list down to zero before the point release to minimize the ISO mastering hassle [17:20] dendrobates: there are a number of server packages on there that aren't getting love; can your team provide some support there? (samba, apache2, openldap2.3) [17:20] (redhat-cluster) [17:20] slangasek: yes. [17:21] there's also an open-iscsi upload I've done that I want to have kirkland or mathiaz review/validate for me; I'll prod them directly [17:21] slangasek: ok [17:22] slangasek: on my todo list for today [17:22] hal also needs hardware-specific SRU verification for a Sony Walkman USB device, anyone have one of those? :) [17:22] (or, just general purpose regression testing of hal for hardy) [17:23] slangasek: the qa team is going to do a testing hug day on monday focusing on 8.04.3 SRU verifications: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090622 [17:23] oh, great :) [17:23] in part to tease out some of the hardware specific SRUs if we can. [17:23] in that case, we probably want good test cases in all of the SRU bug reports [17:24] for many of those, regression testing actually is more important [17:24] ...which we don't always have, today [17:24] it doesn't help if a bug is confirmed to fix hw on a particular system, but break another [17:24] sure [17:24] right [17:24] I tried to say [17:24] testing new versions on any hw and telling us "yep, still working" helps a lot [17:25] we'll also run install tests on all the cert hw as soon as we have test images [17:26] I should have those up Monday [17:26] (unless someone else has time to get them up before then) [17:26] ok, great [17:26] fader: think we can get those going on monday, when they come up? [17:27] sbeattie: Yes, we should be able to do that. If it doesn't get picked up automatically I can always start the tests by hand, so one way or the other we'll get them. === ejat is now known as e-jat [17:27] fader: excellent, thanks. [17:27] that's all I have on the 8.04.3 front; anything else? [17:28] [TOPIC] AOB [17:28] New Topic: AOB [17:28] I'll take that as a no [17:28] #endmeeting [17:28] Meeting finished at 11:28. [17:28] thanks, folks [17:29] thanks everyone [17:29] thanks! [17:29] slangasek: just to confirm, I won't allow new hardy-proposed stuff without your explicit consent [17:29] pitti: ok, thank you :) [17:29] slangasek: with hardy being out for more than a year, there can hardly be so urgent issues right now === rickspencer3 is now known as rickspencer3-afk === fader is now known as fader|lunch === fader|lunch is now known as fader === mikrox is now known as mikro === Quintasan_ is now known as Quintasan === kirkland` is now known as kirkland === rickspencer3-afk is now known as rickspencer3