[16:01]  * slangasek waves
[16:01] <bdmurray> hi
[16:01]  * stgraber waves
[16:01] <slangasek> #startmeeting
[16:01] <meetingology> Meeting started Wed Feb 22 16:01:43 2012 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:01] <slangasek> [TOPIC] lightning round
[16:02] <slangasek> well, down by two today... should be a quick meeting yes? :)
[16:02] <slangasek> $ echo $(shuf -e barry doko stgraber ev bdmurray slangasek)
[16:02] <slangasek> stgraber bdmurray barry ev doko slangasek
[16:02] <stgraber> hello
[16:02] <stgraber> - Networking
[16:02] <stgraber>  - SRUs for ifenslave/vlan/bridge-utils are finally in oneiric-updates!
[16:02] <stgraber>  - Did some more IPv6 testing, trying to switch to single-stack for part of my network so testing current radvd, NM and squid. Filed a few bugs for cyphermox :)
[16:02] <stgraber>  - Updated isc-dhcp to 4.1-ESV-R4 that's their Extended Support Version, did a call for testing and will upload it later today.
[16:02] <stgraber> - Friendly-Recovery
[16:02] <stgraber>  - Implemented the 'system information' option and did a few more bugfixes. James proposed some good changes, will review the merge and ask for a FFe to get that added.
[16:02] <stgraber> - LTSP
[16:02] <stgraber>  - Released LTSP 5.3 after two years of development (well, 729 days so not "exactly"), uploaded to Ubuntu. 5.3.1 has already been released as bugfix release but I'll probably wait till 5.3.2 to update Ubuntu.
[16:02] <stgraber>  - Still some work on the udeb needed to finally kill bug 813837
[16:02] <stgraber> - TPM
[16:02] <stgraber>  - Got pretty close to having a working TPM authenticating on wireless, everything seems to work except for some broken pkcs11 output and problems using the private key...
[16:03] <stgraber>  - Started looking at bug 934799, can probably be fixed by manually trigger the udev rule or doing the chown/chmod in the postinst
[16:03] <stgraber>  - Also bug 926305 is high on the TPM todo list
[16:03] <stgraber> - Installer
[16:03] <stgraber>  - Merged a couple of fixes in Ubiquity, updated test suite and uploaded a new Ubiquity, will spend a lot more time working on installer bugs from now on.
[16:03] <stgraber> - Containers
[16:03] <stgraber>  - Uploaded updated udev to avoid flooding the host with events when a container boots.
[16:03] <stgraber>  - Some bugfixes for the Ubuntu template and review of the Ubuntu server guide's section on LXC.
[16:03] <stgraber> - Other
[16:03] <stgraber>  - pastebinit 1.3 has now been released and is in Precise
[16:03] <stgraber>  - Did quite a few last minute sponsoring of new packages for Precise, most of them are in source NEW
[16:03] <stgraber> (done
[16:03] <stgraber> )
[16:03] <bdmurray> short week as monday was a holiday
[16:03] <bdmurray> tested bug 933035 regarding resolvconf
[16:03] <bdmurray> merged bug patterns from Vadim Rutkovsky
[16:03] <bdmurray> bug control application review for brettcornwall
[16:03] <bdmurray> bugbot fix for package-install-segfault re and mythfrontend
[16:04] <bdmurray> bug triage of some ubiquity hard disk error bugs
[16:04] <bdmurray> duplicate finding kernel install failures on live media (bug 932663)
[16:04] <bdmurray> duplicate finding filesystem.size missing (bug 557388)
[16:04] <bdmurray> flot / jquery work to dynamically set the size of the div for the recent package bug task graphs
[16:04] <bdmurray> modifications to recent package bug tasks graph not to fade the colors of the stacked bar
[16:04] <bdmurray> moved the legend in flot outside of the graph
[16:04] <bdmurray> recent package bug graphs making the labels on the y-axis hyperlinks to full launchpad searches
[16:04] <bdmurray> fixed lucid-proposed version of update-manager (apport hook)
[16:04] <bdmurray> update of OneiricOcelot release notes regarding wubi (regarding rev 241)
[16:04] <bdmurray> wrote lp-grab-descriptions based on lp-grab-attachments
[16:04] <bdmurray> ubiquity apport package hook modifications to fix bug 874727
[16:04] <bdmurray> ␗
[16:07] <slangasek> barry:
[16:07] <barry> telepathy-qt4 ftbfs, libdbusmenu ftbfs, bug 934592 (oneconf ftbfs), sync python-keyring, python issue 13703 (hash collision dos issue), sync'd sphinx, claws-mail, claws-mail-extra-plugins.  todo: looking at ftbfs and nbs reports; bugs, bugs, bugs and more +1 maint work; still working on python issue 13703, hopefully will have joint release candidates in the next day or two.  𝄢
[16:08] <slangasek> ev:
[16:09] <ev> - Released some new versions of whoopsie (0.1.8, 0.1.9, and 0.1.10).
[16:09] <ev> - Don't start the crash reporting daemon if crash reporting is turned off.
[16:09] <ev> - Cleaned up of the core processing code and much of the backend code, in
[16:09] <ev>   preparation for deployment.
[16:09] <ev> - Filed RT 51011 for deploying the crash database.  Had a catch up with James
[16:09] <ev>   to discuss where things stand.
[16:09] <ev> - Started leveraging cloud-init to build out an end to end system testing
[16:09] <ev>   framework, so we can ensure that every change works all the way down to the
[16:09] <ev>   database.
[16:09] <ev> - Figured out, with help from #bzr, how to merge a subdirectory of a branch
[16:09] <ev>   into a subdirectory of another branch without losing history.  Case in
[16:09] <ev>   point, moving Whoopsie's GNOME Control Center preferences page into
[16:09] <ev>   activity-log-manager:
[16:09] <ev>    bzr fast-export /tmp/whoopsie-export
[16:09] <ev>    bzr fast-import-filter -i preferences/ /tmp/whoopsie-export > /tmp/whoopsie-export-filter
[16:10] <ev>    bzr fast-import /tmp/whoopsie-export-filter /tmp/whoopsie-export-branch
[16:10] <ev>    cd /tmp/whoopsie-export-branch
[16:10] <ev>    bzr mkdir diagnostics
[16:10] <ev>    bzr mv * diagnostics
[16:10] <ev>    bzr commit
[16:10] <ev>    cd ~/bzr/activity-log-manager
[16:10] <ev>    bzr merge -r0..-1 /tmp/whoopsie-export-branch
[16:10] <ev>    bzr mv diagnostics src/diagnostics
[16:10] <ev>    bzr commit
[16:10] <ev> - Moved the crash reporting preferences page from a separate page into a tab
[16:10] <ev>   in the activity-log-manager page:
[16:10] <ev>   https://code.launchpad.net/~ev/activity-log-manager/whoopsie/+merge/93899
[16:10] <ev> - Finally finished addressing all of Martin's concerns in my apport merge,
[16:10] <ev>   after lots of subsequent fixes \o/:
[16:10] <ev>   https://code.launchpad.net/~ev/apport/whoopsie/+merge/92753
[16:10] <ev> - Interview calls.
[16:10] <ev> (done!)
[16:10] <doko> surprisingly short today ...
[16:10] <barry> ev: you should write that up somewhere more permanent than irc :)
[16:10] <doko> - openjdk-7 build, currently building in precise
[16:10] <doko> - fixing and forwarding issues in openjdk7 and -web to IcedTea
[16:10] <doko> - openjdk6 pull from the branch to fix GC issues on ARM
[16:10] <doko> - eglibc fixes (gdm restart, ARM dbg package, reboot required)
[16:10] <doko> - look into some gcc-4.6 issues
[16:10] <doko> - python2.7 and python3.2 merges for FF.
[16:11] <doko> - look into gcc-4.7 bootstrap failures on ARM (now fixed)
[16:11] <doko> - help Linaro understanding the eglibc packaging (Ken working on builds)
[16:11] <doko> done
[16:11] <ev> barry: :)
[16:12] <slangasek> are the apport UI changes landed, then? I noticed my last crash had a different dialog
[16:13] <ev> yes, finally
[16:13] <slangasek>  * short week, celebrated Président Day on Monday by eating camembert and butter
[16:13] <slangasek>  * resolvconf upload fixing the last of the known issues
[16:13] <slangasek>  * new upstream release of qemu-linaro uploaded; now usable as a buildd on a hardy kernel
[16:13] <slangasek>  * upload cmake to let more packages in precise/main be auto-cross-buildable
[16:13] <slangasek>  * work on getting upstart in Ubuntu into a usable state
[16:13] <slangasek>  * interviewing
[16:13] <slangasek> done
[16:13] <slangasek> any questions?
[16:14] <slangasek> [TOPIC] Bugs
[16:14] <doko> Andreas Moog did file the ftbfs issues from the last test rebuild, so I hadn't to do it
[16:14] <bdmurray> Not too many to look at today
[16:15] <slangasek> good, I gorged myself on bugs yesterday at Mardi Gras anyway
[16:15] <bdmurray> I assigned bug 883618 to the team recently
[16:15] <doko> would be nice if somebody could approve the setting of the precice release branch
[16:15] <slangasek> doko: what do you mean?
[16:15] <barry> slangasek: ew
[16:15] <slangasek> barry: ;)
[16:16] <slangasek> bdmurray: yeah, I was just assigning that one to jodh
[16:16] <barry> slangasek: and right before lunch!
[16:16] <bdmurray> slangasek: okay, great
[16:16] <slangasek> heh, sorry
[16:16] <barry> :)
[16:16] <slangasek> fwiw I didn't see any references to xset in the current update-manager code, so I'm not sure where that comes from
[16:16] <doko> hmm, looks like it already is: see bug 935038
[16:17] <doko> we just need to confirm these
[16:17] <slangasek> doko: as in, marking them confirmed?
[16:17] <doko> yes
[16:18] <slangasek> I'm not sure that matters anymore, now that LP automatically moves half the bugs to "confirmed" as soon as someone comments on them
[16:18] <doko> heh
[16:18] <bdmurray> comments on? that's a bit unfair
[16:18] <bdmurray> its even easier you just have to click affects me too ;-)
[16:18] <doko> so now we ignore bugs in state Confirmed instead if New? ;-P
[16:19] <doko> of even
[16:19] <slangasek> "triaged" maybe makes a difference; but they should be obvious anyway... don't see the point in spending the effort moving the bug state around
[16:19] <slangasek> let's just fix the bugs instead :)
[16:19] <slangasek> doko: exactly ;)
[16:20] <doko> slangasek, makes sense, thare are more to ignore ;)
[16:20] <slangasek> bdmurray: doesn't it also do it when someone comments though?  which is much less certain to indicate that it's a confirmed bug
[16:20] <doko> can't type today
[16:20] <slangasek> bdmurray: anyway, any other bugs in the menagerie?
[16:20] <bdmurray> slangasek: no affects me too or a bug is made a duplicate of it
[16:20] <slangasek> ah, ok
[16:20] <bdmurray> bug 936761 - is there anything to be done there?
[16:21] <slangasek> looks like the desktop team needs to fix it
[16:22] <slangasek> reassigned the bug to gnome-session
[16:22] <bdmurray> thanks
[16:23] <bdmurray> then bug 824708 has a rather high heat as a lot of people have said it affects them
[16:23] <stgraber> slangasek: I've noticed Xubuntu and Mythbuntu at some point started assuming that they always get installed from a media where they contorl the available set of packages, not sure if it's related though.
[16:24] <slangasek> stgraber: sorta-related
[16:24] <slangasek> the moral of the story is, they shouldn't do that :)
[16:24] <stgraber> slangasek: so for example installing Xubuntu from netinstall will get you unity-greeter that will crash at boot time. Installing from media, they don't have unity-greeter and so fallback to lightdm-gtk-greeter which is what they want and so works
[16:24] <stgraber> that's currently making the automated upgrades for at least Xubuntu fail (so I turned them off for now as they're aware of the issue)
[16:24] <slangasek> they should ensure there are suitable alternatives in the underlying dependencies and use a metapackage to express their preferences
[16:25] <slangasek> bdmurray: do you know why pitti has set a milestone for 824708?
[16:25] <doko> bug 824708
[16:25] <bdmurray> slangasek: no I do not
[16:26] <slangasek> oh, he was just pushing an a2 milestone forward
[16:26] <slangasek> so it has high heat, but I don't think it's something for us to spend time on
[16:26] <slangasek> they can just use 'apt-get changelog' instead
[16:27] <slangasek> (and aptitude has much more serious problems in precise, since it doesn't do multiarch)
[16:27] <bdmurray> okay, makes sense
[16:28] <slangasek> anything else?
[16:28] <bdmurray> that's all from me
[16:28] <slangasek> cool
[16:28] <slangasek> [TOPIC] AOB
[16:29] <slangasek> anything more to discuss?  the floor's open :)
[16:29] <doko> the armel panda buildds did land
[16:30] <doko> but not yet the third powerpc
[16:30] <slangasek> I've pestered IS about the powerpc already
[16:30] <slangasek> the RT ticket has a deadline of Mar 1
[16:30] <slangasek> which I'm told gets looked at :)
[16:31] <slangasek> (and there's activity on the ticket in the past week)
[16:33] <slangasek> #endmeeting
[16:33] <meetingology> Meeting ended Wed Feb 22 16:33:15 2012 UTC.
[16:33] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-16.01.moin.txt
[16:33] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-16.01.html
[16:33] <slangasek> the end
[16:33] <slangasek> thanks all
[16:34] <barry> thanks!
[16:34] <stgraber> thanks!
[17:05] <balloons> yikes yikes..
[17:05] <balloons> 10 mins early to 5 mins late.. so easy to do
[17:05] <balloons> everyone ready?
[17:06] <balloons> #startmeeting Ubuntu QA
[17:06] <meetingology> Meeting started Wed Feb 22 17:06:08 2012 UTC.  The chair is balloons. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:06] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:06] <balloons> Can we get a roll call of who's about? :-)
[17:06] <phillw> o/
[17:06] <josepht> o/
[17:08] <balloons> alrighty... so let's get into the agenda
[17:08] <balloons> [TOPIC] Previous Actions
[17:08] <balloons> ACTION: phillw to update wiki to better reflect activities and automated testing pages
[17:09] <phillw> I've just edited https://wiki.ubuntu.com/QATeam so Automated testing is on the front page, does it need to be highlighted further?
[17:09] <balloons> yes, I see that
[17:09] <balloons> nice
[17:09] <phillw> The actual page reads well as it is. I don't want to make it too long and involved that it is hard to follow.
[17:10] <balloons> I would add the only other change I would make (and perhaps I can learn how, or someone can help) is to add a big icon at the top for the activities link
[17:10] <balloons> thoughts on that
[17:10] <balloons> ?
[17:10] <phillw> That can be done.
[17:12] <balloons> ok, not wanting to add to your workload.. I'll walk down this sidepath a moment
[17:12] <balloons> mm
[17:12] <balloons> looks like I edit this https://wiki.ubuntu.com/QATeam/Header
[17:12] <balloons> that was the key I was missing I think
[17:13] <phillw> balloons: that's right, the 'fun' bit is choosing the icon :)
[17:13] <balloons> ok, I'll take that action as a learning item
[17:13] <balloons> hehe
[17:13] <balloons> [ACTION] balloons to edit the wiki to add activities as an icon link :-)
[17:13] <meetingology> ACTION: balloons to edit the wiki to add activities as an icon link :-)
[17:13] <balloons> ok, that's it for previous items
[17:14] <balloons> [TOPIC] Ubuntu Updates
[17:14] <balloons> jibel, gema you about?
[17:16] <balloons> guess not :-)
[17:16] <balloons> Well, as everyone knows beta1 is coming up soon, and we're going to have some rounds of testing again as part of that
[17:17] <balloons> We are trying to get more people involved in the iso testing, and in addition, make it easier for people who want to help, to be able to do so
[17:18] <balloons> currently the process is a bit confusing at times to follow, in order to coordinate the iso testing -- especially when there is/are respins
[17:19] <balloons> I'd love to hear suggestions about how to make it easier and get more folks involved
[17:19] <albrigha> balloons, i'm here as well
[17:20] <balloons> If your not following @UbuntuTesting on twitter, you can do so. the team is going to try sending status updates thru twitter to help communicate for people who aren't idling all day in #ubuntu-testing
[17:20] <balloons> this way if a respin is needed, etc, it can be communicated more easily
[17:20] <balloons> in addition I'd like to hit up the mailing list a bit more with this information
[17:20] <balloons> hello albrigha ;-)
[17:21] <phillw> I think an email to the list when a respin is done may also be useful. I don't tweet, but I do read my mail :)
[17:22] <balloons> phillw, I'm not a tweeter etheir, but the more communication the better at this point.. I think it's not communicated well atm
[17:22] <balloons> So any other thoughts on getting people involved? what would be helpful to you folks that are doing testing today?
[17:23] <balloons> I found the process over the course of the last 2 iso testing cycles not too bad. the confusion came from understanding how to coordinate more-so than how to run the tests and get the isos.. the wiki explains that part fairly well
[17:24] <balloons> regardless, send to the list any thoughts you may have on that (or anything else you might think about)
[17:24] <balloons> ok, so moving on then
[17:25] <balloons> if there are no more comments :-0
[17:25] <balloons> [TOPIC] Ubuntu Flavor Updates
[17:25] <balloons> phillw, want to talk a bit about lubuntu first?
[17:26] <phillw> lubuntu testing is going okay. A bug has been found and raised regarding the pae headers appearing in a non-pae installation, ppc testing seems also to be progressing well.
[17:27] <phillw> the pae / non-pae affects all flavours, it appears.
[17:27] <phillw> that's about all for lubuntu.
[17:28] <balloons> awesome.. and I saw you might have a couple more iso testers for this next round :-) hopefully they come thru
[17:29] <phillw> yeah, once we hit beta hopefully we will have more people.
[17:30] <balloons> ok, how about kubuntu.. anyone about?
[17:31] <balloons> xubuntu?
[17:31] <balloons> I'm afraid we're missing some folks, but I'll give them a chance if anyone is in here..
[17:32] <balloons> edubuntu?
[17:32] <balloons> ubuntu studio?
[17:32] <Riddell> kubuntu should have a new flavour appearing shortly
[17:32] <Riddell> kubuntu-active for tablets/touch UIs
[17:32] <balloons> hello riddell.. ohh neat
[17:33] <Riddell> minimal QA needs ("tech preview")
[17:33] <Riddell> but should be added to the ISO tracker
[17:33] <balloons> gotcha.. cool cool.. and what hardware will it install on?
[17:33] <Riddell> i386 (not going to bother with ARM until we know it works)
[17:34] <balloons> ok, sounds exciting.. so will it be out before beta1 then?
[17:34] <Riddell> and I don't want to even do install for QA, it's just a case of running the live system to check
[17:34] <Riddell> balloons: hope so, I've been making the changes to the CD build scripts today
[17:35] <balloons> that's exciting.. I saw the spark tablet sold out on pre-order
[17:36] <balloons> lots of interest, it's a cool project I'll be keeping my eye on certainly
[17:36] <balloons> alrighty, if no other flavors have updates, we'll move on to the final topic
[17:36] <balloons> [TOPIC] Other topics
[17:37] <balloons> Which is just really, the catch all. anything anyone wanted to add to the agenda.. nows' the time to speak up
[17:39] <ScottK> BTW, thanks for everyone who tested Kubuntu images
[17:39] <ScottK> Particularly 10.04.4
[17:40] <ScottK> We were able to get the release done, which was in doubt.
[17:41] <balloons> thanks ScottK.. if no one has anything else, then I'll close.. And as always, happy testing to everyone
[17:41] <gema> thanks balloons , sorry I was late and empty handed (i.e. nothing to say)
[17:41] <balloons> I should note I enjoyed getting my feet wet on testing the screenreader install.. I still botched it a bit, but it was fun learning
[17:41] <balloons> thanks to charlie-tca for helping me out on it
[17:42] <balloons> hello gema.. no worries
[17:42] <balloons> we were just ending, hehe
[17:42] <balloons> #endmeeting
[17:42] <meetingology> Meeting ended Wed Feb 22 17:42:13 2012 UTC.
[17:42] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-17.06.moin.txt
[17:42] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-17.06.html
[18:03]  * bdmurray waves
[18:05] <Ursinha> hello
[18:05] <s9iper1> hello people !
[18:05] <bdmurray> #startmeeting
[18:05] <meetingology> Meeting started Wed Feb 22 18:05:23 2012 UTC.  The chair is bdmurray. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:05] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:06] <bdmurray> #topic Previous Actions
[18:06] <bdmurray> so we don't have any actions from the last meeting but we should do something about this list of dbus no reply bugs
[18:06] <bdmurray> that's this - http://paste.ubuntu.com/843325/
[18:07] <bdmurray> any ideas?
[18:07] <Ursinha> bdmurray, yes, considering it's not a huge list we could take some time and find possible valid bugs there and just mark others as incomplete
[18:07] <Ursinha> maybe the reporter won't mind giving us more information so at least we could tell if those are new bugs or duplicates of existing ones
[18:07] <Ursinha> worst cases the bug will expire
[18:07] <Ursinha> but we did what we could
[18:08] <bdmurray> okay, so put it in a wiki page? and each take a few?
[18:08] <Ursinha> bdmurray, that works
[18:09] <bdmurray> #action put list of dbus no reply bugs into a wiki page and email bugsquad regarding list
[18:09] <meetingology> ACTION: put list of dbus no reply bugs into a wiki page and email bugsquad regarding list
[18:10] <bdmurray> #topic Engineering Team Bug Status
[18:10] <bdmurray> Ursinha: do you have anything?
[18:11] <Ursinha> bdmurray, no sir, catching up after carnival
[18:12] <bdmurray> okay, jsalisbury?
[18:13] <bdmurray> I don't have much to report bug wise
[18:13] <bdmurray> However, I made something like lp-grab-attachments that grabs bug descriptions so I could have all the bug descriptions about a package locally available for searching
[18:14] <bdmurray> I found this useful with update-manager at least and was wondering if anybody else would be interested in it.
[18:14] <Ursinha> yes sir
[18:15] <Ursinha> we always need to grab the logs at least
[18:15] <bdmurray> Ursinha: hmm? lp-grab-attachments grabs the logs
[18:16] <bdmurray> with update-manager there are lot of bugs with no log files and just an error message in the description
[18:16] <bdmurray> that's what I wrote grab-descriptions for
[18:16] <Ursinha> I meant this is useful because we need the logs and it grabs the logs :)
[18:16] <bdmurray> lp-grab-attachments is already part of lptools
[18:17] <Ursinha> ok, sorry the confusion, you said you created another one that grabs descriptions instead of logs?
[18:17] <bdmurray> yes, just descriptions
[18:17] <Ursinha> if so, that's useful as well
[18:17] <bdmurray> okay
[18:17] <Ursinha> as lp search doesn't work
[18:17] <bdmurray> Ursinha: right ;-)
[18:17] <Ursinha> :)
[18:18] <bdmurray> #topic Bug Escalations (any High or Critical bugs that community members have seen that need attention)
[18:20] <bdmurray> anyone?
[18:20] <Ursinha> no sir
[18:20] <om26er> the new change made the touchpad problematic for me guess that's important
[18:21] <bdmurray> om26er: is there a bug about that?
[18:21] <om26er> if you double tap with the touchpad it gets stuck that breaks my work flow
[18:22] <bdmurray> I'd imagine so
[18:22] <om26er> bug 934770
[18:24] <om26er> (my internet is crappy with a lag of liek 20sec)
[18:24] <bdmurray> om26er: it looks like chase is aware of it and monitoring it
[18:24] <bdmurray> om26er: so it seems to be a good state
[18:25] <bdmurray> thanks for bringing that up though
[18:26] <s9iper1> bdmurray: another bug which is again affecting the people and also me is this   i am not be able  to  install  google chrome
[18:26] <s9iper1> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/827615
[18:26] <bdmurray> s9iper1: looking
[18:28] <bdmurray> s9iper1: okay, I'll into this more after the meeting that needs some attention.  Thanks for bringing this up!
[18:28] <Ursinha> bdmurray, I can do that as it's a desktop issue...
[18:29] <bdmurray> Ursinha: okay, let me know if you need any help
[18:29] <Ursinha> sure, thanks
[18:29] <s9iper1>  bdmurray:yw and an announcement for us people empathy 3.3.90 will use telepathy-haze to connect to MSN, which means it uses libpurple, the same as pidgin does
[18:29] <bdmurray> #action Ursinha to investigate bug 827615
[18:29] <meetingology> ACTION: Ursinha to investigate bug 827615
[18:30] <bdmurray> with that well move to
[18:30] <bdmurray> #topic any other business?
[18:30] <Ampelbein> o/
[18:31] <bdmurray> Ampelbein: yes?
[18:31] <Ampelbein> I don't know if that's the right meeting, but can something be done about LP auto-confirming developer bugs?
[18:31] <Ampelbein> I mean like, can it exclude bugs tagged e.g. ftbfs, or based on title?
[18:32] <bdmurray> How did a bug get auto confirmed?
[18:33] <Ampelbein> When someone clicks the "This affects me too" link, the bug is set to confirmed by LP.
[18:33] <bdmurray> and why should it not be confirmed?
[18:35] <Ampelbein> Because for example for sponsoring related bugs, the bug status was used to communicate the state with the sponsors. So, "new" -> free to take, "confirmed" -> ready for sponsoring, "In Progress" -> sponsor is looking, "Incomplete" -> needs work.
[18:36] <Ursinha> Ampelbein, shouldn't it be "Triaged" ready for sponsoring, instead of "Confirmed"?
[18:36] <Ursinha> that would solve the issue
[18:36] <Ampelbein> Ursinha: Yes, when the sponsoree is actually able to set that.
[18:36] <Ursinha> besides, the bug is ready to be worked on when it has enough information to be fixed, that should be Triaged
[18:36] <Ursinha> ah, I see the point
[18:37] <bdmurray> I thought the sponsoring process used team subscription to indicate it was ready for sponsorship
[18:37] <bdmurray> Anyway, I'd bring this up with a Launchpad stakeholder
[18:38] <bdmurray> I believe bryce is the community one
[18:38] <Ursinha> he is
[18:39] <Ampelbein> bdmurray: See https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue
[18:39] <Ampelbein> (Section "Notes for contributors"
[18:40] <broder> fwiw, i, as a sponsor, don't really pay a lot of attention to bug status when i'm looking at a bug
[18:40] <broder> i use whether or not ~ubuntu-sponsors is subscribed as an indicator
[18:40] <broder> and i unsubscribe ubuntu-sponsors when i determine something isn't ready
[18:41] <Ampelbein> Me mostly too, but when looking through e.g. the ftbfs bug list, I ignore anything with Status "Confirmed" as that usually indicates someone already worked on the issue.
[18:42] <Ampelbein> And an auto-confirmed bug could potentially fall through the cracks. I agree it's not a very very important problem, and I'll bring it up on the list.
[18:42] <tumbleweed> Ampelbein: you can't trust Confirmed, LP does that automatically these days
[18:42] <Ursinha> Ampelbein, how hard would it be to ask people to add a tag instead?
[18:42] <Ampelbein> tumbleweed: ... yes, that's the whole discussion we have ;-)
[18:43] <tumbleweed> ah, I see
[18:43] <tumbleweed> I'm using Triaged instead of Confirmed for process bugs
[18:45] <bdmurray> any other topics?
[18:46] <bdmurray> okay thanks everyone
[18:46] <bdmurray> #endmeeting
[18:46] <meetingology> Meeting ended Wed Feb 22 18:46:32 2012 UTC.
[18:46] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-18.05.moin.txt
[18:46] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-18.05.html
[18:46] <Ursinha> thanks bdmurray
[20:05] <gilir> #startmeeting Lubuntu Team Meeting
[20:05] <meetingology> Meeting started Wed Feb 22 20:05:13 2012 UTC.  The chair is gilir. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:05] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[20:05]  * gilir looks for people around :)
[20:05] <MrChrisDruif> o/
[20:05] <phillw> o/
[20:05] <wxl> …o/
[20:05] <david_j_r> `°  (back row)
[20:06] <gilir> agenda : https://wiki.ubuntu.com/Lubuntu/IRC%20Meetings/Agenda
[20:06] <Yorvyk> o/
[20:06] <gilir> no actions from previous meeting, so we can move to the next item :)
[20:07] <gilir> if you have a weekly report planned for the meeting, but nothing to say, just ping me outsite the room, so I can skip the item
[20:08]  * gilir tries to make the meeting faster :)
[20:08] <gilir> #topic phillw - Weekly report - Update from QA meeting and team
[20:08] <phillw> Because of confusion caused by re-spins during testing, an email will be sent out to the qa mailing list when re-spins happen. When lubuntu iso's are re-spun, I'll forward them to the main lubuntu mailing list in order to keep the chat down :)
[20:09] <wxl> respins hm?
[20:09] <phillw> when a fault in the iso requires it to be re-issued.
[20:10] <wxl> oh like them being too big ;)
[20:10] <phillw> such as a major bug.
[20:11] <phillw> wxl: the milestone releases are always on-size, it is just the dailys that suffer. Now we aer post-freeze, this also should mean the dailies are CD sized.
[20:11] <phillw> s/aer/are
[20:11] <wxl> delightful as i'd like to do some ppc/ubuntu testing to compare to issues with lubuntu testing
[20:12] <gilir> beta 1 is next week, testing for it should start shortly :)
[20:13] <gilir> phillw, anything more for QA ?
[20:13] <MrChrisDruif> Just an educated guess: after their released?
[20:13] <phillw> it is for that reason they're going to let us know when the Release Candidates for the beta 1 are up. If one of them has a major problem, it will be re-spun in time for beta.
[20:14] <phillw> that's all from QA :)
[20:14] <MrChrisDruif> they're*
[20:15] <phillw> MrChrisDruif: the test versions of each mile-stone is put on test a few days before the mile stone is released. in this case it will be for beta 1
[20:16] <gilir> if people want to start ISO testing for beta 1
[20:16] <phillw> MrChrisDruif: the rather involved proceedure is documented at https://wiki.ubuntu.com/Lubuntu/Testing#QA_testing_of_Milestone_releases
[20:16] <gilir> they can probably ask question on IRC when they start
[20:17] <MrChrisDruif> *noted* (by meetingology)
[20:17] <gilir> or read documentation send by phillw :)
[20:18] <StephenSmally> Damn, i'm always late
[20:18] <phillw> I do ask that testers do join the lubuntu-qa team, even if just until final release
[20:18] <gilir> ok thanks phillw :)
[20:18] <phillw> https://launchpad.net/~lubuntu-qa
[20:18] <gilir> nothing to report for the next items, so I move directly to dev team report
[20:19] <gilir> #topic gilir - Weekly report - Update from Devs teams
[20:19] <gilir> a few thinks to report
[20:19] <gilir> thinks / things
[20:20] <gilir> ISO are under 700 Mo :)
[20:20] <gilir> and maximised windows by default is turn off
[20:20] <Yorvyk> \o/
[20:20] <gilir> artwork was updated, but there is still issue with the theme
[20:20] <david_j_r> :D
[20:21] <gilir> no need to report bugs so far, we are working on it :)
[20:21] <gilir> any questions ?
[20:22] <gilir> ok, moving to next item :)
[20:23] <gilir> #topic Yorvyk - Guidelines for alternative apps in distro
[20:23] <StephenSmally> This is interesting
[20:23] <StephenSmally> (if i got what that means)
[20:23] <gilir> Yorvyk, you want to start with it ?
[20:24] <Yorvyk> OK
[20:25] <Yorvyk> People keep suggesting apps for Lubuntu or replacement apps some of whichg are suitable possibilities others are not.
[20:26] <Yorvyk> I would like to set up somewherre to keep track of them so they can be looked at in more detail but we could do with some sort of guidelines for suitable apps to be considered.
[20:26] <MrChrisDruif> I agree
[20:27] <StephenSmally> Yep, for example some people want LibreOffice on Lubuntu by default, which is clearly not possible (or not useful)
[20:27] <Yorvyk> Is this a good idea and should we through it open to the mailing list forum?
[20:27] <gilir> IMO, testing and considering new application by default is very time consuming, for not so much advantages
[20:28] <MrChrisDruif> It's not suitable for a default installation, but that isn't the current subject ^_^
[20:28] <jmarsden|work> If you care enough to do it, you write the guidelines and manage a wiki page listing the suggestions.  Keep this kind of "suggstions" away from the devs...
[20:28] <gilir> I like the idea to make a page with some advises, balcklisted apps, and already discussed apps
[20:29] <david_j_r> Yes: "already discussed apps" helpful for new users (like me)
[20:29] <jmarsden|work> david_j_r: Why?  As an end user, you can install any app you choose.  The issue is what to *include* on the Lubuntu CD and install by default.
[20:30] <gilir> Yorvyk, maybe you can start to gather some ideas on a wiki page ?
[20:30] <Yorvyk> The problem is apps have been discussed and a re 'lost' in the mailing list somewhere.
[20:30] <MrChrisDruif> jmarsden|work; why would the user-base suggestions be kept from the devs? If they are properly supported by factual tests etc?
[20:30] <wxl> what happened to that whole voting idea?
[20:30] <jmarsden|work> MrChrisDruif: RIght, once a cycle the devs can look at the list, but the devs should not deal with all the suggestions as they flow in...
[20:30] <StephenSmally> Consider that a list of suitable apps for Lubuntu (for example how to choose a photo manager) would be a good idea for newcomers
[20:30] <david_j_r> jmarsden|work: That's what I mean: new types might want something in distro that is already crossed off for good reason
[20:31] <Yorvyk> THis isn't for the ISO.  Unless some app is no longer supported and we need a replacement.
[20:31] <jmarsden|work> david_j_r: OK... new types shouldn't want things "in the distro", they should just add what they themselves want :)
[20:31] <david_j_r> yep :)
[20:31] <david_j_r> (apologies if I am confusing "ISO" with "distro" -  my bad)
[20:32] <gilir> Yorvyk, ok, so the subject is only on application suitable to be used on Lubuntu (not to be installed by default)
[20:32] <jmarsden|work> Yorvyk: if it isnt for the ISO, then every app is perhaps suitable for *some* user out there... so the list of apps is the entire set of apps in the repositories :)
[20:32]  * gilir didn't understant too :-/
[20:32] <gilir> jmarsden|work, but you know some apps is not really recommends for Lubuntu users :)
[20:33] <jmarsden|work> gilir: Well, maybe some Lubuntu users run on a 8 core machine with 32GB RAM... for them, every app could be "suitable" :)
[20:33] <gilir> jmarsden|work, sure, but such people doesn't need the advises :)
[20:34] <jmarsden|work> It's pointless having a list of things that are not suitable for inclusion, but may be OK for some users... you'd have to define a list for "users with 2GB", "users with 4GB", users with quad cores... etc etc...
[20:34] <gilir> I still think Lubuntu is primary for people with computers with low specs
[20:34] <jmarsden|work> I agree.
[20:34] <jmarsden|work> and for them, the included apps are suitable.
[20:34] <Yorvyk> My thought was to try and gather a list of truly lightweight apps somewhere. so that we can offer a suiable alternative if somebody would like to use something that won't run on a low resouce machine.
[20:35] <MrChrisDruif> I *thought* the list was for proposal of inclusion into the default installation? What other use would there be for such a list?
[20:35] <phillw> Yorvyk: I think, as suggested, a wiki page would be excellen t for that.
[20:35] <gilir> jmarsden|work, maybe just adding a note on this page, like "If you want to keep Lubuntu fast on your old computer ..."
[20:35] <jmarsden|work> Yorvyk: if an app is truly lightweight, then it *will* run on a low resource machine...
[20:35] <Yorvyk> After some testing and maybe a vote suitable apps could be highlighted in LSC
[20:36] <wxl> Yorvyk: this is similar to a suggestion that i made before. it requires us to define what makes an app "suitable" and then it requires a lot of work testing apps.
[20:36] <StephenSmally> Definitively possible
[20:36] <jmarsden|work> Yorvyk: If you want to do a wiki page listing such apps, go for it.
[20:36] <StephenSmally> well, is not so difficult define if an app is light
[20:36] <wxl> yeah in the end i think something like a wiki page like jmarsden|work is suggesting makes the most amount of sense
[20:37] <gilir> Yorvyk, yes, I think you have to start this page, before futher discussion can happen :)
[20:37] <wxl> StephenSmally: if you have 256mb of ram versus 1.5gb i'm thinking you probably have a different definition :D
[20:37] <StephenSmally> well, anyway if doesn't have too much dependencies and not use too much ram
[20:38] <Yorvyk> I'll get something set up and thenm I think what I want may make more sense.
[20:38] <wxl> StephenSmally: but what's "too much?
[20:38] <StephenSmally> it depends on the application
[20:38] <gilir> #action Yorvyk to start the suggested apps wiki page
[20:38] <meetingology> ACTION: Yorvyk to start the suggested apps wiki page
[20:39] <StephenSmally> a simple utility (as a text editor) shouldn't use more that 15 Mb RAM on an i386 machine
[20:39] <StephenSmally> *than
[20:39] <MrChrisDruif> An other suggestion might be an AskUbuntu question, where people could vote on answers (like "What is the best lightweight app?")
[20:39] <wxl> i still think the voting idea is best
[20:39] <gilir> MrChrisDruif, but you have to do it for each type of application ...
[20:39] <wxl> of course one can vote with edits on a wiki :D
[20:39] <StephenSmally> And also a light app is an app written in a compiled language (C is the lighter)
[20:40] <StephenSmally> that's the main reason why i'm (and michael) porting lsc to vala
[20:40] <gilir> StephenSmally, you have to consider the memory, cpu and disk usage, depencencies ...
[20:40] <jmarsden|work> Take the definition of what is small enough/light enough outside this meeting... :)
[20:40] <gilir> there are many aspects to consider when you talk about lightweight applications
[20:41] <StephenSmally> yep, but look at the dependecies is a good hint
[20:41] <gilir> Yorvyk, anything to add ?
[20:41] <wxl> i think maybe we should move on, eh? we've beat this idea to death in the past. i think the action will move it forward if it happens. i'd be happy to add to the wiki personally.
[20:41] <StephenSmally> for example, compare goobox and asunder (cd ripper), goobox depends on Gnome, so out
[20:41] <Yorvyk> I think what is wanted is
[20:41] <gilir> ok thanks Yorvyk :)
[20:41] <StephenSmally> Yorvyk: i am available to do some test
[20:42] <gilir> #topic StephenSmally - Lsc in Vala and Elementary Os team collaboration
[20:42] <StephenSmally> Well
[20:42]  * gilir is curious about this one :)
[20:42] <Yorvyk> StephenSmally: OK
[20:42] <StephenSmally> I asked the elementary os team to "steal" some code from slingshot for lxlauncher
[20:43] <StephenSmally> obviously is GPL, but anyway i wanted to ask the permission
[20:43] <StephenSmally> they were very kind and fine
[20:44] <StephenSmally> and they asked me if there is something we (lubuntu team and eos team) can collaborate on
[20:44] <gilir> as long as the copyright attribution and the licence is fine, it should not be a problem
[20:44] <gilir> but it's nice to ask :)
[20:44] <StephenSmally> so we decided to write a common backend for lubuntu software center and elementary app center
[20:44] <StephenSmally> so the next lsc version will be written in vala using PackageKit
[20:44] <gilir> StephenSmally, sounds good :)
[20:45] <StephenSmally> i also plan to modify the UI
[20:45] <StephenSmally> (as somebody may has seen on facebook)
[20:45] <gilir> StephenSmally, as long as it will not bring gnome depends, it's ok to work with them :)
[20:45] <StephenSmally> no one, gilir
[20:45] <StephenSmally> ;-)
[20:46] <StephenSmally> here a mockup of what i think http://imagebin.org/index.php?mode=image&id=200267
[20:46] <gilir> StephenSmally, UI freeze should be in effect tomorow for 12.04
[20:46] <StephenSmally> of course, i'm planning for precise+1
[20:46] <gilir> StephenSmally, ok :)
[20:47] <StephenSmally> i asked rafaellaguna for some hints
[20:47] <StephenSmally> anyway, i think a collaboration with the two teams would be a good thing
[20:48] <gilir> StephenSmally, you can also ask alexander, he worked on UI stuff also
[20:48] <StephenSmally> anyway, only the core of the apps will be the same, the UI is absolutely under our control XD
[20:49] <MrChrisDruif> Re on the previous topic: I was just throwing it out there ^_^
[20:50] <StephenSmally> anyway, the team guys are very available, so if you want to ask something i think you can ask at<EMAIL_ADDRESS>[20:50] <gilir> StephenSmally, sounds good, keep us informed about the progress :)
[20:50] <StephenSmally> i'll absolutely do
[20:50] <wxl> oh!
[20:51] <wxl> sort of side note but StephenSmally have you seen the lsc crash bug on boot in precise?
[20:51] <MrChrisDruif> I also saw a post on Lubuntu Official facebook page about LSC
[20:51] <gilir> wxl, bug number ?
[20:51] <wxl> one sec there's a few of them
[20:51] <MrChrisDruif> StephenSmally; ^
[20:52] <StephenSmally> yes?
[20:53] <wxl> aw shoot
[20:53] <wxl> they're darn private bugs
[20:53] <MrChrisDruif> I thought the outset of LSC was creating a lightweight edition of USC? Now the "developer preview" was without icons at all?
[20:54] <wxl> there's one public https://bugs.launchpad.net/ubuntu/+source/lubuntu-software-center/+bug/938399
[20:54] <wxl> lubuntu-software-center-build-db crashed with KeyError in /usr/sbin/hostname-software-center-build-db: 'ppc'
[20:54] <wxl> seems to be ppc specific
[20:54] <StephenSmally> MrChrisDruif: only the categories are without icons, we can add it if we want
[20:54] <wxl> always on boot
[20:55] <StephenSmally> wxl: gosh! got it, i'll fix it
[20:55] <wxl> after updating, it goes away
[20:55] <gilir> wxl, bug is not private anymore
[20:56] <gilir> StephenSmally, anything to add ?
[20:56] <StephenSmally> mmm, no, the bug should be fixed in an half hour
[20:56] <wxl> thx StephenSmally :)
[20:57] <StephenSmally> is there anybody on ppc right now?
[20:57] <wxl> right now, no, but my machine is at home and can test in ~+6 hours
[20:58] <StephenSmally> thank you
[20:58] <wxl> phillw: have we ever got anywhere re: running ppc in qemu?
[20:59] <phillw> wxl: I asked a few people, never got a reply :/ I will have another dig around to see what I can find.
[20:59] <wxl> StephenSmally: i see it with the live system and the resulting install but after updating it is gone. so the next iso that comes out from your update, i can test
[20:59] <StephenSmally> thanks
[20:59] <StephenSmally> well, i'm done.
[20:59] <wxl> thx
[20:59] <gilir> wxl, to test, you have to remove lsc, and re-install it
[21:00] <gilir> StephenSmally, ok, thanks :)
[21:00] <wxl> gilir: i can try that too but i want to see how it works in situ ;)
[21:00] <gilir> #topic other question ?
[21:00] <phillw> o/
[21:00] <david_j_r> o/
[21:00] <gilir> phillw, ok
[21:01] <phillw> not a question... the new draft for ubuntu.net is coming along well - heck, they've even got volunteer translators already. Well done!
[21:01] <phillw> *lubuntu,net*
[21:01] <phillw> it is at http://www.whiteboar.info/ for those interested.
[21:02]  * gilir have to read the entire thread on the mailing list ...
[21:02] <phillw> fortunately, it is being kept on one email subject now, instead of several :)
[21:03] <gilir> yes, it's nice :)
[21:03] <gilir> maybe a topic to discuss next meeting
[21:03] <gilir> david_j_r, yes ?
[21:03] <david_j_r> Did Leszek get for LXKeymap, and did "obkey" make it in for 12.04? (Multilingual computing something of interest to me.)
[21:03] <david_j_r> *help for...
[21:04] <david_j_r> Maybe that should have been question for dev part of agenda.
[21:04] <gilir> david_j_r, not yet, some bugs still need to be fixed in the new version
[21:04] <david_j_r> OK - thanks!
[21:04] <gilir> nothing new since last week
[21:04] <gilir> ok, no more question, time to end :)
[21:04] <gilir> thanks everyone :)
[21:05] <gilir> #endmeeting
[21:05] <meetingology> Meeting ended Wed Feb 22 21:05:00 2012 UTC.
[21:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-20.05.moin.txt
[21:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-22-20.05.html
[21:05] <gilir> I'll update the wiki later tonight, unless someone want to do it now :)
[21:06]  * MrChrisDruif only cares that it gets done, feel free gilir
[21:06] <phillw> gilir: thanks, as always, for chairing :)
[21:07] <phillw> gilir: if you've other stuff to do (as you usually have) - I'll get it done.