[02:23] <i12> hey, so Im looking for a good channel for general ubuntu help
[02:23] <i12> am i in the right spot? any recommendations welcome
[02:24] <Pendulum> i12: try #ubuntu
[02:27] <i12> thanks!
[14:54] <kirkland> o/
[14:58] <Daviey> \o
[14:59] <ttx> o/
[14:59] <zul> morning
[15:00] <ttx> smoser: ?
[15:01] <ttx> let's get started
[15:01] <ttx> #startmeeting
[15:01] <MootBot> Meeting started at 09:01. The chair is ttx.
[15:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:01] <ttx> Welcome everyone to the Ubuntu Server team weekly meeting
[15:01] <ttx> Agenda is at: https://wiki.ubuntu.com/ServerTeam/Meeting
[15:01] <ttx> I'm the scribe today
[15:02] <ttx> [TOPIC] Review ACTION points from previous meeting
[15:02] <MootBot> New Topic:  Review ACTION points from previous meeting
[15:02] <ttx> * Mathiaz to fix a broken script with bug reporting link above.
[15:02] <ttx> * ttx to follow up with ivoks/RoaKSoax on cluster stack state
[15:02] <ttx> * mathiaz to propose removal of dovecot-postfix on MLs
[15:02] <RoAkSoAx>  o/
[15:02] <smoser> 0/
[15:03] <ttx> mathiaz is absent, I think both of his actions are still on the TODO list
[15:03] <ttx> About cluster stack, I followed up but did not follow-up on the followup yet
[15:04] <ttx> so we'll have these actions for next week again
[15:04] <ttx> RoAkSoAx: I'll bother you after the meeting if that's alright with you
[15:04] <RoAkSoAx> ttx, sure
[15:04] <ttx> [TOPIC] Lucid release status
[15:04] <MootBot> New Topic:  Lucid release status
[15:04] <zul> yay!
[15:04] <ttx> FinalFreeze will hit us tomorrow
[15:05] <ttx> rather sooner than later, if Beta2Freeze is of any indication
[15:05] <ttx> Once we are frozen all uploads will need ReleaseTeam approval
[15:05] <ttx> so get everything you can in by EOD :)
[15:05] <ttx> RC bugs status:
[15:06] <ttx> bug 556343 (zul)
[15:06] <zul> mvo said he hasnt looked at it yet
[15:06] <ttx> quick one-liner on each bug status please :)
[15:06] <ttx> bug 532733 (kirkland)
[15:06] <smoser> (is there an RC bug list ttx ?)
[15:06] <ttx> ah hm
[15:07] <ttx> See https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[15:07] <kirkland> ttx: forwarded upstream;  i haven't made much progress on that one, and i'm not able to reproduce it easily (outside of the odd apt-get circumstance)
[15:07] <mvo> zul: I run the test now again and once its finshed I upload the syslog file
[15:07] <ttx> There is a bug in malone search preventing a dynamic list here
[15:07] <ttx> bug 513273 (kirkland)
[15:07] <ttx> I think this one is done ?
[15:08] <ttx> bug 533029 (zul)
[15:08] <zul> slangasek said he has looked at it but hasnt commented about it
[15:08] <zul> ill bug him again today
[15:08] <ttx> We also need some AA attention on bug 562261, FFe approved for this one already
[15:08] <kirkland> ttx: i uploaded a fix, but it was rejected by slangasek; i've asked the (many) bug commenters to help do some testing on it against bochs
[15:09] <ttx> kirkland: ok, thanks
[15:09] <ttx> On the remaining work items in the specs at http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04.html
[15:09] <ttx> the two in eucalyptus merging and packaging should be done today
[15:10] <ttx> the remaining ones are mostly on track, need mathiaz for an update
[15:10] <ttx> Finally, you can find a list of Lucid targets of opportunity at https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[15:11] <ttx> Mostly a server-oriented view of https://bugs.launchpad.net/ubuntu/lucid/+bugs
[15:11] <ttx> Once your higher-prio items are done feel free to pick up bugs in there ;)
[15:11] <ttx> I think we are mostly in good shape
[15:12] <ttx> we need more testing, so don't hesitate to blog/call for that
[15:12] <ttx> Questions ?
[15:13] <ttx> ok, moving on then
[15:13] <ttx> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[15:13] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[15:13] <ttx> hggdh: hi
[15:13] <hggdh> no Q from me, tested with kirkland yesaterday the problem I opened
[15:13] <hggdh> ttx: hi
[15:14] <hggdh> I am still unable to run KVM locally (my laptop), kernel oops
[15:14] <ttx> Would be good to come to the bottom of those, if only to get some trusted test results
[15:14] <hggdh> yes
[15:14] <ttx> I think we are good with the ISO testcases we came up for beta2
[15:14] <hggdh> sounds and smells like routing
[15:15] <kirkland> ttx: i would like jjohansen and the kernel team to take a serious look at hggdh's kvm issue
[15:15] <hggdh> I am starting to work on the EC2 tests, jump-starting from smoser's work
[15:15] <kirkland> ttx: i think that's likely a portent of things to fcome
[15:15] <ttx> hggdh: if you can't find where it comes from with kirkland, I'll try to get access and have a look, just in case something jumps out
[15:15] <jjohansen> hggdh: try the latest Beta2 kernel
[15:15] <smoser> hggdh, awesome. please ping me if you need any help reading that embarrassing collection of slop
[15:15] <smoser> and please, don't judge.
[15:15] <hggdh> jjohansen: I am running Lucid up-to-date. You mean you want me to downgrade?
[15:16] <kirkland> ttx: hggdh's testing issue is one of networking/routing
[15:16] <jjohansen> hggdh: no, I want you to try the kernel that hasn't been released yet :)
[15:16] <kirkland> ttx: i think mathiaz's knowledge of the lab's networking will solve that bug, thus i re-assigned it to him for now
[15:16] <ttx> kirkland: yes, I asked for more data o nthe bug, but it might be simpler for me to connect and look ;)
[15:16] <jjohansen> I can provide you a dpkg or you can wait a couple days
[15:16] <kirkland> ttx: mathias gets to Austin late tonight; we'll look at it together tomorrow
[15:16] <hggdh> jjohansen: if it is the -21, I just installed it, and will reboot after the meeting
[15:17] <jjohansen> hggdh: -21.31
[15:17]  * ttx thanks the QA team for their help in debunking bug 546743 on the HW enablement labs (fader, thanks :)
[15:17] <ttx> anything else for QA ?
[15:17] <hggdh> jjohansen: matches
[15:18] <jjohansen> yeah
[15:18] <hggdh> smoser: who am I to judge anybody? I will not :-)
[15:19] <ttx> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[15:19] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[15:19] <ttx> hggdh: thanks
[15:19] <ttx> jjohansen: hi !
[15:19] <jjohansen> hi
[15:19] <ttx> jjohansen: how is it going, before I hit you with my issues ?
[15:20] <jjohansen> heh, well not bad considering
[15:20] <ttx> ok, so the biggest issue on server affecting release right now is... bug 546743
[15:21] <ttx> Most IBM/Lenovo servers ship with that ES1000
[15:21] <ttx> and I suspect many others
[15:21] <jjohansen> right, that is basically SRU atm
[15:21] <ttx> if that's SRU, I'd make a plea for nomodeset by default
[15:22] <ttx> cjwatson: around ?
[15:22] <ttx> makes us look very bad to not having a login prompt after an install on a lot of servers
[15:22] <jjohansen> ttx: well basically every thing kernel is SRU, or at least have to make it past the release team
[15:23] <ttx> well, I'll let them choose between the two evils
[15:23] <jjohansen> the kernel froze monday
[15:23] <cjwatson> ttx: yes, I saw - I'm OK with that I think
[15:23] <ttx> jjohansen: if it gets a finalfreeze exception, is it something we know how to fix ?
[15:24] <ttx> cjwatson: the exception or nomodeset ?
[15:24] <cjwatson> nomodeset
[15:24] <cjwatson> if that's the approach recommended and approved by the kernel team
[15:25] <ttx> team: would you mind losing the higher screen resolution on console VTs ?
[15:25] <kirkland> ttx: i very much would
[15:25] <jjohansen> ttx: hrmm nomodeset can be done, I will raise with kernel team
[15:26] <ttx> kirkland: explain
[15:26] <kirkland> ttx: the new 128x35 lines (or whatever) is brilliant
[15:26] <kirkland> ttx: if that's what you're talking about
[15:26] <ttx> I'd argue that our target audience doesn't care about consoles
[15:26] <kirkland> ttx: are you talking about losing that, to downgrade back to 80x25 ?
[15:26]  * Daviey adds a blueprint to flesh out "target audience"
[15:27] <ttx> Daviey: tss :)
[15:27] <kirkland> ttx: what's the method for a user wanting higher res to bump it back up?
[15:27] <ttx> kirkland: remove nomodeset from kernel cmdline
[15:27] <ttx> jjohansen: or would it just affect the ES1000 case ?
[15:27] <kirkland> ttx: if that's a one-liner, that an admin can run once postinstall, or preseed it, I suppose that would suffice
[15:28] <smoser> all impression I have seen of our target audience, first and foremost is fully functional console.  80x25 is acceptable.
[15:28] <jjohansen> ttx: it depends how it is done
[15:28] <zul> smoser: ditto
[15:28] <ttx> jjohansen: I'll let you brainstorm what the options are
[15:29] <jjohansen> easiest would be either system wide or just set that ati card to nomodeset
[15:29] <ttx> jjohansen: then we'll discuss that with release team
[15:29] <ttx> jjohansen: does it sound good ?
[15:30] <jjohansen> ttx: yes, I'll poke some more and see if there are other options at the moment, and get back to you in a bit but I think that is it
[15:31] <jjohansen> the fix for Bug #530361 was snuck in
[15:31] <ttx> yes, that's good, thanks !
[15:31] <kirkland> ttx: smoser: okay, i suppose a functional 80x25 would be acceptable;  i strongly suggest that we have well published documentation on how to get it back
[15:31] <jjohansen> that happened as we had problems with some other critical issues and broke freeze for those issues
[15:31] <ttx> kirkland: ideally that would just affect the faulty card
[15:32] <kirkland> ttx: ah, okay
[15:32] <ttx> kirkland: but if there is any risk of losing console, I perfer to have 80x25 everywhere than 128x35 only for 80% of servers
[15:32] <ttx> and nothing on the remaining 20%
[15:32] <kirkland> ttx: agreed
[15:32] <ttx> jjohansen: cool :)
[15:33] <ttx> anything else for kernel ?
[15:33] <ttx> hopefully the latest kernel will fix hggdh's kvm
[15:33] <zul> thanks for everything jjohansen you are the best
[15:34]  * hggdh hops so
[15:34]  * jjohansen wonders what evil thing zul is going to ask for now :)
[15:34] <zul> hah..
[15:34] <ttx> let's find out
[15:34] <ttx> [TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (zul)
[15:34] <MootBot> New Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (zul)
[15:34] <zul> hi
[15:34] <zul> so there is nothing nominated for dapper, hardy, intrepid
[15:35] <zul> for jaunty and karmic there is one nominated
[15:35] <ttx> the one for jaunty is wishlist -> no
[15:35] <zul> 156636
[15:35] <zul> agreed
[15:35] <zul> and its the same for karmic
[15:35] <ttx> same for karmic
[15:35] <ttx> the fixed buglist is still broken
[15:36] <ttx> heh, looks like this will be a short review
[15:36] <zul> anything in that list
[15:36] <zul> thats broken ;)
[15:36] <ttx> yes :)
[15:37] <zul> nothing in that list from me
[15:37] <zul> ttx: ?
[15:37] <ttx> you can look at http://qa.ubuntu.com/reports/bug-fixing/lucid-fixes-report.html for server bugs recently fixed
[15:37] <ttx> I have no suggestion though
[15:38] <Daviey> it's all eucalyptus, or not relevant IMO.
[15:38] <zul> so next is proposed list
[15:38] <zul> there is 3 of them which need to be reviewed
[15:39] <ttx> http://tinyurl.com/y4xza95
[15:39] <MootBot> LINK received:  http://tinyurl.com/y4xza95
[15:39] <ttx> ubuntu-server recently fixed bugs ^
[15:39] <zul> so when someone has some downtime can they review them
[15:40] <Daviey> zul: https://code.edge.launchpad.net/~ubuntu-server/+activereviews ?
[15:40] <zul> yep
[15:40] <ttx> zul:  ack
[15:40] <zul> anything else?
[15:40] <ttx> zul: do you plan to discuss SRU handling at UDS ?
[15:41] <zul> ttx: yeah i mentioned it to ttx
[15:41] <ttx> or hallway-discuss it ?
[15:41] <zul> not ttx jos
[15:41] <ttx> ok
[15:41] <ttx> looks like our process could still use some improvement
[15:41] <ttx> and since this is LTS time again...
[15:41] <Daviey> +1
[15:41] <zul> i think its part of the qa workflow that needs to be updated again
[15:42] <ttx> zul: ok, anything else ?
[15:42] <zul> and considering the .1 release is going to be happening within the maverick timeframe
[15:42] <zul> nope
[15:42]  * ttx pastes actions to pass to next week for reference
[15:42] <ttx> [ACTION] Mathiaz to fix the "server fixed bugs" broken script
[15:42] <MootBot> ACTION received:  Mathiaz to fix the "server fixed bugs" broken script
[15:43] <ttx> [ACTION] ttx to follow up with ivoks/RoaKSoax on cluster stack state
[15:43] <MootBot> ACTION received:  ttx to follow up with ivoks/RoaKSoax on cluster stack state
[15:43] <ttx> [ACTION] mathiaz to propose removal of dovecot-postfix on MLs
[15:43] <MootBot> ACTION received:  mathiaz to propose removal of dovecot-postfix on MLs
[15:43] <ttx> [TOPIC] Open Discussion
[15:43] <MootBot> New Topic:  Open Discussion
[15:43] <zul> yes...
[15:43] <ttx> anything / anyone ?
[15:43] <Daviey> Any news on blueprints?
[15:43] <ttx> any bug you'd like to bring to general attention ?
[15:44] <ttx> Daviey: we haven't reviewed our scratchlist yet... it's even missing input from some team members
[15:44] <zul> i been working on getting mysql-5.0 out of universe and it should be ready to be removed from universe today
[15:44] <Daviey> ttx: ok thanks
[15:44] <bilalakhtar> zul: But why? Will it go to main?
[15:44] <ttx> Daviey: I think in all cases we'll have a public wikipage by the end of week, reviewed or not
[15:45] <zul> bilalakhtar: because mysql-5.1 is in main
[15:45] <Daviey> ttx: superb,
[15:45] <bilalakhtar> zul: ok
[15:45] <ttx> zul: good
[15:46] <ttx> does everyone sleep well ?
[15:46] <kirkland> meh
[15:46] <zul> no
[15:46] <ttx> ok, I'm not the only one then
[15:47] <smoser> apparently my leg twitches when i sleep
[15:47] <smoser> this is all hearsay
[15:47] <zul> my wife sleep walks and screams in her sleep
[15:47] <zul> and talks in her sleep
[15:47] <zul> and something else about lucid
[15:49] <zul> anyways :)
[15:51] <ttx> ok
[15:51] <ttx> we should have a session on how to make the meeting more lively :)
[15:51] <ttx> [TOPIC] Announce next meeting date and time
[15:51] <MootBot> New Topic:  Announce next meeting date and time
[15:51] <ttx> Next week, same time, same place
[15:51] <ttx> #endmeeting
[15:51] <Daviey> great \o/
[15:51] <MootBot> Meeting finished at 09:51.
[15:52] <ttx> and now let's write up, yay
[15:52] <Daviey> heh
[15:59] <mvo> hi
[15:59] <ev> hello
[16:00] <tremolux> hey!
[16:00] <mvo> can I paste my lighting report and be 5min out? mini conflicts with the schedule?
[16:00] <ev> surely
[16:00] <mvo> did: lots of update-manager/upgrade fixing work, software-center work (UI responsiveness)
[16:00] <mvo> todo: bugfixing in update-manager/upgrades, software-center
[16:00]  * mvo will be back as quick as possible
[16:01] <ev> lool, barry, cjwatson, doko__, slangasek, james_w: ping
[16:01] <james_w> hi
[16:01] <doko__> hi
[16:01] <barry> hi
[16:01] <cjwatson> hi
[16:01] <ev> #startmeeting
[16:02] <MootBot> Meeting started at 10:01. The chair is ev.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <ev> [LINK] Meeting Agenda https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0414
[16:02] <MootBot> LINK received:  Meeting Agenda https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0414
[16:02] <ev> [TOPIC] Lightning Round
[16:02] <MootBot> New Topic:  Lightning Round
[16:02] <ev> order: tremolux, lool, ev, barry, cjwatson, doko, slangasek, james_w
[16:02] <tremolux> k
[16:02] <tremolux> Lots of software-center bug fixing and testing.
[16:02] <tremolux> Channel updating bugs mentioned last week are fixed.
[16:02] <tremolux> Holiday next week!
[16:02] <tremolux> (done)
[16:03] <ev> I don't think lool is going to make it, so...
[16:04] <ev> some installer fixes, meetings with sabdfl and the design team to discuss the latest drafts of the installer design, hopefully fixed an apt bug, and lots of work on ubiquity unit testing
[16:04] <ev> (done)
[16:04] <barry> pep 3147; bug 519541 (abiword hang); spent a little time working on cjwatson's script, but i think we'll need update lazr.restfulclient to 0.9.13 in lucid. (done)
[16:04] <cjwatson> done: buried in customer bugs first half of this week; fixed a few more partitioner and boot loader bugs, almost entirely happy with those for lucid now
[16:04] <cjwatson> todo: sync up d-i component translations for lucid; concentrate completely on https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone=21439, inc. remaining Kubuntu installation issues
[16:04] <cjwatson> --
[16:04] <doko> done:
[16:04] <doko>  * openjdk-6: testing, preparation of the icedtea6-1.8 release, debug plugin failures, make it
[16:04] <doko> robust with our wrongly configured firefox, reduce test failures in the jtreg testsuite.
[16:04] <doko>  * robustify ca-certificates-java updates with unsupported certificates
[16:04] <doko>  * sun-java6 updates for older releases
[16:04] <doko>  * gdc-4.3 updates to fix regressions
[16:05] <doko>  * started archive rebuild
[16:05] <doko>  * toolchain preparation for maverick, updated gcc-plugindir patch, now in trunk, new gcc-snapshot/gcc-4.5 packages
[16:05] <doko>  * ant1.8, bash, libtunepimp uploads
[16:05] <doko>  * java bug triage
[16:05] <doko> todo:
[16:05] <doko>  * eglibc update
[16:05] <doko>  * file bug reports for test rebuild failures
[16:05] <doko>  * get some sleep
[16:05] <doko> --
[16:06]  * mvo is back
[16:06]  * james_w guesses slangasek isn't up yet
[16:06] <ev> indeed, james_w, you're up
[16:06] <james_w> launchpad, bzr-builddeb and sponsoring, with some lucid bug fixing etc. thrown in. More of the same to come. (done)
[16:06] <ev> [TOPIC] Outstanding actions from last meeting
[16:06] <MootBot> New Topic:  Outstanding actions from last meeting
[16:06] <cjwatson> oh, I forgot one thing, I'm working on a dpkg update with backports for some important bugs, though it's taking some coordination with upstream
[16:07] <ev> I didn't see any in the report, but speak up if you have some
[16:08] <barry> ev: i had an old action item for cjwatson, which i spent a little time on.  blocked on an old version of lazr.restfulclient in lucid (which i'll work w/the lp team to get updated)
[16:08] <ev> barry: cool, thanks
[16:08] <ev> okay, moving on
[16:08] <ev> [TOPIC] Outstanding feature freeze exceptions
[16:08] <MootBot> New Topic:  Outstanding feature freeze exceptions
[16:09] <ev> I imagine none
[16:09] <barry> ev: i was trying to get c-j 2.0 into lucid, but that's not going to happen
[16:09] <ev> :(
[16:09] <doko> c-j?
[16:09] <barry> computer janitor.  i couldn't convince pitti ;)
[16:09] <ev> barry: are you going to shove it in -proposed?
[16:10] <cjwatson> or a PPA
[16:10] <barry> it's in my ppa now.  i want to undo the translation changes i made for the ffe and then upload a new version.  i do want to propose it for m
[16:10] <cjwatson> I think for m, Just Do It
[16:11] <cjwatson> (oh yeah, we can say maverick now)
[16:11] <ev> but it could reasonably go in 10.04.1, no?
[16:11] <barry> cjwatson: cool.  i don't think i know the exact process for that, but i'll figure it out :)
[16:11] <barry> ev: well, i'd love that, but i don't know if that would satisfy the concerns pitti had
[16:12] <ev> fair enough
[16:12] <barry> i made a plea for others to test it on ubuntu-devel but got zero responses :(
[16:12] <ev> barry: ubuntuforums is usually good for that kind of thing
[16:13] <barry> ev: oh cool.  i'll give that a try then.  i think with some others testing it, it could have gone in 10.04 final
[16:13] <barry> but oh well
[16:13] <ev> [TOPIC] Milestoned bugs
[16:13] <MootBot> New Topic:  Milestoned bugs
[16:13] <ev> [LINK] https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs?field.milestone:list=21447
[16:13] <MootBot> LINK received:  https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs?field.milestone:list=21447
[16:14] <ev> is that entirely the wrong URL?
[16:14] <cjwatson> isn't that the beta-2 milestone?
[16:14] <ev> yeah, whoops
[16:14] <ev> https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs ?
[16:14] <cjwatson> =21439
[16:14] <ev> ah
[16:15] <cjwatson> the URL was in my lightning round update, actually
[16:15] <cjwatson> https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone=21439
[16:15] <ev> thanks
[16:15] <ev> usb-creator> I'll sort that before release, doesn't depend on the archive
[16:16] <cjwatson> I may unmilestone the partman-auto recipe tweak bug - I'm not sure whether that's a good idea to change at this point
[16:16] <cjwatson> nested progress bars I'd like to fix, but if I can't, not the end of the world
[16:16] <mvo> a new software-center with fixes will go in tonight
[16:16] <ev> ubiquity> the kde frontend makes me sad, but we have most of the problems there sorted
[16:17] <cjwatson> the BIOS hang due to the partitioner has a workaround which can be documented
[16:17] <mvo> plus the apt fix that ev helpfully did \o/
[16:17] <ev> yay
[16:17] <cjwatson> the ATA passthrough stuff in hdparm has a known workaround, will apply it soon after another skim through the upstream discussion to see if it's been resolved properly yet
[16:18] <cjwatson> omap installation are Not Our Problem, that's mobile team
[16:18] <cjwatson> *installations
[16:18] <cjwatson> anyone want to fix dmraid?
[16:18] <cjwatson> oh, that has a branch, guess I'll look at that
[16:18] <cjwatson> plymouth I'm assuming Keybuk/slangasek will handle
[16:19] <ev> I don't know what the rest of your bug mail is like, but it's eerily quiet here.  Or at least significantly quieter than Beta 1.
[16:19] <cjwatson> bug 470550 I guess we should have another look at but it doesn't seem appropriate to change for lucid at this point
[16:19] <ev> I guess that's a good thing
[16:19] <cjwatson> it's quieter than beta-1, though not flatlining by any means
[16:20] <cjwatson> bug 557220 has I think been fixed in debian-cd, will check and close
[16:20] <Riddell> yes it has assuming I got the colours right
[16:20] <cjwatson> I'm concerned about the remaining kernel tasks, don't know what the timeline is looking like for those
[16:22] <ev> https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/549738 is worrying
[16:23] <ev> right, anything else on the bug front?
[16:23] <Riddell> bug 556555
[16:23] <Riddell> that's worrying me, I don't know how to start debugging it
[16:23] <Riddell> and it disappeared when I did
[16:23] <cjwatson> find out how I can reproduce it, and I'll debug it
[16:23] <cjwatson> I think when I tried I couldn't
[16:24] <Riddell> plain OEM install does it for me, on virtualbox or real
[16:24] <ev> I'll give it a try after the meeting
[16:25] <mvo> I'm a bit worried about the threading deadlocks in computer-janitor
[16:25] <mvo> the fix is to move to the dbus branch, but that got rejected because it was too late (unfortunately)
[16:25] <mvo> for me it reliable deadlocks but I haven't found a fix (and other stuff that is also important)
[16:26] <barry> mvo: i didn't get much response on my query to remove c-j-gtk from default install
[16:26] <mvo> I guess that is good
[16:26] <mvo> I mean, not much opposition
[16:26] <barry> mvo: my only concern is that the gtk version could still be useful to people.  e.g. for me it never deadlocked (but i haven't used v1 in a while)
[16:27] <barry> mvo: i guess i am on the fence about it
[16:27] <mvo> hm, ok
[16:27] <mvo> if I'm the only one seeing it its probably a way too big hammer
[16:28] <barry> mvo: i think i will just triage bugs as they come in and point them to my ppa
[16:28]  * mvo nods
[16:28] <mvo> thanks
[16:29] <ev> anything else?
[16:30] <ev> [TOPIC] Good News
[16:30] <MootBot> New Topic:  Good News
[16:30] <barry> looks like pep 3147 will make it into py3k trunk by friday.  symlink farms days are numbered
[16:31] <doko> ... the ABI patch pending ...
[16:31] <mvo> \o/
[16:31] <barry> doko: well, yes, i will be working on that next :)
[16:31] <mvo> the upgrade tester has finally! moved to the datacenter and is in full automatic mode
[16:32] <mvo> there is also a initial version of the pkg-install-tester running (but that is probably a bit buggy still)
[16:32] <barry> mvo: cool! are the results available online or via email?
[16:32] <mvo> http://people.canonical.com/~mvo/automatic-upgrade-testing/current/
[16:32] <MootBot> LINK received:  http://people.canonical.com/~mvo/automatic-upgrade-testing/current/
[16:32] <ev> We finally have a basic test harness for ubiquity (to land in trunk after lucid), with a much more involved set of tests to land as soon as I can figure out EC2 desktop CD testing or I unbreak `fakechroot fakeroot debootstrap`.
[16:33] <mvo> the pkg install tester is http://people.canonical.com/~mvo/automatic-upgrade-testing/auto-install-tester/
[16:34] <ev> [TOPIC] Chair for next meeting
[16:34] <MootBot> New Topic:  Chair for next meeting
[16:34] <mvo> creating additional profiles is simple, if someone has good ideas
[16:35] <barry> mvo: are you looking at the failure details to see if they are fixable?
[16:36] <mvo> barry: yes, lts-ubuntu is pending, d-h-l-ubuntu is a OOo upgrade bug (I attached a fix there)
[16:36] <mvo> barry: I need to make the "Bugs" column filed automatically for known failures
[16:36] <mvo> that is still missing
[16:36] <barry> mvo: cool
[16:36] <mvo> mythbuntu, lts-mythbuntu are profile failures, that will be fixed in the next cron run
[16:36] <mvo> so it looks reasonable well
[16:37] <barry> nice!
[16:37] <ev> Any volunteers to run the next meeting?
[16:38] <barry> ev: i'll do it
[16:38] <ev> barry: awesome, thanks
[16:38] <ev> [TOPIC] AOB?
[16:38] <MootBot> New Topic:  AOB?
[16:39] <ev> going once, going twice...
[16:39] <ev> #endmeeting
[16:39] <MootBot> Meeting finished at 10:39.
[16:39] <ev> thanks everyone!
[16:39] <barry> thanks!
[16:39] <mvo> thanks
[16:39] <tremolux> have a good day everyone
[16:40] <ev> you too
[16:42] <james_w> thanks
[17:59] <hggdh> ~o~
[17:59]  * marjo waves
[17:59]  * bladernr can't find the coffee pot
[18:00] <pedro_> hey hey!
[18:00] <davmor2> bladernr: little to your left
[18:00] <bdmurray> hi
[18:00]  * fader_ waves.
[18:01] <marjo> #startmeeting QA Team
[18:01] <MootBot> Meeting started at 12:01. The chair is marjo.
[18:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:01] <marjo> [TOPIC] Agenda
[18:01] <MootBot> New Topic:  Agenda
[18:01] <marjo> # SRU testing -- sbeattie (Steve Beattie)
[18:01] <marjo> # Bug Day status -- pvillavi
[18:01] <marjo> hi folks
[18:02] <marjo> [TOPIC] SRU testing -- sbeattie
[18:02] <MootBot> New Topic:  SRU testing -- sbeattie
[18:02] <sbeattie> SRU activity was very light this past week.
[18:02] <sbeattie> SRU Activity report for the past week (since 2010-04-07):
[18:02] <sbeattie> * karmic: 1 new packages in -proposed (postgresql-8.4)
[18:02] <sbeattie>       and 3 packages pushed to -updates (eucalyptus, ifupdown, obexd)
[18:02] <sbeattie> * jaunty: 1 new packages in -proposed (postgresql-8.3)
[18:02] <sbeattie> * intrepid: no SRU activity
[18:02] <sbeattie> * hardy: 1 new packages in -proposed (postgresql-8.3)
[18:02] <sbeattie>      and 2 packages pushed to -updates (exim4, pyclutter)
[18:02] <sbeattie> * dapper: 1 new package in -proposed (postgresql-8.1)
[18:02] <sbeattie> Thanks to Leonel Nunez, Robert Hau, Matteo Collina, and Andres Rodriguez for testing SRUs this week.
[18:03] <sbeattie> I suspect the 2nd beta drop may have had something to do with that.
[18:04] <sbeattie> As always, people who are interested in helping to test SRUs can come join us in #ubuntu-testing.
[18:04] <sbeattie> (That's all I've got for SRUs this week)
[18:05] <marjo> any questions for sbeattie?
[18:05] <marjo> thx steve
[18:05] <marjo> [TOPIC] Bug Day status - pvillavi
[18:05] <MootBot> New Topic:  Bug Day status - pvillavi
[18:06] <pedro_> On Thursday 08 we had a bug day based on Rhythmbox, the community contribution was awesome!
[18:06] <pedro_> ~73 bugs were triaged that day, Thanks a lot to our hug days heroes: kamusin, vish, sbarjola, charlie-tca and hernejj for their extraordinary work!
[18:06] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20100408
[18:07] <pedro_> There's a graph at the bottom of the page, which looks great ;-)
[18:07] <pedro_> ok so Tomorrow!
[18:08] <pedro_> We're going to have a bug day for Software Center organized by Draycen DeCator (aka ddecator)
[18:08] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20100415
[18:08] <pedro_> Some folks already started to work on it and there's still plenty of bugs to be triaged so if you have some time and want to learn a bit more about bug triage join us, we'll be glad to help you to start
[18:08] <pedro_> and big Thanks to ddecator for helping us with the organization!
[18:09] <pedro_> that's all from here marjo
[18:09] <hggdh> sorry, kernel oops. Did I miss anything
[18:09] <marjo> folks: any questions for pedro_ ?
[18:09] <marjo> hggdh: no worries
[18:10] <hggdh> thanks
[18:10] <bdmurray> a kernel oops is worrying ;-)
[18:10] <pedro_> heh
[18:10] <marjo> hggdh: please report a bug on your kernel oops
[18:10] <bdmurray> heh
[18:10] <hggdh> marjo: already reported, even twice, now testing a new kernel (-21.31)
[18:10] <marjo> [TOPIC] Lucid Beta 2 Test Report
[18:10] <MootBot> New Topic:  Lucid Beta 2 Test Report
[18:11] <marjo> Lucid Beta 2 Test Report
[18:11] <marjo> 9th April 2010
[18:11] <marjo> = Summary =
[18:11] <marjo> == Test Coverage ==
[18:11] <marjo> Image Coverage: 100%
[18:11] <marjo> Mandatory Testcase Coverage: 207/207 = 100.00
[18:11] <marjo> Optional Testcase Coverage: 9/18 = 50.00
[18:11] <marjo> [18:11] <marjo> 25 Test Failures
[18:11] <marjo> Failure Rate 25/216 = 11.57
[18:11] <marjo> == Serious bugs found in ISO testing status ==
[18:11] <marjo> http://people.canonical.com/~marjomercado/isotestingbugs.html
[18:11] <MootBot> LINK received:  http://people.canonical.com/~marjomercado/isotestingbugs.html
[18:11] <marjo> i want to thank everyone who helped us achieve 100% image & mandatory test coverage
[18:12] <marjo> we really appreciate your work on ensuring a quality release
[18:12] <sbeattie> What were the optionals that we missed?
[18:13] <marjo> sbeattie: don't have that handy
[18:14] <marjo> sorry
[18:14] <sbeattie> marjo: okay. just trying to figure out how we can get to 100% there as well.
[18:14] <marjo> sbeattie: i'll work with ara to make sure we get coverage on all tests; that's always the goal
[18:15] <marjo> even if they're optional
[18:15] <marjo> [TOPIC] Lucid Bug Report
[18:15] <MootBot> New Topic:  Lucid Bug Report
[18:15] <marjo> 15 days left and 276 bug tasks to fix. [1]
[18:15] <marjo> Lucid Final Freeze - 15 April 2010 (1 day away)
[18:15] <marjo> Barring no new work, we need to fix 18 bug tasks a day now.
[18:15] <marjo> The average resolution rate/day during the past month has been 18/day.
[18:15] <marjo> The focus of bug fixing should be on the following tasks:
[18:15] <marjo> 1. The 5 Critical bug tasks. [3]
[18:15] <marjo> 519541
[18:15] <marjo> Abiword 2.8.1 freezes with document
[18:15] <marjo> lost when help is clicked or F1 is
[18:15] <marjo> pressed
[18:15] <marjo> https://bugs.launchpad.net/ubuntu/lucid/+source/abiword/+bug/519541
[18:15] <marjo> 511988
[18:15] <marjo> isdnutils: various licensing issues
[18:15] <marjo> https://bugs.launchpad.net/ubuntu/lucid/+source/isdnutils/+bug/511988
[18:15] <marjo> 532374
[18:15] <marjo> Lenovo Thinkpads with Core i5 and i7
[18:15] <marjo> suspend/resume (with kernel oops)
[18:15] <marjo> once then fail horribly on next
[18:15] <marjo> suspend
[18:16] <marjo> https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/532374
[18:16] <marjo> 548513
[18:16] <marjo> Some firewire & usb disks not
[18:16] <marjo> working under 10.04
[18:16] <marjo> https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/548513
[18:16] <marjo> 542208
[18:16] <marjo> Please blacklist i830 from Kernel
[18:16] <marjo> mode-setting
[18:16] <marjo> https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/542208
[18:16] <marjo> 2. The 24 bug tasks that might cause a regression in Lucid. [4]
[18:16] <marjo> 3. The 99 High bug tasks. [5]
[18:17] <marjo> that's it from me
[18:17] <bdmurray> I think having the bug number appear 2 times in the report is rather redundant
[18:17] <marjo> bdmurray: ack
[18:18] <marjo> bdmurray: you mean just list the link, right?
[18:19] <bdmurray> marjo: yeah or use LP: # in the hopes that everyone uses mutt and terminator ;-)
[18:19] <marjo> bdmurray: can't rely on that hope
[18:19] <marjo> folks: any new topics for today?
[18:20] <marjo> any other questions?
[18:21] <sbeattie> thanks ara and jamesw for pushing a new version of ubuntu-qa-tools into lucid.
[18:21] <marjo> sbeattie: thx for doing the fixes
[18:22] <bdmurray> I'd still like to remove the dependency on python-launchpad-bugs in it
[18:22] <marjo> bdmurray: is there already a bug report on that enhancement?
[18:23] <bdmurray> marjo: its not an enhancement per se but about getting python-launchpad-bugs out of the archive
[18:23] <marjo> bdmurray: ack
[18:23] <bdmurray> and that is bug 552953
[18:23] <marjo> ah
[18:24] <marjo> thx
[18:24] <sbeattie> is there anything in the package that actually uses it still?
[18:24] <bdmurray> yes, but we could just remove it as nobody uses it afaik
[18:25] <bdmurray> I think only check-needs-packaging uses it
[18:26] <bdmurray> oh right and lpl_common.py uses http_connection just a wee bit
[18:27] <bdmurray> just for firefox cookie processing
[18:27] <bdmurray> I don't think I'm in a position to do anything about that though
[18:28] <marjo> sbeattie, bdmurray: any action item appropriate for this topic?
[18:30] <sbeattie> bdmurray: I'll help look at it after this meeting.
[18:30] <bdmurray> sbeattie: cool, thanks
[18:30] <marjo> sbeattie: thx
[18:30] <bdmurray> rewrite or remove check-needs-packaging from ubuntu-qa-tools
[18:31] <bdmurray> rewrite cookie processing in lpl_common.py not to use python-launchpad-bugs
[18:31] <bdmurray> remove the dependecny on py-lp-b in ubuntu-qa-tools
[18:31] <bdmurray> upload new ubuntu-qa-tools
[18:32] <marjo_> sorry folks; i seem to be having network problems today
[18:33] <marjo_> if there are no other topics, i propose we adjourn the meeting
[18:33] <marjo_> going once
[18:33] <marjo_> going twice
[18:33] <marjo_> meeting adjourned
[18:34] <marjo_> thx all!
[18:34] <fader_> Thanks all
[18:34] <pedro_> thanks
[18:34] <marjo_> #endmeeting
[18:34] <schwuk> thanks
[18:35] <marjo_> #endmeeting
[18:37] <marjo> #endmeeting
[18:37] <MootBot> Meeting finished at 12:37.
[19:33]  * Lns waves to everyone
[19:33]  * bencrisford waves back to Lns
[19:34] <bencrisford> weve got half an hour yet havent we?
[19:38] <Lns> Did I miss anything? Seems like everyone is pretty quiet.. hehe
[19:40] <bencrisford> Lns: meeting aint for another 20 minutes
[19:40] <bencrisford> i think anyway :/
[19:40] <bencrisford> :P
[19:40] <Lns> oh really?? I thought it was 40min. ago..keeps changing on me hehe
[19:40] <Lns> stupid dst ;)
[19:40] <Lns> the world just needs to switch to gmt!
[19:40] <bencrisford> i know!
[19:41] <bencrisford> the clocks went forward for us a few weeks ago
[19:41] <bencrisford> so im used to it now
[19:42] <Lns> hehe
[20:00] <highvoltage> Good evening
[20:00] <Lns> hi highvoltage
[20:00] <alkisg> Hi people
[20:01] <grantbow> hello
[20:01] <highvoltage> Agenda is on https://wiki.ubuntu.com/Edubuntu/Meetings/Agenda as usual
[20:02] <bencrisford> hey
[20:02] <mhall119> hey, I made one on time
[20:02] <mhall119> o/
[20:02] <Lns> mhall119: ;)
[20:02] <highvoltage> heh, yay!
[20:03] <stgraber> just finishing something, will be there in 5 min
[20:03] <bencrisford> mhall119: :)
[20:03] <highvoltage> ok, I'll give a technical summary from my side so long
[20:04] <highvoltage>  * We got mhall119's Qimo packages in Lucid!
[20:04] <mhall119> yay!
[20:05] <highvoltage> I didn't actually think we'd made it since feature freeze and beta2 freeze, etc is over, but the archive admins were quite great and mhall119 did a good job of staying in touch with them
[20:05] <bencrisford> :D
[20:05]  * bencrisford is happy for mhall119
[20:06] <highvoltage> we also have the ltsp installer and netbook installer working from the livecd now
[20:06] <highvoltage> it was our biggest goal for lucid, it won't work on todays build though, but it should be fine from tomorrow's build onwards
[20:07] <highvoltage> If you guys could download and test it that would be AWESOME
[20:07]  * mhall119 is happy for me too
[20:07] <highvoltage> we have a small window where we can still make fixes if necessary and I'd like us to take advantage of that before it's finally released
[20:07] <mhall119> and happy for Qimo
[20:08] <highvoltage> alkisg: I'd especially like some of your feedback on the live stuff, I know you've done some things there so your input is especially valuable :)
[20:09] <alkisg> highvoltage: when's the deadline for fixes? I'm a little pressed this period, but I'll try to test it...
[20:09] <alkisg> Tomorrow? FF?
[20:10] <highvoltage> alkisg: yes, basically
[20:10] <alkisg> Ugh, sorry I'll be on a trip for the next 4 days so I'm not sure if I'll be able to test :(
[20:10] <highvoltage> alkisg: although I'm quite confident that we'll be able to do another artwork upload since we're waiting on Canonical for the new Logo
[20:10] <alkisg> Nice
[20:10] <highvoltage> alkisg: and by chance, our livecd stuff is in the artwork package
[20:11] <alkisg> Heh :)
[20:11] <highvoltage> alkisg: so if we need to fix something for the ltsp installer stuff then we can still get it in
[20:11] <alkisg> Gotcha
[20:11] <bencrisford> tommorrow is the deadline for fixes?  whoa is that ubuntu-wide?
[20:11]  * stgraber waves
[20:11] <mhall119> lucid-wide
[20:11] <highvoltage> alkisg: but I don't want to put unnecessary pressure on you, if you can't, then no problem :)
[20:11] <bencrisford> argh, its gonna be a long night :'(
[20:12] <highvoltage> bencrisford: yep, the archive freezes up and only very serious changes are allowd
[20:12] <highvoltage> *allowed
[20:12] <bencrisford> that qcad bug isnt serious, but its bloody annoying
[20:12]  * alkisg starts downloading and will rsync tomorrow if he can find a net connection...
[20:12] <bencrisford> i hope i can sort it..
[20:12] <highvoltage> bencrisford: fixes will still go into -updates and -security and -backports as needed
[20:12] <bencrisford> my qcad one is about missing menu entries :/
[20:13] <bencrisford> but it isnt as simple as i thought
[20:13] <mhall119> highvoltage: are there going to be edubuntu planning sessions at UDS?
[20:13] <highvoltage> mhall119: for maverick, I anticipate there being many
[20:13] <mhall119> good, I'll try to join on IRC
[20:14] <highvoltage> we only had one or two sessions for Lucid, but that's because we already had a good idea of what we wanted to do for Lucid
[20:14] <mhall119> and you guys did a damn good job with it too
[20:14] <highvoltage> for maverick I have quite a long list of wishlist items, I guess it will require quite a bit of evaluation for feasability and deciding what we can realistically do for maverick
[20:15] <bencrisford> i dont know if ill be around on irc during the day on uds week
[20:15] <bencrisford> that sucks
[20:15] <highvoltage> there's also a lot of extending and fixing of the work already done in lucid
[20:15] <highvoltage> mhall119: thanks, that's really appreciated
[20:15] <highvoltage> for example, when you install Edubuntu in Lucid, you get two icons on your desktop that says "Install LTSP" and "Install Netbook Interface" after installation which allows you do those
[20:16] <highvoltage> the problem is that it doesn't use preseeds and you can't automate that quite yet, ideally we want that as a plugin in ubiquity with more options than we do now, and make it all pre-seedable
[20:18] <highvoltage> I think that the moment lucid is released, our website is running nicely etc, then we should start planning for maverick, so by the time we get to the uds sessions we know what we want to discuss
[20:18] <highvoltage> I might also have to participate remotely due to visa issues (canadian embassy has my passport atm and I'm not sure I'll have it back in time to apply for belgian visa)
[20:18] <highvoltage> Anything else technical though before we move on?
[20:19] <stgraber> nope
[20:19] <bencrisford> dont think so :)
[20:20] <highvoltage> I talked to Hedgemadge earlier about the website, the to-do items aren't all that much, she's going to put up some infrastructure (like the mail->forum gateway) up on her server so long until we have somewhere else to run it
[20:20] <highvoltage> (like the canonical server the site is running on atm)
[20:20] <highvoltage> besides that it's mostly logo/branding changes
[20:21] <highvoltage> so when we get the logos from canonical we can finalise our artwork package and also the website
[20:21] <stgraber> sounds good
[20:22] <highvoltage> bencrisford: can you tell us about the changes made in the advocacy group?
[20:22] <bencrisford> highvoltage: sure :)
[20:22] <highvoltage> (and the other things you've been doing the last weel :) )
[20:22] <mhall119> highvoltage: is the website's source in launchpad?
[20:23] <bencrisford> over the last week ive been doing some stuff to organise the advocacy team, because i think that its a really important thing to get sorted at the moment
[20:23] <highvoltage> mhall119: I believe so, I don't have a link handy but I think it is
[20:23] <bencrisford> because there's no sense working hard on edubuntu if we cant get users :/
[20:23] <bencrisford> or contributors for that matter
[20:24] <bencrisford> ive been trying to organise the team on launchpad
[20:24] <bencrisford> highvoltage and I decided it would be best to completely start afresh and de-activate all members
[20:24] <bencrisford> so i did, and sent a message explaining and inviting them to rejoin if interested (as suggested by highvoltage)
[20:24] <mhall119> I like the idea of having a team for contributors who are not ubuntu members
[20:25] <highvoltage> yes they also got a notification message with an explanation and an invite to re-apply
[20:25] <bencrisford> i also accepted the recent applicants and have tried to contact them
[20:25] <bencrisford> including grantbow and rockstar
[20:25] <bencrisford> who i have already spoken to
[20:25] <highvoltage> well, all the edubuntu teams (except for edubuntu-members and edubuntu-council) are open for people who are not ubuntu members
[20:25]  * grantbow waves
[20:25] <highvoltage> hi grantbow
[20:26] <stgraber> hey grantbow
[20:26] <bencrisford> also before i went to germany last week i set up a bzr branch on the team for sharing marketing materials etc
[20:26]  * mhall119 didn't know there are other edubuntu teams
[20:26] <bencrisford> mhall119: if anything there are too many
[20:26] <highvoltage> heh, indeed
[20:27] <highvoltage> at one stage, all the teams were basically maintained by 1 or 2 people, it didn't work out so well
[20:27] <bencrisford> once lucid is release id quite like to work with the team to create some marketing matrial
[20:27] <bencrisford> that can distributed by locos
[20:27] <bencrisford> highvoltage: i found another one still like that today
[20:27] <bencrisford> i think it was an official one
[20:28] <highvoltage> I like that we have a council now and also some specific people taking ownership of some of the specific groups (like bencrisford with the advocacy team, and Hedgemadge and dhillion-v10 with the webesite team)
[20:28] <highvoltage> bencrisford: ah yes the school support one?
[20:28] <bencrisford> highvoltage: sounds right
[20:28] <bencrisford> i might have pinged you about it
[20:28] <highvoltage> that was one that cbx33 started I think, we should probably look at it and decide whether it should be revived or disbanded
[20:29] <bencrisford> highvoltage: i found that alot of applicants to the advoc team were members of it
[20:29] <bencrisford> another thing i wanted to talk about is getting contributors
[20:29] <highvoltage> bencrisford: I think what sometimes happen is, someone wants to contribute to edubuntu so they just apply to all the teams meaning to contribute to most of them at some point
[20:30] <bencrisford> because looking at the applicants to the advoc team, alot of them were not members of any other teams, and didnt even have a public addres
[20:30] <bencrisford> so alot of people have just joined lp in order to help edubuntu
[20:30] <bencrisford> i think we need to focus on getting these people involved
[20:30] <bencrisford> because people internally in ubuntu are way to busy to do anything
[20:30] <bencrisford> highvoltage: i did see a bit of that as well
[20:31] <bencrisford> but i was checking out the applicants expecting to see a long list of teams
[20:31] <bencrisford> and i didnt see anything
[20:31] <highvoltage> bencrisford: when we have just a bit more regular contributors, maybe we should start a mentoring program for people who would want to contribute?
[20:32] <bencrisford> highvoltage: its a good idea yes, but we need alot of experienced regular contributors
[20:32] <highvoltage> mhall119 has been really patient and willing to learn packaging, I'm sure he'll do a great job of teaching someone else to do it if he wants to :)
[20:32] <mhall119> heh, once I figure it out anyway
[20:33] <mhall119> right now I can only make non-compiled, non-program packages
[20:33] <bencrisford> it would definately work on a small scale if we had enough mentors
[20:33] <bencrisford> mhall119: thats more than i can do :P
[20:33] <mhall119> but I'd be happy to mentor on some programming
[20:33] <highvoltage> bencrisford: I think if the ratio of new contributors to experienced ones are ok, then it shouldn't be too much of a problem doing mentoring, but yes I agree we probably wouldn't be able to cope with 10 new very green contributors who ware very eager to contribute at this stage
[20:33] <bencrisford> i can debdiff :P but only just
[20:34] <bencrisford> highvoltage: yeah
[20:34] <mhall119> bencrisford: I just learned how to do that yesterday ;)
[20:34] <bencrisford> mhall119: when i was around before, LaserJock really helped me with all that stuff :)
[20:34] <highvoltage> heh, I was jut about to ask where bencrisford was with that yesterday :)
[20:34] <bencrisford> i think my first bug was under his supervision
[20:35] <mhall119> yeah, he was a good guy
[20:35] <highvoltage> yeah LaserJock gave me a lot of good tips and advice before as well
[20:35] <highvoltage> (especially with all the Debian acronyms like ITP, BTS, etc)
[20:35] <bencrisford> i still follow the howtofix page on the wiki when i debdiff and stuff, but im getting more and more confident :)
[20:37] <highvoltage> bencrisford: you also added "Bzr Branch" to the agenda, I assume that's for the advocacy branch?
[20:37] <bencrisford> yeah
[20:37] <bencrisford> i did briefly mention it i think
[20:38] <bencrisford> at 20:26:18 (but thats BST) :/
[20:38] <highvoltage> oh yes, right
[20:40] <highvoltage> I guess that's it for the agenda then :)
[20:40] <highvoltage> anything else that should be added (I guess I should've asked that at the beginning ;))
[20:41] <highvoltage> bencrisford: I'm not sure if I perhaps cut you off a bit on the advocacy stuff, it there's something more you wanted to say about it please don't let me stop you
[20:41] <highvoltage> I think it's universally accepted in our team that we need to expand though
[20:41] <bencrisford> highvoltage: im all done dont worry :)
[20:41] <mhall119> highvoltage: where's the current wishlist for Maverick?
[20:42] <highvoltage> mhall119: in a tomboy note on my pc!
[20:42] <stgraber> I don't really think we have one
[20:42] <grantbow> can someone create a wiki page?
[20:42] <highvoltage> mhall119: I'll paste it here to give you an idea, it's uncensorred and unfiltered...
[20:42] <highvoltage> Plymouth text-fallbacks
[20:42] <stgraber> we also have some notes on gobby (most of it on gobby.ubuntu.com, not sure if we have notes on the internal one)
[20:42] <highvoltage> • Edubuntu chrootless livecd?
[20:42] <highvoltage> • Edubuntu remote network installer
[20:42] <mhall119> highvoltage: damn, ubuntu one really needs note sharing
[20:42] <highvoltage> • Quite down PXELinux
[20:43] <highvoltage> • Split LTSP packages so that scripts is not in main package
[20:43] <highvoltage> • Split edubuntu-artwork package to edubuntu-art, edubuntu-livecd and edubuntu-settings
[20:43] <highvoltage> • Remove less fonts at end of the installation (takes quite long currently)
[20:43] <highvoltage> • Sugar
[20:43] <highvoltage> • http://www.jonobacon.org/2010/04/08/making-programming-easier-for-kids-with-pyjunior
[20:43] <mhall119> highvoltage: maybe copy/paste to a wiki page?
[20:43] <highvoltage> mhall119: there's also Snowy!
[20:43] <mhall119> snowy?
[20:43] <stgraber> highvoltage: Split LTSP packages so that scripts is not in main package ?? what's that one ;)
[20:43] <highvoltage> mhall119: a server for tomboy with a snazzy web interface
[20:43] <highvoltage> mhall119: currently in development though
[20:43] <mhall119> ah
[20:43] <mhall119> I like the ubuntu one sync
[20:44] <highvoltage> stgraber: that's about splitting the ltsp package so that you can install just the ltsp scripts without installing the entire ltsp
[20:44] <stgraber> highvoltage: ah right, that's for lamont ;)
[20:44] <highvoltage> stgraber: for doing an ltsp-build-image on a build env.... yes for lamont :)
[20:44] <highvoltage> stgraber: if I'm not mistaken there's a bug filed for that already too
[20:44]  * lamont waves
[20:45] <highvoltage> hi lamont!
[20:45] <lamont> I recall filing such a bug, yes
[20:45] <highvoltage> see we don't forget about you :)
[20:45] <mhall119> who's lamont?
[20:45] <highvoltage> so, homework assignments for everyone: look at edubuntu as it is and make up your own wishlists of things you think we can realistically get into maverick
[20:46] <highvoltage> next week we can compare notes and put it into a gobby document that can go on to the wiki
[20:46] <lamont> mhall119: loose canon about town.  or something like that
[20:47] <highvoltage> mhall119: lamont is one of the Canonical sysadmins (amongst other things, and apologies if I got that wrong) who helped us with getting the live ltsp chroot on the disc, since we don't have direct access to the build servers
[20:47] <mhall119> ah, cool
[20:47] <lamont> highvoltage: these days, the proper title is "Ubuntu Operational Sys Admin"
[20:47] <mhall119> so he's the guy I need to bribe to get qimo on the build servers
[20:47] <highvoltage> lamont: cool, I was close then :)
[20:47] <highvoltage> I guess I'd also add Schooltool to the list
[20:47] <lamont> qimo?
[20:47] <mhall119> http://www.qimo4kids.com
[20:48] <lamont> as in package bootstraps?  yeah, those are totally my babies
[20:48] <mhall119> ubuntu-based, packages in Universe
[20:48] <nixternal> oi oi
[20:48] <highvoltage> we couldn't get it in for lucid since there's been a lot of zope packages that didn't make it in in time
[20:48] <nixternal> sorry, i am a bit busy with some team stuff and have been afk for 2 weeks...i will try to catch up later tonight
[20:48] <highvoltage> lamont: yeah qimo is a distribution on it's own which is ubuntu-based, but since it's edu-related we got it into the archives so that ubuntu users can easily install it
[20:48] <lamont> if it's just package uploads, MOTU.  if it needs manual handholding, well, dammit quit making circularly dependent packages, or yeah, rt.ubuntu.com
[20:48] <lamont> oh
[20:49] <highvoltage> nixternal: great! I'll also post a summary to the list later on
[20:49] <mhall119> I need to figure out seeding and bootstrapping
[20:49] <mhall119> to make my own ISO's, instead of modifying the ones Xubuntu releases
[20:50] <highvoltage> mhall119: for qimo? I wouldn't really bother, there's better ways to make isos for something like qimo, I can give you some scripts if you want
[20:50] <mhall119> highvoltage: ah, okay
[20:51] <mhall119> I just want to have daily/weekly builds done automatically, rather than everything being hand-customized
[20:52] <highvoltage> cool
[20:52] <mhall119> this cycle, by the time I was able to finish working on an alpha, the next one was already released
[20:52] <mhall119> I'm currently half-way through working on my beta1 ISO
[20:52] <mhall119> had to skip Alpha 3 all together
[20:52] <highvoltage> mhall119: yes, customizing an existing disc for something once-off is ok, but for a long-term project you really need something more automated and sustainable
[20:52] <mhall119> having packages has/will help with that some
[20:52] <highvoltage> *nod*
[20:53] <mhall119> but I need to setup things like package branches in bzr
[20:53] <mhall119> to maintain those
[20:53] <highvoltage> that's also something I think we should do with the edubuntu packages
[20:54] <grantbow> maybe use the same system as quickly
[20:54] <highvoltage> it will make it very easy for non-edubuntu-dev people to submit patches, etc
[20:54] <highvoltage> grantbow: what does quickly use?
[20:54] <grantbow> s/system/conventions/
[20:54] <grantbow> bzr
[20:54] <highvoltage> ok
[20:55] <highvoltage> I first came across bzr for hosting packaging with ltsp-cluster
[20:55] <highvoltage> it only has a slight learning curve and it works very well
[20:55]  * stgraber has all its packaging in bzr, either in team-owned repository or in his personal branches
[20:56] <highvoltage> yeah, and having external branches is nice for people who'd like to make specific changes to some of the packages, like mhall119 with the qimo packages
[20:57] <highvoltage> we have 3 minutes left, anything else before we finish off?
[20:58] <alkisg> stgraber: it seems that the udhcpc clientid problem is wider than I thought, it also affects cisco routers etc... could we patch udhcpc?
[20:58] <highvoltage> ok that's that then, we can take the rest to #edubunt
[20:58] <highvoltage> *#edubuntu
[20:58] <highvoltage> thanks everyone you are all rockstars
[20:58] <alkisg> Thanks all
[20:59] <grantbow> thanks for the meeting everyone
[20:59] <highvoltage> *BONG*
[20:59] <stgraber> alkisg: not for lucid I'm affraid
[20:59] <highvoltage> (oh yes someone said I should change it to "*GONG*" since "bong" means something entirely different in North America)
[21:00] <alkisg> Sure, but if it is something we can do, I can propose a patch for it in few days...
[21:00] <alkisg> (and I'll just upload it to my ppa for my users)
[21:00] <stgraber> you can always send patches ;)
[21:01] <alkisg> Heh, sure, but I don't like spending days on things that have no chance to be accepted :)
[21:01] <alkisg> k, thanks
[21:03] <mhall119> highvoltage: wait, you meant something different by it?
[21:03] <highvoltage> mhall119: yes, it's the gong I hit to signify the end of the meeting :)
[21:03] <mhall119> that's so much less entertaining
[21:03] <highvoltage> mhall119: not something that we smoke after meetings :)
[21:03] <mhall119> lol
[21:03] <highvoltage> mhall119: but if you'd rather imagine that then I won't hold it against you :)
[21:05] <bencrisford> highvoltage: im with mhall119 on this one, bong is far more interesting
[21:09] <highvoltage> bencrisford: ok, by popular request it will remain bong then
[21:11] <bencrisford> highvoltage: lol :)
[21:11] <bencrisford> highvoltage: maybe we should change to gong..  :P edubuntu is meant to be aimed at young children
[21:12] <highvoltage> bencrisford: indeed :)
[21:12] <bencrisford> dont want them getting ideas
[21:30] <lamont> highvoltage: I'm reminded of The Gong Show
[21:31] <highvoltage> lamont: never had it here, I'm not familiar with it
[21:31] <highvoltage> (although I have early childhood memories of someone hitting a gong in some gameshow)
[21:34] <lamont> that's the gameshow
[21:47] <ScottK> Technically the Gong Show was a game show.