[16:00]  * slangasek waves
[16:00] <jhunt> o/
[16:00] <barry> howdy
[16:00] <mvo> hello
[16:00]  * stgraber waves
[16:00] <cjwatson> hey
[16:01] <doko> hi
[16:01] <bdmurray> hi
[16:01] <slangasek> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is slangasek.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <psurbhi> o/
[16:02] <slangasek> [TOPIC] lightning round
[16:02] <MootBot> New Topic:  lightning round
[16:02] <slangasek> $ echo $(shuf -e cjwatson barry doko csurbhi stgraber jhunt mvo ev vorlon bdmurray)
[16:02] <slangasek> mvo bdmurray stgraber csurbhi cjwatson ev doko jhunt vorlon barry
[16:02] <slangasek> mvo: tag
[16:02] <mvo> What I did last week (shorter week, half a day sick, friday on vacation):
[16:02] <mvo> Spec writing/workitem creation work
[16:02] <mvo> SRU for aptdaemon (#781874) and new oneiric version
[16:02] <mvo> Apt: Apt-ddtp update oneiric, review/merge donkults branch, work on lp:~mvo/+junk/apt-ordering-failure for SoC apt order
[16:02] <mvo> Apturl: work on a fix for overlong urls
[16:02] <mvo> Expenses uds budapest, travel preparing spring dublin
[16:02] <mvo> Review/merge lp:~hodgestar/software-properties/configurable-key-server
[16:02] <mvo> Software-center: add fallback to previous distro series if there are no reviews for the current one yet, upload new version, fix tests for oneiric, debug/fix broken apthistory.p caches, merged lp:~evfool/software-center/smallfixes, work on lp:~mvo/software-center/qml, review/merge lp:~evfool/software-center/qfix774201, review/merge lp:~gary-lasker/software-center/refactor, upload new 4.0.2 SRU with fixes in the reviews loader, work on lp:~mv
[16:02] <mvo> o/software-center/pyflakes branch, work on the lp:~mvo/software-center/refactor
[16:02] <mvo> Update-manager: debug/fix/upload UnitySupport integration problem, review/merge lp:~brendan-donegan/update-manager/bug699660-fix-settings-shortcut, update meta-release (now that new u-m is in -updates)
[16:02] <mvo> (this is for the last week from mon-fri, gtimelog seems to give me
[16:02] <mvo> this weekview whatever day I pick from the week, how do others get wed->wed only?)
[16:02] <mvo> (done)
[16:02] <mvo> I guess this comes down to "lots of software-center work" :)
[16:03] <slangasek> :)
[16:04] <slangasek> bdmurray:
[16:04] <bdmurray> created foundations-bugs team and mailing list, subscribed them to packages we care about
[16:04] <bdmurray> modification of ftbfs bugs for doko
[16:04] <barry> mvo: i distill from the timelog.txt file
[16:04] <bdmurray> modification of bug squad standard replies, bug squad signature greasemonkey script
[16:04] <bdmurray> done
[16:04] <mvo> barry: so you don't use the "create weekly report" menu ? I should just use the file too I thnk :)
[16:04] <slangasek> bdmurray: modification of ftbfs bugs is scripting something against bugs currently in LP?
[16:05] <barry> mvo: exactly!  super easy
[16:05] <bdmurray> slangasek: yes doko asked me to retag, target and milestone them
[16:05] <mvo> barry: thanks!
[16:05] <slangasek> ah cool
[16:05] <slangasek> stgraber:
[16:05] <stgraber> I've spent a good part of Thursday and Friday working with upstream x2go.
[16:05] <bdmurray> I'm happy to do similar things for other people
[16:05] <stgraber> Monday was a public holiday here.
[16:05] <stgraber> Uploaded nxcomp and nxproxy merging changes from x2go and rebasing on a recent upstream.
[16:05] <stgraber> Reviewed and uploaded python-x2go (in NEW) and started working on porting the software-center code to it.
[16:05] <stgraber> These changes and new packages should also land in Debian soon (through pkg-devel-x2go).
[16:05] <stgraber> Been doing a few merges too and otherwise worked on my IPv6 test environment and working on the NFS ipv6 MIR (bug 781516).
[16:06] <stgraber> Started thinking of possible integration of containers to help the App Review Board.
[16:06] <stgraber> Updated a few specs so they look good and are ready for review/approval.
[16:06] <stgraber> (done)
[16:07] <slangasek> stgraber: thanks for that MIR, I've kicked it over to the MIR team now :)
[16:07] <slangasek> psurbhi:
[16:07] <psurbhi> *) Tested 2.6.7.x mdadm fixes for autoboot,partition naming etc again -   uploaded a debdiff for the same.
[16:07] <psurbhi> *) visa documentation, appointment, ticket booking
[16:07] <psurbhi> *) Assessing the need for mountall interface - when root changes while booting (had initially thought that this was needed)
[16:07] <psurbhi> *) ext4 deadlock bug - re-worked on the patches that I sent out earlier.
[16:07] <psurbhi> (done)
[16:08] <stgraber> slangasek: ok, I guess it can be approved with the current content but we should wait for a new libtirpc in Debian or drop the build-dep ourself and then sync whenever Debian does the same thing
[16:08] <slangasek> stgraber: yep
[16:09] <slangasek> cjwatson:
[16:09] <cjwatson> This week:
[16:09] <cjwatson>  * more work on live-build, now properly specced/wikied (foundations-o-live-build) - x86 mostly sorted, working on ARM requirements now
[16:09] <cjwatson>  * wrote up foundations-o-great-cd-debate, hopefully clearly
[16:09] <cjwatson>  * started initial oneiric CD builds
[16:09] <cjwatson>  * moved transition tracker onto DC infrastructure
[16:09] <cjwatson> Next week:
[16:09] <cjwatson>  * make sure the installer is working properly for alpha-1
[16:09] <slangasek> psurbhi: and that mdadm diff is ready for sponsorship, right?  It's on my todo list
[16:09] <cjwatson>  * if possible, cut over to live-build, at least for x86
[16:09] <psurbhi> slangasek, yes
[16:10] <psurbhi> just that its quiet a big one.. :-/
[16:10] <slangasek> yeah :)
[16:11] <slangasek> cjwatson: I was puzzled that foundations-o-great-cd-debate only has one work item
[16:11] <cjwatson> I thought somebody would say that :)
[16:11] <slangasek> surely I should have a work item there to investigate the 703MB CD question further :)
[16:11] <cjwatson> ah, yes, that would be a good plan
[16:11] <cjwatson> I didn't want to write a vague work item that said "maybe increase the CD limit"
[16:12] <cjwatson> and a lot of the items are in reality in other specs (e.g. desktop-o-cdspace)
[16:12]  * slangasek nods
[16:12] <cjwatson> I'll lob a work item in for you
[16:12] <slangasek> ta
[16:12] <slangasek> ev:
[16:12] <cjwatson> (the size benefit from live-build was a pleasant surprise)
[16:12] <ev> Done:
[16:12] <ev> - Investigated Mozilla Input (http://input.mozilla.com and
[16:12] <ev>   http://feedback.mozilla.com) and the old kampyle.com-based feedback system
[16:12] <ev>   used in the Funnel Cake project (recording why people were quitting the
[16:12] <ev>   Firefox install for a day).  Set up a local Django instance of Mozilla Input
[16:12] <ev>   and started poking around the code.
[16:12] <ev> - Taught Wubi to boot straight into the second stage when in Windows Vista or
[16:12] <ev>   later.  Working out an approach for Windows XP.
[16:12] <ev> - Implemented code to present the list of keyboard variants in pertinent to the
[16:12] <ev>   selected language in ubiquity in the panel keyboard indicator, using
[16:12] <ev>   python-xklavier, which I'll have to MIR and seed.
[16:13] <slangasek> oh? there was a size savings with live-build?
[16:13] <ev> - Started trying to untangle kvm-autotest for automated Wubi testing.
[16:13] <ev> - Had a quick play with kexec, enough to confirm that it works.  Still need to
[16:13] <ev>   integrate into ubiquity.
[16:13] <ev> - Lots of discussion around the crash database.
[16:13] <ev> - Tried to address a tech board member's concerns around the community not
[16:13] <ev>   having the full data available for installation success/failure measurement.
[16:13] <ev> - Created an Ubuntu Metrics team to keep the momentum from mpt's UDS plenary.
[16:13] <ev>   Sent out a kickoff email to get things started.
[16:13] <ev> - Had a call with Elliot about his team massively helping plan and resource
[16:13] <ev>   bigger items from the Ubuntu Metrics work.
[16:13] <ev> - Wrote a brief for the Web Team for work on the Spread Ubuntu project.  Sadly
[16:13] <ev>   looks like it might be deferred again :-/.
[16:13] <ev> TODO:
[16:13] <ev> - Catch up on the discussion around the crash database and investigate what
[16:13] <ev>   Mozilla is doing with Socorro, per Elliot's advice.
[16:13] <ev> - Respond to the Technical Board's concerns around the installation
[16:13] <ev>   success/failure measurement.
[16:13] <ev> - Finish drafting results from "Whats wrong with UDS?" session and engage with
[16:13] <ev>   Jono to come up with firmer plans.
[16:13] <ev> - Mock up a network-manager 0.9 D-Bus API for unit testing and to use while I
[16:13] <ev>   wait for the real thing to be packaged.  Create the wireless page in the
[16:13] <ev>   installer.
[16:13] <ev> - Investigate the libcheese pygi bindings and see how much work is required
[16:13] <ev>   for the picture page.
[16:13] <ev> (done) apologies for the poor formatting on that.
[16:14] <cjwatson> slangasek: yeah, about 5 MiB - probably a bit of a memory tradeoff, I think it mostly comes from doing a better job at cleaning up *-old files in /var/lib/dpkg/ and that kind of thing
[16:14] <cjwatson> (since that's about the only file-list difference that's left)
[16:15] <cjwatson> ev: I improved the second-stage boot menu a bit, BTW, by bringing lupin back into sync with GRUB
[16:15] <slangasek> huh, neat
[16:15] <ev> cjwatson: yay, thanks
[16:15] <ev> cjwatson: is it to the point where we don't show the windows option in grub when under wubi?
[16:15] <slangasek> ev: is the TB concern that raw data gathered about successful installs, etc. should be available to the community also?
[16:15] <mvo> ev: woah, impressive list!
[16:15] <cjwatson> ev: one thing that occurred to me in the process though is that there's no way to do certain things in the Wubi environment, because we don't get to write to the GRUB environment block
[16:15] <ev> mvo: mostly noise, really
[16:15] <ev> :)
[16:16] <cjwatson> ev: no, I haven't changed that - that's quite awkward to do right now
[16:16] <ev> slangasek: that was this particular member's concern, yes
[16:16] <ev> which is a hard balancing act against "we don't do headcounts"
[16:16] <cjwatson> ev: do I have a work item for that?
[16:16] <slangasek> clever objection though... if Canonical can be trusted with it, why shouldn't the community :)
[16:16] <ev> cjwatson: no, do you want one?  It was something I noticed when doing a Wubi install and I find it confusing
[16:17] <cjwatson> ev: mm, it's technically accurate and occasionally helpful but I can see how it might be confusing
[16:17] <ev> slangasek: it was phrased in terms of "If I'm a user, I want to be able to look at a database and roughly see my anonymous information in there, knowing the time, etc"
[16:17] <cjwatson> ev: if it bothers you and you want rid of it, give me a work item, yes :)
[16:17] <ev> cjwatson: will do :)
[16:17] <ev> (it means showing two bootloader menus, ick)
[16:18] <slangasek> doko:
[16:18] <cjwatson> ev: (taking to /msg)
[16:18] <cjwatson> (actually #u-i)
[16:18] <doko> - filed MIR's, reviewed and promoted packages for component mismatches
[16:18] <doko> - built OpenJDK b22 for armel, started jtreg tests on armel
[16:18] <doko> - GCC and binutils updates, GCC bug triage
[16:18] <doko> - Linaro toolchain WG call
[16:20] <slangasek> anything interesting coming out of the WG call?
[16:20] <doko> no, business as usual, addressed the powerpc build failure, but nothing else
[16:21]  * slangasek nods
[16:21] <slangasek> jhunt:
[16:21] <jhunt> Post-holiday inbox boxin'. Added workitems to all blueprints bar
[16:21] <jhunt> foundations-o-upstart-for-admins. Provisional planning for Upstart
[16:21] <jhunt> "helpers" (abstract jobs/events). Merging fun (ongoing). Investigating
[16:21] <jhunt> nih+upstart build failures (ongoing) - looks like a toolchain issue on
[16:21] <jhunt> armel.
[16:21] <jhunt> EOF
[16:22]  * mvo read "post-holiday inbox bombing"
[16:22] <slangasek> heh
[16:22] <slangasek> sounds like a holiday in itself
[16:22] <barry> love it
[16:22] <psurbhi> heh
[16:23] <slangasek> jhunt: eta on work items for foundations-o-upstart-for-admins?
[16:23] <ev> (slangasek: https://lists.ubuntu.com/archives/technical-board/2011-May/000873.html - he's made his concerns public now)
[16:23] <cjwatson> doko: thanks for the c-m work, it's been greatly appreciated
[16:23] <jhunt> slangasek: should be done by cob today.
[16:23] <slangasek> ok, great :)
[16:23] <jhunt> what's the deadline for the specs btw?
[16:24] <slangasek> last Friday ;)
[16:24] <jhunt> ah...
[16:24] <cjwatson> slangasek: speaking of which, I'm approver of several undrafted specs where you're the drafter ;-)
[16:24]  * slangasek ducks and runs
[16:24] <slangasek> yep, will have those done today
[16:25]  * cjwatson cracks the whip
[16:26] <slangasek> my turn
[16:26] <slangasek> * blueprint review/approval
[16:26] <slangasek> * followed up on wrong memory requirements information for natty
[16:26] <slangasek> * documenting our UDS output in the proceedings: https://wiki.ubuntu.com/UDSProceedings/O
[16:26] <slangasek> * looking into the possibility of contracting a Windows programmer to help with Wubi
[16:26] <slangasek> * trying to figure out a schedule for an upstart sprint this cycle
[16:26] <slangasek> ... you guys need to plan your vacations together so I have something to work with ;P
[16:27] <slangasek> EOF
[16:27] <ev> oh, I intend on waiting until the last minute and taking 26 straight days off :-P
[16:27] <cjwatson> the "bye, see you next year" option is always fun
[16:27] <slangasek> heh
[16:27] <slangasek> barry:
[16:27] <barry> bug 787822 and debian bug 625784 (virtualenv -p python3 broken), did my first upload to fix this in oneiric!; bug 784662 (winpdb; fix in ppa, maybe backports?); started looking at python3-defaults to drop py3.1; blueprinting; ubuntu packaging guide (copy last bits of wiki to rest and fulfill jorge's mandate by deleting many wiki pages); blog about python plans for oneiric; upgraded dev vm to oneiric; released python 2.6.7rc2; done.
[16:28] <cjwatson> slangasek: cool, that proceedings page makes us look good. :)
[16:28] <slangasek> being the only team to ACTUALLY fill it out does that :)
[16:29] <barry> :-D
[16:29] <jhunt> slangasek, ev: the ultimate - http://dilbert.com/strips/comic/1991-10-31/
[16:30] <ev> ooo, I have to try that
[16:30] <psurbhi> heh

