=== duanedes1gn is now known as M0hi === M0hi is now known as Guest96191 === Guest96191 is now known as duanedesign === lifeless is now known as subunit === subunit is now known as lifeless === doko__ is now known as doko === chrisccoulson_ is now known as chrisccoulson === dholbach_ is now known as dholach === dholach is now known as dholbach [10:50] No actibity? === davmor2_ is now known as davmor2 [13:43] ogra_: you mentioned some options for squashfs, right? [13:43] ppisati, come over to a proper channel :) [14:59] *fnop* [14:59] o/ [15:00] #startmeeting [15:00] Meeting started Thu Nov 17 15:00:03 2011 UTC. The chair is NCommander. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [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] Bah, 3 seconds late :-( [15:00] [link] https://wiki.ubuntu.com/ARM/Meeting/2011/20111117 [15:00] so who's here? [15:01] * janimo waves [15:01] * mrjazzcat is here [15:01] * ogra_ pretends to [15:02] * ahs3 may or may not be here [15:02] cooloney, ! [15:02] good to see you [15:02] * rsalveti waves [15:02] ogra_: thx, man. [15:02] * davidm waves [15:02] * cooloney waves [15:02] morning davidm cooloney rsalveti mrjazzcat janimo and ahs3 [15:03] * GrueMaster is propped up in a corner with a large mug of coffee. [15:03] * cmagina waves [15:03] * NCommander is wondering if he'll ever see the sun again [15:03] [topic] http://status.ubuntu.com/ubuntu-precise/ubuntu-arm.html === meetingology changed the topic of #ubuntu-meeting to: http://status.ubuntu.com/ubuntu-precise/ubuntu-arm.html [15:03] so I grouped all the specs into two topic specs; one for ARM server, and a general one [15:03] But only one is showing up, anyone know who needs to be prodded? [15:04] I have no WIs there apparently [15:04] NCommander, talk with skate [15:04] NCommander, they need the blueprints accurate with WI's before they show up. [15:04] but both infinity and Adam Conrad do [15:04] skaet: they're there :-/ [15:04] NCommander - all they syntax correct? [15:04] NCommander, action me with it [15:04] * davidm thinks his fingers are still not working correctly [15:04] I do not exclude the pssibility of getting the syntax of the WI entries wrong again [15:05] i'll take care of it with pitti on monday if all specs are 100% there [15:05] [action] ogra to smack status.u.c with skaet [15:05] ACTION: ogra to smack status.u.c with skaet [15:05] *everyone* spec deadline is tomorrow !!!! [15:05] make sure to have all your WIs in [15:05] and to have david approve them !!! [15:06] if anyone needs help drafting specs, poke me [15:07] Anyone needs a spec approved poke me today in the next 4 hours [15:07] even if unfinished ? [15:08] well i have all my WIs but not the text complete yet [15:09] I find the LP depednency tree really becomes useless after a LOT ofspecsareadded [15:09] https://blueprints.launchpad.net/ubuntu/+spec/topic-precise-arm-server [15:09] (I can't turn up the zoom enough to even read the names) [15:10] NCommander, stop reading it on your cellphone :P [15:10] heh [15:10] janimo: I can't even read it on my external monitor [15:11] anyway, anything else on specs/status? [15:11] get a projector ! [15:11] * NCommander should add a spec 'if-you-can-read-this-you-dont-need-glasses' [15:12] move ? [15:12] mv [15:12] [topic] ARM Server Status (NCommander, Daviey) === meetingology changed the topic of #ubuntu-meeting to: ARM Server Status (NCommander, Daviey) [15:12] Nothing to report [15:13] well, we did manage to build server images [15:13] last cycle you mean [15:13] :) [15:13] http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/ [15:13] have they built recently? [15:13] No,this cycle [15:13] heh [15:13] well, indeed, why shouldnt they build [15:14] how about alternate, didnt we want to do some testing with that = [15:14] ? [15:14] or did we decide that netinst suffices ? [15:14] We? As it "Build more stuff for GrueMaster to test"? Ok [15:14] I know janimo wanted some live images, but I don't think we've tried to build alternates [15:14] s/it/in [15:14] * NCommander thinks we need to clone GrueMaster [15:15] NCommander, only for servre indeed ... no deskto alternates :) [15:15] NCommander, btw I got a live img from ogra yesterday, needs fixing but a good first step [15:15] but we dont need to [15:15] Bad idea. I refuse to share my coffee mug. [15:15] janimo, i'll bring that up in the image topic [15:15] GrueMaster: we can clone the mug too. We have the technology [15:15] GrueMaster, two straws, come on [15:16] NCommander, mv ? [15:16] I did more testing on the live image. Having a hard time getting it to be recognized on one large vfat partition by the boot firmware. [15:16] [topic] Kernel Status (cooloney, ppisati) === meetingology changed the topic of #ubuntu-meeting to: Kernel Status (cooloney, ppisati) [15:16] nothing new to report except for the usual SRU kernels [15:17] i'm preparing the first P omap4 kernle [15:17] *kernel [15:17] oh, i am working on an internal ARM project. shall i talk here? [15:17] Excellent. [15:17] still the same code as in O/omap4 but we a big config review/change [15:17] ppisati: cool [15:17] omap4 should be much close to master now [15:17] new ac100 kernel uploaded to precise, SRU with speaker fix uploaded to oneiric [15:17] *closer [15:18] both 2.6.38 based still [15:18] ppisati: I also need to ping you later this morning about kernel SRU security failures I am seeing. [15:18] janimo: noone is working on 3.x kernels? [15:18] GrueMaster: impossible! our kernels are perfect! :) [15:18] ppisati, upstream does, but does not consider it stable enough yet [15:18] we'll get there for 12.04 though [15:18] janimo: i see [15:19] janimo, heh, high hopes [15:19] upstream is based on chromeos tree which is 3.0 only [15:19] not sure if we can make 3.2 this cycle, ut at least 3.0 [15:19] * ppisati would like to work on that (since i finally got the cable and the stuff to hack a serial console in( [15:19] ppisati, #ac100 on freenode :) [15:19] ppisati: serial console on the ac100? [15:19] guys dont forget ac100 is a spare time project this cycle [15:20] right [15:20] janimo: i know, but i've to finish some other stuff first... unfortunately... :( [15:20] we cant put much work time in [15:20] NCommander: yep [15:20] NCommander: https://picasaweb.google.com/107597647635512051759/AC100SerialPortModification?gsessionid=ot7C1HbZg5CPWzwsGXXpZw# [15:21] but didn't solder it yet (and my gfriend will be here this weekend too... so no spare time...) [15:21] I never realized how tiny the ac100 main board is [15:21] anyway, moving on [15:21] [topic] ARM Porting/FTBFS status (NCommander, janimo) === meetingology changed the topic of #ubuntu-meeting to: ARM Porting/FTBFS status (NCommander, janimo) [15:21] ppisati, if you fry your board or something, ping me, i got a free ac100 with broken kbd here [15:21] FTBFS list is shockingly happy for week 3(?) of archive open [15:21] thats good for parts :) [15:21] * ppisati knocks wood... [15:21] tended to a few ftbfs packages [15:21] about 4 of them in main [15:22] what about chromium ... did anyone take a look at that ? [15:22] not me, only firefox [15:22] i know there are linaro people looking into it too and micahg is desparate to get help [15:22] but there seems to be no conversation between the two [15:22] we should help to get that going [15:22] maybe he should hang out on #linaro? [15:23] chromium is a pita because its build system is very unlike others and needs quite a learning curve [15:23] probably [15:23] yeah, agreed [15:24] anything else? [15:24] mv [15:24] I haven't tested on armel yet, but perl seems sad on armhf/smp. [15:24] infinity, we have an hf topic now [15:25] keep that for it :) [15:25] Yes, but this isn't hf-specific, I'm sure. :P [15:25] [topic] ARM Hardfloat status (infinity) === meetingology changed the topic of #ubuntu-meeting to: ARM Hardfloat status (infinity) [15:25] But okay. [15:25] heh [15:25] so where do we stand ? [15:26] Perl's (still) grinding through its testsuite on my mx53, but seems happier than the panda that's been stalled on one test for ~20 hours. [15:26] and once thats done we will have autobiuilds magically ? [15:27] Python rdeps still need to shake out, and I have a couple of things to rebuild in Essential to move their linker ref, and then the chroot can go to the librariar. [15:27] librarian too. [15:27] sounds like we're nearly there \o/ [15:28] I'd told people "Tuesday" before, but it seems I underestimated how slow my machines are (or, how nasty glib2.0 and perl are on slow hardware anyway) [15:28] cant you abuse some buildds in the DC ? [15:28] infinity: You mentioned perl may have issues on armel. Give me a testcase and I can start it spinning here. [15:28] ogra_: I can't parallelise single builds terribly well. [15:28] on hf/smp [15:28] infinity, bah, learn it :P [15:29] yeah, understood :) [15:29] ogra_: hf/smp is confirmed, I'm betting sf/smp will have the same problem. [15:29] ah [15:29] * ogra_ didnt catch that [15:29] GrueMaster: debootstrap --variant=buildd precise, build perl 5.14.2 on a panda. See if testsuite hangs indefinitely on dist/Thread-Semaphore/t/01_basic [15:30] Will add it to jenkins for logging. [15:31] janimo: riku is trying to fix the ftbfs at chromium, to be able to cross build it [15:31] rsalveti, yeah, thats what i meant [15:31] rsajdok, that is great [15:31] rsalveti, :) [15:31] rsalveti, do you knwo if he already talked to micah? [15:32] (i asked him to= [15:32] ogra_: not sure yet, need to ping him [15:32] (if i cant tab rikus nick i'm always lost) [15:33] (else i would have mentioned him above :) ) [15:33] ogra_: suihkulokki :-) [15:33] Haha. [15:33] trivial [15:33] yeah, indeed, i'm such a whiner :P [15:33] :) === chrisccoulson is now known as no_it_is_not_fix === no_it_is_not_fix is now known as chrisccoulson [15:34] We could all name ourselves after beagle buildds. [15:34] Or babbage, rather. [15:34] lol [15:34] anoncaeaeaeae [15:34] i prefer to panda then, heh [15:35] * GrueMaster becomes gruecaeaeaeaeae [15:35] NCommander, mv ? [15:35] [topic] ARM Image Status (ogra, NCommander) === meetingology changed the topic of #ubuntu-meeting to: ARM Image Status (ogra, NCommander) [15:35] preinstalled look fine [15:35] live not so much :( [15:36] i managed to build one manually yesterday but capser is unhappy [15:36] janimo is still researching ... we found some missing kernel options though [15:36] or rather differences in squashfs options ... but that doesnt necessarily mean thay cause the issue [15:37] I took the live image and mangled it into one large vfat partition, but the panda wasn't happy (refused to find MLO). Will retry later today. [15:37] so some more research is needed [15:37] i can hand you a new test kernel in a couple of hours [15:37] GrueMaster, the ext4 should actually be fine [15:37] probably sometime bit rotted badly since lucid [15:37] casper has code for handling that, we checked [15:37] Actually, both partitions are vfat. [15:38] NCommander, well, we are missing compression support for squashfs in the kernel [15:38] so that should be the first thing we eleminate [15:38] ppisati, even if the kernel is not the issue we should still have omep4 kernel aligned with ubuntu sauce [15:38] if that is not already I case of course [15:39] agreed [15:39] that's a WI from UDS anyway so no extra work :) [15:39] Yes. Alignment would be good. Kernel SRU tests currently fail because of being out of alignment. [15:40] GrueMaster: i can beleive it [15:40] omap4 and master were hundreds of options away [15:40] ugh [15:40] * NCommander smacks head on desk [15:41] since the inception of omap4 we always had a config that was closer to vanilla than to ubuntu [15:41] Actually, it dates back earlier than that. I have found discrepancies on Dove and babbage before. [15:42] i remember at least two UDSes where lool and i approached the kernel team about that [15:42] happy it finally happens :) [15:43] you didn't bring enough booze with out then :) [15:43] lol [15:43] s/out/you/ [15:43] NCommander, mv ? [15:44] [topic] ARM Image Status (ogra, NCommander) === meetingology changed the topic of #ubuntu-meeting to: ARM Image Status (ogra, NCommander) [15:44] wow [15:44] twice as many images this time :P [15:44] NCommander, mv ? [15:44] :P [15:44] * NCommander beats ogra_ [15:44] [topic] QA Status (GrueMaster, mahmoh) === meetingology changed the topic of #ubuntu-meeting to: QA Status (GrueMaster, mahmoh) [15:45] Hey, that's me. [15:45] Sure is! [15:45] smells like [15:45] Steady work on getting kernel-SRU test automation running in Jenkins. [15:46] GrueMaster, is there a public url for this jenkins instance? [15:46] So far, reimaging of either Oneiric or Precise works very well. Still some tweaks to make, but the process takes ~15-20 minutes. [15:46] I will push jenkins results to jenkins.qa.ubuntu.com in the near future. [15:47] I have also been working with the security team to get the qa-regression-testsuite running properly on arm and make it easier to automate. [15:48] GrueMaster: the OMAP ROM will insist that your partition type matches your FS type; that is, if it's FAT32, you need partition type 0xc; I don't remember offhand the FAT16 type, but you get the idea [15:48] you also want to make sure you have the bootable flag set on your FAT partition [15:48] Still need to figure out a way to auto-install Maverick and Natty on omap4 for SRU testing, but a few ideas are being explored. [15:49] lool: That may be it. I didn't spend much time on it. Will check after meetings. thks. [15:49] One of many tasks for today. [15:49] anything else? [15:49] mv :) [15:49] Automating netinstall is the easiest. Next will be to automate the server preinstalled images. [15:50] [topic] Linaro Updates (rsalveti) === meetingology changed the topic of #ubuntu-meeting to: Linaro Updates (rsalveti) [15:50] * rsalveti waves [15:50] the milestone we're closing this week: https://launchpad.net/linaro-dev-platform/+milestone/11.11 [15:50] a few important things we did [15:50] u-boot-linaro spl usb booting for panda is finally done by jcrigby [15:51] GrueMaster this will work the same way as omap4boot [15:51] but using the official u-boot for it [15:51] Excellent. [15:51] proper instructions and etc will be released next week, once we finish the 11.11 release [15:51] rsalveti: done? [15:51] riku fixed a bunch of packages for multi-arch enablement, but still needs to send the changes to ubuntu [15:52] he was finally able to cross build firefox with multi-arch [15:52] smagoun will be happy to hear that [15:52] he's now looking into chromium to see if we'll be able to also cross build it [15:52] next month we're planning to work pushing most of the changes, as for now it was more a experiment [15:52] Being able to built it at all would be a start. ;) [15:53] s/built/build/ [15:53] yup [15:53] ++ [15:53] other than that we're also enabling the precise images now [15:53] and hope to have them also enabled at lava soon [15:53] intrestingly there are armel debs at google somewheer [15:53] of v14 or even 15 [15:53] rsalveti, is there a list of MA enabled packages being worked on? [15:53] Yeah, jbailey builds chrome for arm. [15:53] and something I'd like to talk with you guys later is how to use lava to help testing the ubuntu images [15:53] Or chromium. Or both. I always forget. [15:53] ah [15:54] rsalveti: You know Jeff? Could be worth poking him. [15:54] well those may be native builds no? [15:54] janimo: sure, 1 sec [15:54] rsalveti: It would be nice if your teams could figure out a way to get u-boot into automated testing. [15:54] GrueMaster: that's in progress [15:54] janimo: I'm sure they're native, but we can't build native right now either. :P [15:54] a lot of discussions with plars about it [15:54] janimo: https://launchpad.net/~linaro-maintainers/+archive/staging-overlay [15:54] infinity, well we sometimes can :) [15:54] janimo: mostly the ones changed by riku [15:55] janimo: also a few others at our overlay ppa [15:55] rsalveti, these imply upstream pushing I suppose [15:55] janimo: yup, work for our next cycle [15:55] rsalveti: is there any final release from linaro based on 3.1 kernel? i think every month you guys will release once [15:55] Libo would be a great candidate [15:55] rsalveti: or will move to 3.2 sometime [15:56] cooloney: yes, linux-linaro 3.1 for 11.11 was already released [15:56] cooloney, there are no final releases from linaro :P [15:56] for now we're still on 3.1 [15:56] its all rolling [15:56] but we should be using tip soon [15:56] got it, thanks [15:56] * cooloney thinks 11.11 is good name for release [15:56] and marcin also pushed a few fixes for the cross toolchain packages [15:56] that's all from my side [15:57] [topic] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:58] * cooloney asks what's AOB for? [15:58] All Other Business? [15:58] Or Any. [15:58] any other bubblingupstuff [15:58] yep [15:58] GrueMaster: we're looking at building some devices that would make it easier for us to do that [15:59] But a bit of a joke with 2 minutes to go. ;) [15:59] infinity: got it. [15:59] plars: cool. [15:59] GrueMaster: but I thought you already had this solved for your purposes with usbboot on panda? [16:00] plars: I was mainly thinking of beaglexm. Still have network issues there. [16:00] we're overtime, so if there's anything urgent, please say it now quickly, else I'll close the meeting [16:00] And I only have 1 system. [16:00] NCommander, close [16:00] #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 [16:00] Meeting ended Thu Nov 17 16:00:42 2011 UTC. [16:00] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-11-17-15.00.moin.txt [16:00] cya [16:40] [topic] wait, unvoice'd users can do this? [16:51] #lol [16:51] ? [16:57] o/ [16:58] o/ [16:59] o/ [17:00] o/ [17:00] o// [17:00] hey all [17:00] hi [17:01] hello! [17:02] o/ [17:02] hey sabdfl [17:04] ok, lets get this party started [17:04] #startmeeting [17:04] Meeting started Thu Nov 17 17:04:03 2011 UTC. The chair is beuno. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [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] there's no proposed topics on the wiki [17:04] I have something to report [17:05] and I wanted to share a quick reminder [17:05] cool [17:05] YokoZar, go for it [17:06] Right, at UDS I was tasked with investigating the voting system [17:06] Briefly, 1) We need to pick an actual algorithm to use, and 2) We need a tie-breaking procedure [17:07] i thought (1) was condorcet [17:07] and (2) was one of the CIVS options [17:07] For 1), the Shulze method (first in the list on CIVS) is the clear answer: it's what Debian and Wikimedia use, amid others, and it's a sound algorithm. You can read about it here: http://en.wikipedia.org/wiki/Schulze_Method [17:07] sabdfl: there are multiple condorcet methods (indeed CIVS lists 4 of them) [17:07] ah, right, tiebreaking when even Condorcet-Shultze ties [17:08] Right, which is indeed what happened between 2nd and 3rd place in the IRCC election [17:09] As far as tie-breaking is concerned, that's actually not handled by CIVS. [17:09] #topic voting algorithm for board elections and tie-breaking procedure === meetingology changed the topic of #ubuntu-meeting to: voting algorithm for board elections and tie-breaking procedure [17:09] Do we know how other projects deal with cases like this? [17:10] YokoZar: so are you suggesting/recommending that going forth we use the Shulze method [17:10] dholbach: I'm not sure what Debian's tie-breaking procedures are, if they even have them. It really is a freak occurance [17:10] czajkowski: Yes, I'm saying we make it official somewhere [17:10] YokoZar: ok makes sense to be honest as I' [17:10] m sure it gets asked the whole time [17:10] I'd suggest to document it on http://wiki.ubuntu.com/CommunityCouncil/Restaffing [17:10] I have no objections about using it [17:10] ey use this: http://en.wikipedia.org/wiki/Cloneproof_Schwartz_Sequential_Dropping [17:10] beuno: it's the same [17:11] (according to http://www.debian.org/vote/) [17:11] beuno: (two names for same method) [17:11] In fact that wikipedia page is a redirect ;) [17:11] very simply, this is our discretion, and how we decide is up to us [17:11] dholbach: I'll look into if Debian has a true tie resolution procedure [17:11] i prefer consensus, but if we vote, there is a casting vote so we never get stuck [17:12] sabdfl: Right, I was just going to suggest we resolve ties by just looking at your ballot and if you rank A > B and there is a tie between A and B, A now beats B [17:12] remember, the mandate stems from us; we poll to get mutual buy-in on delegation, but it is in fact delegation [17:12] who's ballot? [17:13] i don't need or want to be the direct decider on those; we should discuss them, see if we have general agreement, and if not then just vote [17:13] Ok so you would defer a true tie to the CC then [17:14] yes; it's our delegation, we've polled the relevant group in the community, they've said they're equally happy with two candidates we shortlisted, we can choose [17:14] sabdfl's argument makes sense and it should be corner cases, I just think we should document it, so it's clear to everybody involved [17:14] agreed [17:14] That's fine by me. Our other two options would be 1) Just using sabdfl's vote as a casting vote in the actual election, and 2) Doing something pseudorandom [17:14] aye as dholbach said documentaion would be the key here so everyone knows and is on the same page [17:14] note to ourselves, though, is that we should exercise real discretion in the shortlisting [17:15] i do with TB and CC, and we should do the same in the delegation [17:15] so we use Schwartz as an algorithm, and tie-breaks get discussed and decided upon by the CC, yes? [17:15] nobody should be on the shortlist that does not have our full support [17:15] otherwise we're not doing our job [17:15] beuno, +1 [17:15] beuno: +1 [17:15] beuno: Yes, +1. Though I think we should be consistent in calling it Shulze (that seems to be what Wikipedia has settled on, as well as the Elections-Methods mailing list) [17:16] #action update wiki pages describing the algorithm and tie-breaking methods used [17:16] ACTION: update wiki pages describing the algorithm and tie-breaking methods used [17:16] +1, that works for me [17:16] YokoZar: thanks for looking into this [17:16] +1 for me too, sounds fine [17:16] +1 from me as well [17:16] ok, dholbach, you're up [17:16] This is the first time we are doing this, but I would like to remind everybody that we are going to do "team catch-ups" in CC meetings from now on, so we'll invite people from teams such as governance bodies and talk about a variety of things to improve our cross-team communication, etc. Here's the preliminary schedule: https://lists.launchpad.net/ubuntu-council-teams/msg00019.html - please make sure your board/council/team is aware of it. [17:16] Thanks :-) [17:17] Ok, I just realised that we changed meeting dates, so I'll have to update the schedule. [17:17] I'll take that as an action and post it to the ubuntu-council-teams list. [17:17] thanks dholbach [17:17] cheers [17:17] thanks dholbach [17:17] great dholbach [17:18] #info This is the first time we are doing this, but I would like to remind everybody that we are going to do "team catch-ups" in CC meetings from now on, so we'll invite people from teams such as governance bodies and talk about a variety of things to improve our cross-team communication, etc. Here's the preliminary schedule: https://lists.launchpad.net/ubuntu-council-teams/msg00019.html - please make sure your board/council/team is aware o [17:18] * beuno stares at meetingology [17:18] ...f it. Thanks :-) [17:18] dholbach, can we keep that schedule in the wiki, say, on CommunityCouncilAgenda? [17:18] I guess that was TMI [17:18] sabdfl, sure [17:18] groovy, thanks [17:19] might also great to have it in the fridge calendar... [17:19] that might be tricky since it's *during* the CC meeting [17:19] I suggest [17:20] and it's a recurring event [17:20] i think on the agenda page should be fine [17:20] that We start the meeting with it [17:20] #action add the team catch-ups to CommunityCouncilAgenda [17:20] ACTION: add the team catch-ups to CommunityCouncilAgenda [17:20] I mean as a matter of policy have other teams as guests first on the agenda so that they can leave when they done [17:20] YokoZar: good idea [17:20] YokoZar, +1 [17:20] YokoZar, +1 [17:21] * YokoZar remembers an Ubuntu-California meeting that had some international 3AMers present who were made to wait through half an hour of nonsense [17:21] yes, sounds good to me [17:21] yeah, that wasn't good :( [17:21] :) [17:21] if memory serves, next up is: https://wiki.ubuntu.com/DesignTeam [17:22] yep [17:22] so I sent an email to the CC list giving us a heads up, but for the benefit of others, here's the related blueprint: https://blueprints.launchpad.net/ubuntu/+spec/community-p-designing-and-creating-ubuntu-experiences [17:22] #topic https://wiki.ubuntu.com/DesignTeam === meetingology changed the topic of #ubuntu-meeting to: https://wiki.ubuntu.com/DesignTeam [17:22] essentially the community council will be taking over most of jono's tasks here in guidance [17:22] that DesignTeam wiki is slowly coming together, they wrote most of it this morning during their preliminary meeting :) [17:22] also https://blueprints.launchpad.net/ubuntu/+spec/community-p-ux-participation [17:23] the team hasn't formally been announced, right now they're looking for some structure and guidance and after speaking with doctormo and wendar I offered that the CC would probably be in a good place to do this (since we're already committed to checking in with some other teams this cycle) [17:23] thanks for coming, wendar :) [17:23] anyone have any questions at this time? [17:23] I agree [17:23] I think the CC can offer some great guidance here [17:24]