/srv/irclogs.ubuntu.com/2010/06/02/#ubuntu-meeting.txt

=== v is now known as vorian
=== JanC_ is now known as JanC
rozasirenaHello05:31
=== lag is now known as lag-afk
=== thunderstruck is now known as gnomefreak
=== lag-afk is now known as lag
=== thekorn_ is now known as thekorn
evhi16:00
mvohi16:00
evKeybuk, barry, cjwatson: ping16:01
* barry waves16:01
Keybukhai16:01
psurbhio/16:03
evah, I thought you were csurbhi16:03
evapologies16:03
psurbhinp :)16:03
evah, on Canonical16:03
evright16:03
evorder is: mvo, surbhi, cjwatson, Keybuk, doko, barry, ev16:03
ev(I totally lucked out)16:03
evready, go!16:03
mvodid: language-selector mini-sprint, software-center work, update-manager work16:04
mvowill do: merges, work on buy-something spec16:04
mvo(done)16:04
cjwatsonhi16:04
evhi cjwatson16:04
psurbhidoing: btrfs support for grub16:04
psurbhicreated a userspace program that reads a raw btrfs image and finds and reads the btrfs files that its requested to16:04
psurbhithis is done for a single device, no subvolume support and no caching16:05
psurbhiin the process of porting this to grub.. needs testing on grub16:05
psurbhilearning how grub-2 compilation/config process and then plan to test through qemu16:05
psurbhishould  be able to show something by next meeting16:05
psurbhiatleast the first version16:06
psurbhi..16:06
cjwatson(done?)16:06
psurbhisorry, yeah16:06
cjwatson:)16:06
cjwatsondone: lots and lots of grub bug triaging and packaging work, bringing us up to a new snapshot (or will do once the alpha-1 freeze lifts); alpha-1 preparation work; landed grub btrfs-probe branch upstream16:06
cjwatsontodo: alpha-1; rearrange grub-rescue-pc so that we can ship EFI images in it and use it as a d-i build-dependencies, without having to solve the thornier grub-pc/grub-efi-* coinstallability problem; sprint in C16:06
cjwatsonambridge part of next week16:06
cjwatson--16:06
KeybukHaven't accomplished anything this week, feeling demotivated :-(  Sorry16:06
Keybuk~16:06
* mvo hugs Keybuk16:07
evdoko?16:08
cjwatsonmy week has been a bit "need more coffee", FWIW16:08
cjwatson(the cynical may point out that all my weeks are like that)16:08
barry;}16:08
* mvo points out that he got some excellent tea from Arne from .tw16:08
barrymvo: nice!16:09
barrydoko going once, doko going twice...16:09
barryquickly python; bug 585617 w/submitted patch. python 2.7 stack ppa created; uploaded py 2.7 from debian + python-defaults; tested on maverick vm; many more packages needed; more emails on debian-python. cj 2.0.3 to fix bug 586088; udd packaging refactor found bug 587058; bug triage.  us holiday; sprint arrangements; dkim draft discussion w/scottk.  eot.16:09
ubottuLaunchpad bug 585617 in quickly "quickly should support user defined template paths" [Wishlist,In progress] https://launchpad.net/bugs/58561716:09
ubottuLaunchpad bug 586088 in computer-janitor (Ubuntu) "cj 2.0.1 in maverick is missing computerjanitord/__init__.py" [Critical,Fix released] https://launchpad.net/bugs/58608816:09
ubottuLaunchpad bug 587058 in Ubuntu Distributed Development "pushing loom to lp, then branching it, loses threads" [Undecided,New] https://launchpad.net/bugs/58705816:09
barryeot == done :)16:10
* ScottK looks up.16:12
cjwatsonev: your turn?16:12
barryScottK: sorry to wake you up :)16:13
barrycjwatson: maybe his net went down?16:13
Keybuklet's carry on without him16:15
cjwatsonyes - can you?  sorry, browser being stupidly slow16:16
Keybukis there anything else?16:17
Keybukwe've done the lightning rounds, and there isn't anything else on the agenda afaict16:18
cjwatsonmay not be :) I'm just looking through the iso.qa bugs for alpha-1 to see if there's anything that needs to be farmed out16:18
dokopong, sorry for being late16:18
cjwatsonthere are a couple of annoying bugs but I'm not seeing anything that's a true showstopper16:19
evback16:19
cjwatsonah good16:19
ev(oh sure, we'll give you 50Mb, but good luck using it because our service has an uptime measured in seconds)16:19
evdone: lots of Hudson work.  I think I now have a sufficient handle on what needs to be done and how to do it, and have made some headway on that front.  Moving onto installer work and helping xnox with usb-creator stuff for the rest of the week, making sure we're on track with those before I go on vacation for a week (on Monday).16:19
evblocked: installer specification.  Working with Michael Forrest in the office on this.  Will continue to push to have it ready ASAP, but I'm going to start working on the obvious items (debconf passthrough, etc)16:19
ev--16:19
evdoko: back to you16:20
barryev: i'm interested in hearing more about hudson, when you have some time16:20
evbarry: I'm free after the meeting if you want to jump into 1-on-116:21
* mvo finds maverick pretty unusuable currently because of the metacity/gtk issues (iirc #584287)16:21
barryev: sounds good16:21
dokodone: eglibc-2.12 packaging, minor toolchain updates, libstdc++ testing against installed libstdc++, llvm/clang updates. toolchain should be in place now, no more major changes expected16:21
doko--16:21
evback to bugs16:21
evI didn't see anything milestoned for alpha 116:21
barrymvo: ouch.  works okay in a command line vm :)16:22
evdoes anyone have any bugs they'd like to raise?16:22
mvobarry: heh :) yeah, I use xfwm4 currently16:22
evmetacity> yikes!16:22
oubiwannI've got something I'd like to bring up... if now's a good time16:23
cjwatsonthere are a couple of 10.04 hardcodings which are fairly trivial16:23
cjwatsonencrypted home is apparently broken: bug 58870516:23
ubottuLaunchpad bug 588705 in debian-installer (Ubuntu) "maverick alpha1 alternate - impossible creation of encrypted /Home" [Undecided,New] https://launchpad.net/bugs/58870516:23
cjwatsonand bug 588696 probably needs some attention (maybe from me)16:23
ubottuLaunchpad bug 588696 in debian-installer (Ubuntu) "In expert mode install partman assign only 2 GB at / partition" [Undecided,New] https://launchpad.net/bugs/58869616:23
evodd16:24
evI'll take 58870516:24
evany other bugs? (then oubiwann)16:24
* oubiwann nods16:24
oubiwannlooks like no more bugs?16:26
evthe floor is yours, oubiwann16:26
oubiwanncool16:26
oubiwannQ-FUNK left a comment on the Foundations 10.10 blog post I did regarding some concerns about the 686 jump16:26
oubiwannhe's also posted some feedback directly to the blueprint16:27
oubiwannhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-m-686-compile/16:27
oubiwannsome of his concerns:16:27
oubiwann"that compiling to anything more recent than 586 essentially makes LTSP unusable since most thin client hardware out there is based on single-chip 586-compatible hardware"16:27
oubiwann"while those chipsets (mainly VIA and Geode) are just a few instructions short of 686, they nonetheless are essentially souped-up 586-compatible"16:27
oubiwannand16:28
oubiwann"basically, it's rather dangerous to push that sudden bump to i686 without considering the compromise of 586 and without putting some sort of safeguard in the preinst script to prevent upgrade on an unsupported arch"16:28
oubiwannQ-FUNK: anything else to add?16:28
Q-FUNKDebian went through a similar machine bump on SPARC and learned the hard way that the only safe way to prevent upgrades on no longer supported hardware is via a preinst segment. I'd suggest that we use this method as well.16:29
oubiwanndoko: what are your thoughts on this?16:29
Q-FUNKand, above all, I'd suggest reconsidering the jump to 686 down to a more conservative 586.16:30
oubiwanndoko: ping :-)16:31
Q-FUNKas it stands, an awful lot of LTSP users (especially schools) had *chosen* Ubuntu for their classrooms.  a few have already responded to the 686 news by saying goodbye.  this is undesirable publicity.16:31
dokooubiwann: the outcome at UDS was, that we did want to switch to i686; I don't mind if we add some code to prevent updates on these processors. not sure, what was done for sparc16:31
oubiwannQ-FUNK: that's sad news... are they open to engaging in a community conversation about this?16:32
cjwatsonI must say I was slightly surprised that we executed the UDS decision so quickly; I had been expecting a mail to u-d-a and a period of consultation.  I probably should have said that in the session16:32
mvo_I can add code to update-manager that checks for no-longer supported processors16:32
cjwatson(I realise toolchain things always get necessarily pushed early)16:32
Q-FUNKthey would be open to engaging conversation if the UDS crowd did.  unfortunetely, -m686 compiled libc6 has already been pushed without consulting the community.16:32
Q-FUNKfrom my perspective, I cannot help but side with the users.  many of the clean-up goals for maverick were decided at UDS without consultatino with the community at large.16:33
evIn fairness, UDS is not a closed event.  Anyone can participate.16:34
Q-FUNKor at least, were implemented without further ado, as in the -m686 libc6 case.16:34
oubiwannQ-FUNK: yes, I see your point, and thought I can see why tool-chain changes need to happen early on in the cycle, I'm also surprised at how quickly this got done!16:35
Q-FUNKmvo_: not everyone uses update-manager.  some old-timers still use apt-get or aptitude on CLI. :)16:35
oubiwanncjohnston: yes, your right -- we should have sent an intent announcement to the list16:35
cjwatson"down to a more conservative 586" - remind me, what was the state in lucid?  I thought it was effectively 58616:36
dokowell, it's not only libc6, but the defaults in the compiler16:36
Q-FUNKmvo_: hence the need to implement the check in preinst -- whatever the final decision for an eventual minimum arch bump might be.16:36
dokono, lucid is still i48616:36
barryoubiwann: is there One True Place where toolchain changes should be sent?16:36
oubiwannbarry: I don't know, honestly... cjwatson?16:36
cjwatson486, ok.  well, I don't think we'd want to build for 586; IIRC that pessimises for many more modern processors.  it's 486 or 686.16:36
cjwatsonubuntu-devel-announce16:36
barrycjwatson: thx16:38
cjwatsonso I'm very concerned about this, but I also know doko has been asking for this for a long time and it seemed at UDS that we must be reaching the point of diminishing returns for the older processors16:38
Q-FUNKanother issue with -m686 is that even if LTSP users stick with Lucid, in 2 years when LTS+1 comes out, they will come to a dead-end.16:38
cjwatsonI'm really quite surprised that there are so many old processors still around; we looked at the release dates of cmov-supporting processors and they were, remind me, 15 years ago or something?16:38
dokoQ-FUNK: well, it's not that quickly, we discussed this at previous UDS'es as well. and we still have the option to build for i586 in a ppa, at least the subset of packages needed fir ltsp. how many are these?16:38
cjwatsonmaybe more like 1016:38
Q-FUNKcjwatson: the whole Geode line and many of the VIA processors are effectively souped-up 586 compabitles.16:39
Q-FUNKcjwatson: that 686 is already old as a16:39
Q-FUNKn architecture is understood.16:40
Q-FUNKit's just that a lot of low-power hardware is based on 586-compatible cores.16:40
dokoQ-FUNK: which ones of the vias are still sold today?16:40
cjwatsonthe first VIA processor to support cmov was definitely quite some time ago; somebody dug up the release date in the UDS session, I think16:40
cjwatsonI like the possibility of being able to move on with standard Ubuntu, but maintain a 586-compatible version in a PPA, particularly if that could be done automatically16:40
cjwatsonQ-FUNK, do you think that could be an acceptable option?16:40
cjwatson(adding a check to libc6.preinst seems like a no-brainer sane thing to do, BTW)16:41
mvo_if we have such a PPA update-manager could add it automatically on upgrade too16:41
Q-FUNKcjwatson: I'm not so convinced. already, lubuntu and the whole LXDE environment only makes sense if older hardware is supported.16:41
mvo_(plus the libc6.preinst thing for people not using it)16:41
cjwatsonLubuntu isn't one of our primary flavours (yet), and it could easily be made to use a PPA build16:42
dokoQ-FUNK: please could you elaborate which/ho many packages are used by these?16:43
Q-FUNKthe only half-usable alternative I can think would be to have separate libc6 etc. packages to build an LTSP chroot, but even then that would not solve the problem of a dead-end for everyone who has something based on e.g. the ION603.16:44
ogranote that m586 thin clients get more and more rare16:44
cjwatsonit's not a dead-end if there's an archive available for them to migrate to16:44
ogramost common ones you can buy since 1/2 years use atom16:44
Q-FUNKogra: there's already huge deployments of 586 thin clients.  that upcoming products will eventually use LPIA is a separate issue.16:45
ograQ-FUNK, LPIA is dead since ages16:45
cjwatsonBTW everything I can find from searching suggests that Geode has cmov support?16:45
dokoQ-FUNK: it's not just libc6, it's *any* package16:47
cjwatsonthread on fedora-devel-list indicates that it works with gcc's -m68616:47
xnoxHow old hardware are we talking here? Pentium Pro 200MHz processor released in 1995 is i686 processor. Can lubuntu run on that? And it will be 17years old by the next LTS release16:47
cjwatsonerr -march=686 or whatever it is16:47
dokoxnox: yes, it can16:47
ograxnox, there are some via based SoC thin clients that are 586, they might still be around16:47
ogravery old via eipa etc16:48
xnoxIMHO supporting 17year old CPU's is good enough for ubuntu.16:48
Q-FUNKcjwatson: IIRC at least the Geode LX is just one instruction short of supporting 686.  slightly older Geodes are based on slightly older x86 instruction sets, slightly higher than 586, but still not a full 686.16:48
* xnox goes to read up about VIA16:48
cjwatsonQ-FUNK: the question is really whether it works with gcc's idea of 686, and the thread on fedora-devel-list indicates that it does16:48
Q-FUNKcjwatson: the bug I filed results from an illegal instruction error I got on a Geode, since libc6 2.12~ was pushed.  if -m686 worked, I don't think that I would have encountered that error.16:49
cjwatsonif there's a slightly different idea in libc, then going back to carrying a libc6-i686 package for that wouldn't be a big deal.  I would like to keep the gcc change if we can though16:49
cjwatsonQ-FUNK: the question is whether that's in libc or due to gcc optimisation, I think16:49
cjwatsonis it possible to determine that?16:49
cjwatsonbecause that will make a huge difference16:49
Q-FUNKcjwatson: good question.16:49
evokay, lets take this to #ubuntu-devel so we can wrap up the foundations team meeting16:50
cjwatsonif it's due to gcc optimisation, then I think the PPA option is the most likely to be feasible16:50
evright, moving on.  Be a buddy, sponsor a contributor - http://qa.ubuntu.com/reports/sponsoring/16:51
xnoxhttp://en.gentoo-wiki.com/wiki/Safe_Cflags/AMD#Geode_LX16:51
Q-FUNKcjwatson: IIRC cjb of the OLPC team has investigated this and narrowed it down to one single instruction. apparently a patch exists to emulate the missing instruction, but it was rejected by the LKML.16:51
xnoxGeode LX 486, Geode GX1 58616:51
Q-FUNKxnox: that should be the other way around16:52
evI didn't see any business in the activity reports.16:52
cjwatsonQ-FUNK: cjb was the person who posted to fedora-devel-list saying that 686 was generally fine for Geode :)16:52
cjwatsonanyway, #ubuntu-devel please16:52
* ev bangs gavel16:52
evright16:52
Q-FUNKalright -> #ubuntu-devel then. :)16:52
evI take it there's no business from the activity reports then16:52
evgood news?16:52
evWe've got a +1 from an ftpmaster for renaming usb-creator to startup-disk-creator so it may go into Debian16:53
evgreat work on that one, xnox16:53
xnoxk16:53
evany other business?16:54
evplease put your activity reports on https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0602 if you have not already done so16:54
evdon't bother mailing them to me, though if you already have, I'll paste it in16:55
evfinally, who wants to run the next meeting (you're not allowed to leave until we have a victim! ;) )16:55
barryev: when you run the shuffle script, who comes up first? :)16:57
mvo_*cough*16:57
evmvo_: winner16:57
evright, thanks everyone!16:57
psurbhithanks ev!16:58
mvo_thanks ev16:58
barrythanks ev16:58
* psurbhi leaves16:58
=== yofel_ is now known as yofel
* charlie-tca waves17:58
* ara waves17:58
* marjo waves17:58
hggdh~o~17:58
* marjo likes the rotating chairperson concept17:59
pedro_hola!17:59
sbeattiemarjo: I bet you do! :-)17:59
sbeattieAlright, might as well get it going.18:01
sbeattie#startmeeting QA Team Meeting18:01
MootBotMeeting started at 12:01. The chair is sbeattie.18:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:01
sbeattieOur agenda, as usual, is at https://wiki.ubuntu.com/QATeam/Meetings18:01
sbeattie# review previous action items (all)18:01
sbeattie# SRU testing -- sbeattie (Steve Beattie)18:01
sbeattie# Bug Day status -- pedro_18:01
sbeattie# Blueprints update -- all18:01
sbeattie# Sound Card Compatibility Testing - awbancroft18:01
sbeattie# Alpha 1 ISO Testing status - ara18:01
sbeattie# Firefox 3.6.4 security update testing - ara18:01
sbeattie# Selection of new chair - sbeattie18:01
sbeattie[TOPIC] review previous action items (all)18:01
MootBotNew Topic:  review previous action items (all)18:01
sbeattiesbeattie: archive SRU reports in the Ubuntu wiki18:02
sbeattieThis is done: see https://wiki.ubuntu.com/QATeam/SRUReports18:02
sbeattie[LINK] https://wiki.ubuntu.com/QATeam/SRUReports18:02
MootBotLINK received:  https://wiki.ubuntu.com/QATeam/SRUReports18:02
sbeattiehggdh: ask stgraber how often they are having Edubuntu meetings (at 19:00 UTC)18:02
hggdhcould not get in contact with him, will grab him today. Comments around state meetings are every week18:03
sbeattiehggdh: yeah, I noticed they had their meeting last week.18:03
sbeattiehggdh: okay, thanks.18:03
sbeattieara: send txwikinger an overview of the ISO tracker work18:03
arasbeattie, done, he is now looking in to it, and will get back to me when he's ready to contribute18:04
sbeattieara: awesome18:04
sbeattieara: send email to awbancroft about Sound Card Compatibility Testing18:04
sbeattieis awbancroft available for that agenda item today?18:04
arasbeattie, done, he replied and told me that he wants to join today18:04
sbeattieOkay.18:04
arasbeattie, but..he does not seem to be around...18:04
sbeattieyeah. :-(18:04
sbeattiemoving on...18:05
sbeattie[TOPIC] SRU testing -- sbeattie (Steve Beattie)18:05
MootBotNew Topic:  SRU testing -- sbeattie (Steve Beattie)18:05
sbeattieSRU Activity report for the past week (since 2010-05-26):18:05
sbeattie lucid::                                                                                        * 24 new packages in -proposed (abcde, aqualung, brasero, cairo-dock-plug-ins, check, docky, drbd8, epiphany-browser, get-iplayer, gnome-keyring, gnome-panel, gxine, harpia, indicator-application, kdepimlibs, libapache2-mod-fcgid, lxinput, nvidia-graphics-drivers, pcmanfm, software-center, themonospot, tomcat6, update-manager, xsane)18:05
sbeattie   * 20 packages pushed to -updates (abiword, cups, deja-dup, evince, exo, gnome-screensaver, gtk+2.0, gtkmm2.4, gvfs, gwibber, kdebase-runtime, librsvg, netbook-launcher, openal-soft, pygtksourceview, python-apt, rhythmbox, simple-scan, totem, vinagre)18:05
sbeattie karmic::18:05
sbeattie   * 2 packages pushed to -updates (eclipse, postgresql-8.4)18:05
sbeattie jaunty::18:05
sbeattie   * 1 package pushed to -updates (virtualbox-ose)18:05
sbeattie hardy::18:05
sbeattie   * no SRU activity18:05
sbeattie dapper::18:05
sbeattie   * no SRU activity18:05
sbeattie(bah, silly copy & waste)18:05
sbeattieThanks to ahart01, PAUL GIBSON, Otus, enzo, Uqbar, Benedikt Kristinsson, yarly, Pedro Villavicencio (pedro_), Ian Halpern, Guria (Guria), Thorsten Reinbold, nicolagiacobbe, devnulljp, Olivier Tilloy (oSoMoN), C de-Avillez (hggdh), Clovis Peruchi Scotti (cpscotti), Martin Beltov, Tim85, Bo Pearce, wizeman, Pablo Estigarribia and Andrew Straw for testing packages in -proposed.18:05
sbeattieAs always, we'd appreciate people interested in testing the pending SRUs, see http://people.canonical.com/~ubuntu-archive/pending-sru.html for what's currently in the queue.18:06
sbeattieAny questions about SRUs this week?18:06
sbeattie[TOPIC] Bug Day status -- pedro_18:07
MootBotNew Topic:  Bug Day status -- pedro_18:07
pedro_The past Thursday we had a bug day based on the Epiphany Browser18:07
pedro_~52 bugs were triaged during that day. Thanks a lot to our bug day heroes: evfool, vish, kamusin, micahg, dmitrij.ledkov, skarottes and sinzui  you guys rock!18:07
pedro_https://wiki.ubuntu.com/UbuntuBugDay/2010052718:07
pedro_the KDE triagers also organized one for KDEPim18:08
pedro_https://wiki.ubuntu.com/UbuntuBugDay/20100527/KDE18:08
sbeattieWoot, nice work everyone!18:08
pedro_it was the same day though so it generated some confusion, I've been talking with txwikinger and i suggested to move the KDE bug day to another day perhaps Monday18:09
pedro_so they can have more contributors and we can announce it more nicely ;-)18:09
sbeattieAh, yeah.18:09
pedro_more news on that to come, so stay tune for KDE Bug days!18:09
sbeattieI didn't happen to see the KDE announcement, did it go out to ubuntu-qa@ and elsewhere?18:09
pedro_Tomorrow we're having a bug day based on Compiz, there's plenty of bugs waiting to be triaged,  if you have some time and want to learn a bit more about bug triage join us at #ubuntu-bugs , we'll be glad to help you to start18:09
pedro_sbeattie, it went to bugsquad only IIRC18:10
pedro_https://wiki.ubuntu.com/UbuntuBugDay/20100603 <- page for the compiz bug day , again if you have some time you're more than welcome to help us tomorrow ;-)18:10
pedro_sbeattie, that's all from here unless there's a question18:11
sbeattieThanks, pedro_. Questions, anyone?18:11
txwikingersbeattie: I sent out the announcement through various planets18:11
txwikingerand put it into topics in IRC channels18:11
txwikingernext time I will also put it on some more MLs18:12
txwikingerI am planning to start coming Monday18:12
sbeattietxwikinger: okay, that sounds good, thanks for organizing!18:12
txwikingernp18:12
sbeattietxwikinger: do you know what you'll be focusing the next one on?18:13
txwikingeryes kdenetwork package18:13
txwikingeri.e. kopete and so on18:13
sbeattiesounds good.18:14
sbeattie[TOPIC] Blueprints update -- all18:14
sbeattieDoes anyone want to give an updated status on their blueprints?18:14
MootBotNew Topic:  Blueprints update -- all18:14
marjosbeattie: http://people.canonical.com/~pitti/workitems/maverick/canonical-platform-qa.html18:14
sbeattie[LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-platform-qa.html18:14
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-platform-qa.html18:14
ara[LINK] https://blueprints.launchpad.net/ubuntu/+spec/qa-maverick-mago-daily18:15
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/qa-maverick-mago-daily18:15
araThis blueprint covers running mago tests on a daily basis18:15
araI was able to set a Hudson local server to run mago tests as "build" tasks18:15
araNow I need to discover how to run those tests in satellites, rather than the hudson server itself18:16
araev is doing something similar for the installer, and I will coordinate with him to try to avoid duplicating efforts18:16
sbeattieara: interesting. I've seen evan dandrea doing some stuff with hudson, you might ask him for pointers.18:16
ara;-)18:17
sbeattieara: heh.18:17
araif anyone wants to play around with mago and hudson and give us a hand, please, let me know :-)18:17
arahelp always welcome18:17
sbeattieara: do you have sample configurations available anywhere?18:17
sbeattieor, rather, where would we start looking if we wanted to play with it?18:18
arasbeattie, sorry, I have not, I will make a branch under ~apulido/junk and will link it to the blueprint18:18
sbeattieara: that'd be awesome.18:19
araand docs! yes! I could create some documentation as well18:19
sbeattie[ACTION] ara to create hudson+mago branch and write some docs.18:19
MootBotACTION received:  ara to create hudson+mago branch and write some docs.18:19
araok, thanks :-)18:19
sbeattieanyone else have something to talk about their blueprints?18:20
hggdhon my side: I will have to talk with Jos -- too much on my plate18:20
hggdh(UEC Testing is *big*)18:20
* jiboumans perks up18:21
marjohggdh: more like *huge*18:21
sbeattiehggdh: okay, I think we can let you, jiboumans, and marjo sort it out.18:22
hggdhjiboumans: let's see it18:22
hggdhlater18:22
sbeattiealright, moving on.18:23
sbeattie[TOPIC] Sound Card Compatibility Testing - awbancroft18:23
MootBotNew Topic:  Sound Card Compatibility Testing - awbancroft18:23
sbeattieDoesn't seem like awbancroft is here?18:23
sbeattieIf they show up, we can come back to it.18:24
sbeattie[TOPIC] Alpha 1 ISO Testing status - ara18:24
MootBotNew Topic:  Alpha 1 ISO Testing status - ara18:24
sbeattieara: how's alpha 1 testing going?18:24
araOK, Alpha 1 testing coverage is looking good for an alpha 118:24
ara[LINK] http://iso.qa.ubuntu.com/18:24
MootBotLINK received:  http://iso.qa.ubuntu.com/18:24
araBut, as you may see, there are some images that haven't been tested at all18:24
ara[LINK] http://iso.qa.ubuntu.com/qatracker/build/all/untested18:25
MootBotLINK received:  http://iso.qa.ubuntu.com/qatracker/build/all/untested18:25
arait is always nice to reach 100% IMAGE coverage even in alphas18:25
arait is not that urgent to get 100% testcase coverage18:25
arabut we need to make sure that all the images are working correctly (more or less, you know)18:26
fader_ara: It looks like some of the flavors are not being tested; will they be tested in later alphas?18:26
bladernr_ara: I like the new main view (showing all the variants by default)18:26
arafader_, there were some build problems earlier in the week, I guess the will get fixed later in the cycle18:27
arafader_, are you talking about mythbuntu?18:27
fader_Got it... thanks18:27
araor something else?18:27
fader_ara: Yes :)18:27
sbeattiefader_: yes, mythbuntu had some issues, but are expecting to be back available for alpha 2.18:27
fader_sbeattie, ara: cool, thanks.  I didn't even realize that I hadn't gotten the email notification about the mythbuntu builds until just now :/18:28
sbeattieand, yes, thanks ara for continuing to improve the iso tracker.18:28
fader_+1!18:28
arasbeattie, the all/all was a minor change in the database... nothing too fancy18:28
sbeattieara: regardless, we all appreciate it. :-)18:29
araOK, back to testing, please, if you have some spare time/hw/vm, please, focus on untested images18:29
araand then the rest18:29
* sbeattie will be able to help out after the meeting ends.18:29
sbeattieany more questions about alpha 1 testing?18:30
sbeattie[TOPIC] Firefox 3.6.4 security update testing - ara18:30
MootBotNew Topic:  Firefox 3.6.4 security update testing - ara18:30
araOK, just in case you've missed the news, xulrunner 1.9 is no longer maintained by Mozilla anymore18:31
araso, we are going to put Firefox 3.6.4 not only in Lucid, but also in Hardy, Jaunty and Karmic18:31
arayes, yes, yes, I know, that's a new release in a stable release! crazy security team, sbeattie :P18:32
sbeattieara: crazy upstream, more like; the security team's not happy about it, either.18:32
araso, testing (a lot of) is needed18:32
arasbeattie, :-)18:32
araif you guys want to help testing (a VM is OK) you can follow the steps at:18:33
ara[LINK] https://wiki.ubuntu.com/Testing/Firefox3.6.4Upgrade18:33
MootBotLINK received:  https://wiki.ubuntu.com/Testing/Firefox3.6.4Upgrade18:33
araand if you have any questions I am sure chrisccoulson will be happy to answer those18:33
BlackZsure ara, I will test it as well (sorry for the interruption)18:34
araBlackZ, thanks!18:35
sbeattieara: hrm, the tracker at http://mozilla.qa.ubuntu.com/qatracker/build/all/all only lists the hardy build; is jaunty and lucid coming?18:35
arajaunty and karmic, not lucid18:35
sbeattie(or is that a question for chriscoulson?)18:35
arayes, they will come when chrisccoulson has the packages ready in his ppa18:35
sbeattieah, okay.18:35
arathe Mozilla team pushed back the release to June 7th IIRC, so we have a bit more time18:36
sbeattieOkay, thanks.18:38
sbeattie[TOPIC] Next meeting and selection of new chair - sbeattie18:38
MootBotNew Topic:  Next meeting and selection of new chair - sbeattie18:38
sbeattieDo we have a victim, erm, a volunteer willing to chair the next meeting?18:38
* sbeattie listens to the crickets....18:39
sbeattiefader_, pedro_, hggdh: any of you want to take it?18:39
fader_sbeattie: "want" is such a strong word... I'll take it though :)18:40
sbeattiefader_: thanks, appreciated.18:40
sbeattie(perhaps after everyone does a round of it, we should just go in a defined order)18:40
sbeattiewith the next meeting, should we try to do the shifted meeting at 19:00 UTC?18:41
arasbeattie, before knowing if we have room for it?18:41
fader_Doesn't that still conflict with the edubuntu meeting?18:41
sbeattieGiven that edubuntu does seem to hold weekly meetings at that time, we'd have to hold it in #ubuntu-quality18:42
arasbeattie, OK, I can take the action of talking with the IRC Council to see the steps on having a meeting bot there18:42
sbeattieara or anyone else: do you have any idea how long that will take to go through?18:43
arasbeattie, no idea18:43
sbeattie[ACTION] ara to talkwith the IRC Council to find out the stpes for setting up a meeting bot in #ubuntu-quality18:45
MootBotACTION received:  ara to talkwith the IRC Council to find out the stpes for setting up a meeting bot in #ubuntu-quality18:45
sbeattieI don't have a strong opinion on whether we should start with the altered time next; fader_, since you're the next meeting chair I'll leave it up to you.18:47
sbeattie(but we need a decision one way or the other)18:47
fader_sbeattie: My vote would be to do it at the new time since ara is going through the effort of getting us a bot18:48
sbeattiefader_: okay, then let's plan on that. Next week's meeting will be at 19:00 UTC, wednesday, June 8th, in #ubuntu-quality.18:48
sbeattie[TOPIC] Any other business?18:49
MootBotNew Topic:  Any other business?18:49
sbeattieDid awbancroft show up? Doesn't seem like it...18:49
sbeattieOkay, thanks everyone!18:50
sbeattie#endmeeting.18:50
fader_Thanks all18:50
sbeattie#endmeeting18:50
MootBotMeeting finished at 12:50.18:50
aracheers18:50
marjothanks all!18:50
marjosbeattie: thx for chairing18:50
bittinwhat meeting was that?18:50
sbeattiebittin: QA team meeting18:50
hggdhbittin: QA18:50
bittinah18:50
bittinnever mind then iam waiting for the Edubuntu one18:51
bittinand the Fridge Calender is not using Swedish timezone :(18:51
bittinso got confused18:51
xnoxbittin, if you subscribe to fridge in google calendar you can view it in your local timezone =)18:52
bittinxnox: :o i might do that then18:53
bittinxnox: thanks for the info :)18:53
=== jjohansen-afk is now known as jjohansen
highvoltageRight, who's here for the Edubuntu weekly meeting?20:00
bittinme20:00
highvoltagehey bittin20:00
bittinhi20:00
alkisgHi people20:01
highvoltagenot too much on the agenda tonight, I don't have too many updates to be honest, I haven't exactly had the best time-management the last week and tumbled a bit20:02
highvoltagethe first alpha release is scheduled for tomorrow20:02
* bencrisford wanders in20:02
highvoltage( https://wiki.ubuntu.com/MaverickReleaseSchedule )20:03
highvoltagestgraber: can we test todays iso images for the alpha?20:04
highvoltagenone are listed on http://iso.qa.ubuntu.com/qatracker/build/edubuntu/all currently20:04
highvoltageessentially there shouldn't be a lot to test that isn't in Ubuntu20:07
highvoltagebut the idea is that if there's any edubuntu-specific problems we can sort it out early20:07
highvoltagebencrisford: how are things going with the advocacy team, have you had any time to spend on that again?20:08
bencrisfordhighvoltage: dont think there is anything new20:08
bencrisfordI had some thoughts about the structure of the branch20:08
highvoltageI guess we also really need our new website for some of the things we've discussed before20:08
highvoltageI e-mailed hedgemage this morning and asked if she could give me an update.20:09
highvoltageI'm tempted to just go ahead and put a new theme on our old site and update some content in the meantime that urgently needs updating20:10
* stgraber waves20:11
stgrabersorry for being a bit late20:11
highvoltageglad you could make it :)20:11
stgraberhighvoltage: for alpha, you can poke sladen about it (I can add them too if necessary)20:11
highvoltagestgraber: I'll poke sladen20:12
dhillon-v10_hi to all :) sorry guys I am a little late20:12
bittinhello20:12
stgraberhighvoltage: slangasek I mean ;)20:12
highvoltagehi dhillon-v10, are you able to give us some update on the new site?20:12
stgraberhighvoltage: tab-complete FAIL :)20:12
bencrisfordhaha, poor sladen :P20:13
dhillon-v10_highvoltage: hiiiiiii :) long time so see how's it going, well I guess now isn't the time to ask that, yeah I pinged hedgemage a while ago but she didn't reply back20:13
dhillon-v10_stgraber: hi :)20:13
highvoltagedhillon-v10_: well it's good to have you back again, done with all the exams?20:14
dhillon-v10_highvoltage: yeah finally :) it was a pain but now i am done20:14
dhillon-v10_oh and everyone did an awesome job in the last cycle :D20:14
highvoltageexcellent, glad to hear that20:14
highvoltage*nod*20:14
dhillon-v10_highvoltage: so yeah until the website work is fixed, anything else for me like packages and so on?20:15
highvoltagedhillon-v10_: I said earlier that I poked hedgemage by e-mail this morning, so hopefully I'll hear from her this week still20:15
highvoltagedhillon-v10_: oh yes, certainly.20:16
dhillon-v10_highvoltage: alright then, yeah she's the one hosting it so I don't have much control over the site, besides modifying stuff on it20:16
highvoltagedhillon-v10_: if you want you could work on the edubuntu-artwork split-up so long? currently edubuntu-artwork is too big and contains the artwork, settings, and the live cd environment stuff.20:17
dhillon-v10_highvoltage: sure, what exactly do i need to do?20:17
bencrisfordhighvoltage: is there a todo page or something for packaging?20:17
highvoltagebencrisford: currently we have those 3 blueprint pages that basically summarizes what needs to be done20:18
bencrisfordhighvoltage: the ones listed on wiki.u.c/Edubuntu/evel/RoadMap20:18
bencrisford?20:18
highvoltageyes, the ones on https://wiki.ubuntu.com/Edubuntu/Devel/RoadMap20:19
bencrisfordokey doke20:19
highvoltagewe could spend some time tomorrow splitting them up in to-do items, and then people could volunteer for some items if they like?20:20
* bencrisford is free all day tommorrow :D20:21
bencrisfordhi Lns :)20:21
dhillon-v10_highvoltage: sure that works :)20:21
dhillon-v10_Lns: hi :)20:21
Lnshi..wow we're still in meeting ?: )20:21
Lnsi thought i missed it!20:21
highvoltagegreat, I'll split it up and send a message to the list so that everyone can take a look and sign up for something20:21
bencrisfordawesome :)20:22
bittinLns: yea its Edubuntu meeting20:22
dhillon-v10_highvoltage: there's one thing I have had in my mind for quiet some time now its regarding the documentation, can you remind me to talk about that near the end of the meeting20:24
highvoltagedhillon-v10_: you can go for it now, I don't have much else :)20:25
highvoltagedhillon-v10_: I have lots of mixed feelings about documentation so some fresh input there would be good20:25
dhillon-v10_alright people so as we write docs. we want users to benifit from them, most people instead of using docs. use google instead, i want to have an online system, or something rather put into  yelp where people can send back reviews about the docs. now we will use google sidewiki spam algorithm to get rid of the spam and focus really on the issue where we know what the users really want20:26
highvoltagedhillon-v10_: I'm a bit ignorant when it comes to yelp, is it hard to do mark-up for it? are there tools that for example, can export wiki pages to yelp pages?20:28
dhillon-v10_and not only that, we can also use a google custom search to see the websites that people most often go to to get this information, I am pretty sure there are some and then use info. from those sites to automatically update the docs. this right here is the key puch of the idea but is also tricky to implement :)20:28
dhillon-v10_highvoltage: I wrote a major part of docs. in kubuntu thanks to Richard in the last cycle, so I can take care of exporting stuff :)20:28
* bencrisford loves docbook markup :)20:29
dhillon-v10_the best part would be the automatic updates that we can send out, this would involve some changes to yelp but i am pretty sure if we can work out a good plan, Shaun from gnome and others would like it as well20:29
highvoltagedhillon-v10_: indeed, it's also great for people that might not have connectivity20:30
dhillon-v10_and then we would almost never have to take care of updating the docs. because we would just need to pull the relavent information from the sites and then send it out like a sru but only for docs.20:30
dhillon-v10_so do you guys think that this is something that can be done? if so then I can start formally building up a blueprint and all that good stuff :)20:31
highvoltagedhillon-v10_: I think your job should rather be around documentation for now rather than packaging :)20:31
highvoltage+1 from me!20:31
dhillon-v10_highvoltage: :) I can manage some packaging20:32
bencrisford+120:32
bencrisford:)20:32
dhillon-v10_+120:32
dhillon-v10_lolol20:32
highvoltageheh20:32
highvoltageat the beginning stage of that we should probably have a session to plan out what needs to be documented20:33
highvoltagesbalneav has ltsp covered quite well, so at least there's not a lot to write there20:33
highvoltagebut there's quite a bit we have to do that's edubuntu-specific20:34
highvoltagewe had a bit of confusion with live ltsp around release time, some people were a bit uncertain about some things and we lack decent documentation on it20:34
bencrisfordthe System> About Edubuntu stuff needs updating20:34
bencrisfordit has the old artwork20:34
bencrisfordand if you go into the source and look at the translations20:35
highvoltagewould be *great* if we could have help built-in to the system for that20:35
bencrisfordthey still talk about hardy or something, iirc20:35
highvoltagebencrisford: good catch, is there a bug open for that?20:35
bencrisfordhighvoltage: not sure, i'll check20:36
dhillon-v10_highvoltage: alright will look into that as well :)20:37
bencrisfordhttps://bugs.edge.launchpad.net/ubuntu/maverick/+source/edubuntu-docs20:37
bencrisfordthat the right place to be looking?20:37
dhillon-v10_bencrisford: no bugs there :)20:37
highvoltagebencrisford: it could be in edubuntu-artwork too if it's filed20:38
bencrisfordtheres a couple if you drop the maverick bit :)20:38
highvoltage(since that's the package it's ine )20:38
bencrisfordhighvoltage: for the artwork bug yeah :), but there is a load of problems in the translations of aboyt-edubuntu20:38
bencrisfordpretty much all the translations still talk about hardy20:39
bencrisfordit seems that way in the source anyway :)20:39
bencrisfordmight not be hardy :( I cant remember20:39
highvoltageit's not impossible20:39
dhillon-v10_highvoltage: yeah if something like what I have in mind can be implemented, we can take over the world :) but seriously though that would be pretty awesome20:39
bencrisfordbug 45156920:39
ubottuLaunchpad bug 451569 in Ubuntu Translations "Strings in Karmic still refer to Jaunty" [Low,Triaged] https://launchpad.net/bugs/45156920:39
dhillon-v10_bencrisford: the importance of that needs to change :)20:40
highvoltagedhillon-v10_: we currently have no one looking at documentation, and it's a bit of a sore point, and there's a lot of work that has been done in the past (it's on the wiki currently) that is mostly unused and not very googlable20:40
highvoltagewould be nice to have some direction again and have someone who can care about it20:40
dhillon-v10_highvoltage: yeah well, now that I have time we can change that around :)20:41
highvoltagepersonally I'd love to but just don't have the time to do it properly20:41
highvoltagedhillon-v10_: awesome :)20:41
bencrisforddoesnt seem to be a bug about the outdated logo in either -artwork or -docs20:41
dhillon-v10_highvoltage: np :) yeah I have to take some responsibility now that I am an edubuntu developer20:41
bencrisfordi'll report one :D20:42
highvoltagedhillon-v10_: if you could help with those translation issues too that would be great20:42
highvoltagewe shipped our ubiquity slideshow in english-only because we had some issues that we couldn't fix fast enough before release20:43
dhillon-v10_highvoltage: I will try but I don't know how that would work out, i only know 3 languages and I'll translate whatever I can in time20:43
highvoltageit would be really nice if we could get that translatable on LP and then get the translations in20:43
dhillon-v10_highvoltage: ahh that I can do :)20:43
highvoltagedhillon-v10_: I didn't mean translating itself as the technical stuff in making it work :)20:44
highvoltagebittin: btw, is this the first Edubuntu meeting you're attending?20:44
dhillon-v10_highvoltage: yeah, got it :) its been an issue on the launchpad dev. team as well to get a better way of translating things around :)20:44
bencrisfordbug 588890 - should I add an also affects for -artwork?20:45
ubottuLaunchpad bug 588890 in edubuntu-docs (Ubuntu) "Old artwork used in "About Edubuntu" page" [Undecided,New] https://launchpad.net/bugs/58889020:45
highvoltagebencrisford: it's probably fine with edubuntu-docs20:46
bencrisfordhighvoltage: ok, I guess realistically its gonna be someone in this meeting fixing it anyway :P so it doesnt really matter20:46
dhillon-v10_bencrisford: thanks :) I will write up a blueprint and then attach to that bug20:46
bencrisfordok20:46
* highvoltage is catching up on taking notes20:48
dhillon-v10_highvoltage, bencrisford: okay so for now I'll be working on docs. and merge some packages over to ubuntu then :)20:49
highvoltagedhillon-v10_: ok, but you'll start with the blueprint right?20:50
highvoltage(not that I want to add too much beaurocracy, etc, etc)20:50
dhillon-v10_highvoltage: yes today, after nap-time :)20:51
highvoltagedhillon-v10_: heh, great20:51
dhillon-v10_highvoltage: which is around 4 pm20:51
highvoltageif we can get the technical stuff that we planned right, get the website flowing again, have great built-in documentation available through yelp, get our teacher community well-established through the advocacy/ubuntu-education project then maverick is really going to be an exceptional release20:53
highvoltageimo the groundwork is already quite good and we don't really have much in the sense of blockers20:54
highvoltage(although I'll admit I'm slightly scared of the ubiquity changes we planned)20:54
highvoltageanything else before we adjourn?20:55
dhillon-v10_highvoltage: true, but that still is a lot to get through we'll have to work faster :)20:55
highvoltagedhillon-v10_: yep, I think in terms of documentation we'll probabably not have something extermely comprehensive yet for maverick, but if we can cover some basics that we get lots of questions and feedback about then that would already be a huge win!20:56
dhillon-v10_highvoltage: I'll try me best this time :) I really want to have maverick to be as Mark planned: perfect :)20:58
dhillon-v10_alright then time to head to bed, later people :D20:58
bencrisforddhillon-v10_: later ;)20:58
alkisgbb20:58
highvoltagedhillon-v10_: I think in your blueprint it might be a good idea to list some phases, plans it over 2 releases20:58
highvoltagebut that's just details :)20:58
highvoltagehave a nice nap dhillon-v10_20:58
dhillon-v10_highvoltage: thanks :)20:59
dhillon-v10_lol20:59
highvoltageand thanks Lns, stgraber, bencrisford, alkisg and bittin for attending!20:59
highvoltagemeeting adjourned! *GONG*20:59
bittinno problem :p21:00
bittineven if i diden't say that much21:00
bencrisfordbittin: :)21:00
=== lukjad86 is now known as lukjad
=== lukjad007 is now known as lukjad

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