[11:35] <tonyyarusso> @schedule toronto
[11:36] <tonyyarusso> okay....
[11:36] <Ubugtu> Schedule for America/Toronto: 30 Nov 16:00: Ubuntu Development Team | 06 Dec 15:00: Edubuntu | 07 Dec 03:00: Ubuntu Development Team | 13 Dec 07:00: Edubuntu | 14 Dec 11:00: Ubuntu Development Team | 20 Dec 15:00: Edubuntu
[11:36] <tonyyarusso> Oh, it's just slow
[11:37] <Hobbsee> @schedule sydney
[11:37] <Ubugtu> Schedule for Australia/Sydney: 01 Dec 08:00: Ubuntu Development Team | 07 Dec 07:00: Edubuntu | 07 Dec 19:00: Ubuntu Development Team | 13 Dec 23:00: Edubuntu | 15 Dec 03:00: Ubuntu Development Team | 21 Dec 07:00: Edubuntu
[09:50] <mdz> good day
[09:50] <dholbach> good evening :)
[09:50] <BenC> good afternoon
[09:50] <kylem> good coffee
[09:51] <fabbione> hmm nicotine...
[09:51] <fabbione> #include <linux/crack/nicotine.h>
[09:51] <fabbione> int main() {
[09:51] <fabbione>   inject();
[09:51] <fabbione>  exit 666;
[09:51] <fabbione> }
[09:51] <mdz> Syntax error near `exit'
[09:52] <zul> afternoon
[09:52] <BenC> not to mention including kernel headers from user space
[09:52] <BenC> for shame
[09:53] <cjwatson> mdz: disturbingly that implies you have such a header
[09:53] <ajmitch> hi
[09:54] <kylem> BenC, hehe.
[09:54] <seb128> mdz: pong ;)
[09:59] <fabbione> mdz: what would you expect after inject() :P
[10:01] <mdz> we're missing a few people but need to get started
[10:01] <heno> mdz: pong
[10:01] <mdz> welcome all
[10:01] <mdz> heno: you're up first
[10:02] <heno> * Approved: access-gdm, braille-support, color-filters, common-at-conf, orca-laptop-support
[10:02] <heno> * Drafting: multilingual-speech -- this will be taken forward by Gilles Casse from Oralux. I've also created orca-espeak as a prerequisite to this.
[10:02] <heno> feisty-speakup -- Depends on involvement from the speakup community. The next week or so will tell.
[10:02] <heno> * Abandoned: atspi-testing-by-default -- seb128 had issues with this and I see his point.
[10:02] <heno> (not sure about the format today)
[10:02] <cjwatson> atspi-testing-by-default> yeah, I wasn't all that keen either
[10:02] <cjwatson> (sorry etc.)
[10:02] <Simira> mdz: Tollef's here in five mins or so
[10:02] <heno> yeah, I can see why
[10:03] <mdz> heno: apart from atspi-*, are those targeted for feisty?
[10:03] <mdz> Simira: thanks
[10:03] <mdz> hmm, no
[10:03] <heno> oh, I don't think so. Need to look at how LP does that
[10:04] <mdz> heno: ok, please see that the ones which should be on the roadmap are targeted.  the link is labeled 'set release goal' I think
[10:04] <heno> I'll do that now, thanks
[10:04] <mdz> heno: are there assignees for all of those?
[10:05] <heno> all except the feisty speakup one
[10:05] <heno> which is still uncertain
[10:05] <heno> I'm assignee for most of them
[10:05] <mdz> ok; if you can find someone who will aim for feisty, then go ahead and target it, otherwise leave it off
[10:05] <cjwatson> ("Propose as goal"
[10:05] <cjwatson> )
[10:06] <heno> right
[10:06] <mdz> heno: thanks
[10:06] <mdz> fabbione: next
[10:06] <fabbione> feisty-toolchain (approved): fixed a couple of minor glibc things.
[10:06] <fabbione> sparc64-installer (approved): not started. Waiting Herd 1 to settle before starting on it.
[10:06] <fabbione> spart64-niagara-ssl-accelerator (approved): wrote down some pseudo code and read a few times the hw specs to understand how it is supposed to work. This should be object of real coding during sparc sprint in Seattle.
[10:06] <fabbione> integrity-check (approved): fixed the infrastructure to go https://. waiting Herd 1 and d-i merge before moving it in main/cd.
[10:06] <fabbione> ubuntu-feisty-ha-cluster (approved): extremely good progress here. Received even emails from IBM India that confused us as upstream. OCFS2 has been updated and needs testing. GFS1 has been updated to the new FS API but it's not working properly (needs fixing). GFS2 has been updated and it's working almost ok. It fixes a bunch of problems from edgy but it seems i am still one of the few that can crash it :)
[10:06] <fabbione> sparc64-64bit-apps and sparc64-desktop: left to the community. no progress.
[10:06] <fabbione> Done
[10:06] <fabbione>  * SRU for lvm2 completed.
[10:06] <fabbione>  * working on SRU for mdadm in edgy (almost ready).
[10:06] <mdz> fabbione: what are the dates for the sprint again?
[10:06] <cjwatson> fabbione: d-i merge is done
[10:07] <fabbione> mdz: one sec...
[10:07] <fabbione> mdz: 16 -> 23 Dec.
[10:07] <mdz> ok
[10:07] <fabbione> cjwatson: yes i saw it but it was too late today to start :)
[10:07] <cjwatson> right, just saying you aren't waiting for it any more :-)
[10:07] <cjwatson> got to defend my honour etc.
[10:07] <fabbione> mdz: 16 is fly out so nothing will happen other than sitting 12 hours on a plane ;)
[10:08] <fabbione> cjwatson: your honour is untouchable d-i god
[10:08] <mdz> what could be more fun?
[10:08] <mdz> fabbione: how does sparc look for herd 1?
[10:08] <fabbione> mdz: sex?
[10:08] <fabbione> mdz: i am running it on both my machines
[10:08] <mdz> fabbione: I mean installability
[10:08] <fabbione> mdz: i only need to test the installer tomorrow
[10:08] <cjwatson> sparc d-i FTBFS
[10:08] <cjwatson> I have a fix in hand
[10:08] <cjwatson> I'll upload it soonish so fabio can test
[10:08] <fabbione> mdz: i think it's blocked on d-i :P
[10:09] <cjwatson> (but Mithrandir had said he didn't care so I was skipping it in favour of more urgent things)
[10:09] <mdz> ok, we'll get a full herd 1 update from Mithrandir a bit later
[10:09] <mdz> fabbione: thanks
[10:09] <mdz> dholbach: next
[10:09] <dholbach> Done:
[10:09] <dholbach>  * merges
[10:09] <dholbach>  * started bug mailbox cleaning *whine*
[10:09] <dholbach>  * gnome updates
[10:09] <dholbach> Todo:
[10:09] <dholbach>  * implement top prio art builder goals
[10:10] <dholbach>  * more bug cleaning
[10:10] <dholbach>  * GNOME 2.17.3
[10:10] <dholbach>  * more merging
[10:10] <dholbach> Specs:
[10:10] <dholbach>  * art-builder-improvements: approved, started.
[10:10] <dholbach>  * feisty-telepathy: approved, started: landell and telepathy-wilde still need packaging.
[10:10] <dholbach>  * code-review: pending approval, needs one TB sign-off.
[10:10] <dholbach>  * motu: pending approval, needs one TB sign-off.
[10:10] <dholbach> 
[10:10] <mdz> dholbach: is the art team actively using the art-builder repo now?
[10:10] <dholbach> mdz: no, they're not - Troy mailed on how to use bzr and I gave some instructions.
[10:11] <mdz> dholbach: please set me as approver on those TB specs so that I get email; I'll give them a second pass
[10:11] <dholbach> ok - thank you
[10:11] <mdz> dholbach: is there a wiki page for them which explains how to use it?
[10:11] <dholbach> mdz: no not yet, I'll do that.
[10:12] <dholbach> mdz: (done, set the approver of the specs)
[10:12] <mdz> ok
[10:12] <mdz> thanks dholbach
[10:12] <mdz> kylem: next
[10:12] <kylem> done:
[10:12] <kylem>  * ubuntu-dapper-security.git: up to date with kernel-sec svn
[10:12] <kylem>  * ubuntu-edgy-security.git: up to date with kernel-sec svn
[10:12] <kylem>  * ubuntu-{dapper,edgy}-updates.git: enable bnx2 in nic-modules
[10:12] <kylem>  * backported squashfs patch for dapper-security.git
[10:12] <kylem>  * backported ocfs2 patches for dapper-security.git
[10:12] <kylem>  * backported sky2 v1.9 for edgy-updates.git for #68338
[10:12] <kylem>  * fixed up hdaps for edgy-updates.git
[10:12] <kylem>  * looked into msi implications for #73815
[10:12] <kylem>  * trawled stable trees for patches
[10:12] <kylem>  * debugged why i can't push to rookery
[10:13] <kylem> todo:
[10:13] <kylem>  * get the 4 trees uploaded
[10:13] <kylem>  * look into getting git updated so i can push to rookery
[10:13] <fabbione> kylem: we will need ocfs2 also in edgy
[10:13] <Mithrandir> (pong)
[10:13] <kylem> fabbione, it's fixed in edgy, but i didn't have to do any work just apply it. in dapper i had to make sure it still worked because i had to hand apply.
[10:14] <fabbione> kylem: ah ok
[10:14] <fabbione> thanks
[10:14] <kylem> np
[10:14] <mdz> kylem: you're all set up with the access you need to do your work now, yes?
[10:14] <kylem> mdz, yup
[10:15] <mdz> kylem: ok, thanks
[10:15] <mdz> BenC: next
[10:15] <cjwatson> kylem: is bnx2 urgent? if so we need a d-i update
[10:15] <BenC> driver-device-manager: Approved, work in progress.
[10:15] <BenC> driver-backports: Pending Approval (just finished this last minute spec this morning).
[10:15] <BenC> Kernel work this past week:
[10:15] <BenC> * Lowlatency kernel/lrm added. Joy to the world.
[10:15] <BenC> * 2.6.19 released, our tree is moving on with 2.6.20 as planned.
[10:15] <BenC> * Merged some ubuntu kernel patches upstream.
[10:15] <BenC> Kernel work for next week:
[10:15] <BenC> * Initial 2.6.20 patches rolling into upstream. Will get out a new kernel based on this ASAP.
[10:15] <BenC> * Moving all linux-source-2.6.19 lp bugs to linux-source-2.6.20 after this upload. All traces of 2.6.19 will disappear.
[10:15] <BenC> * Revamp of the kernel-team git repository to enable better security patch handling (embargoed patches, etc), and better collaboration between myself and Kyle.
[10:15] <cjwatson> well, er, maybe, depending on the installation method
[10:15] <kylem> cjwatson, well, i'm sure elmo would appreciate it. :)
[10:15] <cjwatson> kylem: check with me tomorrow?
[10:16] <mdz> BenC: I'll have a look at driver-backports after the meeting
[10:16] <zul> heh dont forget me in the kernel-team git repository ;)
[10:17] <BenC> zul: likely it will be on a canonical machine, so might not get that
[10:17] <mdz> BenC: any kernel blockers for herd 1?
[10:17] <BenC> mdz: No, kernel is uploaded and stable for herd-1
[10:17] <mdz> and d-i up to date with it?
[10:17] <BenC> lrm and linux-meta synced as well
[10:17] <BenC> cjwatson: ^^
[10:17] <cjwatson> mdz: yes
[10:18] <cjwatson> done today
[10:18] <mdz> ok, thanks BenC
[10:18] <BenC> we have a few udeb quirks to work out, but colin says herd-1 is good
[10:18] <kylem> cjwatson, https://bugs.launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/73647 <- bnx2.
[10:18] <Ubugtu> Malone bug 73647 in linux-source-2.6.17 "Broadcom NetXtreme II BCM5708 not detected on install" [Undecided,Fix committed] 
[10:18] <mdz> mvo: next
[10:18] <mvo> Did:
[10:18] <mvo> - specs
[10:18] <mvo> - merges
[10:18] <mvo> - work on the auto-dist-upgrade testing (better control scipt, most-of-main install profile
[10:18] <mvo> - release-upgrader for edgy->feisty uploaded
[10:18] <mvo> - prototype/experiments for apt mirror method
[10:18] <mvo> - SRU xorg uploaded to edgy-updates
[10:18] <mvo> Will do:
[10:18] <cjwatson> BenC: well, it builds anyway - haven't *tested* yet
[10:18] <mvo> - merges
[10:18] <mvo> - LSB face-to-face meeting berlin
[10:18] <mvo> Feisty specs approved:
[10:18] <mvo> - auto-dist-upgrade-testing, binary-driver-education, common-customizations, dist-upgrader-fixes, enabling-additional-components,   dynamic-mirror-decisions,   server-upgrade-tool, apt-sha256
[10:19] <mdz> mvo: auto-dist-upgrade-testisg doesn't seem to be targeted?
[10:19] <mdz> please target it to feisty
[10:19] <mvo> mdz: oh, I fix that
[10:20] <mdz> mvo: is the dist-upgrader ready for herd 1 testing?
[10:20] <mvo> mdz: yes, it should be fine
[10:21] <mdz> mvo: so we can include update-manager instructions in the announcement and start real world upgrade testing?
[10:21] <mvo> mdz: yes, I can update the announcement in the wiki
[10:21] <mdz> ok, great
[10:21] <mdz> thanks mvo
[10:21] <mdz> Mithrandir: next
[10:21] <Mithrandir> network-roaming: not started; will have to read up on this again, it seems to have changed a bit from the bof discussion
[10:21] <Mithrandir> changelog-closes-bugs: not started
[10:21] <Mithrandir> misc: herd 1 fixing, getting there slowly
[10:21] <Mithrandir> next week: herd 1 release, get changelog-closes-bugs done
[10:21] <Mithrandir> herd 1: getting there, was blocked on d-i stuff and some bits of cdimage not being updated to know that feisty is current.  I'll roll CDs and test them tomorrow.  Bug status isn't too good, I've tried to chase people up about the "later"-targetted bugs, but not being too successful about this.  Ideas for making this happen better welcome
[10:23] <cjwatson> IME "later" has been entirely snowed under by merges and getting the world working at all
[10:23] <seb128> Mithrandir: when you say "next week", that's tomorrow? ;)
[10:23] <cjwatson> I think first milestone may have been a bit ambitious for "later"
[10:23] <mdz> cjwatson: agreed
[10:23] <Mithrandir> seb128: next week is what happens from today until next distro team meeting.
[10:23] <mdz> we should figure a realistic date for closing them, but it should be soon
[10:23] <cjwatson> although obviously ambitious targets mean we're more likely to hit the realistic targets
[10:23] <Mithrandir> cjwatson: I've intentionally not chased you down due to you being ideal in too many places already.
[10:24] <mdz> Mithrandir: perhaps mail -devel-announce with a summary of 'later' in concert with herd 1 and aim for herd 2
[10:24] <Mithrandir> mdz: I'll do that.
[10:24] <mdz> Mithrandir: do you have a date for herd 2?
[10:25] <Mithrandir> mdz: hmm, I thought we put those on the release schedule, but apparently not.  I'll find some dates.
[10:25] <mdz> I thought so too, but they didn't make it into the version on the wiki
[10:25] <Mithrandir> dec 14th might work
[10:26] <mdz> I think we said every 2-3 weeks?
[10:26] <Mithrandir> yeah, but I'm on xmas vac from the 19th, and I suspect bits of the rest of the team will be starting their vacation that week too
[10:26] <mdz> at any rate, yes, please add milestone dates to the schedule
[10:26] <Mithrandir> I'll do that.
[10:26] <mdz> Mithrandir: please make notes about the edgy->feisty bits of cdimage etc. and add them to the checklist
[10:27] <Mithrandir> ReleaseProcess?
[10:27] <cjwatson> I think they're already there (just DIST=feisty)
[10:27] <cjwatson> but we'll check
[10:27] <mdz> Mithrandir: perhaps a new page linked from there, for opening a new release
[10:27] <cjwatson> hmm, no, perhaps not
[10:27] <cjwatson> I should probably write that; I know the guts of it
[10:27] <mdz> or on the page itself, I'm not fussed so long as they're not forgotten at the end of the  previous release
[10:27] <mdz> cjwatson: please do
[10:28] <mdz> thanks Mithrandir
[10:28] <Mithrandir> ok, I'll do the skeleton, Colin did most of the meat of it this time around so he should fill it in.
[10:28] <mdz> seb128: next
[10:28] <seb128> Done:
[10:28] <seb128>  * merges with Debian
[10:28] <seb128>  * GNOME updates
[10:28] <seb128>  * DesktopTeam talk for Ubuntu OpenWeek
[10:28] <seb128>  * catching up with mails
[10:28] <seb128>  * a bunch of edgy-proposed and edgy-updates updates
[10:28] <seb128>  * bug triage, bug triage, bug triage
[10:28] <seb128> .
[10:28] <seb128> To Do:
[10:28] <seb128>  * keep merges with Debian
[10:28] <seb128>  * bug triage, bug triage, bug triage, bug triage, you got the idea by now :p
[10:28] <seb128>  * GNOME 2.17.3
[10:28] <seb128>  * get tracker uploaded
[10:28] <seb128>  * updated desktop team
[10:28] <seb128> .
[10:28] <seb128> Specs:
[10:28] <seb128>  * easy-codec-installation: approved, waiting on gstreamer upstream changes
[10:28] <seb128>  * tab-consistency: pending approval, not started
[10:28] <seb128>  * desktop-slab: review, that's a "small" spec, basically getting promotion for the gnome-main-menu package and maybe looking at a panel profiles switcher
[10:28] <seb128> "updated desktop team" = "update wiki for desktop team"
[10:28] <mdz> seb128: I'm not keeping up with so many SRUs
[10:29] <cjwatson> I'm trying to do them about weekly, so tomorrow is the next round
[10:29] <seb128> mdz: you only have to approve them
[10:29] <seb128> think how much work it takes me filling them :p
[10:29] <mdz> seb128: I need to read and understand them first :-)
[10:29] <ogra> only ...
[10:29] <seb128> mdz: most of mine are fairly easy patches though ;)
[10:29] <mdz> seb128: we should only be doing these for critical issues, since they create work for others
[10:30] <mdz> I would like to do them for trivial fixes as well, but in reality it may not be worth it
[10:30] <seb128> right, I've adjusted for that
[10:30] <cjwatson> seb's have been pretty good in that regard from what I've seen
[10:30] <seb128> we got some not so cool bugs to edgy though due to the short cycle and the flood of bugs we didn't manage very well before edgy
[10:30] <cjwatson> they've all been "oh god, we released with that?" to one extent or another
[10:30] <mdz> it looks like it from the ones I've read, but as I said, I'm behind
[10:31] <mdz> cjwatson: I'd like for you to take primary responsibility for those for now; perhaps you and pitti can discuss sharing it
[10:31] <seb128> I should probably not have done the "libgnomeprintui has 2 strings not translatable", I noticed today, it's not worth the work
[10:31] <cjwatson> mdz: ok
[10:31] <mdz> it's not realistic for me at present
[10:31] <seb128> but that was in the pipe before I really think about it
[10:31] <cjwatson> I would like people to put more effort into writing descriptions of bug impacts
[10:31] <cjwatson> (for SRUs)
[10:32] <cjwatson> I've had several where that wasn't really there and I had to go back and distill one
[10:32] <mdz> does that need more emphasis in the documentation?
[10:32] <seb128> cjwatson: what sort of description?
[10:32] <mdz> it was explicitly part of the process
[10:32] <cjwatson> seb128: how the bug affects users. see the wiki page
[10:32] <mdz> to describe the impact of the bug on users, justifying the update
[10:32] <mdz> "this bug causes babies to be eaten"
[10:32] <dholbach> or 250 duplicates in gnome bugzilla (and counting)
[10:33] <mdz> right
[10:33] <seb128> cjwatson: I've read the wiki page, I'm not sure if you want "what the bug is doing" or "how many people it's annoying"
[10:33] <cjwatson> maybe just send out another reminder or something - I'll see what irritates me tomorrow
[10:33] <seb128> dholbach: I actually did some of those
[10:33] <seb128> "upstream has over 100 dups and asked us to push the crash fix"
[10:33] <cjwatson> seb128: I'd prefer its effect on end users; the latter doesn't hurt but the former is what we need to justify ourselves in the event that something goes wrong
[10:33] <mdz> seb128: both; "this bug causes foo to crash for many users"
[10:33] <dholbach> seb128: I know
[10:33] <cjwatson> "we chose to do this because ..."
[10:33] <seb128> cjwatson, mdz: ok, noted
[10:33] <mdz> it's not only for the benefit of the SRU team but to remind you to think about whether the work of an update is justified before you go further
[10:34] <mdz> seb128: we need to take a decision regarding beagle/tracker
[10:34] <mdz> seb128: what is upstream doing?
[10:34] <seb128> mdz: nothing
[10:34] <mdz> neither is going to be part of gnome?
[10:34] <seb128> beagle has not been proposed
[10:35] <seb128> and tracker will not be accepted since it has not being deployed by any distro yet and they are not sure about it neither
[10:35] <seb128> no, GNOME is pretty conservative
[10:35] <mdz> seb128: have CCed you on followup re: gstreamer
[10:36] <sfllaw> Can we update the SRU policy to get people to put this stuff in the Description?
[10:36] <seb128> ok
[10:36] <sfllaw> Reading long strings of comments is amusing, but inefficient.
[10:36] <mdz> sfllaw: that's fine with me
[10:36] <sfllaw> Especially for you.
[10:36] <cjwatson> sfllaw: please go ahead
[10:36] <seb128> mdz: why do we need to decide now for beagle or tracker, feature freeze is not good?
[10:37] <seb128> did you read my reply to your mail?
[10:37] <mdz> seb128: do you expect things to become clearer before then?
[10:37] <mdz> seb128: I did, but haven't replied yet
[10:37] <seb128> yes
[10:37] <cjwatson> sfllaw: that also makes it easier for users of stable releases to look up the bug and figure out why we changed it, which is a significant part of the point of the process too
[10:37] <mdz> it sounded indecisive :-)
[10:37] <seb128> I'm in contact with tracker upstream
[10:37] <seb128> and I think we will get tracker uploaded next week
[10:37] <seb128> I can't speak for tracker before getting user feedback on it
[10:37] <seb128> it looks a better choice on the paper
[10:37] <mdz> seb128: is it possible to use both in parallel?
[10:37] <seb128> C, smaller, extra features, good community
[10:38] <seb128> no
[10:38] <mdz> jdub said there was some discussion on desktop-devel-list
[10:38] <seb128> tracker has been proposed for GNOME 2.18
[10:38] <seb128> it's not likely to be accepted though
[10:38] <seb128> and beagle has not been proposed
[10:38] <mdz> ok, well the first step is to get them both in so that they can be tested, then send an announcement to -devel-announce to ask for testing and start a discussion about which works better for users
[10:39] <seb128> yeah that was my plan
[10:39] <mdz> will you do that?
[10:39] <mdz> ok ,thanks
[10:39] <seb128> yep, I'm on it
[10:39] <seb128> np
[10:39] <mdz> no word from doko?
[10:39] <mdz> (he was next)
[10:39] <mvo> I have tried to call him today without success
[10:39] <mvo> got the mailbox only on his mobile
[10:39] <mdz> mvo: will you try him tomorrow also?  I hope he is OK
[10:39] <mvo> mdz: yes
[10:40] <mdz> keep me updated
[10:40] <ogra> he joined for a short minute in #canonical on tuesday
[10:40] <dholbach> maybe I should do my morning run to his place tomorrow and bang on his door
[10:40] <mvo> ogra: I talked to him at the start of the weel
[10:40] <ogra> ah, right
[10:40] <mvo> week even
[10:40] <mdz> sfllaw: you're next then
[10:41] <sfllaw> Done:
[10:41] <sfllaw>  * Taught two classes for UbuntuOpenWeek
[10:41] <sfllaw>  * Verified many StableReleaseUpdates
[10:41] <sfllaw>  * Bug triage
[10:41] <sfllaw>  * Decided on two interns for the Montreal office
[10:41] <sfllaw>  * scalable-installation-testing spec is drafted
[10:41] <sfllaw> To do:
[10:41] <sfllaw>  * Interview more interns on Friday
[10:41] <sfllaw>  * Start getting thin clients for interns
[10:41] <sfllaw>  * Write documentation on Wiki about Ubuntu QA and TestPlans/TestCases.
[10:41] <sfllaw> Blocked:
[10:41] <sfllaw>  * synaptic SRU is waiting in the edgy-proposed NEW queue
[10:41] <sfllaw> Specs:
[10:41] <sfllaw>  * bug-reporting-tool (Approved)
[10:41] <sfllaw>  * scalable-installation-testing (Discussion)
[10:41] <sfllaw>   * We should probably implement some form of scalable-installation-testing, even if it isn't sufficiently general.  The Testing/Current wiki page must die.
[10:43] <mdz> sfllaw: was the decision positive or negative on the interns?
[10:43] <mdz> sfllaw: I talked with pitti this morning about scalable-installation-testing; I think it may need some revision
[10:44] <sfllaw> sfllaw: Ah.  Interviewed five interns.  Picked two.
[10:44] <sfllaw> mdz: ^^^
[10:44] <mdz> what I've proposed is a small but fundamental change
[10:44] <sfllaw> mdz: Can this change be done for the Feisty timeline?
[10:44] <mdz> it's essential that we be able to collect feedback from people outside of the formal testing framework
[10:44] <sfllaw> mdz: If so, I agree.
[10:45] <mdz> yes, I think it's not significantly more complex
[10:45] <sfllaw> mdz: OK.  Either talk to me or pitti after the meeting and we'll update the spec until you're happy.
[10:46] <mdz> ok
[10:46] <mdz> sfllaw: when do the interns start?
[10:46] <sfllaw> January.
[10:46] <seb128> what are they going to do? ;)
[10:46] <sfllaw> We have desks for them, but we'll need stations.
[10:46] <mdz> bugs!
[10:46] <seb128> new hands to help on bug triage? ;)
[10:46] <sfllaw> seb128: Yes.
[10:46] <seb128> WAOUH
[10:46] <ogra> YAY
[10:46] <dholbach> YEEEHAA
[10:46] <sfllaw> And verification if they can handle it.
[10:46] <mdz> their start should be a good opportunity to review and improve the bug documentation as well
[10:47] <sfllaw> Yeah.
[10:47] <mdz> so that it can be used to train future interns
[10:47] <sfllaw> We should be able to source free people from Jan-Apr.
[10:47] <mdz> sfllaw: great work
[10:47] <sfllaw> Some free people Sep-Dec.
[10:47] <sfllaw> But summer months will be lean.
[10:47] <sfllaw> Kids expect pay from summer jobs.
[10:47] <mdz> if someone has proven themselves in an internship, we can consider them for a summer arrangement
[10:47] <sfllaw> That'd be cool.
[10:47] <seb128> sfllaw: that's why we have SoC :p
[10:48] <ogra> hahaha
[10:48] <sfllaw> Let's talk about this in two or three months.
[10:48] <mdz> sfllaw: thanks
[10:48] <mdz> ogra: next
[10:48] <ogra> * last-week:
[10:48] <ogra>  - travelling the wild wild east
[10:48] <ogra>  - merging
[10:48] <ogra>  - prepared new ltsp feisty branch
[10:48] <ogra>  - prepared --workstation plugin for ltsp-fat-clients (running fine, only network auth bits are missing)
[10:48] <ogra>  - seed merge
[10:48] <ogra>  - OpenWeek edubuntu Q&A session
[10:48] <ogra> * next week:
[10:48] <ogra>  - herd1
[10:48] <ogra>  - merge debian ltsp patch backlog
[10:48] <ogra>  - finishing the parts of ltsp-fat-clients that work without network auth
[10:48] <ogra>  - start working on edubuntu-network-auth-server/client
[10:48] <ogra> 
[10:48] <ogra> * approved specs:
[10:48] <ogra>  - ltsp-fat-clients - nearly implemented (a full ubuntu runs awesome in 196M/500Mhz, 32M nbd swap ;) )
[10:48] <ogra>  - edubuntu-network-auth-server - not started
[10:48] <ogra>  - edubuntu-network-auth-client - not started
[10:48] <ogra>  - edgy-plusone-thinclient-sound - started
[10:48] <ogra>  - ltsp-management-gui - started
[10:48] <ogra>  - student-control-panel-upgrade - not started
[10:48] <ogra>  - edubuntu-on-two-cds - not started
[10:49] <ogra>  - ltsp-persistent-home - started by sbalneav (actually implemented during MTV, just not merged yet)
[10:49] <mdz> ogra: your specs don't seem to be targeted for feisty yet
[10:49] <mdz> ogra: have you reviewed them with RichEd?
[10:49] <ogra> they are proposed for it ... anything else i need to do ?
[10:50] <ogra> yes
[10:50] <ajmitch> ogra: I'll try & find some time to talk to you tomorrow or so about e-n-a-c/s
[10:50] <mdz> ogra: and all 8 are feisty targets?  are their priorities set appropriately?
[10:50] <ogra> ajmitch, try to do it at a time where we can get moquist to attend (US time)
[10:50] <ajmitch> right, tomorrow is weekend for me, I'll track him down
[10:50] <ogra> mdz, the edubuntu-auth ones would be more appropriate with high status
[10:50] <finalbeta> mdz they are visible to me on the Feisty spec page.
[10:51] <mdz> ogra: they are not proposed for it; if you are in -core-dev they should go straight through anyway
[10:51] <ogra> weird
[10:51] <mdz> ah, there they are
[10:51] <mdz> ogra: you must have done them since the meeting started :-P
[10:51] <finalbeta> He did.
[10:51] <ogra> yeah
[10:51] <dholbach> just in time
[10:52] <mdz> ok, thanks ogra
[10:52] <mdz> anyone heard from Keybuk?
[10:52] <dholbach> hi pitti
[10:53] <mdz> iwj: next
[10:53] <iwj> Approved:
[10:53] <iwj>  gnome-app-install-codecs: Started looking at g-a-i database generation.
[10:53] <iwj>  udev-lvm, consistent-login-screen: Implementation not yet started.
[10:53] <iwj>  package-dependency-field-breaks: Beta Available.  Should be ready for full deployment now; I will rerun my search-for-candidates.
[10:53] <iwj>  automated-testing-deployment: parts of implementation deferred from edgy.  Work will continue.
[10:53] <pitti> hello
[10:53] <iwj> Approved but problem:
[10:53] <iwj>  usb-adsl-modems: lacking an Assignee.  It would be nice to assign this to someone who understands the subject.
[10:53] <iwj> Drafting:
[10:53] <iwj>  dbus-restarts: This needs discussion.  Ideally we could discuss it at the next UDS or perhaps at a sprint, to write a clear and correct spec for feisty+1.  Upstream disapprove but we all agree they're wrong.
[10:53] <iwj> New - needed (and still need) discussion, but not scheduled at uds-mtv:
[10:53] <iwj>  winmodem-support: IMO should be deferred to feisty+1.
[10:53] <iwj>  edgy-fontconfig: There is no spec.  IMO should be deferred (or rejected).
[10:54] <mdz> iwj: we don't have an expert on hand for usb-adsl-modems; you'll need to learn about it
[10:54] <mdz> iwj: hardware and service can be provided if needed
[10:54] <iwj> I'll see what I can do.
[10:54] <mdz> iwj: let me know what you need and how much it costs
[10:55] <mdz> iwj: same goes for winmodem-support.  there is no formal spec, but there is a wealth of information from the community
[10:55] <iwj> OK, I'll look into both of those.  I don't want to make any promises ...
[10:55] <mdz> it deserves a proper review to identify which bits can be automated, which are licensing issues, etc.
[10:55] <cjwatson> for winmodem-support I think we need to be careful to select what we do
[10:55] <cjwatson> it's in danger of being a bit of a rabbit-hole
[10:55] <iwj> It did look quite open ended.
[10:56] <cjwatson> I agree it should be reviewed, just would like the time to be spent wisely
[10:56] <mdz> we should make sure we're doing the best we can with the available software to enable the hardware
[10:56] <pitti> meeting is over already?
[10:56] <iwj> I'll see what I can do to improve the situation.  (I already have a winmodem in my laptop in fact ...)
[10:56] <cjwatson> pitti: no
[10:56] <mdz> it isn't more than a day's work to review what's out there, and that would be time well spent
[10:56] <mdz> pitti: no
[10:56] <iwj> review> OK, I'll do that.
[10:57] <pitti> ah, just my terrible initial lag
[10:57] <mdz> iwj: ok, let me know what you find out
[10:57] <mdz> iwj: edgy-fontconfig was a discussion placeholder for UDS; should be marked informational and not targeted
[10:57] <iwj> OK.
[10:58] <mdz> dbus-restarts sounds like something which needs discussion, especially with some upstreams
[10:58] <mdz> not urgent for feisty
[10:58] <iwj> mdz: I don't think discussing it with upstreams will get us anywhere.
[10:58] <iwj> not urgent for feisty> Indeed.
[10:58] <iwj> We just need to fix it.
[10:58] <mdz> it's a lot of work and a large delta for us to take on; we shouldn't do it without some buy-in elsewhere
[10:58] <iwj> So I'd like to actually talk to people about what would be a good thing to do so we have a clear plan.
[10:59] <iwj> Without that it's hard to get buy-in.
[10:59] <iwj> I think Debian would take sane changes at least.
[10:59] <cjwatson> iwj: not dbus upstream themselves, perhaps, but upstreams of packages using dbus
[10:59] <iwj> cjwatson: Mmmm.
[10:59] <mdz> ->ubuntu-devel then, CCing relevant upstreams for the packages we'd be modifying
[10:59] <iwj> marked informational> Err, how do I do that in LP ?
[10:59] <mdz> it's under 'title and summary' or such
[11:00] <iwj> Aha.
[11:00] <mdz> iwj: breaks isn't targeted for feisty; if it's ready to go then target it
[11:00] <iwj> mdz: Right.
[11:00] <mdz> automated-testing-deployment needs targeting also; I think it's still set to edgy
[11:00] <iwj> Willdo.
[11:01] <mdz> ok, thanks iwj
[11:01] <mdz> cjwatson: next
[11:01] <cjwatson> Specifications:
[11:01] <cjwatson>   setup-console-under-usplash: Approved, beta available; apparently broke though (#73955) so need to investigate.
[11:01] <cjwatson>   intel-mac-support, ubiquity-advanced-partitioner, ubiquity-automation, ubiquity-driver-updates, ubiquity-release-notes: Approved.
[11:01] <cjwatson>   feisty-ubiquity: Approved. Part bite-size tasks for new developers, and part stuff that I need to do; who should be the assignee?
[11:01] <cjwatson>   ubiquity-slideshow: Approved. Part artwork and part me; who should be the assignee?
[11:01] <cjwatson>   increase-hwdb-participation: Approved. Assignee probably shouldn't be me.
[11:01] <cjwatson>   ubiquity-more-user-config: Still drafting, but mostly there on the condition that it satisfies the requirements, which I'm not sure about; sent to sabdfl for review. Need to talk to sysadmin too.
[11:01] <cjwatson>   simplify-oem-installation: Still in requirements gathering. There are some fairly obvious things we can do listed at the bottom of the brain-dump, but I don't know how far we can take this without better commercial input.
[11:01] <cjwatson>   ubiquity-oem: Not written up, and probably not happening.
[11:01] <cjwatson> Other:
[11:01] <cjwatson>   Installer all merged, and more or less ready for Herd 1 bar the bug-fixing.
[11:01] <cjwatson>   Who volunteered to be distro->LP-meeting delegate? I thought it was sfllaw, but I don't remember for sure, and the LP meeting is not obviously conveniently timed for him.
[11:01] <cjwatson>   <SteveA> I like the idea of having a delegate from the distro team
[11:01] <cjwatson>   <SteveA> one way to manage this with simon is to have simon talk with me or kiko on wednesday
[11:01] <cjwatson>   <SteveA> and feed points / topics of concern to us for the meeting
[11:01] <cjwatson> (the bit at the end was because I chipped into the LP meeting with something random and SteveA /msged me to thank me for contributing)
[11:02] <mdz> cjwatson: feisty-ubiquity: primary assignee should be you, but please farm out the bite-size bits.  maybe talk to dholbach or jono if no one in the core team is interested
[11:02] <cjwatson> ok
[11:03] <sfllaw> As for the LP delegate, it should probably be me.  As I basically spend all day using LP.
[11:03] <cjwatson> I know sivang expressed interest
[11:03] <cjwatson> sfllaw: time sucks for you, doesn't it? it's always noon UTC
[11:03] <sfllaw> sivang: Ping?
[11:03] <mdz> cjwatson: ubiquity-slideshow is yours but low priority; would be great to find someone else to take it and be able to bump it up, but your others are more important
[11:03] <cjwatson> sfllaw: I mean in ubiquity work
[11:03] <sfllaw> Yeah, that time is terrible.
[11:04] <cjwatson> mdz: understood; shortly I'll be putting together some kind of guide for installer development and mailing it out in the hope of generating some interest
[11:04] <cjwatson> sfllaw: but, as SteveA says, if you want to feed info to him and kiko on Wednesday, and read the logs/summaries afterwards, that would work fine
[11:04] <sfllaw> When are their meetings?  Thursday?
[11:05] <cjwatson> yes
[11:05] <mdz> let's take that discussion to distro-team@
[11:05] <sfllaw> I might do that.
[11:05] <mdz> distro-team@ and launchpad@, even
[11:05] <mdz> it might be that that person doesn't need to attend the meetings
[11:05] <cjwatson> I mentioned increase-hwdb-participation at last week's meeting too. Mithrandir expressed some interest then, but I think he thought it was in casper, which it doesn't really seem to be
[11:06] <mdz> any volunteers for increase-hwdb-participation?
[11:07] <cjwatson> (it's basically a desktop notification plus a few other bits)
[11:07] <ogra> yeah, its only a notification bubble and a change of the .desktop file status ...
[11:07] <pitti> doesn't sound too scary, I can take a look at it, but I don't know the spec yet
[11:07] <mdz> pitti: please have a look and let me know
[11:07] <cjwatson> I think it's fairly trivial, if you have time.
[11:08] <mdz> cjwatson: does that cover all the non-limbo specs of yours?
[11:08] <pitti> the time is the problem here, but that applies to everyone
[11:08] <ogra> it mentions apport as well ;)
[11:08] <pitti> heh
[11:08] <cjwatson> mdz: I believe they're all covered above. ubiquity-more-user-config, simplify-oem-installation, ubiquity-oem are the only ones not targeted.
[11:09] <mdz> *oem* I think has to be targeted for feisty+1 after proper requirements definition
[11:09] <sladen> if increase-hwdb-participation is really that minor, I'll consider it
[11:09] <mdz> more-user-config is blocked on IS?
[11:09] <lifeless> I need to finish the hwdb client changes to - pitti can we coordinate please
[11:09] <lifeless> s/to/too
[11:09] <cjwatson> ubiquity-slideshow> I expect that my side of it will be pretty small, FWIW. I agree it's less important than the others
[11:09] <pitti> lifeless: of course
[11:09] <cjwatson> mdz: yes
[11:09] <cjwatson> will send mail about that
[11:10] <mdz> ok, should probably be in RT
[11:10] <mdz> cjwatson: thanks
[11:10] <Burgwork> cjwatson: email marketing team asking for content
[11:10] <lifeless> pitti: great. I have have it working, just needs to be made pretty.
[11:10] <mdz> pitti: next
[11:10] <pitti> Done:
[11:10] <pitti>  * lots of package merges
[11:10] <pitti>  * spec reviews, discussions, and approvals; my own (assignee/drafter) feisty specs are all approved; I approved most of the specs I'm approver for, except:
[11:10] <pitti>   - simple-x-mode-selection: still in drafting, pinged rodarvus yesterday
[11:10] <pitti>   - scalable-installation-testing: was approved this morning with our original design; mdz had a different idea which got discussed shortly this morning, but which requires more intrusive changes in ubiquity, the db design, and other components, so I set it back to discussion for now
[11:10] <cjwatson> Burgwork: art team too I think
[11:10] <cjwatson> Burgwork: but ok
[11:10] <pitti>   - ltsp-local-apps: utterly complex and a quick discussion with cjwatson revealed that this needs much more thought (this one is not marked for feisty)
[11:10] <pitti>  * Note: bug-reporting-tool is currently assigned to sfllaw, but since it's mainly apport work, I should probably the assignee.
[11:10] <pitti>  * cleanup-audio-jumble: tested pulseaudio and attempted to create the mentioned (in spec) patch to not hog the audio device; this failed due to the principal design of pulse; upstream works on a cleaner and more generic solution, but this will not be ready for feisty; since I do not want to break compatibility with commercial OSS apps and the multiuser case, I did not continue working on this for now
[11:10] <pitti>  * zero-configuration-networking:
[11:10] <pitti>   - did the required changes to base-files, avahi-autoipd, avahi, libnss-mdns, and ifupdown, so that the stuff works OOTB now when using dhclient
[11:10] <pitti>   - filed bug for zeroconf package removal
[11:10] <pitti>   - still missing: fix network-manager to not clobber the avahi-autoipd address (so that .local name resolution works with n-m), teach network-admin about the new ifupdown method (not that urgent, though, most people will not use the new /e/n/interfaces method and just rely on n-m or dhclient), and seed avahi-autoipd to ubuntu-desktop (after herd freeze)
[11:10] <pitti>  * apport-improvements: got apport bits in for intercepting Python crashes, discussed a battle plan for Mono with slomo
[11:10] <pitti>  * two OpenWeek talks
[11:10] <pitti>  * started discussion and coding for automated package tests (mainly to improve QA of securi
[11:10] <pitti> ty updates so far, but this topic seems to grow and grow)
[11:11] <pitti> Todo:
[11:11] <pitti>  * finish zero-configuration-networking implementation
[11:11] <mdz> pitti,sfllaw: happy for pitti to take bug-reporting-tool if you two agree
[11:11] <pitti>  * fix feisty's and edgy's gnome-system-tools authentication problem
[11:11] <pitti>  * change dapper's and edgy's ~/.xsession-errors rotation handling to new plan
[11:11] <pitti>  * dive into bug triage
[11:11] <mdz> consider cleanup-audio-jumble deferred for now
[11:11] <sfllaw> pitti: Agreed.
[11:11] <pitti> sfllaw: if you want to hack on apport, go ahead, of course; but I guess I'll give a hand with that anyway
[11:11] <cjwatson> pitti: ltsp-local-apps> do you mean the ssh Cipher=none thing?
[11:11] <pitti> mdz: audio> I agree
[11:11] <sfllaw> pitti: When I get not busy.  :)
[11:11] <sfllaw> In the meantime, you can hack on it.
[11:11] <pitti> cjwatson: yes, that still seems to be an issue, I didn't hear an update so far?
[11:11] <ogra> cjwatson,  ssh Cipher=none isnt in any spec
[11:12] <cjwatson> pitti: haven't looked at it yet, I didn't realise it was blocking this spec rather than just random would-be-nice-if
[11:12] <ogra> thats a whishlist thing from upstream ltsp ... to not having to switch to xdmcp
[11:12] <mdz> pitti: Mithrandir is going to be working on n-m, so coordinate with him re: zero-conf-net
[11:12] <pitti> cjwatson: well, it's not the only thing; the spec lacks verbosity in general
[11:12] <ogra> if it shouws up in that spec it needs to be taken out, it has nothing to do with local-apps
[11:12] <pitti> mdz: yes, we already had a quick talk
[11:12] <cjwatson> pitti: ok; if it's something else then I'm afraid I've entirely forgotten our discussion ;)
[11:13] <cjwatson> I need to look at scalable-installation-testing
[11:13] <mdz> pitti: automated package tests -> iwj's stuff or something different?
[11:13] <pitti> cjwatson: I mainly needed that
[11:13] <pitti> mdz: eventually it would merge with that, yes
[11:13] <pitti> mdz: keescook and I had a discussion on the allhands how to improve our security update QA process
[11:14] <mdz> lifeless: ^^
[11:14] <pitti> mdz: and we agreed to testing security updates at least by two people, and writing automated tests where appropriate
[11:14] <pitti> sfllaw, lifeless, keescook, iwj, and I had a small discussion recently
[11:14] <pitti> since it turned out that these tests should be applicable to QA team as well, and might be integrated into autopkgtest
[11:15] <lifeless> mdz: yup
[11:15] <iwj> There's a reasonably good fit; most of my stuff is infrastructure and there are quite a few actual tests there that it would be nice to glue in.
[11:15] <mdz> ok
[11:16] <mdz> tkamppeter: are you here?
[11:16] <tkamppeter> Yes.
[11:16] <mdz> tkamppeter: ok, you're next then
[11:16] <mdz> pitti: thanks
[11:16] <pitti> I didn't yet take a look at autopkgtest, I just wanted some initial bits to play with, but I definitively want to make it fit there
[11:16] <tkamppeter> ACCEPTED FEATURES (for Feisty):
[11:16] <tkamppeter> https://blueprints.launchpad.net/people/till-kamppeter/+specs
[11:16] <tkamppeter> UDS outcomes:
[11:16] <tkamppeter> - "Easy configuration of printer sharing"
[11:16] <tkamppeter> - "Replace gnome-cups-manager by printerdrake"
[11:16] <tkamppeter> - "Automatic download of printer drivers through the internet"
[11:16] <tkamppeter> - "Automatic hotplug printer configuration"
[11:17] <tkamppeter> - Answered to bug report
[11:17] <tkamppeter> - Re-submitted EDgy update for foo2zjs bug 65618
[11:17] <Ubugtu> Malone bug 65618 in foo2zjs "Firmware upload to LJ 1000/1005/1008/1020 broken (fix to be proposed as Edgy update)" [Medium,Fix committed]  http://launchpad.net/bugs/65618
[11:17] <mdz> pitti's concerns with printerdriverautodownload were addressed?
[11:17] <pitti> mdz: yes
[11:17] <pitti> (from my POV, that is)
[11:18] <tkamppeter> Also discussed how to save space with the PPDs bug 39847
[11:18] <Ubugtu> Malone bug 39847 in foomatic-db "Getting (more) manufacturer-supplied PostScript PPDs onto the Ubuntu desktop CDs" [Undecided,Confirmed]  http://launchpad.net/bugs/39847
[11:18] <mdz> tkamppeter: 65618 -> cjwatson
[11:19] <mdz> automatic hotplug printer configuration is not for feisty, correct?
[11:19] <cjwatson> the SRU team is subscribed to 65618, so I'll catch up on it tomorrow
[11:19] <cjwatson> sorry for the delay
[11:19] <tkamppeter> Yes, this I wanted to say, too.
[11:19] <mdz> ok
[11:19] <mdz> thanks tkamppeter
[11:20] <mdz> did I miss anyone, or is there any other business to discuss (briefly)?
[11:20] <zul> just me..
[11:20] <fabbione> distro sprint?
[11:20] <mdz> zul: go ahead
[11:20] <pitti> ^ any dates yet?
[11:20] <zul> this week
[11:20] <zul> ---------
[11:20] <zul> * xen kernel update
[11:20] <zul> * kernel security for breezy.
[11:20] <zul> * bug triaging
[11:20] <zul> next week
[11:20] <fabbione> we are about 7 weeks and no dates have been confirmed
[11:20] <zul> ---------
[11:20] <mdz> fabbione: please mail distro-team@
[11:20] <zul> * big xen/kernel push
[11:20] <ogra> ^ any places yet ?
[11:20] <zul> * bug triaging
[11:20] <zul> * merges
[11:20] <zul> Specs
[11:20] <zul> ----
[11:20] <mdz> fabbione: we do need to finalize that soon
[11:20] <zul> * xen-fesity spec apprvoed (approved), started
[11:21] <mdz> zul: are you comfortable with how xen-feisty turned out?
[11:22] <zul> yes i am
[11:22] <ajmitch> mdz: what do do with any other specs that may be stuck at needs review or pending approval?
[11:22] <mdz> zul: will xen support paravirt-ops?
[11:22] <mdz> ajmitch: review -> review team, approval -> technical-board
[11:22] <zul> it looks like it from what i been seeing ive asked the upstream developers
[11:23] <mdz> that would make it a candidate for main
[11:23] <zul> thats what im hoping for
[11:23] <mdz> we'll see what happens
[11:23] <ajmitch> mdz: right, thanks, wasn't sure if it was too late
[11:23] <mdz> we're well over time
[11:23] <zul> thanks everyone
[11:24] <mdz> yes, thanks all
[11:24] <pitti> zul, BenC, kylem: any remaining trouble for the kernel security update? any ETA?
[11:24] <mdz> until next week
[11:24] <cjwatson> not really for this meeting I suppose, but do we know the status of new TB appointments?
[11:24] <mdz> adjourned
[11:24] <seb128> thank you mdz
[11:24] <dholbach> thanks
[11:24] <mdz> cjwatson: that's all sabdfl as far as I know; will raise it with him the next time we speak
[11:24] <kylem> pitti, i've been building them today to make sure i don't brown paper bag my first piece of work...
[11:24] <dholbach> and a TB meeting? people have been asking me for that already
[11:24] <kylem> pitti, but afaict, it seems good.
[11:24] <zul> pitti: i think im almost ready i just have one patch to ask about
[11:25] <zul> but ill do that tonight when i get home (still at work)
[11:25] <zul> later
[11:26] <pitti> zul, kylem: thank you
[11:26] <pitti> thanks all!
[11:26] <kylem> cheers
[11:30] <sfllaw> Thanks.
[12:15] <tonyyarusso> @schedule toronto
[12:15] <Ubugtu> Schedule for America/Toronto: Current meeting: Ubuntu Development Team | 06 Dec 15:00: Edubuntu | 07 Dec 03:00: Ubuntu Development Team | 13 Dec 07:00: Edubuntu | 14 Dec 11:00: Ubuntu Development Team | 20 Dec 15:00: Edubuntu