/srv/irclogs.ubuntu.com/2008/09/03/#ubuntu-meeting.txt

=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 09 Sep 15:00: Server Team | 03 Sep 17:00: QA Team | 03 Sep 22:00: Platform Team | 04 Sep 13:00: Desktop Team | 05 Sep 20:00: MOTU | 08 Sep 04:00: Arizona LoCo IRC
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 09 Sep 15:00: Server Team | 03 Sep 17:00: QA Team | 04 Sep 13:00: Desktop Team | 05 Sep 20:00: MOTU | 08 Sep 04:00: Arizona LoCo IRC | 03 Sep 20:00: Maryland LoCo IRC
=== sabdfl is now known as sabdfl_home
=== mdz_ is now known as mdz
=== dholbach_ is now known as dholbach
ma10@now rome11:35
ubottuCurrent time in Europe/Rome: September 03 2008, 12:35:57 - Next meeting: Server Team in 6 days11:35
=== fdd-0 is now known as fdd_
=== fdd_ is now known as Guest48574
RG3rYhi12:50
RG3rYcan i ask here a technical question about nvidia install on ubuntu ?12:50
persiaRG3rY: Yes, but nobody will answer you here.  Depending on the nature of your question, you may want one of #ubuntu, #ubuntu+1, or #ubuntu-devel.12:54
RG3rYthanks12:55
RG3rYim on it12:55
RG3rYgood day12:55
=== asac_ is now known as asac
calchi16:00
cjwatsongood afternoon16:00
ArneGoetjehi16:00
liwgreetingses16:00
james_whi all16:00
cjwatsoncould somebody chair this for me until this call is finished, please?16:01
cjwatsonI sent out the agenda16:01
cjwatsonI haven't yet reviewed the fstab change in ubiquity, so unless evand's done that, that's carried over again :(16:01
evandnegative16:02
brycehi16:02
asachi16:02
liwdoes it matter who chairs?16:03
asacliw: lets do a shared chair then ;)16:03
cjwatsonnot as long as you keep it moving :)16:03
asacwho is supposed to be here?16:04
asacslangasek: doko: there?16:04
calceveryone but ogra i think16:04
slangasek'morning16:04
cjwatsonTheMuso?16:04
dokohi16:04
ogra.oO(that odesnt mean i'm not lurking though :) )16:04
liwthemuso and slangasek missing16:04
* calc points at slangasek saying 'morning16:05
asacliw: s/slangasek//16:05
cjwatsonoh, TheMuso is on holiday16:05
cjwatsonlet's start then16:05
liwoh yes16:05
liw#startmeeting16:05
cjwatsonrecent experience suggests mootbot is not terribly alive atm16:05
liwfirst on the agenda: outstanding actions, carried over from previous meeting16:05
liwArneGoetje, "Arne to email ubuntu-devel@ or distro-team@ if still stuck with language-selector PyGTK needs, by end of week."16:06
ArneGoetjeliw: solved already16:06
liwand Colin and Evan confirmed that the /etc/fstab change (whatever it was...) is not yet done, so carried over16:06
liwnext: "Outstanding feature freeze exceptions from last week"16:06
cjwatsonoh, let me find a list of that16:07
cjwatsonI spewed it into the release team meeting last Friday16:07
cjwatsonhttp://irclogs.ubuntu.com/2008/08/29/%23ubuntu-meeting.html search for "new pulseaudio" for the start16:08
liw17:32cjwatson * new pulseaudio to match new alsa and new kernel16:08
liw17:32cjwatson* experimental python 3 packages (not by default, maybe not really FFe)16:08
liw17:32cjwatson* system-cleaner (tonight, I'm told)16:08
liw17:32cjwatson* usb-installer-images (ditto)16:08
liw17:33cjwatson* dvd-performance-hacks (ditto)16:08
liw17:33cjwatson* timezone map changes for ubiquity16:08
liw17:33cjwatson* openoffice.org 3 (again, not by default, parallel-installable)16:08
liw17:33cjwatson* xorg-options-editor needs promotion to main I think16:08
liwjust for the record...16:08
liwpulseaudio would be TheMuso's territory, yes? anyone know that status?16:09
liwdoko, python3?16:09
cjwatsonpython 3 has been controversial on distro-team@, though I only just noticed that thread today16:10
liwsystem-cleaner is waiting in REVU (I guess I should active find someone to review/sponsor it)16:10
liwevand, is usb-installer-images you?16:10
evandliw: ja16:10
evandit's through NEW, thanks to cjwatson16:10
dokoliw: well, lets address this on the distro list; I personally would like to see this (at least) in universe16:10
cjwatsonsystem-cleaner> please do, there should be plenty of people who can16:11
cjwatsonI just accepted usb-creator from NEW about ten minutes ago16:11
liwdvd-performance-hacks and timezone map changes I have no idea about whom to ask16:11
liwopenoffice.or 3 is calc, surely?16:11
liwxorg-options-editor is bryce?16:11
calcyes16:11
liw(am I going too fast?)16:12
brycedone16:12
calcopenoffice.org is still waiting to release rc1, hopefully this week finally, then i will get the parallel installable debs into intrepid16:12
bryceI filed both MIR's last week (thanks for the reminder colin)16:12
cjwatsondvd-performance-hacks/timezone> evand16:13
cjwatsoncalc: I asked for this to go ahead with the beta; assuming that the rc1 is delayed semi-indefinitely, do we need to wait for it?16:13
calccjwatson: for the languages it would be useful, yes16:14
cjwatsonusb-creator will still need MIR review and such16:14
evanddvd-performance-hacks is in ubiquity (though w/o triggers), the timezone stuff I'm going to have to defer as the weekend was spent entirely on the usb installer.16:14
calccjwatson: beta2 just ships en-us16:14
cjwatsoncalc: ack, though we could get some initial testing16:14
evandcjwatson: noted16:14
calccjwatson: they seem fairly confident about releasing rc1 (whether or not its ready i think) this week so it shouldn't be much of an issue16:15
cjwatsons/confident/determined/ ? :-)16:15
calcyea perhaps determined is a better word ;-)16:15
cjwatson"it doesn't build, ship it"16:15
calcyep :)16:15
cjwatsonok, so the FFe focus for this week seems to be: system-cleaner, usb-creator, dvd-performance-hacks triggers, xorg-options-editor16:16
liwanyone know about pulseaudio?16:17
cjwatsonwe'll have to check that with Luke when he gets back, I think; it sounds as if nobody here does. I believe it's essentially an upstream update that's been needed for quite a few reasons but was blocked on new alsa16:17
asaccjwatson: the mobile broadband wizard and DB needs a FFe ack i think... its sitting in NEW as well16:17
asacits #26366816:17
cjwatsonmobile-broadband-provider-info?16:18
asacyes + libmbca16:18
asaccjwatson: like in the bug16:18
asaconce its in I'll draft the MIR so we can build against that.16:18
cjwatsonI think it can go into universe safely, so I'll process it after this meeting and we can look at it from there16:19
cjwatson(this call seems not to be happening, hence attention ...)16:19
liwanything else about FFes?16:19
evandI believe Agostino Russo is going to apply for one for Wubi16:20
evandBut he wanted some time to further develop before he makes a decision on whether or not to approach the release team with it.16:21
cjwatsondo you know what the planned changes there are?16:21
evanda complete redesign :/.  It's taking the current code and rewriting it in something not-NSIS.16:22
evandIn this case, python and bindings to MFC, if I recall correctly.16:22
liwanything else about FFes or shall we continue to the next topic?16:24
cjwatsonwhich is a good idea in general, but perhaps we should arrange for custom CD images with a wubi branch on them so that we can test that before merging16:24
cjwatson(NSIS has been a pain in the neck)16:25
cjwatsonlet's continue16:25
liwnext topic: Milestoned/targeted bugs16:25
evandindeed, noted16:25
* calc pushing his milestoned bugs back to the next release16:26
cjwatsonlinks to milestoned/targeted bugs?16:26
slangasekmilestoned for alpha-5: https://bugs.launchpad.net/ubuntu/intrepid/+bugs?field.milestone%3Alist=132316:27
cjwatsonthanks16:27
slangaseknone of which belong to anyone here, unless someone wants to try tackling #25217416:27
slangasek(262539 is specifically going to be deferred, as soon as I errata it)16:27
cjwatsonnothing for us there, though I think we should ask for 262539 to be in place by alpha-516:27
cjwatsonhm, really?16:27
cjwatsonit seemed like a simple userspace fix16:27
brycewow, amazingly few milestone bugs16:28
slangasekoh, is it?16:28
slangaseksorry, I assumed it was bound up to the kernel ABI changes and that it wasn't an issue for pristine installs with alpha-516:28
cjwatsonhttp://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid-lrm.git;a=commitdiff;h=7a1611ef0f30469da0353d438d1a71a326eb3ca916:28
slangasekok, will ping the kernel team after the meeting16:28
cjwatsonthough I think you're right that it isn't an issue for pristine installs16:29
cjwatsonhow about targeted bugs? we're getting to the point where we should be aggressively getting those out of the way16:29
slangasekanyway, there are other bugs besides the milestoned ones that we should be looking at: https://bugs.launchpad.net/ubuntu/intrepid/+bugs16:29
cjwatsoncritical for us are 247376 fglrx (blocked on upstream), and 261847 openjdk (which I believe doko's looking at)16:30
cjwatsonseveral firefox/xulrunner high16:31
pittimilestone bugs> that URL above is weird, https://edge.launchpad.net/ubuntu/+milestone/intrepid-alpha-5 has a lot more bugs16:31
dokoyes, had given the gcc update priority. will be fixed before the alpha. local builds are running16:31
asacwell ... the IO thing is something not trivial to fix16:31
slangasek185311, still some xcb locking concerns?16:31
asacthe background image thing should work though16:31
slangasekpitti: anyone can set a milestone for a bug, the URL above are the milestone-critical ones16:32
pittislangasek: ah, thanks16:32
cjwatsonand OOo, libxcb (that assertion failure again?), an LVM failure I still need to track down, some X driver issues, an n-m crash, oem-config/Kubuntu16:32
asacactually i thought the background image thing was fix committed16:32
slangasekasac: an easy bug report to resolve, then ;)16:32
asacslangasek: yeah ;)16:33
asacah. i think the idea was to get that committed upstream and let that sink down to us.16:34
bryceslangasek: I'll take a look.  Last I heard, the java changes pretty much took care of the remaining known xcb issues16:34
liwanything else about bugs?16:36
bryceslangasek: also I talked with Bart about the status of the rearchitecting work monday, and he said it's not looking like it will hit in the near term16:36
cjwatsoncalc: bug 224469 seems to be in a slightly indeterminate state; is it fixed in intrepid or not?16:36
ubottuLaunchpad bug 224469 in openoffice.org "[upstream] [hardy] openoffice complains that jre is not present or is broken. It is actually present and unbroken." [High,Fix committed] https://launchpad.net/bugs/22446916:36
calccjwatson: i can't reproduce it any longer after some fixes went in but apparently some users can still16:37
cjwatsonok, please update the bug to say that16:38
calchmm actually i must be thinking of another bug, just reread the description16:38
calcyes this one should be fixed afaict16:38
calci just forgot to mark it as fix released for intrepid yet16:39
calcit was uploaded to hardy then copied over to intrepid16:39
cjwatsonok, please sync it up, then16:40
cjwatsonright, we should move on from bugs16:41
liwnext topic: Sponsorship queue16:41
cjwatsonI've done my hour this week ;-)16:41
cjwatsonhttp://people.ubuntu.com/~dholbach/sponsoring/16:41
liwI can't sponsor...16:41
cjwatsonpeople without upload privileges are excused16:41
slangasekheh :-)16:42
asacmy list should be zero (well except swfdec that needs FFe)16:43
cjwatsonso, of the uploaders, who has done sponsoring this week?16:43
calci have one that was assigned yesterday apparently will get to it this week16:43
slangaseknot me, this is day one of my week ;)16:43
asaci even sponsored two that werent on my list ;)16:43
cjwatsonI've done usbutils, ichthux-default-settings, cobex, showfsck, anacron, mplayer16:43
evandI unfortunately have not found time for it with the FF, but will endeavor to today.16:43
slangaseklinux-wlan-ng is mine to resolve, though unfortunately it's an upstream merge from the beginning of the cycle that never got done, so the resolution may well be "postponed" once I've looked at it16:44
ograslangasek, i might pester you about a moodle FFe ...16:47
ograbut not right now/yet16:47
liwany other people doing/not doing sponsoring?16:48
liwif not... the next topic would be "Any business from activity reports"16:50
cjwatsonok, well consider this a reminder to help clear out the sponsorship queue for next week; I'll be going around and asking people :)16:51
cjwatsoncall done, I have the activity reports, one moment while I scan16:52
cjwatsonmissing reports from bryce, doko16:52
asacon this front: personallly, i dont think that the new way of doing activity reports is an improvement. i would really like to read what people did last week _before_ the meeting.16:53
asacwhat do others think?16:53
bryceoh shoot, forgot to send.  cjwatson I'll get that to you shortly16:53
cjwatsonmaybe we should ask for distro-activity16:53
cjwatsonI really appreciate the new readable distro-team16:53
dokocjwatson: hmm, ok. this is a one day report: email catchup, gcc fix16:53
liwan opt-in distro-activity would be fine, I think16:53
bryce(was off yesterday and just plumb forgot)16:54
cjwatsondoko: oh, of course you were off. never mind then16:54
asaccjwatson: i appreciate the new summaries too. but i think that getting the team-colleagues reports _before_ the meeting allows us to discuss things/news while they are still new16:54
cjwatsonok, I'll pass that idea around then16:55
asacbut maybe thats not a practical issue. if noone else feels the same, then i can certainly step back on this point :)16:55
pittiwhy can't we still use distro-team@ to discuss stuff before the meeting? these could become separate mails, instead of being buried in reports16:55
cjwatsonI suggest distro-activity with enforced reply-to: distro-team16:56
cjwatsondistro-team was really, really noisy. I just didn't read it16:56
cjwatsonwhich I think is bad16:57
asaccjwatson: ack from me. reply-to @distro-team16:57
asacwith an opt-in distro-activity list16:57
cjwatson(no business from activity reports that I can see, btw)16:57
asac(or maybe even foundations-activity ... which is at least mandatory to read for foundations team members?)16:57
liwnext topic would be "Any other business"16:58
calc2m left :)16:58
cjwatsonasac: list explosion :)16:58
liwmore mandatory mail to be read is unlikely to be successful in communicating things16:59
liwno other business? can we end the meeting on time? :)17:00
cjwatsonsounds like it17:00
liw#endmeeting17:00
asacliw: true. thats why i said: if there is noone actually feeling the same way then we dont even need distro-activity17:01
liw(that doesn't have anywhere near the satisfaction you get from a fifteen pound gavel)17:01
james_wthanks all17:01
asacthanks17:01
evandthanks17:01
slangasekcheers17:01
liwgracias17:01
ArneGoetjethanks17:01
cjwatsonasac: I definitely see the usefulness of having an opportunity for discussion17:01
liwwhat are we doing for minutes this time? (this quarter?) I forgot17:02
calcthanks17:02
liwcjwatson, will you do the minutes?17:05
brycethanks17:06
cjwatsonliw: yes17:06
* stgraber waves17:58
LaserJockhi stgraber18:00
heno_Hello everyone!18:00
bdmurrayhowdy18:00
pedro_hey hey18:00
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: QA Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 04 Sep 13:00: Desktop Team | 05 Sep 20:00: MOTU | 08 Sep 04:00: Arizona LoCo IRC | 03 Sep 20:00: Maryland LoCo IRC
persia\o18:00
heno_got bot? I wonder18:01
heno_#startmeeting18:01
heno_nope :(18:01
heno_the agenda is here as usual: https://wiki.ubuntu.com/QATeam/Meetings18:02
arahello everyone18:02
sbeattiehey18:03
heno_[TOPIC] Regression tracking guidelines and web page prototype.18:03
heno_sbeattie: can you give a summary/update?18:03
sbeattieUm, sure.18:03
sbeattieThis is an overview https://wiki.ubuntu.com/QATeam/RegressionTracking18:04
LaserJockso is there any plan on how we're going to deal with and/or triage regression bugs?18:05
sbeattieWe'd like to track 3 things, potential regressions in the devel version (e.g. intrepid), regressions between released versions (e.g. gutsy -> hardy), and regressions in updated versions (e.g. hardy -> hardy-updates)18:05
LaserJockI can just imagine a flood of bugs18:05
sbeattieSort of, I was envisioning web pages to track all of the different tags18:07
heno_The plan is to first get a better overview of where we are regressing so we can a) minimise that and b) release note better where we cannot fix18:07
heno_It's not a campaign to collect more bugs as such :)18:07
LaserJockheno_: so, sorry to be predictable, what about Universe in this?18:07
sbeattiePlus perhaps another script that looks for untagged bugs that mention regression.18:08
LaserJockheno_: no, but once you say "we're trying to find out about regressions" you're going to get a lot of people filing regression bugs for every feature that changes18:08
sbeattieUniverse included, I don't see why it would be different18:08
* persia likes the idea of a campaign to collect more bugs: more feedback means better understanding of how to improve18:08
arasbeattie: adding a task in the release notes project, as soon as we discover a potential regression... could it be possible that we add a release note of a regression not happening18:08
heno_LaserJock: does that need a different process? I would think a regression between releases would be the same in main and universe18:08
LaserJocksbeattie: because it'd perhaps be hard to write release notes if Universe bugs outnumber Main by a lot18:09
ScottKpersia: I think there would be more incentive if there was less closing of bugs not yet fixed.18:09
persiaLaserJock: We might have a lot of wontfix bugs, but that's still useful for later bug filers.18:09
persiaScottK: That too.18:09
persia(but unrelated)18:09
ScottKpersia: I think it's related to the odds of success of such a campaign.18:09
LaserJockheno_: no, not different processes.18:10
heno_LaserJock: good point - have universe issues been release noted in any way in the past?18:10
LaserJockheno_: not that I know of18:10
persiaThere've been a few cases where release notes mentioned something of especial interest in universe, but it's not common, except for parts of universe that constitute the universe flavours.18:11
LaserJockI'm also slightly concerned about lots of stats without any developer effort to back them up, if that makes sense18:11
heno_LaserJock: hm, ok. should we encourage that to be started?18:11
LaserJockheno_: I'm not exactly sure. I have no idea how it'd be even written18:11
sbeattieara: I'm not sure exactly what you're asking, but I could see release notes worthy stuff that aren't regressions being added to the release-notes project; that's more a question for slangasek18:12
heno_LaserJock: the idea is to use the metrics to inform and focus devel effort18:12
LaserJockheno_: right, but I think it's important to make sure that actually happens18:12
heno_does anyone have ideas for other fields in the regression data template?18:12
LaserJockI love stats, don't get me wrong. I'm a scientist and I live on data18:13
LaserJock:-)18:13
heno_I'm a theoretical scientist so I'm not as worried about data ;)18:13
sbeattieLaserJock: Heh. With actual evidence rather than hand-waving it can become easier to convince people of the need to take action.18:13
LaserJockbut I think the QA team can get a bunch of stats without any connection to actual development efforts18:13
LaserJockso then users see all these stats and developers not working on them and get upset18:14
LaserJocki.e. OMG, look at all those regression bugs!!!!18:14
heno_status.qa.ubuntu.com is an example of how we can use bug data to target the fixing work18:14
LaserJockso while I think it's a great thing to have, we might want to think about recommendations for ubuntu-devel18:14
heno_in what sense?18:15
heno_do you envision objections to using these tags?18:15
LaserJockthings like "heah, we've noticed X number of regression bugs in package Y, you guys might want to get on that" :-)18:16
LaserJockno, I doubt there will be objections18:16
heno_and they would be right18:16
sbeattieLaserJock: I think you're correct to point out that we, as the QA team, need to be advocates for our users to the developers based on the stats we collect.18:17
heno_ok, please add further comments and ideas to the wiki page18:17
heno_moving on18:17
LaserJocksbeattie: I'd go further and say that we are a *part* of the development team and should drive QA within Ubuntu development18:17
heno_[TOPIC]: QA server setup - who is setting up what services18:18
heno_Brian has agreed to coordinate placement of services on the server, URLS, etc18:18
heno_several people here are already moving stuff there18:18
heno_can we get a brief overview from each?18:19
heno_ara, bdmurray, sbeattie, ogasawara? others?18:19
bdmurrayI've setup a new bug stats database using postgres and storm on the server18:19
LaserJockheno_: this is on the new server in the DC?18:19
araI just got instructions from bdmurray on the access permissions. I will be adding the automated tests starts there18:19
heno_LaserJock: yes18:20
bdmurrayI need to import data from p.u.c and then move graph generation to the new server18:20
ogasawaraI haven't officially moved anything over - but could migrate all the pkg-stat, weather report, kernel bug lists, etc over18:20
heno_dhobach plans to move harvest there as well18:20
heno_so anyone wishing to migrate stuff there, please coordinate with bdmurray18:21
LaserJockdoes that server use the *.qa.ubuntu.com ?18:22
LaserJocks/the//18:22
heno_yes, except some drupal things will stay on the old server for some time18:22
bdmurraylike brainstorm and the isotracker right?18:23
heno_this one is PHP-free18:23
heno_bdmurray: right18:23
LaserJockright, but in terms of URL they're all going to use qa.ubuntu.com18:23
heno_brainstorm will always remain PHP afaik, and is really not related to QA much anymore18:23
bdmurrayLaserJock: Correct, just not *18:24
heno_LaserJock: right18:24
LaserJockk18:24
heno_next18:24
heno_[TOPIC]: Alpha 5 ISO testing18:24
heno_images are appearing now and we need testing help!18:25
heno_Who has working spare HW or VMs ATM?18:26
heno_I have troble with vbox here ATM18:26
araI am downloading now alternate i386 and will give it a try tomorrow. I will run also the automated tests18:27
ogasawaraheno_:  I've got a spare system I can run some tests on18:27
heno_unfortunately davmor2 who normally does a lot of testing is away this weel18:27
sbeattievbox hosted on hardy?18:27
heno_sbeattie: right, and intrepid as well18:28
heno_I'll try kvm later though18:28
schwukheno_: I've been playing with mvo's sandbox kvm scripts, so my vm's are working18:28
LaserJock * I just created https://wiki.ubuntu.com/QATeam/Services to list our hosts/services. Please fill in when you get a chance18:29
heno_schwuk: excellent. do you have admin access to the iso tracker btw? to help coordinate18:29
schwukheno_: let me check18:29
persiaLaserJock: On that page: what about services hosted by Canonical but not on qa.ubuntu.com?18:29
heno_if not I or stgraber can help set that up18:29
* persia is thinking of things like the conflictschecker18:30
LaserJockpersia: I was gonna put that under "hosted elsewhere"18:30
LaserJockbut I guess that's a good point18:30
heno_Ideally we should move those over18:30
LaserJockheno_: that's what I was thinking18:30
heno_persia: are you interested in running the conflict checker?18:31
heno_now being open sourced btw18:31
persiaheno_: All of them?  There's quite a few, and for some things (like most of the contents of p.u.c/~ubuntu-archive), there are lots of external scripts depending on the location.18:31
schwukheno_: How can I tell if I have admin access?18:31
persiaheno_: Yes, but my plate is far to full to accept anything new right now.18:31
heno_ok18:32
arawhat is conflict checker used for?18:32
heno_schwuk: you should be able to add builds18:32
heno_ara: check for file conflicts in packages18:32
persiaara: It checks for files that conflict between packages that don't declare the conflict properly, for all possible upgrade paths.  That way, it identifies issues users will encounter before the users encounter them.18:33
schwukheno_: In that case I suspect not - nothing like that is jumping out.18:33
sbeattieschwuk: there should be an Adminstration box in the left column.18:33
araheno_, persia: thanks18:33
heno_bdmurray, pedro_, sbeattie do you have hw/VMs and time to test a bit?18:33
sbeattieheno_: yes, I can help out.18:33
heno_we won't aim for full coverage for the alpha but absolutely need that for Beta18:34
bdmurrayI've no vm's but could test with my laptop I believe18:34
pedro_heno_: yep I'll do some, it will be slow since I'm using an old laptop atm but i can help anyways ;-)18:34
heno_ok, cool we should have decent coverage then18:34
heno_thanks folks!18:34
heno_[TOPIC]: http://status.qa.ubuntu.com - just an fyi18:35
* heno_ cheers ogasawara, stgraber and bdmurray for this work!18:35
ogasawarayup, just wanted to make an announcement here that the pkg stat pages have been pushed to production18:35
heno_new we just need to start pimping it :)18:35
ogasawaraI can make a more formal announcement to the ml18:35
schwuksbeattie: there isn't. heno_ could you fix my permissions please?18:36
heno_ogasawara: excellent, please do. -devel and -qa18:36
* ara hugs ogasawara, stgraber, bdmurray18:36
heno_schwuk: sure, after the meeting18:36
schwukwell done ogasawara, stgraber and bdmurray. They look good.18:37
heno_I'm sure we'll tweak the look and content as we go18:37
heno_the LP pages may also adopt some of this info with time18:38
heno_in which case we may need to revisit our offering18:38
heno_[TOPIC]: Posting meeting summaries on the QA blog (as the server team does).18:38
heno_Someone mentioned this would be a good idea18:39
heno_other teams may adopt this as well18:39
LaserJockI would personally rather have individuals blog about things18:39
LaserJockbut meeting summaries should be going to mailing lists for sure18:40
heno_mailings lists> agree18:40
persiaActually, I'd like to argue against such double posting.18:40
LaserJockpersia: in what way?18:41
persiaI personally find it annoying to have to skip the server team minutes in one forum or another depending on which I encountered first.18:41
heno_I think meeting summaries and announcements are appropriate for a team blog though18:41
persiaThen they oughtn't be on the mailing list.  I just object to the duplication.18:41
schwukheno_: +118:41
schwukpersia: people read in different places - just because you monitor both doesn't mean everyone will.18:41
heno_persia: but may people don't read both18:41
persiaOK.  Let me put this differently then.18:42
persiaIf we want to have an effective means of communication with people, we should direct them to some resource from which they can expect to get e.g. meeting summaries and announcements.18:42
persiaHaving multiple places where this information is presented is inherently confusing.18:42
LaserJockpersia: agreed18:43
persiaSome people may prefer one or the other, but there's no reason one can't provide RSS of a mailing list, or receive a blog in one's inbox.18:43
LaserJockI personally dislike that the Server Team puts the log on Planet, it just seems inappropriate18:43
schwukLaserJock: Why? It's Ubuntu related.18:44
LaserJockschwuk: because it's against Planet Ubuntu's stated purpose18:44
LaserJockand makes it hard to find the stuff that it *is* supposed to have18:44
heno_perhaps we should have a team planet where such things go18:44
bdmurrayLaserJock: where is this stated purpose?18:45
LaserJockbdmurray: on http://planet.ubuntu.com18:45
heno_then you could get all announcements and summaries there18:45
bdmurrayIs the QA Team not a contributor?18:45
schwuk"Planet Ubuntu is a window into the world, work and lives of Ubuntu developers and contributors."18:45
persiaheno_: Do you mean like the stated purpose of the fridge?18:45
LaserJockwhy not put announcements and summaries where they go?18:45
persiabdmurray: No, the QA Team is a Team.18:46
schwukMeeting minutes seem to fit the bill there LaserJock.18:46
pedro_do you mean persons and not projects ?18:46
LaserJockand let Planet Ubuntu do what it's supposed to, aggregate individual blogs18:46
pedro_so you should move all the projects blogs to somewhere else then18:46
bdmurraySo if were to blog about the pkg landing page who should do it? me? ogasawara? stgraber?18:46
heno_it provides an insight into our work18:46
LaserJockpedro_: +1 to that18:46
bdmurrayIt was a team effort18:46
pedro_well the GNOME project does that planet.gnome.org/news <-18:46
heno_persia: I agree that would be more appropriate actually18:46
pedro_and i think nobody visit that page18:46
heno_can we teach the fridge to aggregate team blogs as well as atricles?18:47
LaserJockbdmurray: anybody/everybody18:47
heno_*articles18:47
LaserJockbdmurray: you can individually talk about the stuff you want even18:47
persiaheno_: I'll admit that much of the info on the fridge is duplicate to info in my mailing lists, but I'm less bothered by that, if only because I expect the fridge to have such summaries.18:47
LaserJockheno_: teams can just submit a story for inclusion in Planet18:48
persiaheno_: Very likely.  Contact ubuntu-news-team@ I've yet to have a request not posted relatively quickly.18:48
heno_ok, I'll check in with other team leads and fridge editors18:48
LaserJockFridge editors want more stuff to put up18:49
heno_it would be easier if we had a simple technical gateway so we could post post directly18:49
heno_but I dream :)18:49
LaserJockheno_: agreed18:49
heno_any other business?18:49
stgrabersorry, I wasn't around for the last few minutes :(18:49
stgraberbdmurray: having something on the fridge seems to be a good idea, we can still individually blog about it18:49
heno_(so we'll not blog meeting summaries for now)18:50
LaserJockwhat about a Testing Day?18:50
LaserJockI totally dropped the ball on sending an email to ubuntu-qa last week, sorry :(18:50
persiaThanks.  Apologies for the noise about it, it's just one of my pet peeves with the server team, and I actually care more about reading the QA summaries as I'm often not awake for the meeting.18:50
heno_today would be a great testing day! :)18:50
LaserJockheno_: are available to support a testing day?18:51
heno_LaserJock: do you want to try to organise something for next week?18:51
LaserJockbah, *are people available18:51
araI think that someone should be the person in charge of this and try to coordinate efforts18:52
araping people to add the information to their blogs, create wiki pages, etc.18:52
LaserJockheno_: I'd personally rather somebody closer to ISO testing were organizing it18:52
heno_agreed - I have limited bandwidth atm though18:52
heno_stgraber, sbeattie, schwuk, ara: ^ volunteers?18:53
LaserJockthe thing I'm kind of most concerned about is making sure that the release team is coordinated with18:53
araI could do it, maybe for the beta?18:54
LaserJockwhen I've done ISO testing before a lot of the time the candidates were invalidated before I even got them downloaded18:54
schwukLaserJock: when were you thinking for?18:54
araor is it too late? alpha 6 maybe?18:54
LaserJockit's critical for gaining testing contributors that we don't waste their time18:55
heno_LaserJock: that's an inherent problem with the process unfortunately18:55
LaserJockheno_: perhaps, but maybe we can do some stuff about that18:55
heno_ara: I think we should start with alpha 618:55
heno_so we can work out the kinks for beta18:55
heno_ara: thanks for stepping up!18:55
LaserJockI think we should plan a Testing Day for *every* alpha, Beta, RC until Intrepid is released18:55
heno_LaserJock: agreed18:56
LaserJockwe don't have to make a huge deal over it, just blog it, announce it to ubuntu-devel-announce perhaps, and make sure people are around to help18:56
LaserJockit sets us up well for Intrepid+118:56
heno_ara: you may want to take advice from dholbach who coordinated the bug jam18:56
araheno_: ok, i will18:57
LaserJockone thing I've been thinking about is not throwing away results when an ISO is invalidated18:57
aramonday sep 22nd? it is a couple of days after the alpha, so at least we should know that the minimum test passes18:57
schwukara: let me know if you need any help with organising it18:57
LaserJockcan we let people continue testing whatever .iso they manage to get and add that information somehow to the total testing?18:58
heno_LaserJock: we had that feature on the tracker before but it's gone missing :(18:58
heno_22nd sounds good18:58
LaserJockso we'd have like the last few .isos on the tracker, but somehow distinguishing from the current candidate18:59
LaserJockand then people can just not file bugs on known .iso issues18:59
persiaOr can be referred to existing bugs if there is good guidance on how to title the bugs.19:00
LaserJockyeah19:00
heno_I don't think we should collect results from obsolete ISOs but we should keep historic data in view when considering release-readiness19:00
LaserJockI just think it's awful disheartening to download the thing, burn it, and do a test, only to have your results tossed out a minute later, if not earlier19:01
heno_rsync is pretty quick though if the changes are minimal19:01
heno_ok, we are out of time19:02
LaserJockI've got several hours before without getting a single valid candidate tested19:02
LaserJock*gone19:02
sbeattieLaserJock: note that for the testing day, we're talking about testing alpha 6 as is, not candidates for alpha 6.19:02
heno_let's continue in #u-q19:02
LaserJockit's not just download19:02
heno_#endmeeting19:02
LaserJocksbeattie: I think we should do both19:02
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 09 Sep 15:00: Server Team | 04 Sep 13:00: Desktop Team | 05 Sep 20:00: MOTU | 08 Sep 04:00: Arizona LoCo IRC | 12 Sep 15:00: Ubuntu Release | 14 Sep 18:00: Mozilla Team
Seeker`#startmeeting20:24
persiaSeeker`: The Bot is hibernating.20:39
Seeker`persia: We are currently trying to fix it20:39
persiaCool!20:40
Seeker`people should prod me harder if it stops working20:40
persiaSeeker`: Sorry.  I didn't know who to prod.  I'll hunt you agressively next time it doesn't work.20:43
Seeker`:D20:43
Seeker`#startmeeting20:45
MootBotMeeting started at 14:45. The chair is Seeker`.20:45
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]20:45
Seeker`#endmeeting20:45
MootBotMeeting finished at 14:45.20:45
jpdsSeeker`: Yay.21:09

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