=== kees_ is now known as kees === Tm_K is now known as Tm_T === smb` is now known as smb === android is now known as jussi === amithkk is now known as Andrew__ === Andrew__ is now known as AndrewStrong === AndrewStrong is now known as ubuntu__ === ubuntu__ is now known as xubuntu === xubuntu is now known as a === a is now known as b_ === b_ is now known as amithkk === brendand_ is now known as brendand === Pendulum_ is now known as Pendulum === jdstrand_ is now known as jdstrand [17:02] \o [18:03] * jjohansen \o [18:03] Hello [18:03] * sbeattie o/ [18:05] o. [18:05] o/ [18:06] \o [18:06] hi! [18:06] #startmeeting [18:06] Meeting started Mon Apr 23 18:06:33 2012 UTC. The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [18:06] 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 [18:06] The meeting agenda can be found at: [18:06] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:06] [TOPIC] Announcements === meetingology changed the topic of #ubuntu-meeting to: Announcements [18:07] Friendly reminder, we are releasing this week, so be sure to do your ISO testing :) [18:07] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [18:07] I'll go first [18:07] I'm on community this week [18:07] I'm also patch piloting (not sure how that is supposed to work this week...) [18:07] I need to do final install audits [18:07] iso testing [18:08] finish up the last bits on work items [18:08] and get back to some updates [18:08] that's it from me [18:08] mdeslaur: you're up [18:08] I'm in the happy place [18:08] I'm working on jetty updates [18:08] and will release mysql from -proposed most likely [18:09] and will pick something else [18:09] and will test isos [18:09] that's it for me [18:09] sbeattie: you're up [18:09] I'm also in the happy place [18:09] I'm working on fixes for an apparmor SRU [18:10] I need to finish up one work item [18:10] and test isos and get back to updates [18:10] I think that's it for me. [18:10] micahg: you're up [18:11] It's mozilla release week, Thunderbird 11 should go out to -updates for lucid/natty tonight, with Thunderbird 12 (barring nasty CVEs) going out late Thursday, Firefox updates going out as well, then back to webkit [18:12] that's it for me [18:12] micahg: what do you mean tb11 and tb12? [18:13] mdeslaur: Thunderbird 11 is in -proposed, I'll run the final tests today and push to -updates, then 12 is the security update for that (releasing tomorrow), that we'll push out at the end of the week [18:13] this is for the stable release migration [18:13] you're going to push two updates in the same week? [18:13] why don't you just push 12 directly instead of making everyone upgrade twice? [18:13] yes, unfortunately [18:14] well, I'd like some bake time in -updates in case we missed anything with the 3.1 -> 11 update [18:14] that hopefully prevents a regression in the security pocket [18:15] I'm not quite sure how that helps any, besides piss off users getting a GUI change twice in the same week [18:16] mdeslaur: second update isn't a GUI change [18:16] ok [18:16] I'm handling triage this week [18:17] I'm currently working on an eCryptfs bug that leaves zero length files in the lower filesystem when ecryptfs_create() fails === arun__ is now known as arun_ [18:17] tyhicks: \o/ [18:17] I think it is the underlying cause behind the recent uptick in users getting zero length file warnings in their logs [18:18] * kirkland hugs tyhicks [18:18] I also have 2 small eCryptfs work items left [18:18] tyhicks: are you getting close to a fix on that one? [18:18] jdstrand: Yeah - I just realized the underlying cause late Friday and I should have a fix ready by EOD today [18:19] and I'll take another update this week [18:19] I think that it is [18:19] jjohansen: You're up [18:19] I have Bug #987371 that is causing problem for lxc in the cloud to look into more. I think we may already have a fix but it hasn't been verified. [18:19] I still have a couple of other apparmor bugs to finish up testing and get fixes committed for Bug #955892 in particular may be causing problems when used with eCryptfs [18:19] Launchpad bug 987371 in lxc (Ubuntu) "unconfined containers are not starting" [Critical,Confirmed] https://launchpad.net/bugs/987371 [18:19] Launchpad bug 955892 in apparmor (Ubuntu) "Failed name lookup - disconnected path error for long path names" [Undecided,Confirmed] https://launchpad.net/bugs/955892 [18:20] I have a whole lot of UDS prep to do and will be refreshing the dbus prototype against current, so that testing and further development can continue [18:20] I still have 2 work items to finish off, and I will try to finish them [18:20] up this week. [18:20] oh and I suppose there is some iso testing to do too [18:21] I think that is it from /me jdstrand back to you [18:21] thanks [18:21] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [18:21] The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. [18:21] See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/dstat.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/phpgroupware.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/barnowl.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/roundup.html [18:22] http://people.canonical.com/~ubuntu-security/cve/pkg/libpar-packer-perl.html [18:22] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [18:23] another friendly reminder that we should be adding items to the wiki for UDS preparation so we can get this all prepared next week (possibly late this week) [18:23] Does anyone have any other questions or items to discuss? [18:28] #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 [18:28] Meeting ended Mon Apr 23 18:28:38 2012 UTC. [18:28] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-23-18.06.moin.txt [18:28] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-23-18.06.html [18:28] mdeslaur, sbeattie, micahg, tyhicks, jjohansen: thanks! [18:28] thanks jdstrand [18:28] thanks jdstrand! [18:29] thanks jdstrand [18:29] jdstrand: thanks! [18:29] np :) [18:29] thanks jdstrand! === bdrung_ is now known as bdrung [19:01] hi! [19:01] * barry waves [19:02] !dmb-ping [19:02] bdrung, cody-somerville, Laney, micahg, barry, tumbleweed, stgraber: DMB ping [19:02] barry: Meeting's canceled. Go fix bugs. [19:02] o/ [19:02] hello [19:02] Oh. Nevermind. Different meeting. [19:02] heh [19:02] ScottK: what are these "bugs" of which you speak? [19:02] o/ [19:02] * Laney co-opts ScottK onto the DMB [19:02] isn't ubuntu bug free? [19:03] it must be, we're releasing [19:03] lol [19:04] hmm, of all animals of Ubuntu releases, none of them have been actual bugs...maybe not a coincidence? [19:05] who's chair? [19:05] cody-somerville [19:05] who's backup chair? [19:05] me? [19:05] #makingfalafel [19:05] IIRC Laney [19:06] cody-somerville: you missed one last cycle, so we rescheduled you [19:06] alright [19:06] #startmeeting [19:06] Meeting started Mon Apr 23 19:06:17 2012 UTC. The chair is cody-somerville. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [19:06] 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 [19:06] hah, sucker :P [19:06] :) [19:07] #topic PerPackageUploader Application: David Henningsson === meetingology changed the topic of #ubuntu-meeting to: PerPackageUploader Application: David Henningsson [19:07] #link https://wiki.ubuntu.com/Diwic/PulseAudioUploaderApplication [19:07] diwic, Hello. Could you please introduce yourself and your application? [19:07] hi! [19:08] Well, I've been co-maintaining PulseAudio for a while now. I work with PulseAudio and ALSA daily at my job at Canonical. [19:08] I should maybe point out that my main interest is really in the debian/patches directoro [19:08] directory [19:08] which does not mean the other stuff is uninteresting [19:09] but a lot of what I do is to try to actually fix bugs and then get them into Ubuntu [19:09] and into upstream [19:09] also keeping track of bugfixes that come in upstream and apply them to Ubuntu as well. [19:09] As for the packaging itself, I had a meeting at last desktop summit with the debian maintainer [19:10] bringing PulseAudio closer to Debian would be a long term goal for me [19:10] perhaps even being able to merge/sync it one day. [19:11] I guess that suits as an introduction :-) Any questions, feel free to ask [19:11] diwic, How familiar do you feel you are with debian packaging in general and again how familiar do you feel you are with the packaging of pulseaudio, alsa, etc? Do you ever find gaps in your skill set when working on audio related packages? If so, how do you go about working around that? [19:12] diwic: an epoch bump in ubuntu does not help to get to a syncable version [19:12] ah, the package is in Git. Perhaps you could talk to Sweetshark about his experience with co-maintaining Libreoffice :-). [19:13] cody-somerville, well, I guess the reason why I'm not applying for motu or core-dev right away is that I'm not totally familiar with *everything* but rather the PulseAudio package [19:13] diwic: do you have a plan for getting debian and ubuntu versions back in sync? [19:13] cody-somerville, and to some degree the alsa packages as well perhaps. [19:14] bdrung, not exactly :-) but perhaps one could be creative in finding ways to collaborate. [19:15] diwic: why just PA and not the alsa stack too? [19:15] oh, perhaps you just answered that [19:15] are they more complicated packages? [19:16] barry, at this point? Well, sjoerd who maintains it in Debian would like us to sync it some day. In any way we can collaborate about issues and packaging, we can spread knowledge across and reduce workload, leading to more efficient package and better quality essentially. But I haven't looked in detail to it, yet [19:16] diwic: do you have any sense for the major bottlenecks for a sync? [19:17] also, are you the only person concentrating on the audio stack currently? I understand crimsun has reduced his involvement. [19:17] barry, and I can't give you a definite promise that it will happen any time soon. But the upstream relations are good. [19:17] diwic: great! [19:17] Laney, I was actually considering alsa-* as well, as you see Daniel's endorsement, he seems to trust me with that as well. It's mostly a matter of experience. I've been more into the PulseAudio package. [19:18] Laney, TheMuso does a lot of the packaging for the ALSA and PulseAudio packages also. [19:18] Laney, he's the one who has sponsored most of my work lately. [19:18] diwic, What would you consider more important: breadth of support for devices and features + or adverseness to risk? How do the weights of these two concerns change over the course of a Ubuntu release cycle for you? [19:18] ah. [19:21] cody-somerville, that's always a balance, of course. And it's spread over the cycle so bigger features goes in early. One can say that maybe things go in different categories here: [19:22] hello everyone! [19:22] cody-somerville, if it's something that I'm drop dead sure that it won't affect anything else - or at least almost anything else - e g we can match something against a specific device ID (or subsystem ID), it can even go in as an SRU. [19:22] * ogra_ cheers for diwic [19:22] cody-somerville, that's consistent with what the kernel people do. [19:22] * tumbleweed has just been reading some bugs, and everything seems to have been sponsored without any back-and-forth. Nice. [19:23] cody-somerville, but if it touches generic code, it's another matter. No features after Feature Freeze :-) === hggdh_ is now known as hggdh [19:23] cody-somerville, and no uploads in Alpha/Beta/Final Freeze, unless its terribly important (and double-checked with relevant people, such as the release team) [19:24] cody-somerville, does that answer your question? [19:24] Aye. [19:24] diwic, Are you familiar with the SRU and freeze exception processes? Have you ever driven a request through them before? [19:24] * ogra_ remembers multiple SRUs i worked on with diwic [19:25] * tumbleweed sees a few: http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=David+Henningsson&sponsoree_search=name [19:25] cody-somerville, I've been writing SRUs. Freeze exceptions, not so much. I think TheMuso's been sorting out the paperwork there [19:26] cody-somerville, but the best is of course if you've fixed enough bugs so you don't have to make either of them :-) [19:26] diwic: are you subscribed to ubuntu-devel-announce? [19:26] as i said: ubuntu is bug free. ;) [19:27] tumbleweed, yes. [19:27] bdrung, shhh [19:27] out of interest, why did you wait a year to apply? [19:27] diwic, Do you feel integrated in the Ubuntu development community? Do you participate on MLs, devel channels on IRC, etc? [19:27] (dont tell anyone) [19:28] tumbleweed, to gain sufficient experience. [19:29] * tumbleweed appreciates that [19:29] cody-somerville, yes. I'm on #ubuntu-devel and #ubuntu-kernel daily. [19:30] +1 on crossing the chasm ;-) [19:30] diwic: do you feel your sponsors gave you sufficient feedback to improve your skills [19:30] cody-somerville, and I find all these kinds of things interesting, how we drive things forward, and it's also a constant learning experience [19:32] #vote PerPackageUploader Application: David Henningsson - PulseAudio [19:32] Please vote on: PerPackageUploader Application: David Henningsson - PulseAudio [19:32] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [19:32] micahg, hmm, it was a while since that was necessary, but in general yes. I remember bdrung helping me out with audacity when I was starting out here. crimsun has also been very helpful. [19:32] +1 [ keep up the good work ] [19:32] +1 [ keep up the good work ] received from tumbleweed [19:32] +1 - Strong plus one based on interview here today, endorsements on application, and evidence of great work. [19:32] +1 - Strong plus one based on interview here today, endorsements on application, and evidence of great work. received from cody-somerville [19:33] +1 [19:33] +1 received from bdrung [19:33] +1 [19:33] +1 received from Laney [19:33] +1 [19:33] +1 received from barry [19:33] please come back and apply for alsa :-) [19:33] * ogra_ would plus 1 if i could :) [19:33] Laney, noted :-) [19:33] * bdrung remembers the collaboration on audacity. [19:33] +1 - good endorsements, good packaging work, would have liked more feedback in bugs, but I guessas diwic said it's been a while since his uploads have required it [19:33] +1 - good endorsements, good packaging work, would have liked more feedback in bugs, but I guessas diwic said it's been a while since his uploads have required it received from micahg [19:33] is that all of us? [19:34] i believe so [19:34] yes [19:34] #endvote [19:34] Voting ended on: PerPackageUploader Application: David Henningsson - PulseAudio [19:34] Votes for:6 Votes against:0 Abstentions:0 [19:34] Motion carried [19:34] diwic, Congratulations. Your application has been approved. [19:34] * ogra_ hugs diwic [19:34] thanks everyone for your work as well! [19:34] diwic: congrats! [19:34] well deserved [19:34] ogra_, vanhoof thanks for the moral support :-) [19:34] :) [19:35] #topic PerPackageUploader Application: Cesare Falco === meetingology changed the topic of #ubuntu-meeting to: PerPackageUploader Application: Cesare Falco [19:35] #link https://wiki.ubuntu.com/c.falco/DeveloperApplication [19:35] diwic: i recommend to get commit right to the debian repositories to get started with collaboration with debian. [19:35] here I am! Hello everyone! [19:35] bdrung, noted, thanks [19:35] cfalco, Hello Cesare Falco. Please introduce yourself and your application. [19:36] I've been the official maintainer for a couple of package for many years [19:36] mame and btpd [19:37] I'll be honest and I'll say I can't be on IRC so much and I prefer the lists [19:37] that's because I my free time is unfortunately not much [19:38] I'm applying for upload rights for my packages only for that reason [19:38] I'd like to help others, but _at present_ I can't do more [19:38] and I feel I need some more experience too ;) [19:38] cfalco: are you involved with the Debian side of these packages at all? [19:39] yes, for mame only [19:39] * micahg notices btpd isn't in Debian [19:39] btpd is not in debian AFAIK [19:39] did you know that Vcs-* for mess points to mame? [19:39] no... [19:39] I know the debian games team has packaged mess too [19:40] cfalco: I've noticed that btpd hasn't seen an update since maverick, is the package still useful? [19:40] which I'll help to bring into ubuntu too [19:40] micahg, hard to say... it didn't get updates for a long time now [19:40] still I use it and it works good for me [19:41] I see that recently a bug has been opened against 11.10 [19:41] but I'm not been able to reproduce it by far [19:41] cfalco, Have you been able to sync mame from Debian into Ubuntu yet? [19:42] plan is to sync it for 12.10 [19:42] package is now fully merged and working in ubuntu (on my box) [19:42] So you are now working with the games team? [19:42] yes [19:42] cfalco: have you considered adding btpd to Debian? [19:42] _Debian_ games team [19:42] What did you mean by "I know the debian games team has packages mess too" then? [19:42] micahg, yes I did [19:43] That made it sound to me like your package is something else. [19:43] cfalco, I also note that it looks like you're an uploader for the package in Debian but you uploaded 0.144-0ubuntu1 to Ubuntu and then Debian did their own packaging of the new upstream a few months later. Whats the reason for that? [19:44] Laney, mame and mess are different packages; I had never the chance to package it for ubuntu, the debian team arrived first ;) [19:45] codi-somerville, we've been working on different ways until 0.144, we've joined forces starting with 0.145 [19:45] 0.145 is still different because we had to take some time to merge our debian/ tree === pangolin is now known as quantal [19:46] mame and mess both show you merging Ubuntu packaging into the Debian packaging in version 0.142-2 which was uploaded 12 May 2011. What sort of collaboration have you had with them since then? [19:47] Laney, mess is a derivative from mame, for a long time it has been distributed in an incremental form to be applied to the mame source tree, which puzzled me a lot [19:47] cfalco: if one moves files between packages, what are the required changes for debian/control? [19:47] It was the /too/ that confused me [19:47] but I get it now. [19:48] after answering micahg, can you quickly outline our major freezes and how they affect the uploads you'll make? [19:50] cody-somerville, I know they started their package from an old version of mine, then they got in touch and we started to work together to make things good both for debian and ubuntu [19:50] micahg, sorry I didn't get it... what are you referring to please? [19:51] cfalco: if files move from mame-common to mame, what changes do you need to make in debian/control [19:52] micahg, just change the dependencies I guess? :blush: === quantal is now known as pangolin [19:53] that's not enough [19:53] cfalco: dpkg will warn if you're trying to overwrite files in another package unless you tell it something about the package relationship [19:54] s/warn/error out/ [19:54] Laney, freezes come when a new "stable" mame release occur; you can note on mame site that several "u"(nstable) releases are issued between them; these are not suitable for inclusion in the repos because they are often alpha and seldom break something [19:55] I was referring to Ubuntu freezes [19:55] i.e. can you just upload a new mame release whenever it happens to come or do you need to take something else into consideration? [19:56] Laney, do you mean if I'm aware of the release cycle? [19:56] yes, he does :) [19:56] pretty much [19:58] cfalco: any further thoughts on my question after the comment I made? [19:58] Laney, yes I do, I also had to ask for an exception for btpd to fix a bug if I recall correctly [19:58] cfalco: go ahead and answer Laney first [19:59] micahg, well on debian/control I can't think on anything more at present, I surely had to change other files in debian/ to allow the files to reach the correct packages [20:00] cfalco: right, but there's something about the package relationships that are defined in debian/control that you'd have to add or modify [20:00] Laney, I'll have to read some more about the debian import process [20:01] well, why did you have to ask for an exception for btpd? [20:02] Laney, I added the logrotate file if I can recall correctly [20:03] micahg, do you mean that I have to manage the package renaming (conflicts/replaces/provides)? [20:04] (apologies for mistakes, you may have guessed english is not my mother tongue) [20:04] cfalco: yes, can you elaborate [20:04] I'll put it more directly: do you know what Feature Freeze is? [20:08] micahg, I had to rename former sdlmame to mame when they merged sources upstream, so I know how to do this... but to be honest, I can't state this by heart, sorry :( [20:08] Laney, FF is the day by wich you have to upload the upgraded/new packages. After FF you can't but for very important reason [20:09] I'm also aware that a similar deadline exists named Debian Import Freeze or something similar, which I'll have to consider from now on [20:10] DIF shouldn't get in the way of any work. It's just the point where autosyncs stop [20:10] cfalco: what changes with the debian import freeze? [20:10] correct, although "very important" is a bit strong - any upload which only fixes bugs is acceptable [20:11] and other things are acceptable too, with justification [20:11] cfalco: are you aware of anybody else in ubuntu who is helping to maintain mame? if so, how have you worked with them? [20:11] cfalco, If you're uncertain about something, how would you go about finding out the answer / getting help? [20:13] micahg, I'll try saying that if I move files from mame-common to mame -> mame will have to provide mame-common and to conflict with it to force removal of the deprecated package, and also provide it to allow smooth transition to the new package [20:13] cfalco: ok, what if only some files move [20:14] bdrung, I'll have to match DIF starting with 12.10, I still haven't synced it at present [20:14] We're now running out of time. Does the board wish to vote now or ask cfalco to return to continue interview at later meeting? [20:14] Laney, aknowledged :) [20:16] cfalco: what needs to be done to get a package synced after DIF, but before the feature freeze? [20:16] +1 on continue later [20:16] yes please let's defer [20:17] * bdrung agrees. [20:17] +1 for deferring [20:17] yeah, I'm with that [20:17] I feel like this is harder due to you not being a native speaker of English [20:17] next time, we should try to limit it to one active question at a time to ease this I think [20:17] Laney, yes I agree... it's difficult for me :( [20:18] yeah [20:18] cfalco, Are you open to coming to the next (or later) DMB meeting to continue interview? [20:18] cody-somerville, of course :) [20:18] cfalco: thanks for sticking with it! [20:18] cfalco, Great. Please update the date next to your entry in the agenda with the date of the next meeting you'll be able to attend. [20:18] thanks to all for you patience and your work! :) [20:19] cfalco, Thank you! [20:19] cfalco: thank you for your patience and work as well [20:19] #topic AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [20:19] cody-somerville, ok [20:20] UDS [20:20] Quick Note. The next DMB meeting will take place during UDS. [20:20] we're going to schedule a meeting. Any prefences on day/time? [20:20] which time slot and which timezone? [20:20] tumbleweed, any time during Eastern work day works for me. [20:21] tumbleweed: which time zone? === Cees_ is now known as Cees [20:21] timezone will be utc-7 [20:21] * tumbleweed doesn't know the process for scheduling meetings, I tried to get micahg to do the paperwork :) [20:21] :) [20:21] yeah, I can do that [20:21] #action tumbleweed to ensure micahg gets things sorted for UDS meeting [20:21] ACTION: tumbleweed to ensure micahg gets things sorted for UDS meeting [20:21] i think we just need to file a blueprint and make all of us essential participants [20:21] heh [20:22] anything else? [20:22] do we also want a UDS session? [20:22] well [20:22] for those you might not get conf call equipment in the room AFAIK [20:22] maybe you can schedule it as a "private meeting" [20:22] I believe we can ask Marianna to sort that out [20:22] tumbleweed: i think we should take the opportunity to discuss things we might be able to do to make the process better for ourselves and applications [20:22] once I know who will be there, I can arrange it [20:23] barry, tumbleweed: I'm open to that provided we have something prepared and ready to discuss [20:24] due to the timezone, i would prefer a meeting before 14 o'clock local time [20:25] bdrung: i believe that works out to 9am us/pacific time [20:25] well, the earliest meeting used to be ~12:00 UTC, you're suggesting 11:00 UTC [20:25] barry: no, 14:00 local for him is 05:00 US/Pacific [20:26] 14:00 local for uds (-> 23:00 local for me) [20:26] ah [20:26] #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 [20:26] Meeting ended Mon Apr 23 20:26:33 2012 UTC. [20:26] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-23-19.06.moin.txt [20:26] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-23-19.06.html [20:26] cody-somerville: thanks! [20:27] \0_ === lamont` is now known as lamont