=== ubotu changed the topic of #ubuntu-meeting to: Current meeting: TriLoCo-Midwest Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Feb 19:00 UTC: Platform Team | 20 Feb 20:00 UTC: Education Team | 20 Feb 21:00 UTC: Server Team | 21 Feb 14:00 UTC: Desktop Team | 21 Feb 20:00 UTC: Community Council [02:29] @schedule cst [02:30] @schedule chicago [02:30] Schedule for America/Chicago: 20 Feb 13:00: Platform Team | 20 Feb 14:00: Education Team | 20 Feb 15:00: Server Team | 21 Feb 08:00: Desktop Team | 21 Feb 14:00: Community Council | 27 Feb 06:00: Education Team === ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Feb 19:00 UTC: Platform Team | 20 Feb 20:00 UTC: Education Team | 20 Feb 21:00 UTC: Server Team | 21 Feb 14:00 UTC: Desktop Team | 21 Feb 20:00 UTC: Community Council | 27 Feb 12:00 UTC: Education Team [04:08] hello === lokisan is now known as FeRcHo === FeRcHo is now known as fe === fe is now known as eBeneezer === eBeneezer is now known as spark1 === spark1 is now known as switc1 === switc1 is now known as cras1 === cras1 is now known as acidburn [04:18] hello there [04:18] noones talking... so boring.... === cjwatson_ is now known as cjwatson [06:55] good morning [06:55] the fridge calendar is wrong, apparently; I've poked them about it [06:55] good morning [06:56] good $timeofday [06:56] good morning (well, almost) [06:57] I've not forgotten, just come back from an hour away from the keyboard after my stint today. [06:57] morning [06:58] TheMuso: perfect timing [06:58] Hey evand. [06:58] * asac waves [06:58] yaaawn [06:58] morning [06:58] evand: WHen you have a minute, we need to talk re dmraid. I just read your report. [06:58] hi TheMuso, good evening to you. [06:58] TheMuso: sure [06:59] ok, so first things first, I've noticed that I'm taking a while to get the meeting notes out [06:59] would anyone like to volunteer as a secretary? [06:59] it's not particularly hard, I just find it tends to get pushed out of the way by other stuff [07:00] I'll do it if nobody else has a desire to... (Knowing that his essentially commits me to doing them, but oh well.) [07:00] I have done a few MOTU meeting minutes, so I know its not hard. [07:00] more than one volunteer means you get to alternate ;-) [07:01] There is that yes. [07:01] or use mootbot? [07:02] mootbot might help but won't suffice; we want something human-edited [07:02] I don't think mootbot is applicable for these meetings. [07:02] No real need. [07:02] BTW, though I haven't historically got round to it, the notes should go up on the wiki somewhere as well as being posted to distro-team [07:03] TheMuso: ok, thanks for offering, and in that case please go ahead [07:03] cjwatson: Ok. What wiki URL format do we want to use? [07:04] I.e do we want the minutes udner a particular area in the wiki? [07:04] desktop is DesktopTeam/Meeting/YYYYMMDD [07:04] so PlatformTeam/Meeting/YYYYMMDD sounds good to me [07:04] fair enough [07:05] * Actions from last week: [07:05] * Arne to consult with Martin and Michael regarding [07:05] langpack-o-matic/language-selector work [07:05] ArneGoetje: I understand Martin's side is done; how is Michael's side going? [07:06] mvo will do it, I guess he was to busy yesterday, but it is on his agenda for these days [07:06] ok, as long as it hasn't fallen off [07:06] * Chris to check whether en_GB strings where msgid == msgstr have [07:06] been stripped out of the English langpacks [07:06] nope, it hasn't. I'll keep you posted [07:07] calc: you mentioned something about this last night; any further progress? [07:07] cjwatson: hadn't had a chance to talk to doko about it yet, been beating on the xulrunner stuff most of the day [07:07] cjwatson: i emailed him but i don't know if he read it yet [07:08] doko_: i seem to recall you mentioning before if we strip out messages it causes problems with OOo is that the case for cjwatson is talking about here? [07:11] doko_: are you in fact here? [07:11] ok, I think doko is present in body but not in spirit [07:12] let's move on and we can come back to that if he appears [07:12] * LTS point release team [07:12] ok, well i think he had said before that it causes crashes, but i may be misrembering and i'll try to find out for certain asap [07:12] calc: indeed, this ought to be subject to experimental verification once you get a chance [07:12] ok [07:13] so, as I think has been mentioned, we're going to be doing point releases of 8.04, as an LTS [07:14] and we would like to put enough resources into that to make it pretty respectable, without burning people out who are already focusing on 8.10 development [07:14] most likely in the middle of the server support cycle? (e.g. 2.5 years?) [07:14] asac: more frequently than that; the first point release is likely to be a few months out from 8.04 itself [07:15] I don't want to go into an exact schedule since this is a public channel and we haven't settled on it yet, and rumours do tend to spread :-) [07:15] cjwatson: Will it be similar to 6.06.2, where it will only be for servers, and not desktops? Or does that depend on what has been fixed? [07:15] cjwatson: ok [07:15] TheMuso: in this case it'll be both [07:16] 6.06.2 was just servers because desktops were starting to look not worth the effort given the support lifetime [07:16] Yeah I thought thatwas the case. [07:16] but, in this case, it's a question of keeping a few desktop guys focused on 8.04 when they would ordinarily have switched over [07:16] like catching up on features that didn't make the real release? [07:17] the current agreement is for Steve to lead this effort, and have a virtual team of a few platform, a few desktop, a few server, a few QA [07:17] asac: I think catching up on bug-fixing is more likely [07:17] ok [07:17] this is, essentially, a stabilisation effort [07:17] are we really large enough to lose that many people to such an effort without feature development in the next release seriously suffering? [07:18] feature development in 8.10 will likely take some kind of a hit, yes [07:18] although I don't think it will be a critical one [07:19] this is sort of similar in some ways to what we did with the 6.06 delay and its effect on 6.10, but hopefully a bit less severe [07:19] ok [07:19] while 6.10 didn't open until June, 8.10 will open in April or early May as usual, and everyone who isn't still focused on 8.04 will be able to get it up and running [07:20] 8.04 is more important in many ways, though, and there is growing consensus that we need to be able to deliver stable and timely point releases of LTSes, rather than it being a side effort [07:21] so what I want to do here is both explain what's happening and answer questions on it, and also look for the right people to take part in this from this group [07:22] my feeling is that it should be the people who would be most snowed under with SRU work anyway [07:23] and also people with a capacity to field general platformish bugs from all over, which QA will be hunting down [07:24] deafening silence :-) [07:25] you scared them all off! [07:26] well, I don't fit the criteria... :) [07:26] bryce: I suspect we may need somebody able to field X problems, for instance [07:26] cjwatson: sure thing [07:26] ok, I think I will select people over the next week or two and talk with you about it [07:27] but if you feel you are particularly appropriate or inappropriate for the task, please shout [07:27] * Routines post-FF [07:28] I think I'd probably be inappropriate only because there is a lot of a11y stuff happening next cycle, and we need to keep on top of it, however, if I'm asked, I'll consider it. [07:28] TheMuso: *nod*, thanks [07:29] this is perhaps obvious to old-timers, but I just wanted to sketch out the routine from here to 8.04 so that everyone is clear on what we're expected to be doing from here on [07:29] with the exception of a few ... exceptions, features should be complete, although I expect that many of them may still need to have their bugs shaken out [07:30] for anything non-trivial, please go to special effort to gather explicit testing, and fill out the testing plan section on the wiki specification [07:30] other than that, we should be in full steam for fixing as many bugs as we can for hardy, and making it a great stable release [07:31] Leann has prepared a qa-hardy bug list just for us, http://people.ubuntu.com/~ogasawara/qa-hardy-list-archive/sort-by-package/platform-buglist.html [07:31] Nice [07:31] * TheMuso bookmarks [07:32] if you have things on that, please either talk to me or her about untagging them (there's at least one infeasible grub bug I need to get untagged), or fix them at your earliest convenience [07:33] please also make sure you are adequately kept informed of new bugs coming in, and make sure to be responsive to them [07:33] the firefox bugs don't make much sense ;) ... we should untag them all [07:33] even those you can't fix should get an update and forwarded upstream where appropriate [07:33] i will talk with lean to figure the real bugs [07:33] asac: thanks [07:34] cjwatson: regarding feature exceptions, I'd like to talk with you about the xrandr configuration gui - RedHat is working on a tool which will be going upstream, and I'd like your direction about adopting and polishing that. Or perhaps since we're past FF, other options I should take. [07:34] asac: looks like she was trying to gather the most-duplicates crash reports [07:34] bryce: yep, was going to come to that shortly [07:34] ok cool [07:35] in order to be kept informed of new bugs and new comments on existing bugs, Launchpad really isn't quite up to providing the sort of feed-type information you'd need to do this entirely with the web UI yet, and so it's important that you become friends with bugmail if you aren't already [07:35] pitti wrote https://wiki.ubuntu.com/Bugs/HowToFilter which may be helpful in dealing with the flood [07:36] X-Launchpad-Message-Rationale is a useful filter. [07:36] * TheMuso uses that for all bugmail that doesn't go to an ML. [07:39] bryce: ok [07:39] bryce: my concern on your question is that I thought you were already some way into your UI, and were nearing feature-completion [07:40] the UI is pretty well done, and I have been working on the application of the xrandr changes. [07:42] I estimate being about a week from having it feature complete, however the redhat tool is more likely to be accepted upstream [07:42] what's the current state of the RH tool? [07:43] it is functional and feature complete except for a couple minor things, but needs integration / packaging work done to it, and the UI needs a few tweaks [07:43] I dug through it and experimented with it a bit over the weekend, and it looks pretty well thought out. It does need polish though. [07:44] I assume you only became aware of it over the last week? :-) [07:44] correct; I learned about it wednesday [07:45] is the reason that RH's tool is more likely to go upstream that it is being written by existing core X developers? [07:45] it came to light after I proposed what I was working on to the gnome-control-center list (whose archives I'd dug through before starting my effort) [07:46] The RH person working on it has been involved in gnome-control-center in the past, and I gather had discussed this with some of the gnome folks at a conference a while ago [07:48] hard choice [07:48] yeah [07:49] it sounds like the best plan is to grab desktop team folks and talk about the best way to get the RH work integrated ASAP; if possible, perhaps even for alpha 5 [07:49] (though that's very close now) [07:49] other options I've thought about include just setting it aside for now, and fixing up displayconfig-gtk best we can, or even just dropping gui config and sticking with the command line solutions [07:49] but keep your existing work around in case we need to fall back to that [07:49] * bryce nods [07:50] we'd already decided against displayconfig-gtk, I thought, and I don't think a command-line solution is good enough [07:50] yup [07:50] it is unfortunate that it's one more thing that the /. crowd can complain came from RH rather than Canonical ... but so it goes [07:52] yep, I was really looking forward to putting something from canonical upstream but I really get the sense it's not going to be an option here. [07:52] bryce: definitely grab seb128 and talk through it with him [07:52] great, thanks, will do. [07:52] any other business? [07:53] maybe can take care that the previous meeting minutes go to wiki/public as well? [07:54] wiki/public? [07:54] I can do that over time, though I will have to check that I didn't put anything confidential in them [07:54] * What's the status of the pycentral issue? We haven't had a new live [07:54] filesystem since the 9th. [07:54] cjwatson: ok [07:54] pycentral only came up yesterday; I thought Michael fixed it yesterday too? [07:54] evand, fixed [07:55] my dist-upgrade just went through like a breeze [07:55] I updated during today to find it fixed. [07:55] bug 192992 is still Confirmed [07:55] Launchpad bug 192992 in python-central "[hardy] pycentral crashed with ValueError in parse_versions()" [High,Confirmed] https://launchpad.net/bugs/192992 [07:55] is it fixed? the bug is listed as open [07:55] i dont think mvo added any LP entries to his changelog [07:55] ah, we still seem to have trouble with the following though: [07:55] so need to be closed manually [07:55] ssl-cert [07:55] cupsys [07:55] cupsys-driver-gutenprint [07:55] hal-cups-utils [07:55] ubuntu-desktop [07:55] not saying that's related to pycentral though [07:55] from: http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/hardy/ubuntu/20080220/livecd-20080220-amd64.out [07:55] cupsys is likely java related [07:56] (that's from an hour or two ago) [07:56] and desktop is because of cupsys indeed [07:56] ogra: ok; it was fixed in a python-central upload though, right? [07:56] slangasek, yep [07:56] mvo isnt around yet i think thats the reason he didnt close it yet (wanting feedback first) [07:57] ogra: cupsys fails because it depends on ssl-cert which fails [07:57] (read the log :-)) [07:57] well, i was guessing :) [07:57] ok, good to hear it's fixed then, that means I'll be able to get to sleep sooner tonight :) [07:57] ssl-cert looks like it's failing because hostname says "Unknown host" [07:57] heh [07:57] oh ugh, that'd be my bug then [07:57] yeah, seems the network connection on the buildds sucks ... :) i just learned that with edubuntu-addon-meta :) [07:57] cjwatson: the only change is hostname -> hostname -f; why does the one work and the other fail in the livefs build env? [07:58] (hmm, we can take that out of the meeting) [07:58] (joking) [07:58] we do need to get new live filesystems today, but that's obvious :) [07:58] ok, if that's all, then we'll adjourn [07:58] thanks all [07:58] goodnight everyone :-) [07:58] thanks! [07:58] thanks [07:58] thank! [07:58] Np, minutes may either be tongiht my time, but certainly tomorrow. [07:58] thanks [07:59] my time [07:59] thanks [07:59] thanks === awalton__ is now known as edud_eoqqq === edud_eoqqq is now known as awalton__ === doko_ is now known as doko === cjwatson_ is now known as cjwatson === Adri2000_ is now known as Adri2000 === cjwatson_ is now known as cjwatson === mrevell is now known as mrevell-lunch === ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Feb 20:00 UTC: Education Team | 20 Feb 21:00 UTC: Server Team | 21 Feb 14:00 UTC: Desktop Team | 21 Feb 20:00 UTC: Community Council | 27 Feb 07:00 UTC: Platform Team | 27 Feb 12:00 UTC: Education Team === _czessi is now known as Czessi === mrevell-lunch is now known as mrevell === dholbach_ is now known as dholbach === mc44_ is now known as mc44 === asac_ is now known as asac [17:26] is there anyone here from the community council? [17:34] anyone? === mvo__ is now known as mvo [18:43] heya === Pricey is now known as PriceChild [18:59] hello! [18:59] * ogasawara waves [18:59] hi! [19:00] hola [19:00] hello [19:00] Hi [19:00] * stgraber waves [19:01] hey everyone! [19:01] let's start [19:01] #startmeeting [19:01] Meeting started at 19:01. The chair is heno. [19:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [19:01] agenda: https://wiki.ubuntu.com/QATeam/Meetings [19:02] [TOPIC] qa-hardy-list promotion [19:02] New Topic: qa-hardy-list promotion [19:03] ogasawara: thanks for splitting that up. I've emailed various lists about it and will attend IRC meetings to follow up [19:03] I don't think that needs discussion [19:03] [TOPIC] QA poll site beta testing [19:03] New Topic: QA poll site beta testing [19:03] hi! sorry, a bit late [19:04] nand: just getting to your topic [19:04] heno: Do you promotion in terms of advertising? [19:04] perfect timing :) [19:04] heno: some news on the subdomains? [19:04] bdmurray: yes [19:04] nand: http://brainstorm.ubuntu.com/ ... [19:05] it's up? [19:05] bdmurray: any further ides on that? [19:05] nand: yes [19:05] heno: no, I was thinking of promotion as "escalation" not promoting [19:05] but I guess it needs some drupal magic [19:05] hmm, cookie seems broken on brainstorm.ubuntu.com [19:06] nand: the cookie thing I told you about ^^ [19:06] I'm all set now though [19:06] ok, cool [19:06] nice! Tomorrow, we'll update the htaccess and sql updates [19:06] stgraber: yes, I guess we will have to do with it [19:07] That will give us a short time to test [19:07] should we devise a test plan for the site? (everyone here add 3 ideas and 3 bugs or something) [19:07] nand: well, as it's now I just can't login on brainstorm.u.c, so I'll have to update the cookie part of the config file to fix that [19:07] just asking 'please test' doesn't seem to be working [19:08] indeed :) [19:08] yes, let's ask everyone to add a few bugs/ideas, at least to have some pagination [19:09] ok, hands up all who volunteer to add 3 items to each site and do some voting and poking around [19:09] o/ [19:10] what a crowd today :) [19:10] [... silence ...] [19:10] ok, I'll flood it myself... [19:10] I'll try to do some testing [19:10] I can o/ [19:10] it should take about 7 minutes :) [19:11] heno: do you want to know right now the planned release date, to coordinate and such? [19:11] nand: did you switch to GET instead of POST for the ajax stuff in your next commit ? (I'm not sure it'll fix my PROXY bug but it's worth a try and shouldn't cause any regression) [19:11] does everyone have access to the beta? [19:11] if everyone means people speaking in this chan, then yes [19:12] stgraber: not yet. I'll try tonight [19:12] ok, cool [19:12] I was thinking of Thursday the 28th as a release date [19:12] stgraber: I've logged in and it doesn't work here, I've got a cute 403 again [19:13] pedro_: use qa.ubuntu.com/qapoll/ideas and qa.ubuntu.com/qapoll/bugs instead [19:13] stgraber: I can't log in either as above [19:13] pedro_: brainstorm.u.c doesn't work yet [19:13] davmor2: same as pedro_ [19:13] wait for tomorrow's update [19:13] stgraber: yes [19:13] ok ok [19:13] 28th : we can try for it [19:14] monday we reset everything, remove the restriction [19:14] that means everything must be ok friday [19:14] stgraber: ping me when it's safe to test [19:14] I'll be on holiday next week so I should have time to fix last minute stuff for the release [19:14] nice [19:15] davmor2: you can use qa.ubuntu.com, it'll be the same module but with a different URL [19:15] yeah I just noticed that too. brainstorm.u.c won't work just yet i guess [19:15] stgraber: yes I mean the brainstorm [19:15] bdmurray, ogasawara: please have a quick poke at the bugs part at least http://qa.ubuntu.com/qapoll/bugs/ [19:15] nand: IIRC the site config which contains the cookie definition is a php file, so we probably can update the cookie field depending on the URL [19:16] nand: the user will have to login twice anyway [19:16] heno: will do [19:16] heno: okay [19:16] davmor2: brainstorm.ubuntu.com will be an alias for http://qa.ubuntu.com/qapoll/ideas [19:17] about launch date: I'm happy for nand and stgraber to decide on that [19:17] stgraber: that works :) so you just want a bunch of ideas dropping in there to test it? [19:17] davmor2: yep [19:17] stgraber: np [19:17] * heno looks at https://wiki.ubuntu.com/HardyReleaseSchedule [19:18] nothing bit happening just after Alpha 5 [19:18] 28th will be the UI/artwork freeze [19:18] *big [19:18] Isn't it a bit late for ideas since we are past feature freeze? [19:19] heno: How many days before the release do you want to be warned, for coordination and stuff? [19:19] bdmurray: these would be seed ideas for the next UDS [19:19] bdmurray: of course, it's ideas for hardy+1 :) [19:19] bdmurray: it can be like the one I am currently writing an on going idea :) [19:20] Okay, they doesn't seem to be conveyed at qapoll/ideas/ [19:20] bdmurray: well, just report those as usability bug then :) [19:20] nand: a day or two is fine for me personally [19:20] ok [19:21] I do want to write some docs explaining the purpose of each site [19:21] can we have an About link on each? [19:21] I think managing people's expectations is important and should happen right at the site. [19:21] stgraber: seems to work fine :) [19:21] yes, we should. And with some contacts too [19:22] bdmurray: agreed [19:22] nand: I did a quick demo of QA-Poll to one of my teachers this morning and something that was hard to understand/use was the duplicate UI [19:22] I think instead of the "Ubuntu website" link, we could put a "About" box [19:23] stgraber: what was confusing? [19:23] nand: IIRC, you can't just select two ideas in the idea list and mark those as duplicates and the link on the idea page was hard to find [19:23] sounds good [19:23] let's continue the details of that in #u-testing or so [19:24] [TOPIC] Kernel bug list migration. see: https://wiki.ubuntu.com/QATeam/KernelBugMigration [19:24] New Topic: Kernel bug list migration. see: https://wiki.ubuntu.com/QATeam/KernelBugMigration [19:24] ok, please continue! [19:24] ogasawara and I have been looking at this with the LP folks [19:25] it's a sensitive issue; automatically modifying lots of bugs [19:25] the transition to a new package name is a good time to do it though [19:26] pedro_: have you been doing the gaim -> pidgin migration? any fall-out from that? [19:26] heno: I think as long as we are clear to our bug reporters that we are not closing their bugs but rather making sure we're carrying them forward we won't have too much backlash [19:26] ogasawara: I check with markus regarding adding a task [19:27] heno: it was just for the upstream project and there's like 20 bugs or so, so changing that wouldn't be hard [19:28] so are we agreed on the approach? add a 'linux' task set to incomplete and set the others to 'Won'f fix'? [19:29] at point 4 of the process which metadata you loss if you change the task from linux-source-something to linux? [19:29] the name of the package? [19:29] can that be resolved with a tag? [19:29] yeah, what meta data is lost? [19:30] I'm concerned about "Won't fix"ing some that may be sru worthy [19:30] because for me it seems that the option 4 is the best one [19:30] i was concerned about losing the history of a bug being open across multiple releases [19:30] bdmurray: are you worried that they will slip off our radar as well (the won't fix can be changed again) [19:31] I seem to recall talking about Ben about that and that is something he didn't want to lose. [19:32] heno: I think that 2.6.15 or 2.6.22 bugs that are high or critical should be manually inspected. [19:32] bdmurray: agreed, I assume we can black list those in the script [19:33] or ust looked at first [19:33] *just [19:33] when should we move forward with this? do we need a dry run of some kind? [19:34] right, either way. [19:34] we'll need to investigate the adding new tasks functionality with plb [19:36] ok, let's add a todo list to https://wiki.ubuntu.com/QATeam/KernelBugMigration [19:37] I'll add it [19:37] * new task functionality, * manually clean up some categories of bugs, * dry run, * live run [19:37] or so [19:37] ok, cool. net topic [19:38] ah, my typing sux today :( [19:38] [TOPIC] malone buglist - tagging these so they are viewable in Launchpad. see: http://people.ubuntu.com/~ogasawara/malone-buglist.html [19:38] New Topic: malone buglist - tagging these so they are viewable in Launchpad. see: http://people.ubuntu.com/~ogasawara/malone-buglist.html [19:38] heno: my typing sucks everyday :) [19:39] so mpt was inquiring why we don't just tag the bugs lists here and then use lp to display them [19:39] I assume we are looking for volunteers here? ;) [19:39] I have a script to tag bugs [19:39] ogasawara: right, that's what bjorn wants as well [19:39] * heno cheers ogasawara [19:39] so can we agree on a tag name? [19:39] let's JUST DO IT [19:39] ubuntu-qa? [19:40] sounds good, that lets other teams use ubuntu-desktop etc. [19:41] How could we convey the importance of the bug to us? === calc_ is now known as calc [19:43] we don't do it ATM, apart from the comment column [19:43] we could easily just have it as part of the tag for ex - ubuntu-qa-high [19:43] adding a separate tag or changing it to ubuntu-qa-high both seem like cludgy [19:43] Actually, I'm not certain how useful that is. [19:44] ogasawara: yeah, but then you have to search on 3 tags [19:44] I mean its no different than someone saying I have to have this piece of hardy working. [19:44] does lp allow you to search for more than one tag? [19:44] right... [19:44] pedro_: yup [19:44] wow, bad typing is contagious. I meant this piece of hardware [19:44] bdmurray: does this list not pertain to bugs already listed if so wouldn't the bug itself have a rating? [19:44] perhaps we should just pick out our top 10 and email the list to bjorn [19:45] ... once a week :) [19:45] heno: heh [19:45] does the Importance that's already set in the report not properly reflect the priority we think it should be? [19:46] ogasawara: often not; as that's LP's own take on the priority [19:46] ogasawara: That's my point I think. Just put better :) [19:46] Ubuntu is only one of many users of LP (though by far the biggest ATM) [19:47] can we use ubuntu-qa + ubuntu-high? [19:47] so will us marking our own priority actually get them to resolve it faster? [19:47] Thinking about it some more I've never seen a definition of how the Launchpad team uses bug Status, but it is probably not the same as we, the Ubuntu distro, use them. [19:47] that way you avoid the permutations at least [19:48] and you can get a full ubuntu-qa list easily [19:48] I think by shoehorning our priority in there we are setting a bad precedent. [19:49] that's true [19:49] I think we should be no different than any other lp users [19:49] we see reports all the time where bug reporters feel their bugs are top priority [19:49] I think intel do this on some bugs [19:49] with an intel-high tag === ubotu changed the topic of #ubuntu-meeting to: Current meeting: Education Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Feb 21:00 UTC: Server Team | 21 Feb 14:00 UTC: Desktop Team | 21 Feb 20:00 UTC: Community Council | 27 Feb 07:00 UTC: Platform Team | 27 Feb 12:00 UTC: Education Team [19:50] heno: right, they do [19:50] shall we proceed with just the ubuntu-qa tag and look at social forms of communicating priority first? [19:50] email and bug comments [19:50] that sounds best to me [19:50] agreed [19:50] sounds good [19:51] good, next topic [19:51] [TOPIC] yesterday's bugs formatting discussion draft at https://wiki.ubuntu.com/NewBugs/20080219 [19:51] New Topic: yesterday's bugs formatting discussion draft at https://wiki.ubuntu.com/NewBugs/20080219 [19:52] are we getting a wiki page for each day? [19:52] not yet, I wanted opinions on its utility / formatting [19:53] could be useful for 5-a-day work [19:53] I was thinking having a column for the sourcepackage might be more useful than the Status/Importance [19:53] someone might chose to focus on those pages [19:53] heno: right, I also though it would be useful in "staying on top" of New bug reports [19:54] yep Status/Importance is a bit pointless here [19:54] of the 170 new yesterday 123 are still New [19:54] that's very approximate [19:55] I think it'd be helpful to see the package name [19:55] but some are fix released :) [19:55] how often is it updated? ever? [19:55] I think that's why there is the disclaimer at the top no? [19:56] it would be very cool to look at a page like this from a month ago [19:56] It isn't updated and the query took about 140 minutes [19:56] with updated statuses [19:57] eeek [19:57]