[16:30] <slangasek> barry: congrats on the upload! :)
[16:30] <barry> slangasek: thanks!
[16:30] <ev> barry: was it automatix?
[16:31] <barry> ev: automatix?
[16:31] <slangasek> so with the ubuntu packaging guide moved out of the wiki, are there stubs left somewhere that direct to the new guide?
[16:31] <slangasek> ev: harsh
[16:31]  * barry didn't sleep a wink last night
[16:31] <slangasek> barry: automatix, because every package management system needs a four-speed blender
[16:31] <ev> barry: http://mjg59.livejournal.com/77440.html
[16:32] <ev> killall -9 dpkg! yay
[16:32] <slangasek> [TOPIC] AOB
[16:32] <MootBot> New Topic:  AOB
[16:32] <ev> yes
[16:32] <ev> https://lists.ubuntu.com/archives/technical-board/2011-May/000873.html
[16:32] <slangasek> [LINK] https://lists.ubuntu.com/archives/technical-board/2011-May/000873.html
[16:32] <MootBot> LINK received:  https://lists.ubuntu.com/archives/technical-board/2011-May/000873.html
[16:33] <ev> I'm interested to know if anyone has thoughts on how I can remove myself from between the rock and hard place that is giving developers access to the raw data and not giving people data to infer head counts with
[16:33] <slangasek> people always infer head counts anyway, don't they?
[16:33] <ev> or how I can play the tech board against itself for massive win
[16:33] <slangasek> heh
[16:34] <barry> ev: perhaps assign people a random uid and offer to email that to them so they can track their own data but no one elses?
[16:34] <barry> oh wait
[16:34] <cjwatson> Scott has an interesting point about the data being genuinely useful to third parties as well
[16:34] <cjwatson> I think I'd prefer to discuss this in a TB meeting though ...
[16:35] <cjwatson> infer head counts> one option would be expiring the data
[16:36] <slangasek> right - we can share whatever data we have, but just not keep interesting data
[16:36] <slangasek> if what we want is success rate over time, only keep that
[16:36] <slangasek> sorry, not to imply that's not interesting data :)
[16:37] <ev> expire the real data, but keep the percentages forever?
[16:37] <slangasek> yeah
[16:37] <ev> that works for me
[16:37] <ev> but sure, we can discuss this in the TB meeting
[16:37] <stgraber> so have the server store the data for the day, at the end of the day generate the stats and remove the data?
[16:38] <cjwatson> or something like that - possible compromise anyway
[16:38] <slangasek> yep
[16:38] <slangasek> you can't aggregate those numbers over time because you don't have the scale
[16:38] <slangasek> so it does limit the utility to some degree
[16:38] <slangasek> food for thought, at least :
[16:38] <slangasek> )
[16:38] <slangasek> anything else?
[16:39] <stgraber> yeah, and we'll still have "interesting data" like how many installs do we get on release day... ;)
[16:39] <ev> I created a metrics team
[16:39] <ev> people should join it and participate
[16:39] <mvo> ++
[16:39] <ev> if they're interested in this sort of stuff, of course
[16:39] <ev> http://launchpad.net/~ubuntu-metrics
[16:39] <MootBot> LINK received:  http://launchpad.net/~ubuntu-metrics
[16:39]  * slangasek creates ~ubuntu-imperials in response
[16:40] <slangasek> ;-)
[16:40] <ev> lol
[16:42] <slangasek> #endmeeting
[16:42] <MootBot> Meeting finished at 10:42.
[16:42] <slangasek> thanks, all :)
[16:42] <mvo> thanks!
[16:43]  * jhunt is on holiday - please leave a message after the prompt
[16:43] <jhunt> Oops - sorry! :)
[16:43] <doko> bye
[16:43] <psurbhi> jhunt is coughing... :D
[16:43] <mvo> in the good news section (that we did not have): I played with qml and its really really nice for UI work
[16:43] <stgraber> thanks
[16:43] <psurbhi> thanks
[16:43] <barry> mvo: nice
[16:43] <ev> thanks
[16:43] <stgraber> mvo: oh cool, it's on my todolist of stuff to look at (since UDS-O) ;) will try to spend some time on it this weekend
[16:44] <ev> qml> ick
[16:44] <ev> "people are moving to the web, and they're using javascript as part of that.  I know, we'll stop the tide by putting javascript on the desktop! This cannot fail!"
[16:44] <mvo> barry, stgraber: llp:~mvo/software-center/qml for the curious
[16:44] <mvo> ev: gnome-shell!
[16:45] <ev> yep, equally awful
[16:45] <ev> Also, Qt bad, very bad.
[16:45] <mvo> ev: out of curiosity, what do you dislike about the approach? just the layout stuff in qml is vastly more powerful than gtk
[16:45] <barry> ev: ecmapython
[16:46] <ev> I am very weary of us moving to Qt in general for a number of reasons
[16:46] <ev> not least of which, it doesn't have an owner
[16:46] <ev> but more importantly, it's just reliving the battle of the 1990s
[16:46] <ev> we don't need another WIMP model to compete with Windows 95
[16:47] <ev> we need something new and revolutionary, that, if we're not going to develop upstream software ourselves, leverages the hard work being done in our open source industry
[16:47] <ev> so, webkit + other things
[16:47] <stgraber> mvo: cool, I'll have a look. Off for lunch now, see you.
[16:47] <ev> if I have to pick between Google creating an open source layout engine and a company that laid off most of its employees on Qt, I'm going to go with Google.
[16:48] <ev> (equally, I don't think this is the kind of thing we can hope for some PhD student to knock out as part of their thesis)
[16:48] <cjwatson> javascript on the desktop: I think I confirmed at UDS that I wasn't the only one who was reminded of Active Desktop
[16:48] <mvo> right, fair enough. the future is very uncertain for qt, that is unfortunately true
[16:50] <barry> not that i have a horse in the race, but qt is free software and has a big fan base right?  it's not going anywhere, though it may not progress as quickly.  heck, even tcl is still around :)
[16:50] <ev> I just want us to be forward thinking. We're not going to compete with the big boys by playing with yesterday's technology, or even today's.
[16:51] <barry> that i agree with
[16:52] <mvo> right, and yet we need to have solution today that are compelling
[16:59] <ev> sure, but this seems to be positioned as the future
[16:59] <ev> and too many transitions will kill our developers and users
[16:59] <ev> so I think it's wiser to invest heavily in developing future technology and smoothing out the rough bits of what we already have
[17:00] <mvo> that is something I very much agree with, we need to keep the transitions as low as possible
[17:04] <Ahmuck-Sr>  /topic
[17:05] <patrickmw> QA meeting?
[17:06] <patrickmw> hggdh ^
[17:07] <hggdh> darn it!
[17:07] <hggdh> OK
[17:07] <cp1> was over about 25 minutes ago
[17:08] <patrickmw> hggdh, I can help gather the troops
[17:08] <hggdh> patrickmw: isn't it at 1200?
[17:08] <patrickmw> I see 1700 UTC on the fridge
[17:09] <cp1> QA is next hour about 50 minutes away
[17:09] <hggdh> yes
[17:10] <hggdh> patrickmw: 'date -u' return 16:09 ere
[17:10] <patrickmw> grrr Foiled again by google calendar
[17:10] <hggdh> here
[17:10] <hggdh> patrickmw: welcome! Been there so many times...
[17:10] <hggdh> cp1: thank you
[17:10] <hggdh> :-)
[17:10] <hggdh> pffuiiii, not guilty this time
[17:11] <patrickmw> hggdh, sorry for the hearth attack :)
[17:11] <hggdh> :-)
[17:11] <hggdh> my heart seems to be still strong, of sort of ;-)
[18:00] <hggdh> almost time....
[18:00] <hggdh> no, it *is* time
[18:00] <jibel> ~o~
[18:00] <hggdh> OK
[18:00] <hggdh> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is hggdh.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <hggdh> good morning/afternoon/evening/night to all
[18:01] <hggdh> we will go thru the following agenda:
[18:01] <patrickmw> good *
[18:01] <hggdh> Previous Actions (all)
[18:01] <hggdh> Community Efforts/Testing
[18:01] <hggdh> Automated/Systems Testing
[18:01] <hggdh> Engineering Team Bug Status
[18:01] <hggdh> Other Topics
[18:01] <hggdh> Chair Selection
[18:01] <hggdh> [TOPIC] Previous Actions
[18:01] <MootBot> New Topic:  Previous Actions
[18:01] <hggdh> I cannot see any pending actions. Anybody has a better view than mine (known to be flaky)?
[18:02] <jibel> There was an action to move the meeting on #u-meeting at 1700UTC and update the calendar
[18:02] <jibel> here we are!
[18:02] <jibel> done
[18:02] <hggdh> :-)
[18:02] <hggdh> so
[18:02] <hggdh> [TOPIC] Community Efforts/Testing
[18:02] <MootBot> New Topic:  Community Efforts/Testing
[18:03] <hggdh> we are starting a new cycle, and today the first ISOs for the desktop were put available. I understand they are quite unstable, though
[18:03]  * charlie-tca waves
[18:03] <pedro_> ooh yes :-)
[18:03] <hggdh> but, generically, help testing the new Oneiric images is extremely welcome
[18:04] <hggdh> Anything from the community relating to test?
[18:04] <jibel> o/
[18:04] <hggdh> (BTW -- there are no server ISOs available)
[18:04] <hggdh> jibel: please go ahead
[18:05] <jibel> only alternate and desktop on i386 are available.
[18:05] <jibel> so, we need help with sru testing and especially 3 bugs:
[18:05] <jibel> bug 665185 sysvinit (Lucid) High
[18:06] <jibel> it is targeted to 10.04.3 and needs verification asap
[18:06] <jibel> bug 695290 grub2 (Lucid, Maverick) High
[18:06] <jibel> Requires dual RAID controllers
[18:06] <jibel> if anyone has a dual raid controller please give it a try
[18:06] <jibel> bug 778026 lirc (Natty) Critical
[18:06] <jibel> Requires an Infrared Remote Control
[18:07] <jibel> if anyone has an Infrared Remote Control and is running natty please give it a try
[18:07] <hggdh> for the record, Lucid 10.04.3 is looming... we need to check these SRU bugs really, really, ASAP
[18:07] <jibel> ..
[18:07] <hggdh> OK. Moving on
[18:07] <hggdh> [TOPIC] Automated/Systems Testing
[18:07] <MootBot> New Topic:  Automated/Systems Testing
[18:07] <patrickmw> Hello all
[18:07] <patrickmw> We are currently running the individual test suites that get executed for Kernel SRU to collect data:
[18:07] <patrickmw> What type of tests get run
[18:07] <patrickmw> What kind of results are generated
[18:07] <patrickmw> How do they perform in a CI environment
[18:08] <patrickmw> We have been making steady progress and have been able to run LTP lite to completion.  After reviewing the other test suites (DBench, TBench, TioBench, SignalTest) we will need to transform the results to a standard format.  Most of these test suites started development before test runners like unittest were widely used.
[18:08] <patrickmw> Ubiquity testing:
[18:08] <patrickmw> There is currently a piloted set of test scripts for automating the Ubiquity installer. Those scripts will be developed into a full-fledged framework so we can continue to add tests
[18:08] <patrickmw> Not much to report until after the Automation Sprint
[18:08] <patrickmw> Package continuous integration:
[18:08] <patrickmw> Engineering teams have been asked to submit lists of critical packages to Ubuntu. Those packages are being added to the CI process and will be built, tested and reported upon on a more frequent basis whether it be daily, hourly, or upon code push.
[18:08] <patrickmw> Questions?
[18:08] <hggdh> o/
[18:09]  * patrickmw is all ears
[18:09] <hggdh> we are currently running kernel SRUs -- what should we change, if anything?
[18:10] <patrickmw> nothing right now.  We are still in discovery mode.  As soon as we can get the SRU tests in the hands of Jenkins we will let you know :)
[18:10] <hggdh> ok
[18:11] <hggdh> anything else?
[18:11] <patrickmw> not from me
[18:11] <hggdh> moving on
[18:11] <hggdh> [TOPIC] Engineering Team Bug Status
[18:11] <MootBot> New Topic:  Engineering Team Bug Status
[18:11] <hggdh> pedro_: ?
[18:12] <hggdh> (or am I jumping the gun?)
[18:12] <pedro_> as you all know the desktop on Oneiric is a 'bit' broken
[18:12] <pedro_> and probably more breakage is coming since the transition to Gnome 3
[18:13] <pedro_> so if you encounter a bug that i'm not aware of (commented on) or anybody from the desktop team, please raise it to me so i can assign it to the right person and get it fixed
[18:13] <hggdh> (pedro_ can usually be found on the #ubuntu-bugs channel)
[18:14] <pedro_> yes on that and at #ubuntu-desktop if i'm not around
[18:14] <pedro_> and also! on the desktop page, we're having a bug day for the amazing Compiz
[18:14] <pedro_> which is tomorrow https://wiki.ubuntu.com/UbuntuBugDay/20110526
[18:14]  * hggdh forgot -desktop, shame, oh shame
[18:14] <pedro_> so if you have some time and wanna learn a bit more about it  please join us :-)
[18:14]  * pedro_ hugs hggdh
[18:14]  * hggdh hugs pedro_ back
[18:15] <hggdh> done?
[18:15] <pedro_> guess that's all from here
[18:15] <pedro_> yeah
[18:15] <hggdh> folks, when you are done typing, please enter a line with just two dots -- like
[18:15] <hggdh> ..
[18:15] <hggdh> (just an example)
[18:15] <charlie-tca> o/
[18:15] <hggdh> charlie-tca: please go ahead
[18:16] <charlie-tca> Are we going to need oneiric to work those compiz bugs, or will testing in natty be good?
[18:16] <hggdh> for tomorrow, you mean?
[18:16] <charlie-tca> yes
[18:16] <pedro_> the version of compiz in both is the same
[18:16] <charlie-tca> So, if it works/fails in 11.04, that will be valid
[18:16] <charlie-tca> ..
[18:17] <hggdh> OK, moving on. Next in line is bdmurray
[18:17] <pedro_> lot of issues about compiz are related to video drivers though, so it would be good if you cna test with oneiric if its working for you
[18:17] <pedro_> otherwise natty is fine
[18:17] <pedro_> ..
[18:17] <hggdh> bdmurray: there?
[18:18] <hggdh> let's try JFo -- there?
[18:18] <bdmurray> hggdh: what is this topic about exactly?  is it the status of engineering team bugs or what I've been up to?
[18:18] <hggdh> bdmurray: I understand it to be status of the eng team bugs
[18:19] <hggdh> and, why not, what you have been up to :-)
[18:19] <bdmurray> I've nothing really to report regarding specific bugs / issues.
[18:20] <bdmurray> I've been working on sorting out packages the foundations team is interested in.
[18:20] <bdmurray> .......
[18:20] <JFo> hggdh, I'm here
[18:21] <hggdh> bdmurray: the dots there mean you are really, completely, utterly done?
[18:21] <hggdh> JFo: just a sec, please
[18:21] <bdmurray> indeed ..
[18:21] <JFo> ok
[18:21] <hggdh> bdmurray: will your work on the foundation packages be extensible to the other teams?
[18:22] <bdmurray> hggdh: I've one script that looks at packages that members of a team in Launchpad are subscribed to which may be useful as a starting point
[18:22] <crazedpsyc> Anything I can do to help with tomorrow's powerusers meeting?
[18:23] <bdmurray> however, I found there were lots of false positives there as people subscribe to things they care about in their spare time
[18:23] <hggdh> oh
[18:23] <bdmurray> additionally, I have an ubuntu-changes mailing list parser that counts package uploads per person
[18:23] <hggdh> crazedpsyc: please wait a bit, this meeting is about QA
[18:23] <bdmurray> this was the most useful for finding packages the team has an interest in
[18:24] <crazedpsyc> hggdh: Ahh, sorry, didn't know there was anything happening at the moment :)
[18:24] <hggdh> bdmurray: can it be shared later on? I think all teams would be interested
[18:24] <bdmurray> then I have another launchpadlib script to subscribe people or teams to pacakges
[18:25] <bdmurray> that one could be unused not nicely though I think so I will sit on that
[18:25] <bdmurray> hggdh: yes, I'll share my code
[18:25] <bdmurray> . . . ;-)
[18:25] <hggdh> :-)
[18:25] <hggdh> JFo: sorry for the delay, floor is yours
[18:25] <JFo> no sweat, what would you like to know?
[18:26] <JFo> (I was unprepared for this meeting ;))
[18:26] <hggdh> JFo: I understand kernel triage is changing -- you now do something a bit different. Care to share?
[18:26] <JFo> sure
[18:26] <JFo> so, I have begun working solely on development release bugs
[18:27] <JFo> in addition to that, and because there are so few just now, I am taking some time to dive a bit deeper into career/job development
[18:27] <JFo> with those subject matter experts in certain kernel subsystems
[18:27] <hggdh> oh, there goes another triager...
[18:27] <hggdh> ;-)
[18:28] <JFo> I'm taking an hour at least a week to work with Graphics/BIOS and sound subsystem engineers so that I can help them get more clear bugs
[18:28] <JFo> :-)
[18:28] <hggdh> will there be somebody dedicated to stable releases for thr kernel?
[18:28] <JFo> that will benefit the Analyst portion of the new direction
[18:29] <JFo> not yet, but the plan is to record what I am able to accomplish this cycle as a means of identifying the need
[18:29] <JFo> so the SRU team will be working on their bugs (even though I am helping them still a bit)
[18:30] <JFo> I am positive that my assistance to them will wane as the number of development bugs increases
[18:30] <JFo> which is sad really
[18:30] <JFo> but I digress
[18:30] <JFo> are there any questions on that? :)
[18:30] <JFo> any of that?
[18:30] <JFo> ..
[18:30] <hggdh> then... should we try to help on stable?
[18:31] <JFo> not yet I don't think. That may be something we can revisit in several weeks. I am still working with them to determine how SRU bugs will be handled
[18:31] <hggdh> thank you
[18:31] <JFo> my pleasure
[18:31] <hggdh> moving on
[18:31] <hggdh> [TOPIC] Other Topics
[18:31] <MootBot> New Topic:  Other Topics
[18:32] <hggdh> open mic, please raise hand for attention
[18:32] <jibel> o/
[18:33] <hggdh> jibel: please go ahead
[18:33] <jibel> on the topic 'community testing' 2 more things
[18:33] <hggdh> o/ (when jibel is done)
[18:34] <jibel> the test cases for Ubuntu desktop and alternate have been updated. A review would be greatly appreciated
[18:34] <jibel> We need help to update non english test cases
[18:34] <jibel> and Oneiric alpha 1 is scheduled next week.
[18:34] <jibel> https://wiki.ubuntu.com/OneiricReleaseSchedule
[18:35] <hggdh> so -- for those of you fluent in other languages: please help on the translation
[18:35] <jibel> The first candidates will be published on the tracker hopefully on tuesday.
[18:35] <jibel> A major user visible change is the transition to gnome 3, so testing promises to be fun.
[18:35] <jibel> don't forget to sync your images over the week end.
[18:36] <jibel> thanks
[18:36] <jibel> ..
[18:36] <charlie-tca> will we have all the images by Saturday?
[18:36] <jibel> charlie-tca, I don't think so, but if you sync over the week end there is less to sync when the candidates are published.
[18:37] <hggdh> my turn -- I give the floor to myself
[18:37] <hggdh> there is a survey going on -- community based. You can see/fill it at https://spreadsheets.google.com/spreadsheet/viewform?formkey=dGRLSmxTQ05VYzh6NmdBN3BsakhpM3c6MQ#gid=0
[18:37] <maco> Please share it with the non-technical users in your life too
[18:38] <hggdh> I am really curious to find out what it will give us as result
[18:38] <hggdh> and -- thanks again to maco for putting it up
[18:38] <maco> Answers solely from power users and programmers are a bit biased ;-)
[18:38] <hggdh> ..
[18:39] <hggdh> so. Without any other questions...
[18:39] <hggdh> [TOPIC] Chair Selection
[18:39] <MootBot> New Topic:  Chair Selection
[18:39] <hggdh> who shall be the next chair?
[18:39] <hggdh> hum. The silence is thunderous
[18:39] <charlie-tca> this is bit different, but being it will be the first of the month, it must be my turn
[18:40] <hggdh> :-)
[18:40] <hggdh> charlie-tca: so you are proposing yourself?
[18:40] <charlie-tca> sure
[18:40] <hggdh> you WIN!
[18:40] <charlie-tca> put me down, gets me to the meeting, too
[18:40] <hggdh> [ACTION] charlie-tca to chair next meeting
[18:40] <MootBot> ACTION received:  charlie-tca to chair next meeting
[18:41] <hggdh> and I think this is it -- thank you, charlie-tca
[18:41] <charlie-tca> You are welcome
[18:41] <hggdh> #endmeeting
[18:41] <MootBot> Meeting finished at 12:41.
[18:41] <hggdh> thank you all
[18:41] <charlie-tca> Thanks for chairing, hggdh
[18:41] <pedro_> thanks
[18:41] <jibel> Thanks for chairing hggdh
[18:41] <charlie-tca> and now, lunch
[18:41] <hggdh> indeed
[18:41] <jibel> and now dinner
[18:43] <Ahmuck-Sr> o/
[18:43] <Ahmuck-Sr> nm
[20:08] <highvoltage> hi!
[20:08]  * alkisg waves
[20:08] <highvoltage> stgraber: around? :)
[20:08] <stgraber> kind of
[20:09] <highvoltage> anyone else for the Edubuntu meeting?
[20:09] <highvoltage> all I really need to add is that I'll be updateing our roadmap page to match what we discussed at UDS
[20:09] <highvoltage> and I'll send some notes to the list too
[20:10] <highvoltage> (should've done that before already, but been busy)
[20:11] <highvoltage> these are basically our blueprints from UDS:
[20:11] <highvoltage> https://blueprints.launchpad.net/ubuntu/+spec/community-o-edubuntu
[20:11] <highvoltage> and
[20:11] <highvoltage> https://blueprints.launchpad.net/ubuntu/+spec/community-o-debian-edu-edubuntu-collaboration
[20:12] <highvoltage> anything else that's worth noting?
[20:12] <highvoltage> we've had a few new requests for http://edubuntu.org/marketplace recently, it's been growing steadily. there's probably another one that will be added soon
[20:13] <stgraber> nothing on my side. I'm probably going to update the -o-edubuntu spec with the WI I already worked on
[20:15] <alkisg> Thanks for the update :)
[20:16] <highvoltage> sending some details to the list will at least force me to think of some things I haven't had bandwidth for :)
[20:18] <highvoltage> well, I guess it's back to lurking in #edubuntu then :)
[20:19] <stgraber> short meeting ;)
[20:19] <alkisg> :)
[20:20] <highvoltage> I *could* find enough edubuntu stuff to blabber about for an hour but not sure if that would be exactly productive :)
[20:20] <stgraber> :)