=== AndrewMC is now known as SpockVulcan === doko_ is now known as doko === jodh is now known as jhunt === yofel_ is now known as yofel === dholbach_ is now known as dholbach === greyback is now known as greyback|lunch === Quintasan_ is now known as Quintasan === greyback|lunch is now known as greyback === SpockVulcan is now known as AndrewMC [15:00] #startmeeting [15:00] Meeting started Thu Feb 2 15:00:06 2012 UTC. The chair is ogra_. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:00] 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 [15:00] https://wiki.ubuntu.com/ARM/Meeting/2012/20120202 [15:00] bah [15:00] [link] https://wiki.ubuntu.com/ARM/Meeting/2012/20120202 [15:00] * davidm waves at ogra_ [15:00] hmm, wh doesnt the bot take my link ... [15:00] anyway [15:00] everyone here ? [15:01] * ogra_ sees them roll in :) [15:01] :) [15:01] I initially logged in to ubuntu-meeting on another server finding the room empty [15:01] heh [15:01] convenient [15:01] hey GrueMaster [15:02] * GrueMaster waves [15:02] so lets get rolling ... mind you my Y key is apparently broken, dont laugh if i type weird things :) [15:02] ogra_, do you need to use the # and not[? [15:02] #link https://wiki.ubuntu.com/ARM/Meeting/2012/20120202 [15:02] nope :) [15:02] Interesting [15:02] not that important [15:03] so NCommander isnt around, i'll run the meeting .... [15:03] Standing Items ... [15:03] http://status.ubuntu.com/ubuntu-precise/ubuntu-arm.html [15:03] * ogra_ waits for GrueMaster running gag ... [15:04] sorry, I was busy testing all the images and gaging on my coffee. [15:04] we're pretty well under tthe trend line ! (if it would be angled correctly) [15:05] and ppisati apparently found a fix for the blocker of the "no initrd" spec ... he's my hero of the week ! [15:05] Neat. [15:05] ogra_: wait until you try it out... :) [15:05] indeed :) [15:05] Of course, unblocking it creates work. ;) [15:06] mahmoh seems pretty behind (25 WIs, only 2 done) shoudl we ask him if he needs help ? [15:06] I ask every week. [15:06] (likely due to NCommander assigning the world to him) [15:06] k [15:07] nothing else seems to stick out badly atm ... [15:07] moving on .... [15:07] [topic] == ARM Server Status (NCommander) == === meetingology changed the topic of #ubuntu-meeting to: == ARM Server Status (NCommander) == [15:07] anyone here who can report about that ? [15:08] * ogra_ can say that we have approval to get the unsupported kernel to main to fix our d-i issues [15:08] Image automation is currently stuck due to no initrd generated during install. [15:08] but we dont have a kernel package yet [15:08] Not an official kernel, no. [15:09] no initrd generated during install? [15:09] f-k-i issue [15:09] If we have approval to get it in main, we can tidy up dannf's and JFDI. [15:09] ppisati: Only on the server platform. [15:09] infinity, feel free if you dont have anything else to do ... [15:09] Not an f-k-i issue. I have tested it, it does the right thing. [15:09] ogra_: I have lots else to do, but this is important enough to make time. [15:09] cooloney will do it otherwise ... once he returns from new year drinking :) [15:10] i know its on his TODO [15:10] ogra_: Since getting the kernel in will cascade into massaging d-i and other bits. [15:10] right [15:10] GrueMaster, well, then kernel package postinst ... one for these things :) [15:10] NCommander had a test kernel working based on 3.0 with a minimized patch. Whittled down the 500k lines to ~15k. [15:10] * ahs3 pokes dannf on another channel...and volunteers his time to help with the kernel :)... [15:11] ahs3: That works too. [15:11] davidm, do you know when cooloney returns ? does it make sense to have infinity look at the kernel ? [15:11] ah, k [15:11] If dannf can tidy up a kernel package, I'll do the d-i bits. [15:11] And we'll be golden. [15:11] i guess any preparation work cooloney can get is fine [15:11] ok [15:11] infinity: excellent [15:11] Next mondya [15:12] And cooloney can worry about 3.2, which is what he should be doing. :P [15:12] [action] dannf to tidy up a kernel package [15:12] ACTION: dannf to tidy up a kernel package [15:12] [action] infinity to pull said kernel package into d-i [15:12] ACTION: infinity to pull said kernel package into d-i [15:12] Waste of his time to package old kernels anyway. [15:12] ok, anything else ? [15:13] movinmg on then [15:13] [topic] Kernel Status (cooloney, ppisati) === meetingology changed the topic of #ubuntu-meeting to: Kernel Status (cooloney, ppisati) [15:13] nothing exciting: omap4 1405.7 is finally out [15:14] and there's a new round of SRUs [15:14] Yea, good timing on that. :P [15:14] aprt from that, yesterday i palyed with UUID (aand with GPT + UUID it works) [15:14] \o/ [15:14] and now i've some stuff in the queue for audio (both omap3 and omap4) [15:15] that's all from me [15:15] well, TI says there are fixes in the new tree [15:15] for omap4 at least [15:15] ogra_: right, i'll have to try them [15:15] I need to stop getting distracted from other work and test jcrigby's mx5 kernels. [15:15] btw, audio on beagle has never worked, right? [15:15] s/from/by/ [15:15] ++ [15:15] Not since the kernel was from main. [15:16] infinity, doesnt janimo also have the mx5 ? [15:16] GrueMaster: k [15:16] ogra_: We all do, don't we? [15:16] janimo, could you take over that test ? [15:16] janimo: If you have time... What he said. [15:16] infinity, i dont [15:16] Actually, I should test the mx5 kernel, as I have both old & new platforms. [15:17] * ogra_ still recovers from babbages ... still needs another CPU iteration before i can touchj FSL HW again ;) [15:17] I can run the mx5 tests sure [15:17] GrueMaster: You were busy alphaing, which was why I didn't ask earlier. ;) [15:17] it just seemed everyone was already on the new mx5 kernels :) [15:17] [action] janimo or GrueMaster to test the mx5 kernel from jcrigby [15:17] ACTION: janimo or GrueMaster to test the mx5 kernel from jcrigby [15:17] Which reminds me, A2 will not run on the new mx53 Quickstart board (Rev R). [15:18] janimo: Err, they were? [15:18] anthing else ? [15:18] * ogra_ counts to three [15:18] infinity, well you and GrueMaster have been talking about the ppa since over a week IIRC [15:18] moving on ... [15:18] [topic] ARM Porting/FTBFS status (NCommander, janimo) === meetingology changed the topic of #ubuntu-meeting to: ARM Porting/FTBFS status (NCommander, janimo) [15:18] Talk is easy. :P [15:18] GrueMaster, mine is rev F so hopefully is still fine. It was last week anyway [15:19] anyone ? [15:19] the only one I tried fixing is the qtwebkit [15:19] * ogra_ didnt look at ftbfs at all this week [15:19] gcl and acl2 got off the FTBFS list this week. A couple other minor bits and bobs. [15:19] ay [15:19] but has the same memory exhausted error on my panda as in the buildd [15:19] yay even [15:19] bah [15:19] I need to look more deeply into the "mmap" issue, which has nothing at all to do with kernel bugs. :P [15:19] with 8G of swap even [15:20] use 16 :P [15:20] I'm fairly sure binutils is leaking. [15:20] well, if your process need more than 3GB, you are screwed [15:20] More swap won't help. [15:20] you can add as much swap as you want, but it's still 32bits [15:20] * ogra_ wasnt serious [15:20] and with the 3/1 split [15:20] 3GB is for userspace [15:20] Anyhow, powerpc is a 2/2 split, and it doesn't fail in the same places. [15:21] binutils is pretty clearly doing something Very Bad on ARM. [15:21] ok [15:21] (ppc32 having a 2/2 split is a bug, mind you, which I should file...) [15:21] Someone also should look at bug 925246. Only fails (repeatedly) on armhf panda. [15:21] Launchpad bug 925246 in kde-workspace (Ubuntu) "ksysguardd is causing a kernel oops on armhf only" [Undecided,New] https://launchpad.net/bugs/925246 [15:21] so its all doko's fault anyway [15:21] infinity: wait [15:21] infinity: did you have the same bug with 1405 too? [15:22] s/did/do/ [15:22] ppisati: 3.2.0-1405-omap4 <-- Still exists on that kernel. [15:22] infinity: ok [15:22] ppisati: Err, by "bug", we mean binutils exhausting RAM. The 2/2 -> 3/1 thing is fixed. [15:22] infinity: i see [15:23] So, binutils just eats 3G instead of 2G now. :P [15:23] Not really progress. [15:23] hungry toolchain :) [15:23] Anyhow. Needs more investigation and round tuits. [15:24] right [15:24] I might end up delaying other things I'm doing to just make it happen, since it's now causing failures in main. [15:24] heh. [15:24] infinity: is there a way to reproduce it? [15:24] ppisati: Build qtwebkit-source or haskell-src-exts. [15:24] ppisati: Wait patiently. [15:24] infinity: how long does it take? [15:24] reall patiently [15:24] ppisati: And once you have a failed tree, you can just re-run the last line over and over. :P [15:25] infinity, is this a bug acked by Linaro too? [15:25] ppisati: It takes ~4h to fail the first time, after that, it's maybe 10m to fail the link over and over? [15:25] and the last line failing takes an hour or more IIRC :) [15:25] we can ask rsalveti when he's up :) [15:25] janimo: Nah, it's nowhere near an hour, if you're swapping to disk like a sane person. [15:26] infinity, USB external disk yes. I remember going away and finding Qt still linking after a loong time [15:26] will time it, I stil have the tree around I think [15:26] * infinity times it right now. [15:27] Anyhow. [15:27] Moving on? [15:27] yep, wanted to wait until you guys are done :) [15:27] :) [15:27] janimo: Oh, and no, I haven't gotten around to filing a bug and involving Linaro, because "binutils sucks" is more of a guess than something I've confirmed, so far. [15:28] ah ok [15:28] [topic] ARM Porting/FTBFS status (NCommander, janimo) === meetingology changed the topic of #ubuntu-meeting to: ARM Porting/FTBFS status (NCommander, janimo) [15:28] err [15:28] sorry [15:28] This seems familiar. [15:28] [topic] ARM Image Status (ogra, NCommander) === meetingology changed the topic of #ubuntu-meeting to: ARM Image Status (ogra, NCommander) [15:29] nothing to report, we're ready for A2 [15:29] anyone ... anything ? [15:29] oh, one thing [15:29] Nope. [15:29] All images tested and no major show stoppers. [15:29] Yup? [15:29] doesn anyone know who enabled d-i server images ? [15:29] ??? [15:29] Looking at /etc/default-arches, they've been enabled for ages. [15:30] we seem to have built normal alternate server dailies for a while [15:30] And no one noticed. [15:30] weird [15:30] Or, people noticed, but no one cared. :P [15:30] yeah ... [15:30] I downloaded one, will look at it later today. [15:30] I think it's come up before, and we kept forgetting to turn them off. [15:30] disable them and start building omap4 live images in the same time slot :D [15:30] janimo: Uhh. [15:30] janimo: They build in about 3 minutes. [15:30] well, once the new kernel is around we want them, n o ? [15:31] janimo: Not really the same "time slot". ;) [15:31] well, when I mean time slot, I mean ..... instead :D [15:31] We will want them for the actual server platforms, yes. [15:31] iirc the target image for that kernel is a server alternate [15:31] right, so lets just keep them running [15:31] * rsalveti waves [15:31] its not that its a big waste [15:31] ogra_: Yeah, we can scrub default-arches and build for just that subarch. [15:31] sorry, 2 meetings at the same time :-) [15:32] rsalveti, take your time, ou're not up yet :) [15:32] anything else about images ? [15:32] * ogra_ moves on then [15:32] On other images, I propose turning off armel on some platforms (omap). [15:32] that should wait until after FF [15:33] since we havent actually made the decision yet [15:33] davidm, opinions ? [15:33] wait until after FF [15:34] k [15:34] moving on [15:34] we need to evaluate el vs hf and then shutdown images in the one we are not going to use [15:34] right, thats what i thought [15:34] though tobin is drowning in images atm [15:34] from where I'm sitting hf is looking better and better every day [15:34] yep [15:35] i also think hf it is :) [15:35] understood, only another week [15:35] [topic] QA Status (GrueMaster, mahmoh) === meetingology changed the topic of #ubuntu-meeting to: QA Status (GrueMaster, mahmoh) [15:36] Lots of milestone testing this week. All images on all platforms tested. Minor bugs found, some more annoyances than anything. [15:36] (FF is in two weeks, BTW, not one..) [15:36] No show stopper bugs. [15:36] Also started testing SRU kernel updates (excellent timing). [15:36] FF is my b-day :) [15:37] * ogra_ will tr to get the oem-config preseeding fixed around FF btw [15:37] * GrueMaster can't imagine any of ogra_'s features freezing, but it is cold in the EU. [15:37] i have planned a timeslot for it [15:37] yeah, -10 °C.... [15:38] not even the cats want to go out [15:38] Good. That will greatly help automate smoke testing images. [15:38] anything else apart the weather ? [15:38] * ogra_ moves on ... [15:38] [topic] Linaro Updates (rsalveti) === meetingology changed the topic of #ubuntu-meeting to: Linaro Updates (rsalveti) [15:39] * rsalveti waves again :-) [15:39] :) [15:39] https://launchpad.net/linaro-dev-platform/+milestone/12.02 [15:39] our planning for this cycle [15:39] mostly trying to get things in place, and working on improving the lava usage [15:39] for unity, also making sure it's always working [15:39] by enabling it by default at our images [15:39] how about the compiz bits ? [15:40] that still something we need to sort out next week [15:40] we would like them in the archive [15:40] at linaro connect [15:40] k [15:40] rsalveti: Any interest in looking at the binutils memory exhaustion thing? ;) [15:40] who is going to connect? [15:40] o/ [15:40] infinity: bug? :-) [15:40] David and I, I believe. [15:40] infinity, oh, you go ! [15:40] rsalveti: Unfiled so far, was investigating. [15:40] awesome ! [15:40] great [15:40] rsalveti: But it's the one people were calling a kernel "mmap" bug until we fixed the kernel and it wasn't. :P [15:41] infinity: please check our sessions at https://blueprints.launchpad.net/linaro-ubuntu?searchtext=linaro-platforms-q112 [15:41] got it :-) [15:41] is linaro in any way intrested in LibO ? [15:41] seems NCommander is out for another few days and will then be swamped in ubuntu-server [15:41] rsalveti: Steve and markos already subscribed me to a fair few things, I think, but I'll poke. [15:41] and we would like to get it fixed [15:42] ogra_: Does NCommander have a working tree he can hand off to someone else? [15:42] ogra_, if NCommander is swamped I can continue with LibO [15:42] infinity, i have *no* clue at all [15:42] janimo, that would surely help ! [15:42] [action] janimo to look into LibO [15:42] ACTION: janimo to look into LibO [15:42] janimo, yes please grab Lib0 [15:42] ok [15:42] great :-) [15:43] I have his panda he was using to build LibO on. [15:43] we can try to have a look at that [15:43] it's important for armhf anyway [15:43] yeah [15:43] janimo: I'll ping you after the meeting with the ipv6 info. [15:43] GrueMaster, I'll ping you once I am at a point that I need his changes, thanks [15:43] that's all from my side [15:43] GrueMaster, ok [15:43] its still a lot time until release... but would be good to finally fix it [15:43] sorry, also at another meeting at the phone [15:43] yeah [15:43] * ogra_ moves on [15:43] [topic] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:43] Yeah, plenty of time to release, but I want our armel/armhf decision at feature freeze to be as informed as it can be. [15:44] anyone ? [15:44] anything ? [15:44] seems not ... [15:45] RAISE YOUR HAND NOW OR STAY SILENT ! [15:45] going once [15:45] twice [15:45] adjourned [15:45] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [15:45] Meeting ended Thu Feb 2 15:45:22 2012 UTC. [15:45] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-02-15.00.moin.txt === fenris is now known as Guest60985 === seeker_ is now known as seeker === dholbach_ is now known as dholbach [17:01] hello all [17:02] hey sabdfl [17:03] hey [17:03] o/ [17:04] #startmeeting [17:04] Meeting started Thu Feb 2 17:04:03 2012 UTC. The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:04] 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 [17:04] so, I just had a look at https://wiki.ubuntu.com/CommunityCouncilAgenda [17:04] o/ [17:04] and it seems we have a chat with the DMB today :) [17:04] Aloha [17:05] bdrung, cody-somerville, Laney, micahg, tumbleweed, stgraber: anyone of you around? [17:05] yes [17:05] dholbach: hi [17:05] OH that is TODAY! [17:05] excellent [17:05] * tumbleweed wa just about to run off :P [17:05] #topic Meeting the Developer Membership Board === meetingology changed the topic of #ubuntu-meeting to: Meeting the Developer Membership Board [17:05] how are all of you doing? [17:06] rocking [17:06] today just took a bad turn, personally, an hour ago, but I've been typing hard at a UDW session for an hour, so the adrenaline is there :P [17:06] * dholbach hugs tumbleweed :) [17:06] dmb is looking good, I think [17:06] how do you generally feel is the DMB doing? [17:07] always on top of things? no backlog building up? [17:07] I think we get by pretty well these days [17:07] we haven't missed a meeting in ages [17:07] * stgraber waves [17:08] I was also under the impression that meetings are now quite regularly - which is great [17:08] * Iowan is FC rep - si 2b late [17:09] we've also been talking about things to do to improve the application process [17:09] maybe some self-test questions to let you know if you're ready, but nothing much happening theree atm... [17:09] tumbleweed: great to hear [17:09] tumbleweed, so new applicants have a better idea if they should apply or not? [17:10] dholbach: yeah, and also so they know what we expect all ubuntu developers to do [17:10] (i.e. subscribe to ubuntu-devel-announce, understand freezes) [17:10] *e.g. [17:10] tumbleweed: do you feel the number of DMB members is enough ? [17:10] that might indeed work [17:11] tumbleweed, aching wrists? [17:11] czajkowski: we've been quorate for the last few months, so yes [17:11] although I did come in as a standin for a missing persia :/ [17:11] the developer advisory team I set up with huats recently started mailing people who had done a lot of great work to offer a bit of support - if we can get any feedback, we could share it with you [17:11] tumbleweed: great to hear, that is sometimes an issue for boards. glad the dmb is ok [17:11] tumbleweed: Is there anyone (or a lot of anyone)'s that you feel should have been developers long ago but aren't now for some reason? [17:11] sabdfl: hah, actually a death in the family, but nm that right now :) [17:12] sorry to hear that :-( [17:12] :-( [17:12] YokoZar: hopefully most developers tell people when they should apply [17:12] we had to push jtaylor for months :P [17:13] * YokoZar recalls it was debian's developer-membership rigidity that drew him to Ubuntu to begin with, whereas at Ubuntu he was directly asked to join... [17:13] yes, I hope the d-a-t can help identify cases like that a bit earlier going forward :) [17:13] YokoZar: yeah, ubuntu's open community was a big reason I got drawn in [17:13] (I hardly even run it on any machines...) [17:14] how much of your work do you feel is directly related to dealing with applications? is there many other things which need discussion or organisation as well? [17:14] tumbleweed: That interests me greatly :) I'm wondering if the next me is out there and if we're doing everything we can to find him and tell him "Hey, this is great, not only will I sponsor your packages but I want you to go through this super easy process and upload them yourself." [17:15] dholbach: hrm, maybe 5-15 mins of each meeting [17:15] I would hope that Debian sponsors are encouraging people to go through NM when they are ready too. Although granted it is a lot more in depth. [17:16] and then there is out-of-meeting stuff, micahg has been doing lots of packageset team structure cleanup [17:16] Also we should discuss whether Ubuntu Contributing Developer is worthwhile. [17:16] Laney: did you mean here or in general? [17:17] Laney, as far as I recall a lot of RMBs were very happy that there was a board out there which could review development contributions and make a better informed decision about it [17:17] the CC are probably interested in it. [17:17] well, I think it's worthwhile, but should be used sparingly for those who just need to keep the safety net [17:18] yeah, well the problem is we hardly ever get applicants from it and people say that they find it confusing [17:18] s/from/for/ [17:18] yes, it probably does sit as an unecessary extra step for many people [17:18] * tumbleweed encourages people to bypass it when I think they are ready [17:18] it shouldn't be a step for most people, maybe I can give editing the wiki a shot to make that more clear [17:19] do you get many applicants for membership? [17:19] I don't get the impression that new developers are bothered about it [17:19] no [17:19] it's been quiet recently [17:19] not that we get many new MOTU at all though [17:20] I guess there's still a few motu work items from a blueprint :) [17:20] always [17:20] eep [17:20] which wouldn't instantly solve the problem.... but probably invite some folks again [17:20] yeah, always need more motu [17:20] well, 2 in the last 2 months with another most likely after precise releases [17:21] is there anything you feel which should be really fixed in the DMB? you all seem to be generally quite happy with how the board is running [17:21] Also is there anything the CC can help the DMB with ? [17:21] still, I think I have come to the opinion that it's probably not worth having UCD as a Separate Thing [17:22] * tumbleweed had entirely forgotten that this meeting was coming so, nothing on my mind [17:22] micahg: Regarding clarifying the wiki, thank you muchly [17:23] Laney: I don't think people should be forced to get upload rights, if someone wants to help, but without getting upload rights, we should be able to recognize that [17:23] when has that ever happened? [17:24] on the other side of the coin, the membership requirements can make it harder for us to give PPU [17:24] Laney, maybe it'd be an idea to write a blog post explaining what UCD was designed to be and then ask for comments from everyone to get an idea of how many folks would like to go through the process - maybe it's not sufficiently advertised or explained - or maybe there's no interested in it at all [17:24] it creates a lot of confusion for a theoretical possibility that could be handled in some other way (RMBs) [17:24] I've posted to -devel about it before and didn't really see anyone who strongly cares about it [17:24] well, I'm going to try to clear up the confusion on the wiki [17:25] if we really want it just say "We can also award membership without upload rights if you meet the [[general guidelines]]" [17:25] (This is called being a Contributing Developer). [17:25] or something. [17:26] yeah, that sounds reasonable [17:26] de-emphisising it should remove most of the issues there [17:26] right, bury it [17:26] anything else on your list of pressing concerns? :) [17:27] if this person ever comes along then someone can tell them that the possibility exists [17:27] well, just the continued absence of persia, but that's not just us :'( [17:27] I seem to recall someone where PPU was clearly grantable, but the person hadn't done much to deserve membership, yet [17:27] but I can't remember offhand [17:28] not sure anyone is unhappy with upload rights implying membership in all cases, even when we perhaps wouldn't grant membership separately [17:28] i'm quite relaxed about that tbh [17:29] Yeah that seems reasonable [17:29] yeah, it's not a big issue [17:29] I didn't run into cases where it would have concerned me [17:29] the CC is aware that all developers are added to ~ubuntu-dev, and that that is in ~ubuntumembers [17:29] usually there's quite a bit of work involved into understanding the process, learning about all the bits involved, where work is happening, but you can't just see it yet [17:29] Laney, I am :) [17:29] i am glad that this advisory team effort is happening [17:30] it felt like a bit of an expansion too far to expect the dmb to be responsible for recruitment as well as assessment [17:30] yes, Christophe and I are going to announce it some time next week and hopefully get a few new contributors to help us out [17:30] I agree [17:30] any more questions from the CC? [17:31] or anything from the DMB members where CC members could help with? [17:31] nope, pub quiz time for me! [17:31] no, I think in the past when we've needed the CC, they've been responsive [17:32] the only thing on my list is: take a look at the motu blueprint again :) [17:32] which? [17:33] https://blueprints.launchpad.net/ubuntu/+spec/other-p-motu-bof [17:34] but that's unrelated to the general DMB + CC meet-up [17:34] czajkowski, beuno, Gwaihir, YokoZar, pleia2, akgraner: any more questions from you? [17:34]