/srv/irclogs.ubuntu.com/2011/12/14/#ubuntu-meeting.txt

MrChrisDruifMeeting?00:00
Unit19300:0000:00
IAmNotThatGuybodhi_zazen, Hi00:00
bodhi_zazenAnyone here for the bt meeting ?00:00
bodhi_zazen#startmeeting00:00
meetingologyMeeting started Wed Dec 14 00:00:54 2011 UTC.  The chair is bodhi_zazen. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.00:00
meetingologyAvailable 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 #votesrequired00:00
IAmNotThatGuyo/00:00
bodhi_zazenAgenda - https://wiki.ubuntu.com/BeginnersTeam/Meetings00:01
* Unit193 00:01
bodhi_zazen[link]https://wiki.ubuntu.com/BeginnersTeam/Meetings00:01
bodhi_zazen[LINK]https://wiki.ubuntu.com/BeginnersTeam/Meetings00:01
IAmNotThatGuyAll of you raise your hands o/00:01
MrChrisDruifo/00:01
bodhi_zazen[link] https://wiki.ubuntu.com/BeginnersTeam/Meetings00:01
ashickur-nooro/00:01
MrChrisDruifIt accepts quietly bodhi_zazen00:02
IAmNotThatGuybodhi_zazen, I believe it will set it and show in  logs00:02
bodhi_zazen[TOPIC] Focus Groups00:02
=== meetingology changed the topic of #ubuntu-meeting to: Focus Groups
bodhi_zazenI think focus groups have been discussed before00:03
bodhi_zazenany focus group leaders here ?00:03
IAmNotThatGuyFor the time being, No. duanedesign is working on the MOTU FG00:03
bodhi_zazenany suggestions for focus groups ?00:03
IAmNotThatGuyI am not seeing any other FGs active00:04
MrChrisDruifIAmNotThatGuy; I might be able to get some activity back in the Wiki FG00:04
MrChrisDruifBut I'm not the Head of it00:04
* bodhi_zazen thinks too much time is spend discussion how FG will work and not enough time forming groups to accomplish specific tasks00:04
bodhi_zazenHow about if we start with one or two tasks , define the task, see who is interested ?00:05
ashickur-noor+100:05
IAmNotThatGuybodhi_zazen, it will be the Heads to design the FGs. We can find people whoo has time and nominate him/her for the FG and let them form a group and work on structuring00:05
JackyAlcineo/00:05
bodhi_zazenspeak up JackyAlcine00:06
MrChrisDruifI think he just said he was here ;-)00:06
bodhi_zazenI would make the FG very task specific00:06
JackyAlcine+1 to bodhi_zazen's idea.00:06
JackyAlcineI've been interested in the Dev FG for a while, I don't have the time to run it, but I'd love to be active in it.00:06
bodhi_zazenAny additional suggestions for the focus groups ?00:07
IAmNotThatGuyNope00:08
MrChrisDruifAssigning tasks like updating a certain section on the wiki (for Wiki FG of course)00:08
bodhi_zazenI think they sort of die off because everyone gets excited about a topic, like development or packaging, without any tasks , so excitement dies out00:08
JackyAlcinePerhaps passing bitesize bugs to the Dev FG.00:08
JackyAlcinebodhi_zazen: +100:08
bodhi_zazenlearning to file a bug report -> triage bug reports ?00:09
JackyAlcineand packaging's a world of hurt in itself :P00:09
IAmNotThatGuyor we have many project ideas, where we can pull the new comers and work on00:09
bodhi_zazenwe could do a classroom session on either packaging or bug reports00:09
IAmNotThatGuyNoted00:09
ashickur-noorbodhi_zazen: +100:09
JackyAlcineIAmNotThatGuy: working on a project from scratch is hard work.00:09
bodhi_zazen[idea] can the people interested in a focus group identify a task or classroom session - update the wiki page - and engage the team for assistance ?00:10
Unit193Do current tasks not count?00:10
IAmNotThatGuyI think it can be done00:11
bodhi_zazenOther suggestions ?00:11
IAmNotThatGuyJackyAlcine, But it is the best way to learn both team work and complete development. ;]00:12
bodhi_zazen[topic] Team participation00:12
=== meetingology changed the topic of #ubuntu-meeting to: Team participation
coalwaterwhats the question :D00:12
bodhi_zazenAs a general reminder to the team, our goal is to help new users, new to ubuntu (beginners) and new to the ubuntu community00:13
bodhi_zazenPlease help out on IRC, forums, askubuntu ...00:13
JackyAlcineTrue.00:13
ashickur-noorYa00:13
bodhi_zazenInvite people to the team to participate, if they are lost and need direction00:13
* MrChrisDruif has lost interest in helping on the main help channels. Also pretty busy on other parts in the community00:14
ashickur-noorI am thinking of it, to invite people00:14
MrChrisDruifBut I'm still answering questions when they show up on the team channel00:14
MrChrisDruifOr anywhere else for that matter00:14
IAmNotThatGuyto be honest, The main thing missing is that we have people around, but none stepping forward to blast google and help the beginner. Thats the way I learnt about Ubuntu through the community00:15
ashickur-noorMe too00:16
IAmNotThatGuyMost of the time, what people think is that they don't know the answer and it is better to let someone help. But before coming to a decision, Just search in the net and see whether you can help. ;]00:17
MrChrisDruifLike I said, I'm pretty preoccupied with being active in the community myself...00:17
IAmNotThatGuyMrChrisDruif, Gotcha00:17
MrChrisDruifI know your not pointing any fingers around, but still...=]00:18
JackyAlcineI do my best whenever I think I can help. :$00:18
bodhi_zazenAll good ideas00:19
ashickur-noor:-)  I also do it, when ever anybody need help I try my best00:19
IAmNotThatGuySo, the main point to remember from now is, "UBT's goal is to support the Beginners seeking help". So, try engaging some time in the support channel =]00:19
bodhi_zazen[idea] Try to be more proactive, even if it is for 10 minutes, do something and solicit team participation ;)00:19
IAmNotThatGuybodhi_zazen, and I am not sure whether people idling in #ubuntu-beginners are active in IRC. I see many nick idling for years without talking a word00:20
bodhi_zazensuch is irc00:20
IAmNotThatGuy;P00:20
ashickur-noorIRC00:20
ashickur-noorwhat is IRC?00:20
coalwaterthis is00:20
bodhi_zazen[topic] Open floor00:20
=== meetingology changed the topic of #ubuntu-meeting to: Open floor
ashickur-noorthis is a common talk in my local community00:21
coalwaterwhat we are talking through is irc ashickur-noor00:21
bodhi_zazenany other suggestions / comments / agenda items ?00:21
ashickur-noorcoalwater: I know that00:21
ashickur-noorI am talking about my local community, who only know FB00:21
ashickur-noor:-D00:21
ashickur-noorWhich makes me mad some times00:22
bodhi_zazenFluxBox ?00:22
bodhi_zazenFramBuffer00:22
bodhi_zazenThe team is what you all make of it00:22
IAmNotThatGuybodhi_zazen, Regarding FG, for the time being, lets go with duanedesign With MOTU and Wiki with myself and MrChrisDruif. If people comes forward for taking up the other groups, then we can officially bring them in. What do you think?00:22
bodhi_zazenSounds good so long as the FG have tasks and spam -team looking for support00:23
IAmNotThatGuyMeanwhile, I will discuss with jacky and you in setting up the base for -dev team00:24
bodhi_zazengreat00:24
ashickur-noorgreat00:24
bodhi_zazenOther agenda items questions ?00:24
coalwateryou're gonna create a -dev team?00:25
MrChrisDruifI had one, but forgot it later =]00:25
IAmNotThatGuycoalwater, Set a platform for -dev team. (We already have one ;P)00:25
coalwateri know, thats why i was a little confused00:26
coalwaterso um whats this platform00:26
IAmNotThatGuybodhi_zazen, Will we be setting up a separate membership for each FG?00:26
bodhi_zazenNot unless the FG are active00:27
IAmNotThatGuycoalwater, Will come back to you in a minf =]00:27
IAmNotThatGuyokay00:27
bodhi_zazenOnce they are active, FG lead can decide00:27
bodhi_zazenI suggest open team, informal membership00:27
bodhi_zazenpeople spend too much time with membership, not enough time doing, and then membership becomes a barrior00:28
IAmNotThatGuycoalwater, We have a dev team, without knowing what we have to work with. So, we are planning to find and list projects and places to find bug reports so that BT dev team can work on it and help them learn and contribute =]00:28
coalwaternice00:28
IAmNotThatGuy+1 bodhi_zazen00:28
ashickur-noorIAmNotThatGuy: +100:28
IAmNotThatGuyAny other topics?00:29
IAmNotThatGuyUnit193, did we miss anything?00:30
bodhi_zazen#endmeeting00:32
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Dec 14 00:32:14 2011 UTC.00:32
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-14-00.00.moin.txt00:32
bodhi_zazenGo forth and activate00:32
IAmNotThatGuyunimix, Update the channel with the next meeting, MrChrisDruif clear the BeginnersTeam/Meetings page and post the minutes of meeting. Thank you all for coming :)00:32
IAmNotThatGuyerr Unit193 *00:33
IAmNotThatGuySure thing bodhi_zazen =]00:33
MrChrisDruifWhere did I sign up for that? =P00:33
unimixIAmNotThatGuy, no problem :)00:34
ashickur-noorbodhi_zazen:  I am not sure about FG00:34
ashickur-noorwhat is focus group?00:34
bodhi_zazena group of people interested in accomplishing a task00:35
bodhi_zazenthe task is their focus of effort00:35
ashickur-noorInteresting00:35
ashickur-noorHow they work?00:35
IAmNotThatGuyMrChrisDruif, We recruited you before 2 meetings I guess ;P00:35
MrChrisDruifFor 2 meetings? I think it can be traced back to the log00:36
ashickur-noorR they belongs to UBT?00:36
bodhi_zazenthey work by people being active to define and accomplish a task , it is sort of a circular argument ashickur-noor00:36
IAmNotThatGuyMrChrisDruif, hahaha. But MoM is for you00:36
s-foxo/00:37
MrChrisDruifMoM?00:37
IAmNotThatGuyHello s-fox. Bodhi ended the meeting :[00:37
MrChrisDruif\o00:37
IAmNotThatGuyMrChrisDruif, Minutes of meeting00:37
ashickur-noorNeed to learn more about FG00:37
MrChrisDruifHaha, it's alright ;-)00:37
ashickur-noorBTW how r u everyone?00:37
MrChrisDruifashickur-noor; did you just got invited for an other channel?00:38
ashickur-noornope00:38
ashickur-noorI attended the last meeting00:38
MrChrisDruifAlright, try this "/join #ubuntu-beginners-team"00:38
bodhi_zazen'lo s-fox00:38
ashickur-noorFrom then I am regular in UB and UBT00:39
ashickur-noorI need some suggestion00:40
ashickur-noormy local fellow Ubuntu users don't know how to communicate in the community00:41
ashickur-noorHow I can teach them about it?00:42
MrChrisDruifashickur-noor; might I suggest we continue this in #ubuntu-beginners-team ?00:42
bodhi_zazenashickur-noor: should probably move the discussion to #ubuntu-beginners-team00:42
MrChrisDruifHaha00:42
IAmNotThatGuyShall we move to #ubuntu-beginners-team and continue the discussion ashickur-noor and MrChrisDruif ?00:42
* MrChrisDruif is off00:42
ashickur-noorI have no problem00:42
=== bladernr_afk is now known as bladernr_
=== EvilJackyAlcine is now known as JackyAlcine
laoshimorn05:36
laoshisry. wrong channel05:37
=== bladernr_ is now known as bladernr_afk
=== apachelogger_ is now known as apachelogger
=== doko_ is now known as doko
=== yofel_ is now known as yofel
=== 18WAAHZ7Q is now known as jacob
=== JackyAlcine is now known as Guest75450
=== [Jacky] is now known as JackyAlcine
=== JackyAlcine is now known as JackyAlcine_
* slangasek waves16:02
* stgraber waves16:03
jodho/16:04
slangasek#startmeeting16:04
meetingologyMeeting started Wed Dec 14 16:04:06 2011 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.16:04
meetingologyAvailable 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 #votesrequired16:04
slangasek[TOPIC] Lightning round16:04
=== meetingology changed the topic of #ubuntu-meeting to: Lightning round
slangasek$ echo $(shuf -e cjwatson barry doko stgraber jodh ev bdmurray slangasek)16:05
slangasekcjwatson barry ev slangasek bdmurray doko stgraber jodh16:05
slangasekev and doko are out, so this should be quick :)16:05
slangasekcjwatson:16:05
cjwatsonSome ubiquity fixes: DPKG_UNTRANSLATED_MESSAGES=1 as requested by bdmurray; armhf support; fix for next button to say "Install Now" more reliably when it's supposed to (bug 766265).16:05
ubottuLaunchpad bug 766265 in ubiquity (Ubuntu Precise) "Ubiquity proceeds to use free space without warning" [High,Fix committed] https://launchpad.net/bugs/76626516:05
slangasek(I'll fill in doko's status for him)16:05
cjwatsonAdded uninstallable output for -updates suites (http://people.canonical.com/~ubuntu-archive/testing/lucid-updates_probs.html et al).16:05
cjwatsonSerious cleanup so I actually have some free space on my SSD ...16:05
cjwatsonSubmitted several more Launchpad branches for review (bug 551510, bug 118227, bug 240965, bug 383044).  This is mostly because it's clear that there's no Launchpad development resource for a lot of these things and they aren't going to get fixed otherwise; in particular it's been a thorn in my side for some time that installer images aren't signed.16:05
ubottuLaunchpad bug 551510 in Launchpad itself "Port to new python-apt API" [Low,In progress] https://launchpad.net/bugs/55151016:05
cjwatsonWorking on getting germinate output generated directly from the database (for foundations-p-image-build-pipeline).  Partly done but I need to rewrite mvo's Supported extra-overrides handling to work with it.  Some germinate fixes to support this.16:05
ubottuLaunchpad bug 118227 in Launchpad itself "main/debian-installer missing from Release files" [Low,In progress] https://launchpad.net/bugs/11822716:05
ubottuLaunchpad bug 240965 in Launchpad itself "publisher doesn't deal with pockets becoming empty" [Low,In progress] https://launchpad.net/bugs/24096516:05
ubottuLaunchpad bug 383044 in Launchpad itself "No GPG signatures for nonstandard installers" [Low,In progress] https://launchpad.net/bugs/38304416:05
cjwatsonConverted libproxy to multiarch.16:06
cjwatsonStarted on investigating bug 709363.  Hopefully I'll have more luck than previously.16:06
ubottuLaunchpad bug 709363 in ubiquity (Ubuntu Precise) "swap partition disappeared during installation" [High,Confirmed] https://launchpad.net/bugs/70936316:06
cjwatson..16:06
barrybug 901840 (cython ftbfs); python 3 porting blog post; udd meeting w/poolie; python-dbus porting - submitted upstream, some parts are already being committed to trunk; will be committing more atomic changes to personal git branch and working with upstream on each smaller change.  done.16:06
ubottuLaunchpad bug 901840 in cython (Ubuntu) "FTBFS due to test failures" [Undecided,Fix released] https://launchpad.net/bugs/90184016:06
* ScottK gives a big +1 on the python3 porting post.16:06
slangasekI just got a chance to read that yesterday... good stuff16:07
barryScottK: thanks!  been some good comments there too16:07
barrythanks16:07
slangasek * sync cricket to unblock IS16:07
slangasek * progress on multiarch: gstreamer stack is nearly done now!  maybe done by the end of the year16:07
slangasek * following up on bootcharts:  trying to figure out why there's still a lot of noise in the numbers (10% variance between two successive runs?)16:07
slangasek * rally planning16:07
slangasek * working with other teams regarding the vulnerable sun-java6 packages that we need to get rid of16:07
slangasek * merging armhf eglibc support into Debian for infinity16:08
slangasek(done)16:08
bdmurrayChanged arsenal reporter light-style.css to use launchpad's status and importance coloring16:08
bdmurrayRepushed arsenal's cbd since it was lost or over written16:08
bdmurrayUpdated bug bot to tag ubiquity bug reports ubiquity-upgrade16:08
bdmurrayInvestigation into ubiquity bugs not matching bug patterns / discovery of bug 90138116:08
ubottuLaunchpad bug 901381 in ubiquity (Ubuntu) "excepthook in gtk_ui.py should write a crash report instead of calling ubuntu-bug" [Undecided,New] https://launchpad.net/bugs/90138116:08
bdmurraymodification to bug bot to not mention sponsors when commenting on reviewer bugs16:08
bdmurrayreview of bug reports for the defect analyst bug dashboard16:08
bdmurraywork on bug pattern consolidation job on cranberry16:08
bdmurrayworking with defect analysts regarding a bug workflow diagram16:08
bdmurrayworking with d3 (javascript graphing) and recent package bugs16:08
bdmurraycreated a team-recently-(triaged|confirmed) bug report16:08
bdmurray done16:08
slangasek(doko)16:09
slangasek- armhf bootstrap, fixing some build failures16:09
slangasek- look for compiler ICE's in the armhf builds, reproduce and file gcc reports16:09
slangasek- llvm/clang/dragonegg updates16:09
slangasek- staring at clang, started to fix the default settings for armel and armhf.16:09
slangasek- python-central demotion, mostly finished16:09
slangasek- GCC and binutils updates16:09
slangasek- syncs and merges16:09
slangasek- gnat build for armhf, still in progress16:09
slangasek(done)16:09
stgraber- Testing tracker16:10
stgraber - Production instance upgraded on Thursday!16:10
stgraber - Spent part of Friday fighting bugs (wrong version of PostgreSQL and squid breaking the API)16:10
stgraber- Flavours16:10
stgraber - Daily automated testing is now running and posting the results to the tracker (showing a week's history on the tracker)16:10
stgraber- Networking16:10
stgraber - New ifenslave has been uploaded, followed by another upload to fix bridging (bug 889423)16:10
ubottuLaunchpad bug 889423 in ifenslave-2.6 (Ubuntu) "802.3ad bonding not configured correctly" [Undecided,Fix released] https://launchpad.net/bugs/88942316:10
stgraber - Started to look at SRUing ifenslave, will need some discussion with the SRU team as the change are quite extensive16:10
stgraber - Started looking at eventifying the vlan package, still need to test and upload16:10
stgraber - Posted review of dnsmasq and discussed with security team about turning it on by default16:10
stgraber - Wrote patches to Network Manager to start dnsmasq with the right parameters (bug 903854)16:10
ubottuLaunchpad bug 903854 in network-manager (Ubuntu) "Change default dnsmasq flags to not include --strict-order and disable caching" [High,Triaged] https://launchpad.net/bugs/90385416:10
stgraber- Containers16:10
stgraber - Sent patch to James to make mountall work in a container without the need for our current lxcguest upstart jobs16:10
stgraber- Installer16:10
stgraber - Going through casper bugs, especially these with patches attached, reviewing/merging and cleaning up some of the code16:10
stgraber- TPM16:10
stgraber - Pushed opencryptoki bugfix as an SRU to lucid, maverick and natty (bug 645576)16:11
ubottuLaunchpad bug 645576 in opencryptoki (Ubuntu Natty) "TPM token fails to reinitialize properly on reload" [Undecided,Fix committed] https://launchpad.net/bugs/64557616:11
stgraber- TODO (pretty much unchanged since last week)16:11
stgraber - Look at the new ifupdown in Debian (beta2), isolate the fix for bug 876829 and SRU to Oneiric16:11
ubottuLaunchpad bug 876829 in ifupdown (Ubuntu Precise) "Oneiric's ifupdown breaks ip aliases" [High,Triaged] https://launchpad.net/bugs/87682916:11
stgraber - Start poking at resolvconf16:11
stgraber - Talk with cyphermox now that he's out of +1 :) (IPv6, complex networking in NM, dnsmasq, VPN stuff, ...)16:11
stgraber - Still need to get my iSCSI test setup online again and then look at the merge...16:11
stgraber(done)16:11
jodhReleased Upstart 1.4. Working on merge of lp:upstart into Ubuntu (icky:16:11
jodhhttp://paste.ubuntu.com/769005/ - thanks to cjwatson for guidance!).16:11
jodhCurrently we have a failing test which appears to be caused by the16:11
jodhbuilds chroot environment. Lots of cookbook updates (prolly release16:11
jodhlater today). Plan: Finish Upstart merge and work on plymouth bug 55374516:11
jodhand bug 849414). My last day before Christmas is Friday.16:11
ubottuLaunchpad bug 553745 in plymouth (Ubuntu Maverick) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()" [High,Triaged] https://launchpad.net/bugs/55374516:11
ubottuLaunchpad bug 849414 in plymouth (Ubuntu Precise) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()" [High,Incomplete] https://launchpad.net/bugs/84941416:11
jodh16:11
slangasekthanks all16:13
slangasekany questions re: statuseses?16:13
slangasek[TOPIC] Bugs16:13
=== meetingology changed the topic of #ubuntu-meeting to: Bugs
slangasekbdmurray: anything new bubbling up this week?16:13
bdmurrayslangasek: no not really16:14
slangasekok16:14
bdmurrayactually bug 818177 has seen some recent activity16:15
ubottuLaunchpad bug 818177 in udev (Ubuntu Precise) "boot failures because 'udevadm exit' times out while udevd waits for an already-dead thread" [High,Fix released] https://launchpad.net/bugs/81817716:15
besmirgoguHi Everybody!!16:15
slangasekbdmurray: I think those comments are misdirected and I'm not sure they're worth following up on individually; we know that we have two other bugs related to udev races still, apw is working on one (bnx2 firmware) and hallyn is working on the other (lvm2) and waiting for me to review/merge16:17
bdmurrayslangasek: okay, that makes sense16:17
cjwatsonWould anyone like to attack bug 545790?  It's on rls-p-tracking, and it has a relatively clear explanation from mdz; it should be a matter of saving errno until it comes time to display it16:17
ubottuLaunchpad bug 545790 in dpkg (Ubuntu) "package PACKAGE failed to install/upgrade: error writing to '<standard output>': Success" [High,Confirmed] https://launchpad.net/bugs/54579016:17
slangasek<crickets>16:19
slangasek:)16:19
slangasekwell, I'll mark that one 'triaged' at least :)16:20
* jodh wonders what a "crashed recycle bin" is...?16:21
slangasekheh16:21
jodhdon't recycle whilst driving I say!16:21
slangasekok, well, that one remains on the list of bugs for us to tackle this cycle then16:23
slangasek[TOPIC] AOB16:23
=== meetingology changed the topic of #ubuntu-meeting to: AOB
slangasekanything else?16:23
cjwatsonor I'll take it, I was just hoping somebody else would :)16:23
slangasekI think everyone else's queue is also full at the moment :)16:23
slangasekbtw, if anyone has outstanding expenses for the year, remember that it's a good idea to do those before you go on end-of-year holidays :)16:24
slangasekand next week will be the last meeting of the year... for whoever's still around by that point16:26
slangasek:)16:26
barry:)16:26
slangasek#endmeeting16:27
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Dec 14 16:27:03 2011 UTC.16:27
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-14-16.04.moin.txt16:27
slangasekthat's all, folks16:27
slangasekthanks!16:27
jodhthanks!16:27
barrythanks!16:27
stgraberthanks!16:28
gemahi everyone, we are about to start the QA Meeting16:59
gema#startmeeting QA Meeting16:59
meetingologyMeeting started Wed Dec 14 16:59:59 2011 UTC.  The chair is gema. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.16:59
meetingologyAvailable 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 #votesrequired16:59
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic:
gemahello, can you raise your hand if you are present and reading ?17:00
* alourie preps his cut of tea17:00
roignaco/17:00
alourieo/17:00
nuclearbob0/17:00
nuclearbober17:00
* alourie s/cut/cup17:00
nuclearbobo/17:00
kalosaurusrexo/ (but I might be afk for a bit in a min)17:00
gemakalosaurusrex: no probs17:00
phillwo/17:00
gemaexcellent, so let's get started17:01
gema#topic Previous Actions17:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Previous Actions
gemaso we had patrickmw with one action from last week17:01
besmirgoguhi new to the meeting17:01
gemahe told me he couldn't make it today, so we'll keep the action for next week17:01
gemahi besmirgogu , welcome!17:01
gema#action patrickmw to publish a list of launchpad projects that conform our automated testing in jenkins17:01
besmirgoguhi everybody17:01
meetingologyACTION: patrickmw to publish a list of launchpad projects that conform our automated testing in jenkins17:01
gema#topic Blueprints Update Precise17:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Blueprints Update Precise
alourieo/17:02
gemaalourie: go for it17:02
alourieregarding previous actions17:02
brendando/17:02
gemayes, alourie17:02
alouriehow about posting smoke test cases that we run?17:02
gemaalourie: do you mean results?17:03
alouriewas it posted somewhere?17:03
alourieno, the tests17:03
gemagive me a sec17:03
roignaci guess, patrickmw should present the list of launchpad project, and there we can get the code for unittests17:03
alourieah17:04
roignacs/project/projects17:04
alourieok, so I'll get back to this later then17:04
alourie..17:04
gemaalourie, roignac , this is the code that runs, as far as I know: https://launchpad.net/ubuntu-server-iso-testing17:04
gemaI am in the process of reviewing it and trying to make some sense of the testing we are running17:04
gemaI don't believe we have test case descriptions yet17:04
gemabut we will17:04
alouriegema: looks like it17:05
alourieok, great, I'll look at it later17:05
gemaalourie: where?17:05
gemaok17:05
gemabrendand: ?17:05
brendandcan you clarify what it means 'conform our automated testing'?17:05
brendandwhat does the package need to have?17:05
gemabrendand: anything that we run and publish results on jenkins17:05
brendandso packages with automated tests?17:06
gemabrendand: no, test cases that we are running automatically in jenkins17:06
gemais the list patrickmw is putting together17:06
brendandgema - ok, i think i understand now17:06
gemabrendand: I am not clear what to expect myself either, so let's keep an open mind17:07
gemamoving on to the blueprints themselves then17:07
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing17:07
gemaWe have created a new dashboard by installing some jenkins plugins, but it is not 100% there yet. We are looking into aggregating results to show all the results for each ISO together and to show build number17:07
gemaLink: https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/17:07
gemaany question?17:08
alourielooks great17:09
alouriegreenish :-)17:09
gemaalourie: that's wrong, today we had a failure in the lab and nothing run17:09
gemait should be all red17:09
alourieha!17:09
gemawe are working on it x)17:09
alouriethat's funny17:09
gemayep17:09
alourieso17:09
alourieI'm thinking17:09
alourieis it possible to have, like, a session on Jenkins?17:10
alourieto realize better what it is and what it isn't?17:10
alourieand how do things work ther?17:10
alouriee17:10
gemawhat do you mean a session on jenkins?17:10
alourie..17:10
gemaahh, like a training session?17:10
alourieyes17:10
gemaindeed, hggdh has been putting a wiki together, I can ask him17:10
alourieeven if it take 15 minutes17:10
gema#action gema to talk to hggdh about some jenkins training for the community17:11
meetingologyACTION: gema to talk to hggdh about some jenkins training for the community17:11
alouriegreat, appreciate it17:11
gemano prob17:11
gemamoving on then17:11
gema#subtopic #subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-boot-speed-testing17:11
gemano update today, since patrick is not here, but he is actively working on this17:11
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-kernel-sru17:11
gemasconklin is not around this week, but he told me he didn't have much to report17:12
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-standard-sru-testing17:12
gemajibel didn't have anything to report either17:12
* gema has been doing some questioning before the meeting :D17:12
jibelthis blueprint is not started yet17:12
gemaah, jibel you are there17:12
gemaok17:12
jibelhi o/17:13
gemaso maybe I should move it to the end of the list17:13
gema#action gema to move the standard sru testing blueprint to the end17:13
meetingologyACTION: gema to move the standard sru testing blueprint to the end17:13
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-test-case-management-tool17:13
jibelI'll start it after https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upload-intermediary17:13
gemayes?17:13
jibelbecause we'll use the same tool to test the packages17:14
gemaok, sounds good17:14
gemaso regarding case conductor17:14
gemaWe've gathered the requirements for case conductor and sent them to the Mozilla QA team. Please, see my last email to the Case Conductor thread in the list for details17:14
alourieo/17:14
gemayes, alourie17:14
alouriewill you have an official "meeting" with Mozilla folks?17:15
gemaalourie: I am not sure, I asked them at the bottom of the email how they wanted to proceed17:15
gemaalourie: I will let you know if it happens, it can be open to more people than just me17:15
alourieok17:16
gemabut I sent the email to the Project Manager because I had the original discussion with him17:16
gemato advice on how to proceed17:16
gemaok, moving on then17:16
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-backlog17:17
gemaany updates on wikis or stuff like that?17:17
roignaco/17:17
alourieo/17:17
gemaroignac: ?17:17
roignacwe have started updating the testcases17:18
roignacsome for nautilus and desktopwhole are under review17:18
gemaroignac: sounds excellent, you could send an email to the list asking for feedback on those17:18
roignacso we need a qualified review for them in docs.google.com shpreadsheet17:18
roignacok, will do17:19
gemayep, I will set some time aside tomorrow for the review17:19
gemaalourie: ?17:19
alourieok, so I wrote a short guide for rewriting test cases17:19
alourieI'd love some feedback for that17:20
gemayou sent the link to the list, didn't you?17:20
alourieyes17:20
alourieadditionally, I started rewriting wiki, so thanks gema for comments17:20
roignacalourie, I've been using it, seems rather useful, thanks17:20
alourieI'd like to have more feedback for wiki as well!17:20
gemaok, it may be good if you asked for the feedback on a more formal email17:20
alouriebut overall, I see it progressing well17:20
alouriegema: I have17:21
gemaalourie: it may help if you say this is the guide , and I would like to have feedback by the end of this week or so17:21
alourieor, rather, you mean more formal that the one I sent?17:21
gemasothat people know when is the deadline17:21
gemayep17:21
gemaa formal review request17:21
alourieah17:21
alourieok17:21
gemaso that fromt he topic of the email, it sounds like there's work to do17:21
* alourie wrotes himself to set deadlines17:21
gemaif you know what I mean17:21
alourieyes, sure17:22
gemait is just an orientation, but tends to give people a sense of urgency :)17:22
alourieindeed :-)17:22
gemaok, I will send you feedback on that tomorrow too17:22
alouriegreat, thank you17:22
gemahggdh: are you around?17:23
alourieso, I will continue working on these items with mail list, it feel it is better for brainstorming and pushing ideas back and forth17:23
gemaalourie: agreed17:23
alourieadditionally, I may write a general guide for writing test cases17:23
alourieI think we need something like that17:23
gemaI thought that is what you wrote on that wiki17:23
alouriethat wiki is more "rewriting" oriented, not a generic one17:24
gemaahh, ok17:24
gemasounds good then17:24
alourieit could be a basis for the generic document17:24
gemaok, excellent17:24
alourieI'm done17:24
alourie..17:24
gemaso, on behalf of hggdh , this is the jenkins documentation he has written:17:24
gemahttps://wiki.ubuntu.com/QATeam/AutomatedTesting/UnderstandingJenkinsResults17:25
brendando/17:25
gemalet us know on the list if there's anything that you don't understand or so17:25
gemabrendand: ?17:25
brendandi wanted to comment on the test cases re-write a bit17:25
gemaok, go for it, I was done with jenkins anyway :)17:25
brendandshould we be taking the opportunity now to split test cases out where they need to be?17:26
gemaI think so17:26
brendande.g. 'Check that user can create files and folders, move files to folders and delete files and folders to Trash'17:26
brendandis not a test case17:26
gemayes, splitting it would give us better understanding of problems, when there is one17:26
roignaco/17:26
gemaand more realistic results17:27
brendandroignac - btw, i'm not pointing the finger at you17:27
gemago for it roignac17:27
gemaspeak freely guys, we are discussing a topic :)17:27
roignacI completely agree with brendand17:27
roignacas testcases should be rewritten17:27
roignacso I guess, we should have a plan for this17:27
gemawhat kind of plan, roignac ?17:27
roignaca list features, at least, like: Nautilus: 1) Cover folder creation, 2)File creation etc.17:28
brendandi think we should say here (and on the mailing list) that you shouldn't shy away from re-working test cases where they don't work17:28
roignacalso, we would need an updated list of application, included in base Ubuntu installation17:28
roignacas writing testcases for Banshee should get less priority than Rhythmbox, as rhythmbox is default one17:29
gemaroignac: I believe kalosaurusrex is working on that17:29
roignacgema, great, that would be very useful17:29
brendandroignac - if test cases are there for an application which is not in ubuntu now then they should be removed or deprecated i guess17:29
alourieo/17:29
gemago for it, alourie17:29
brendandroignac - but writing new ones is outside scope for now mayeb17:29
alourieI want to get focus a little bit here17:29
alourieI'd love to have all test cases rewritten17:30
alouriebut (putting the "effort coordinator hat"), I think we need to handle ISO testing cases first17:30
alourieso that for the next alpha/beta, or when Constructor is ready - we have them done17:31
roignaci'd love to see that as a wiki page - default application and their features17:31
alourieor, at least, some part of them17:31
roignacalourie: agree, ISO testcases should get the highest priority17:31
phillw+117:31
alourieso we would concentrate on them17:31
gemayes, sounds reasonable17:31
alourieat least for the starters..17:31
alourieso I can volunteer myself picking a set of Images to rewrite17:32
gemayep, we could also update the wiki once the test cases are reviewed, so that people can use them before case conductor is online17:32
alourieyes17:32
alourieI'll just pick a couple from each category we have now17:32
gemaok17:33
roignaci've already rewritten desktopwhole testcase - and I'd love to get some feedback on it17:33
gemaindeed, we'll give you feedback17:33
roignacas it might be a good example and a template for installation cases17:34
roignacthanks!17:34
gemaroignac: you may want to have a look at https://wiki.ubuntu.com/QATeam/AutomatedTesting?action=AttachFile&do=get&target=Test+analysis+and+specification+for+Ubiquity.pdf17:34
gemain case it gives you any idea17:34
gemaI put this together last cycle but didn't get the chance to extract any test cases from there17:35
gemabecause we had more pressing matters at hand17:35
gemait may help with the rewriting in some cases, but I don't expect us to run all of them manually17:35
gemathe idea is automating them in the long run17:35
roignacgema, thanks, would be useful17:35
gemaany feedback on it also welcome17:36
gemait's still under review17:36
roignaca basic test is already automated btw, so others will follow, i'm sure17:36
gemayes17:36
gemaok, so moving on to next topic unless someone has anything else17:36
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-qa-regression-testing17:36
gemanuclearbob: ?17:37
nuclearbobI've got an autotest package ready for the new lab hardware17:37
nuclearbobI'm determining whether we want the qrt tests as another package, or whether just a tarball is fine17:37
nuclearbobI've been running them on some daily builds and having good luck so far17:37
nuclearbob..17:38
gemagood thanks, any questions?17:38
gemamoving on then17:38
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-automated-test-submissions17:38
gemaagain, nothing from patrick today17:38
gema#subtopic https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics17:39
gemaI have been doing some code coverage trialling and discovered how to use gcov and lcov. As it happens, the development teams are starting to make changes to their makefiles to enable coverage as well17:39
gemaI need to talk to the tech lead coordinating that to be able to make it happen. I will probably do that in January during our gathering in Europe17:39
gema#subtopic Community Tasks - https://wiki.ubuntu.com/QATeam/TasksPrecise17:39
gemaAnything to report on any of the tasks we are working on that we haven't covered yet?17:40
gemaok, moving on then17:40
gema#topic Update Lubuntu17:40
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Update Lubuntu
gemaphillw: ?17:40
phillwHi, things are going okay - with the slight exception that someone just noticed that Chromium hasn't been building since 25th November last year.17:41
gemaok, we can get the update later if he comes around17:41
gemaahh, you were writing, sorry17:41
phillwThe alpha seems stable enough17:41
gemaphillw: so noone has been using chromium or were they using an outdated version?17:42
phillwas far as I understand there is currently no maintainer for Chromium, so I'm not sure what will happen.17:42
gemaok17:43
gemaanything else? questions?17:43
=== tester_ is now known as alourie|web
* alourie|web has a huge lag17:44
gema#topic Update Xubuntu17:44
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Update Xubuntu
besmirgoguI would have many questions17:44
besmirgogu:)17:44
besmirgogusince i am new17:44
besmirgoguto all this17:44
gemabesmirgogu: we have 14 mins, shoot17:44
besmirgoguhow do i start getting involved17:44
besmirgogupreferably testing releases17:44
gemaby subscribing to the ubuntu-qa list17:45
gemaand saying what you know how to do and what you'd like to do17:45
besmirgoguok17:45
gemasomeone will guide you in the right direction17:45
besmirgoguok thanks17:45
alourie|webbesmirgogu: and bring friends17:45
gemawe are in between releases now, so you have some time to learn how to do the testing before Alpha 217:45
besmirgoguI will try17:45
besmirgoguthat is great news for me17:46
gemain between milestones, I mean17:46
besmirgogui really want to help17:46
gemaexcellent, thanks a lot!17:46
alourie|webbesmirgogu: excellent, thanks17:46
gemaI have to move on now, since charlie doesn't seem to be around17:46
gemaand we need to wrap up the meeting17:46
gema#topic Update Ubuntu17:46
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Update Ubuntu
gemajibel: do you have anything to say here?17:47
gemaok, so moving on then17:48
gema#topic Other Topics17:48
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Other Topics
gemaanything else?17:48
gema#topic Chairing, anyone?17:48
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | QA Meeting Meeting | Current topic: Chairing, anyone?
gemaok, so .. does anyone want to chair next week's meeting?17:49
alourie|webI just wanted to say, amazing week, happy to be part of the team17:49
* gema forgot to ask last week17:49
phillwAs I said, at a pinch I will do so if there are no other volunteers17:49
gemaalourie|web: me too, it is really exciting times17:49
alourie|webI don't have stable schedule, so I won't volunteer for now17:49
gemaphillw: I can do it too, I am around next week, I thought it'd be fair to offer it if someone wants to do it17:49
gema:)17:49
gemaI think we will have a week off for Xmas unless everyone plans to be around17:50
phillwI'll keep my powder dry, in that case :)17:50
gemacool, so I will do it next week!17:50
alourie|webyea!17:50
gemathanks everyone for your time17:50
gema#endmeeting17:50
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Dec 14 17:50:48 2011 UTC.17:50
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-14-16.59.moin.txt17:50
phillwgema: thanks for chairing17:50
gemano problem17:50
alourie|webthanks gema, all17:50
roignacgema, all: thanks a lot =)17:51
besmirgoguthank you all17:51
gemahave a good night everyone, I am going to slowly crawl away from the computer :)17:51
phillwtc - i have another meeting in 2 hours!17:51
* bdmurray waves18:01
* jsalisbury o/18:01
bdmurray#start-meeting18:03
bdmurray#startmeeting18:03
meetingologyMeeting started Wed Dec 14 18:03:32 2011 UTC.  The chair is bdmurray. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.18:03
meetingologyAvailable 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 #votesrequired18:03
bdmurrayHi, its time for the weekly "Bugs" meeting18:03
bdmurrayhttps://wiki.ubuntu.com/BugSquad/Meetings18:03
bdmurray#topic Previous Actions18:05
=== meetingology changed the topic of #ubuntu-meeting to: Previous Actions
bdmurrayACTION: bdmurray update the topic in #ubuntu-bugs regarding meetings: DONE18:05
bdmurrayACTION: bdmurray send bugs meeting announcement before the next meeting - that didn't get done18:05
bdmurray#topic Engineering Team Bug Status18:05
=== meetingology changed the topic of #ubuntu-meeting to: Engineering Team Bug Status
jsalisburyFrom the kernel side, no specific bug to report.  However, a report on new kernel bugs can be found at:18:06
jsalisbury[LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt18:07
bdmurrayI saw that bug 894768 is fixed which is great18:07
ubottuLaunchpad bug 894768 in linux (Ubuntu Precise) "Installation randomly fails with: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 621, in copy_file targetfh.write(buf) IOError: [Errno 22] Invalid argument " [High,Fix released] https://launchpad.net/bugs/89476818:07
jsalisburyyes that was an important bug that was found during iso-testing18:08
bdmurraybug 850264 is still being worked on18:08
ubottuLaunchpad bug 850264 in apt (Ubuntu Precise) "given a foreign architecture of i386 on amd64 machine, and an outdated libc, apt tries to remove libc-bin" [High,Triaged] https://launchpad.net/bugs/85026418:08
bdmurrayI've written a bug pattern for that but it only matches english error messages18:09
bdmurrayso there may be some more duplicates hiding18:09
bdmurraypedro_: do you have anything?18:10
pedro_m nope nothing on the top of my head, i've been doing cleanup in some products like rhythmbox brasero, quite a lot of unattended bugs there18:10
bdmurraypedro_: oh, that reminds me of bug 73759818:12
ubottuLaunchpad bug 737598 in rhythmbox (Ubuntu) "apport package hook should not be run if it is a crash" [Medium,New] https://launchpad.net/bugs/73759818:12
bdmurrayoh, that was really a question in the last comment.18:13
bdmurraypedro_: I actually don't see a package hook for rhythmbox.  Do you know what happened?18:14
bdmurray[ACTION] bdmurray find out where the rhythmbox apport hook went18:16
meetingologyACTION: bdmurray find out where the rhythmbox apport hook went18:16
bdmurray#topic Bug Escalations18:17
=== meetingology changed the topic of #ubuntu-meeting to: Bug Escalations
bdmurrayAre there any bugs that should be brought to our attention?18:17
bdmurrayI'd like this be a time when community members can bring up bugs that are important and aren't seeing progress being made.18:18
bil21albdmurray we dont have the empathy triager now days the bugs are more i am triaging them but i am not so experience but i try my best i am in touch with kenvandine and cassidy those days for this purpose18:20
bdmurraybil21al: as you learn things it would be great if you could document them18:20
bdmurraythat way everyone can learn how to help18:22
bil21alyes but here is a problem i cant set the importance of bug  can you say some one of bug control to do so give empathy 1 hour in a day18:22
bdmurraybil21al: have you asked for someone to set the importance in #ubuntu-bugs.  usually if you say I think bug xyz should be high people will help you out18:23
bdmurraybil21al: alternatively if you email the mailing list with a list of bugs and importances I'm sure it'd be acted on18:24
bdmurraybil21al: How does that sound?18:24
bil21alok18:25
bdmurraygreat18:25
bil21ali will ask some one in our channel.at bug squard18:25
bdmurray#topic Other Topics18:25
=== meetingology changed the topic of #ubuntu-meeting to: Other Topics
bdmurrayIs there anything else to discuss?18:26
bdmurrayWho'll be around for next week's meeting?18:26
bdmurrayI will ;-)18:27
bil21alu are the head  u should be :)18:27
bdmurrayokay, thanks everyone18:29
bdmurray#endmeeting18:29
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Dec 14 18:29:15 2011 UTC.18:29
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-14-18.03.moin.txt18:29
kamusinthanks to you guys :)18:29
bil21albdmuarry: thanks for encouraging me18:30
* gilir takes a seat20:01
jmarsden|worko/20:01
Yorvyk0/20:02
* phillw waits for #startmeeting :)20:02
gilir#startmeeting20:03
meetingologyMeeting started Wed Dec 14 20:03:27 2011 UTC.  The chair is gilir. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.20:03
meetingologyAvailable 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 #votesrequired20:03
gilirhi everyones :)20:03
david_j_r`°    (= back row)20:04
StephenSmallygilir: Hi, hope i'm not late20:04
gilirfor the record, the agenda is still at this page : https://wiki.ubuntu.com/Lubuntu/Meetings/2011113020:04
michaelrawsonhi!20:04
kbhaskarhello :)20:04
StephenSmallyhi michael20:04
gilirhum no, here : https://wiki.ubuntu.com/Lubuntu/IRC%20Meetings/Agenda20:04
michaelrawsonhi stephen.20:04
david_j_rhttps://wiki.ubuntu.com/Lubuntu/IRC%20Meetings/Agenda20:04
giliras usual we will follow the topics on the agenda, if you want to ask a question, just o/20:05
gilir[TOPIC] Review ACTIONS from the last meeting20:06
=== meetingology changed the topic of #ubuntu-meeting to: Review ACTIONS from the last meeting
phillwgilir: roll call?20:07
gilir[LINK] https://wiki.ubuntu.com/Lubuntu/Meetings/20111130#Action_items20:07
* Unit193 20:07
jmarsden|workphillw: You waited, so now you don't get a chance to o/  <grin>!20:07
gilirit should be just after the startmeeting ;)20:08
phillwjmarsden|work: no point o/ before #startmeeting :D20:08
gilirok, I'll improve the introduction next week :p20:08
phillwnp :)20:09
gilirSo from last meeting, I still need to do a summary about ARM testing20:09
wxlok i'm alive20:09
gilirstill an action for me :p20:09
rafaellagunaHi20:09
StephenSmallyhi20:10
gilirAbout QA meeting, I saw last week that it's more about doing a summary of what it's done for QA in Lubuntu20:10
phillwgilir: I have added that for later.20:10
gilirpersonnaly, I can't be at the meeting, and I'm not sure we have enough material to do a full report20:10
gilirphillw, ok, let's talk about this later20:11
gilirYorvyk, I saw a mail about Ubuntu news on the list, do you have more news about it ?20:12
YorvykI forwarded the information they asked for to the news mailing list, all the y require is a link to the team meeting minutes/logs20:13
YorvykI'll do that each week as sson as the logs are up20:13
gilircool, not too much work for us :)20:14
gilirYorvyk, thanks20:14
YorvykYes a nice easy job for a change :020:14
gilirI'll keep the same format for the wiki pages, should be easier even for them to find the information :)20:14
gilirAbout the wiki page, any progress on the prototype ?20:15
gilirwxl, ^20:15
gilirok let's move on, we can about it at the end of the meeting20:17
gilir[TOPIC] LXProxy - we need this tested thoroughly and working20:17
=== meetingology changed the topic of #ubuntu-meeting to: LXProxy - we need this tested thoroughly and working
gilirYorvyk, you want to start ?20:18
YorvykCan we revist this later as I've lost my notes on this at the moment20:18
gilirok20:18
gilir[TOPIC] User - Devel separate mailing list20:18
=== meetingology changed the topic of #ubuntu-meeting to: User - Devel separate mailing list
gilirI'll introduce this one20:19
wxlsorry i disappeared20:19
gilirso, with lubuntu official, we can request a "real" mailing list on https://lists.ubuntu.com/20:19
YorvykGood idea20:19
wxlso it was suggested i do dpkg --list and put it on the wiki which i could have done but i was unable to create a new wiki page20:19
rafaellaguna_Seems we're moving onto Ubuntu servers for everything...20:20
gilirI think it's a good idea to move there, instead of our launchpad mailing list20:20
phillwgilir: too true :)20:20
phillwyou may also request lubuntu cloaks for members whom are deemed worth them.20:20
gilirphillw, that's another topic :)20:20
wxlooh a lubuntu cloak i want one ;)20:21
phillwgilir: soz :/20:21
Unit193Also, need to either move people or packages out of the -desktop ppa20:21
gilirone question remain, do we stay with 1 mailing list, or do we split between devel and users ?20:21
phillwgilir: I'd go for splitting it.20:22
michaelrawsonI say devel and users.20:22
Unit193I'd vote for split20:22
gilirUnit193, we can keep the PPA, I just plan to move the mailing list20:22
wxlmeh i'd say otherwise20:22
YorvykThe problem with splitting them is things tend to get cross posted with a small team.  This can be seen on the LXDE lists.20:22
wxli agree with the logic of organizing but the traffic is so low it's almost pointless, at least at this point.20:22
phillwwxl: you can be member of both20:22
StephenSmallyi think split the mailing lists is a good idea20:23
wxl+1 Yorvyk20:23
rafaellaguna_mee too20:23
wxl(tho i do understand phillw's point)20:23
wxlin general i'm not a big fan of mailing lists anyways so i'm jaded. nevermind me ;)20:23
phillwgeneral support questions and dev's chatting are two different animals.20:23
gilirwell, I think like Yorvyk, there is still low traffic, and it's nice to have everyones in the same place20:24
wxlthere is often overlap20:24
wxlespecially when bugs are unveiled20:24
wxland often times the devs need user help to figure out the symptoms of what's going on20:24
rafaellaguna_gilir: will be complicated when traffic increase?20:24
gilirphillw, but sometimes, support request are bug reports ;)20:24
wxl+1 gilir20:24
gilirrafaellaguna_, probably20:25
jmarsden|workSuggestion: start with one list for now; decide on a volume (say 50 msgs/day? average for 1 week) at which we will split off a dev list20:25
phillwgilir: as I said, there is nothing to stop devs being on the general mailing list. It just reduces chatter for the devs. But, as always in lubuntu - we do what the devs want / need :)20:25
gilirjmarsden|work, it sounds like a good plan20:26
YorvykOne list and see how it goes.20:26
michaelrawsonAlthough I agree, I think it needs to be handled in a way that doesn't make ordinary users feel it's "us and them".20:26
gilirphillw, I don't have a strong feeling about this :)20:26
wxlshould we vote? ;)20:27
YorvykIs it easy to transfer everybody from launchpad to https://lists.ubuntu.com/  or will we have to subscribe to the new list20:27
StephenSmallyIMHO the problem is that if a new user use the mailing list, will see a lot of devs threads, and can feel confused (just like "What the hell are they talking about!")20:27
phillwmichaelrawson: any 'us' (user) can mail to 'them' (devs)20:27
wxli don't see a lot of dev threads at all20:27
gilirYorvyk, subscription, but maybe we can subscribe lubuntu-desktop mailing list for the transition20:27
wxli see the occassional one.. and i like to see it even if it's not directly relevant to me20:27
StephenSmallywxl: you're right, but i hope they'll increase20:27
wxlStephenSmally: good question-- has the lack of a dev list kept the devs from posting more?20:28
michaelrawsonphillw: good point. Although I can see the dev list being obscure, and the lubuntu support list being quite obvious. But I'll shut up. ;)20:28
YorvykAn increase in traffic could make the list look more useful as it can be a bit quiet at times20:28
phillwgilir: Yorvyk how does xubuntu go about their lists? It's great to learn from others :)20:29
Unit193Xubuntu has users and devel20:29
rafaellaguna_<cof>or copy<cof>20:29
YorvykLike everyvody but us they have a dev and user list20:30
gilirok, let's start with 1 mailing list, we can always revisit this decision if we need, and make another one later20:31
michaelrawsonsensible decision.20:32
phillwcould we, as we as we used to do, pop it as a vote on the mailing list for a vote?20:32
phillw-vote20:32
wxloh boy20:32
wxli'd rather not personally20:32
gilirphillw, I don't think it's enough important / strategic for a vote :)20:32
phillwokies :)20:32
wxlif anything i would suggest posting a poll somewhere (not on the mailling list)20:32
jmarsden|workgilir: #action someone to ask for a list on lists.ubuntu.com -- who will do this?20:33
wxli don't want 20,000 messages with yays and nays in them20:33
YorvykLest just se if the devs start to make a lot of noise and take it from there.20:33
* gastly sneaks in20:33
gilir[ACTION] gilir to request creation of a list on lists.ubuntu.com20:33
meetingologyACTION: gilir to request creation of a list on lists.ubuntu.com20:33
gilir[TOPIC] A POC for maintaining Lubuntu FAQ pages20:33
=== meetingology changed the topic of #ubuntu-meeting to: A POC for maintaining Lubuntu FAQ pages
gilirHum is Mohi here ?20:34
YorvykBRB20:34
michaelrawsono/20:34
giliryes michaelrawson ?20:35
michaelrawsonwhat's a POC?20:35
jmarsden|workIf the FAQ is a Wiki page, does it really need a designated person?  everyone with an account can edit it...20:35
phillwgilir: 17:08:40 UTC, which was 3 hours, 27 minutes, and 34 seconds ago.20:35
jmarsden|workPoint Of Contact20:35
phillwhe seems to have vanished?20:35
wxlproof of concept20:35
wxl?20:35
gilirok let's move to the next one20:36
phillwI was chatting to him earlier in the day.20:36
gilir[TOPIC] non-PAE support future20:36
=== meetingology changed the topic of #ubuntu-meeting to: non-PAE support future
gilirok, so there are news about non-PAE support20:36
gilirfor now, the decision for ubuntu is to switch to PAE support by default, but to keep non-PAE available for 12.0420:37
gilirthe non-PAE support will probably be removed for 12.1020:38
Yorvyko/20:38
giliran interesting statistics was given during the meeting : about 5 % of users who report bugs on Launchpad don't have PAE support20:38
wxla surprising twist given linus' caustic opinion on the subject but c'est la vie20:38
YorvykDoes that mean the PAE kernel will be the one the ISOs boot from20:39
YorvykI expect it to be less than 1%20:39
wxlor am i getting confused?20:39
wxloh well, it's fine20:39
gilirmy idea is to keep PAE by default on the live ISO, but using the non-PAE for alternate ISO20:39
jmarsden|workgilir: I wonder if that is people posting bugs from inside VMs with PAE emulation disabled?? :)20:39
StephenSmallycan't we just use general kernel? (probably there are problems, but i don't know'em)20:40
gilirjmarsden|work, I don't have this information ;)20:40
phillwgilir: that makes sense.20:40
Yorvykgilir:  that sounds like a good compromise20:40
StephenSmallyWhy not launch the live with non PAE, then install it if the cpu has support?20:41
gilirStephenSmally, it's better to keep what ubuntu uses, especially for such complex piece of software :)20:41
michaelrawsongilir: you could argue that lubuntu was designed for old hardware such as this.20:41
gilirStephenSmally, the code to auto-detect the PAE support exist in the installer20:41
phillwmichaelrawson: he did, that's why it is there on the alternate :)20:42
wxli guess i'm confused about this: before was pae, now non-pae will be available too, but non-pae is going to disappear in the future? i.e. nothing is changing relative to the past?20:42
gilirStephenSmally, it's probably possible, but we will have to keep 2 kernel on the live ISO20:42
StephenSmallymmm20:42
StephenSmallyright20:42
gilirbut, it's only a problem of space on the CD, which is not so problematic of us20:42
rafaellaguna_michaelrawson: not really designed for that, but works better on those20:42
michaelrawsonphillw: I was referring to his comment to stehpen, but confused now, so never mind me.20:42
gilirof us => for us20:42
gilirStephenSmally, I'll look at this possibility, it's a good idea :)20:44
* wxl is confused.20:44
StephenSmallythanks :-)20:44
gilir[ACTION] gilir to see if we can keep the 2 kernels on live CD20:44
meetingologyACTION: gilir to see if we can keep the 2 kernels on live CD20:44
gilirso with this solution, nothing would change for 12.04 :)20:45
* phillw keeps fingers crossed20:45
gilir[TOPIC] Quick Update on Q.A. Testing.20:45
=== meetingology changed the topic of #ubuntu-meeting to: Quick Update on Q.A. Testing.
gilirphillw, ^ :)20:45
phillwHi, the QA team are setting up auto-testing of the more mundane things.20:46
phillwthey are also liasing with Mozilla about a new testing scheme20:46
phillwthis should take some of the drudgery out of testing RC's20:46
phillwBut, in the process, they are after iso testing, concentrating on *Ubuntu* specific included apps.20:47
StephenSmallyo/20:47
phillw as writing testcases for Banshee should get less priority than Rhythmbox, as rhythmbox is default one20:47
phillwStephenSmally:20:48
StephenSmallyi can't still get what Q.A. is...20:48
gilirquality assurance20:48
wxlmore or less, testing20:48
gilirit's == to testing, to be simple :)20:49
StephenSmallythanks20:49
phillwStephenSmally: Qualtity Assurance, before a milestone release is set upon the public, it is tested heavily against certain criterea20:49
rafaellaguna_but reports go to the same place...20:49
gilirphillw, I saw that there are many efforts to make automated testing for this cycle20:50
phillwon the subject of them concentrating upon standard ubuntu stuff, they are also going to write up a system for adding non-standard ones. Which I think will be AbiWord & GnuMeric20:50
giliri didn't request lubuntu specific stuff, mostly because I'm not sure we will have the time to look at them (the logs of the tests)20:51
phillwThe updating of existing tests is on-going and they are due to write up how to make a new one in the coming weeks,20:51
phillwgilir: you can action that one to me :)20:51
phillwI'm really interested in how the auto-testing pans out across the whole of QA20:52
wxldoes this explain why unity and compiz are installed with lubuntu 12.04? ;)20:52
phillwwxl, I would not know.20:52
gilirphillw, well, the problem it's when it failed, you have to analyze it and find what's going on20:53
phillwI've read that bit :)20:53
gilirwxl, it's bug20:53
jmarsden|workSo they will do tests for Firefox, OOo, Thunderbird... not Chromium, Abiword, Sylpheed, ... if they automated installer testing (using preseeding?) for a variety of install scenarios, that would be good to have for Lubuntu...20:53
* gilir should fix it today ....20:53
phillwthe only other thing of note was the recent mail regarding Chromium failing to build since november last year?20:53
wxlgilir: understand, just didn't know if the root cause had something to do with this automation.20:54
phillwjmarsden|work: it is all pretty much developing week by week. I am keen to keep up to speed with it :)20:54
gilirphillw, what is currently automated ? Only ISO testing or is there some applications already ready for automated testing ?20:56
phillwgilir: jenkins has the list https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/  We're hoping to have the guy give us a run through after the holiday period20:57
phillwcurrently, it is only doing 'core' stuff.20:58
phillwISO testing is not yet automated, it is the 1st priority for the new system.20:58
jmarsden|workphillw: OK... if you need a few test cases to try, installation testing for Lubuntu would be my suggestion :)20:58
phillwjmarsden|work: you will be pleased to know that now I have lubuntu 11.10 on piglet, I have all my VM's back :)20:59
jmarsden|workOh, good, that's progress :)20:59
gilirphillw, I'll be happy if you keep an eye on this QA stuff :)21:00
phillwand my master iso is zsync, so I can chop my iso's over quite quickly21:00
phillwgilir: I'm more than happy to do so.21:00
gilirok, I think it's time21:00
gilirnobody with emergency topic ?21:01
phillwgilir: it was hinted as to if there was a chance of you re-starting your weekly emails to the lubuntu tam?21:01
wxlnope just fix that bug gilir :D21:01
gilirphillw, which email ? the one to the release team ?21:01
phillwyou used to send one to the lubuntu ML. We had to have stuff in by Thursday for you to include it on the Friday email?21:02
gilirI still make an update on Friday for the release team, you can still send me topics to add before it21:03
phillwoops, we are out of time. Can I pm you, please?21:03
gilirthe organisation of the release team meeting changed, I'll do an email to the team about this21:04
gilir[ACTION] gilir to update how the release team is informed21:04
meetingologyACTION: gilir to update how the release team is informed21:04
gilir#endmeeting21:04
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Dec 14 21:04:44 2011 UTC.21:04
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-14-20.03.moin.txt21:04
gilirthanks everyones :)21:05
phillwthanks for making the time both to attend and chair gilir21:05
StephenSmallybye21:05
michaelrawsonbye everyone, thanks to gilir and the other major contributors.21:05
YorvykBye21:05
Unit193Awesome, that's helpful21:05
Unit193Did we ever get back to Yorvyk? He was looking for notes21:06
YorvykIt'll do nest week haven't restored them to the computer yet21:07
gilirYorvyk, put it on the agenda anyway, I will have something to add about lxproxy21:08
MrChrisDruifWhat is up?21:16
rafaellaguna_Welcome, MrChrisDruif21:16
rafaellaguna_well, a pleasure being here :)21:21
MrChrisDruifIndeed21:22
bkerensa=o21:27

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!