[03:19] @schedule sydney [03:19] Schedule for Australia/Sydney: 13 Dec 10:00: Kubuntu Developers | 14 Dec 01:00: Desktop Team Development | 19 Dec 02:00: Server Team meeting | 21 Dec 01:00: Desktop Team Development [03:22] The more I see ubotu do, the more useful he appears :) [03:22] kudos to ubotu's developer [03:22] ardchoille: ther eare multiple [03:22] ardchoille: and contrary to what scottk says, kubuntu and ubuntu membership are pretty much the same. [03:23] Hobbsee: Ah, ok.. well I'm on the agenda for both. I just didn't wanna miss the meetings. [03:25] What does ScottK have to say about that? [03:25] CC meetings take forever [03:25] He told me to become an Ubuntu member and bug Hobbsee until she added me to kubuntu membership too [03:26] That was cute of him [03:26] scottk has now been enlightened. [03:27] somerville32: people make mistakes at times. [03:27] somerville32: do you even have an edubuntu council yet? [03:27] Hobbsee, I'm pretty edubuntu has a council but I'm not a part of it. I only got involved in Edubuntu recently [03:27] *pretty sure [03:28] erm, s/edubuntu/xubuntu/ sorry. [03:28] No, it doesn't have a council - just xubuntu-team really [03:28] edubuntu has a council [03:29] cool === asac_ is now known as asac === doko_ is now known as doko === \sh_away is now known as \sh === _czessi is now known as Czessi === Shely is now known as Schneeflocke === dholbach_ is now known as dholbach === Gunirus is now known as [Gunirus] === Hobbsee is now known as Peer === Peer is now known as Hobbsee [15:53] hi [15:57] * asac waves [15:57] hi [15:58] hi [15:58] hi, evand [15:58] * pedro_ waves [15:58] evand, asac: do we have a meeting room clash again? - platform/qa [15:58] ah, apparently [15:59] hi liw [15:59] hrm, off to #ubuntu-platform then [15:59] oh [15:59] * ArneGoetje waves [16:00] * Hobbsee wonders why neither of them are on the fridge calendar. [16:00] ArneGoetje: -> #ubuntu-platform [16:00] hi [16:00] asac: got it [16:00] seb128: u2 ;) [16:00] * heno did email the fridge editors requesting a posting [16:01] did you sacrifice a pigeon? they're quite partial to pigeons. [16:01] * bdmurray wonders what he missed [16:01] heh [16:01] quite unlike launchpad, really. perhaps a good thing, that. [16:01] bdmurray, :) "* heno did email the fridge editors requesting a posting" [16:02] bdmurray: only discussions about sacrificing qa developers for various causes. [16:02] only if we run out of pigeons [16:02] Weird, I think I had a dream about being eaten by a hippo last night [16:03] #startmeeting [16:03] Meeting started at 16:03. The chair is heno. [16:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:03] https://wiki.ubuntu.com/QATeam has the agenda [16:03] Welcome all! Agenda: https://wiki.ubuntu.com/QATeam [16:04] [TOPIC] Cool QA stuff happening [16:04] New Topic: Cool QA stuff happening [16:04] This shouldn't require much discussion, just FIY [16:05] all very cool though :) [16:05] I have a quick question [16:05] ok [16:06] ogasawara, how close are you to accepting random new sources of information with the weather report? I'm thinking that the hardy piuparts results might be a good addition [16:06] liw: should be easy enough, it's basically just a template that I dump the data to [16:07] ogasawara, ok, in that case could you e-mail me what you would need from me? I can adjust the piuparts output to what you need easily [16:07] liw: will do [16:07] ogasawara, when you're ready to add things, that is, no hurry yet from me [16:08] liw: how would you plan to condense it? Total number of errors, warnings, etc? [16:08] ok, I'm done on this topic :) [16:08] heno, in useful ways that I haven't decided yet :) [16:08] ok [16:08] anyone else on this topic? [16:09] moving on [16:09] [TOPIC] Spec status: https://wiki.ubuntu.com/QATeam/Specs [16:09] New Topic: Spec status: https://wiki.ubuntu.com/QATeam/Specs [16:10] any notable achievements or blockage on specs? [16:10] none here [16:10] (this meeting item will become more central later in the cycle) [16:10] nothing from me; I haven't really started work on the automated desktop testing thing, having spent my time wrestling with piuparts and qemu and wandering about the Spanish plains [16:11] none here either, just waiting for the QA feedback module === ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 12 Dec 20:00 UTC: Edubuntu | 12 Dec 23:00 UTC: Kubuntu Developers | 13 Dec 14:00 UTC: Desktop Team Development | 18 Dec 15:00 UTC: Server Team meeting | 20 Dec 14:00 UTC: Desktop Team Development [16:11] liw: the lintian and piuparts stuff could have been represented by a spec I guess [16:11] heno, I guess [16:12] ok, next [16:12] [TOPIC] QA hardy bug list - we are preparing a list of long-standing and 'popular' bugs for hardy which we will present to the development community shortly [16:12] New Topic: QA hardy bug list - we are preparing a list of long-standing and 'popular' bugs for hardy which we will present to the development community shortly [16:12] I just sent an email to the QA list about this [16:13] I've had feedback from Pedro by email so far [16:14] I think it sounds like a great idea; I don't have any particular bugs to suggest, though [16:14] I guess the main question is: can we do this in ~10 days? [16:14] (except anything I've reported myself, obviously ;-) [16:15] yes, that would be why I didn't post it to the ubuntu-users mailing list :) [16:15] every bug in LP would be nominated [16:15] bdmurray, ogasawara: views? [16:16] this list is going to be compiled with the best possible taste, I guess, not by voting? [16:16] liw: drawing on the accumulated knowledge of our esteemed triage team, yes [16:16] heno: I think I can get mine done by then [16:16] heno: yah, seems reasonable [16:16] The next hug day should be pretty easy to setup I think [16:17] bdmurray: focusing on this list? [16:17] we also have a few nominations here : https://launchpad.net/ubuntu/hardy/+nominations [16:17] heno: I meant it won't take that much of the rest of my time [16:17] pedro_: yep, I'll take on looking at those [16:18] bdmurray: ok cool [16:18] ok! [16:18] any other meeting topics? [16:18] ogasawara: and I have talked about it but we were thinking kernel bugs for the 19th [16:19] asking people to test with Alpha 2 [16:19] * liw has no more topics for today [16:19] bdmurray, ogasawara: sounds good [16:20] We could start doing some statistic collecing on the +nominations . . . [16:21] bdmurray: what sort of stats? [16:21] heno: just numbering gathering - the standard stuff [16:21] er number gathering ;) [16:21] heno: forums should be able to help you with that, too [16:22] * heno still has a fair number of +nominations to go through [16:22] interestingly 18 of the hardy ones are New [16:22] Hobbsee: yep, jono is looking at that [16:23] most of the gutsy ones i've looked at were new [16:23] (now generally something else) [16:24] heno: cool [16:24] Will everybody be around on the 2nd of January for the next Hug Day? [16:24] bdmurray: I'll be here [16:24] I will [16:24] pedro_: ? [16:24] yep me too [16:24] I will, too [16:24] assuming it is of any help [16:25] sure it is [16:25] finally note that there is a bug day today as well! focusing on ubiquity bugs. -> #ubuntu-bugs [16:25] #endmeeting [16:25] Meeting finished at 16:25. [16:25] ok, thanks all! [16:26] 25 minutes, not bad :) [16:26] we're learning :) [16:26] So Friday it will be 4 weeks past the update-manager bug day [16:26] * liw needs to run [16:26] bye bye [16:26] So please go through your Incompletes or I'll be happy to do it for you [16:26] I've a bugtriage suggestion [16:26] needs to mail the list about that [16:27] but it would be nice to encourage users to get backtraces using apport === sourcercito_ is now known as sourcercito [16:27] rather than pointing them to the "how to use gdb instructions" === \sh is now known as \sh_away [16:27] seb128: what do you mean? [16:27] that would be much easier for them and would allow automatic retracing and duplicates closing [16:27] bdmurray: https://wiki.ubuntu.com/Bugs/Responses [16:27] Missing a back trace [16:28] "Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at [WWW] http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem." [16:28] I meant more the process for using apport to get the back trace [16:28] hello [16:28] well, tell them to go to /var/crash and double click on the .crash [16:28] rather than send them to "how to get a backtrace using gdb" [16:29] okay, I understand [16:29] this way we get automatic retracing, dub finder, etc [16:29] and they don't have to figure what dbgsym to install [16:29] easier for everybody [16:31] seb128: If you could mail then list and/or add it to the todo list that would be great [16:31] I'll mail the list === ogra__ is now known as ogra === Martinp24 is now known as Martinp23 === ubotu changed the topic of #ubuntu-meeting to: Current meeting: Edubuntu Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 12 Dec 23:00 UTC: Kubuntu Developers | 13 Dec 14:00 UTC: Desktop Team Development | 18 Dec 15:00 UTC: Server Team meeting | 20 Dec 14:00 UTC: Desktop Team Development [19:52] is the edubuntu meeting in a few minutes? [19:53] yep [19:53] great, thanks [19:56] Is the kubuntu meeting going to be held in here in about 3 hours? [19:59] ardchoille- according to the fridge, yes [19:59] scrapbunny: Thanks. [20:00] I have a habit of being somewhere other than where I wanted to be, lol [20:00] * stgraber waves [20:00] "fridge", that was a cool name. I wonder who thought of that. [20:01] ardchoille, eff waugh [20:01] *jeff [20:01] :) [20:02] ok, I'm here [20:02] oh what a relief we can begin ... the *main man* Mr LaserJock is in attendance [20:02] :) [20:02] hah [20:03] thanks to the mailing list i finally figured out how to tell what time these meetings are at [20:03] evening all ... the usuals ... and welcome to any newcomers [20:03] scrapbunny, yeah the fridge urgently needs fixing [20:03] scrapbunny: Indeed, I dislike time zones [20:03] hi scrapbunny ... yep we need to get our meetings back up on the fridge ... it got dinged a while back [20:04] well, for the other teams in the topic it seems to work [20:04] ogra: i asked for today's meeting to go up in the fridge channel ... and requested to the end of jan via the mail list [20:04] ah, good [20:04] we'll skip "boxing day" to have a decent break from komputas [20:04] yeah, I'll try to get to those [20:05] I'm not sure why we don't have a decent event scheduler yet, but it is what it is [20:05] the time zone thing got me but i learned how to find out the universial time in terminal :) [20:06] scrapbunny: yeah, it's a life saver for sure [20:06] one sec ... let me get the list for the next while and paste [20:07] --> Edubuntu Meeting : Dec 19 : 12h00-14h00 UTC [20:07] Edubuntu Meeting : Jan 02 : 20h00-22h00 UTC [20:07] Edubuntu Meeting : Jan 09 : 12h00-14h00 UTC [20:07] Edubuntu Meeting : Jan 16 : 20h00-22h00 UTC [20:07] Edubuntu Meeting : Jan 17 : 12h00-14h00 UTC [20:07] Edubuntu Meeting : Jan 23 : 20h00-22h00 UTC [20:07] Edubuntu Meeting : Jan 30 : 12h00-14h00 UTC [20:07] <-- that will all go up on the fridge [20:07] okay ... let's kick off with TECHNICAL [20:07] take it away ogra ... [20:08] well, i actually have done nothing edubuntu related apart from working on the classmate image autobuilder stuff with the livefs tools [20:09] beyond that debian import freeze is tomorrow and i had to do merge stuff [20:09] (still two packages left for the night) [20:09] due to traveling i didnt to and dev work during the beginning of the week [20:09] *do [20:10] ahead we have the alpha2 release on dec 20th [20:10] i'll try to get the major CD changes done for that [20:10] so we are going to drop the 1st CD for Hardy? [20:10] yes [20:10] hey corey :) [20:10] ogra- you might not think it technical but without your tech help this month I would have nothing working so I really thank you :) [20:11] and ltsp needs to go on the ubuntu alternate CD properly [20:11] for the benefit of the new people, ogra please explain: [20:11] #1 what is happening with LTSP [20:11] #2 and your new reporting structure ... being part of a bigger team === dev_n00b is now known as dev_n00b|WoW [20:12] scrapbunny, well, even though i was slightly bitter when answering the mail on the list today, there is a grin of truth in the thread about degrading quality and we need to adress that [20:12] ( please :) [20:12] *grain [20:13] * RichEd pleads in our defence that we have recognised almost all of the problem areas, and are already adressing some [20:13] well, LTSP is team maintained by a board of developers from fedora, debian, upstream and ubuntu now, we changed the whole code structure and sparated the distro specific packaging ... [20:14] inside ubuntu it will move on the ubuntu alternate CD as an option [20:14] hey RichEd [20:14] the first edubuntu CD will go away and edubuntu will completely turn into an addon [20:16] ... [20:16] i moved back into the distro team from being a developer "team" on my own [20:17] distro specific tasks i had to do in edubuntu will rather be delegated to the specalists for the specific feature ... i.e. server related work will be done with the server team [20:17] who will work on LTSP? [20:18] so i can share out more workload whle helping the team as a whole [20:18] LaserJock, upstream or in ubuntu ? [20:18] ubuntu [20:18] me fr now [20:18] *for [20:18] so with hardy for a school lab we would install ubuntu from the alternate cd for ltsp and then edubuntu-desktop? [20:19] scrapbunny, right [20:19] that way edubuntu-desktop can be only lots of edu apps and branding while it depends on ubuntu-desktop ... i.e. we dont need to maintain ubuntu-desktop and only have to care for the edu related stuff [20:20] that raises quality since more time for the actual apps is available [20:20] the sam goes for the distro core ... installer, etc [20:20] *same [20:20] that will be good. will we go to having edubuntu-desktop updated once a year? [20:20] it drops off a lot workload and ubuntu benefits as well [20:21] edubuntu is tied o the ubuntu cycle [20:21] what we coud do is to call one a beta release [20:21] *could [20:21] I don't think we really gain anything by doing 1 year releases [20:21] but we will have to stick to the release schedules of ubuntu [20:22] me neither to be honest [20:22] scrapbunny: the alternating "production / evaluation" release for education was just a suggestion (as per the mail list today) [20:22] i think that sounds good and goes with what people were saying on the mailing list [20:22] we can try to do a "we're gonna focus on crack on .10 releases and bug fixing/stability on .04" but we should still release every 6 months IMO [20:22] we can debate it through ... but the school terms north/south is still an issue [20:23] beyond that as i said we're bound to the schedule [20:23] * ogra points to https://wiki.ubuntu.com/HardyReleaseSchedule [20:23] there is only a slim time of development [20:23] then the different stabilizing freezes kick in [20:24] for doing a 1 year release that doesnt do well [20:24] scrapbunny: the idea of a stable tested release alternating with a whizz bang preview release seems to have some support [20:24] since everything breaks in the middle of your relese schedule if ubuntu resyncs with debian [20:24] so you can start over [20:24] we'll still release every 6 months, but could pay more attention to testing and stability for an agreed annual release [20:24] really given what ogra is saying that edubuntu will now be an add on I think people will be able to pick if they want to update to 8.4 or 8.10 or both [20:25] i'm pretty sure that makes it less stable that imply getting enough (read more than 3) testers [20:25] *simply [20:25] :) [20:25] let's keep that discussion going in the mail list ... 8.04 is LTS ... so the point is moot for another cycle at least [20:26] well, the point of more manpower is never moot [20:26] ogra: agreed ... but it may be easier to rope the community into an annual wall-to-wall testing effort [20:26] like a "test fest week" :) [20:26] sorry for a silly question but when can we start testing 8.04? [20:26] today :) [20:27] there are daily isos being built ... we made the first alpha CD [20:27] stgraber: you've got a neat testing admin process ... is there a newbies follow the yellow footsteps guide to getting involved ? [20:27] well, IIRC current images have gnome-orca and OpenOffice broken, but you can still get the Alpha1 and upgrade [20:27] https://wiki.ubuntu.com/HardyReleaseSchedule has the release dates for alpha CDs [20:28] i would be happy to test it out as we go on a winter break next week [20:28] wrt to ltsp that will move over to the ubuntu alternate iso so testing will have to happen with that one [20:28] stgraber: ^ my comment ?? [20:28] RichEd: joining #ubuntu-testing the week we release the Alpha is a start, the Testing/ wikipages are currently being rewritten to be more attractive and understandable to newcomers [20:30] stgraber: well as I said in the mail response today, testing is *vital* to oliver ... let's make sure that *anyone* who wants to help can get invoved as easily as possible ... [20:30] *involved [20:31] highvoltage: you around ? [20:31] 7.10 is not working well with my client load so i am trying to decide if I should a)use 7.04 b)try debian-edu c)test 8.04 or d) give up since i am still pretty new to everything and in over my head :) [20:31] /part ubuntu [20:31] a nice prominent "you can be a tester" link on edubuntu.org would be good [20:31] scrapbunny: https://wiki.ubuntu.com/Testing/ISO [20:32] scrapbunny: you don't want to try testing 8.04 in production, although it is very valuable in general [20:34] for the classmate interested people, i played a bit with XUL while sitting on trains the last days http://people.ubuntu.com/~ogra/LightBrowser/ :) [20:34] laserjock- since i'm using my lab as thin clients testing is no big, if it totally false I just switch some cables and the computers boot to their windows xp harddrives :) [20:35] ah, that's very cool [20:35] yeah [20:35] ogra: what is that exactly? [20:35] gotta love having a donated server to play with :) [20:35] LaserJock, a little browser based on xulruner [20:36] ogra: that would *so* rock for documentation [20:36] LaserJock, has all firefox features out of the box but uses way less ram, only one win and no tabs [20:36] (can have all ff features i didnt enable many :) ) [20:37] ogra- will it handle flash or quicktime sites? [20:37] but its a lot of fun to write apps in :) [20:37] scrapbunny, if the plugins are installed, yes [20:37] it uses all FF plugins ou of the box [20:37] *out [20:37] very cool [20:38] the engine is the same .... only behavior and ui are small :) [20:38] but that cuts down a lot [20:38] ogra: will we actually have that for Hardy? [20:39] LaserJock, its no official project, its a spare time thing i started [20:39] but if i manage to get all functions working properly it will go into universe in any case [20:39] as you may remember one of my issues is that i need to be able to run flash internet sites in my lab and my server runs out of cpu too fast with firefox [20:39] yeah, I'm just thinking it would be a very nice documentation tool for Hardy [20:41] LaserJock, the fon size thing only exists in the ui yet ... you cant remove bookmarks either and the code is crap and needs to be sanitzed .... f i get that done i'll release it [20:42] (and put it into universe) [20:42] its really hackish atm ... i wrote it in 5h train ride and a boring evening in the hotel === Adri2000_ is now known as Adri2000 [20:43] scrapbunny, there is not much we can do about flash's cpu consumption i fear apart from making gnash better [20:43] That's what I was going to ask..how's gnash dev going? [20:43] on testing did i understand correctly that we need to wait for ltsp to be added to the alternate cd? [20:44] scrapbunny, no, the latest splitted ltsp packages need testing already [20:44] they are already in hardy [20:44] ltspfs is still waiting for some upstream changes but ill come soon [20:44] *will [20:45] this is the site i want to grab things from right? https://iso.qa.stgraber.org/ [20:45] ldm is still waiing for me to split out a themes packgae ... [20:45] right usually 3 days before a milestone is released is best to start some testing [20:46] or two days if you dont want to experience the worst bugs :) [20:47] if we build a milestone we usually start shuffling the CDs and clening out bugs for that on monday ... to release it on thursday [20:47] testing during that time is the most valuable one [20:47] for first Alphas, we usually have the first candidates on Tuesday (Monday when we are lucky), Tuesday evening is just standard testing, Wednesday is where the fixed images are usually built, then testing on Wednesday evening for all the remaining testcases [20:47] since we're all focused and in bugfixing mode :) [20:48] then published Thursday afternoon [20:51] ... nothing more from my side about tech so far ... [20:51] oh, one thing ... [20:51] i heard from someone who installed in the triple e pc [20:52] it seems to work very well with a normal install [20:52] (it was a question from some weeks ago) [20:52] cool [20:52] cool [20:53] suspend/resume seems to have the same probs as the classmate though [20:53] but since t has a bigger flashdisk a normal instal wors just fine [20:53] ok, will order one as soon then [20:53] (i really need to work on my typing) [20:54] so thats it for tech [20:54] any other questions ? [20:54] okay ... LaserJock wanted to jump in on tech if noone else has questions for oliver [20:55] from my side (iTalc), the one that was recently uploaded has non-working logout/shutdown/reboot [20:55] I have a new one with that fixed and I'm debugging the demo mode as we speak [20:55] side qustion-is the suspend/resume fixed in the hardy being tested now? [20:55] stgraber, ping me for uploading [20:55] the LTSP scripts are also working but need some tweaking before being integrated [20:55] ogra: Just have to solve a bad segfault when entering demo mode ... [20:55] scrapbunny, suspend/resume in which context ? [20:56] stgraber, well, still plenty of development time :) [20:57] and i really count on a better community participation in the future ... [20:57] for standalone laptops. i can't suspend on my dell d600 with 7.10 [20:57] ogra: yes, I'm working on iTalc when I'm getting bored of working on the QA website, but I'm pretty proud of how it currently works, it's far better than what I had at UDS :) [20:57] i wasnt happy about the mail thread today, but it shows something starts to move there [20:57] which is a good thing [20:57] stgraber, you rule ! [20:58] * ogra cheers for stgraber [20:58] * RichEd adds to the cheer [20:58] \o/ [20:58] ok, so I had 6 things real quick I came up with [20:58] stgraber: you done ? LaserJock wants to raise a couple of points [20:58] RichEd: yep [20:58] couple != 6 [20:58] they're quick [20:58] ;-) [20:59] scrapbunny, did you file bugs ? such things are really very specific to one hardware usually ... [20:59] i think it is hard for people to understand that this is not windows or mac releases after 7 years of testing but a small group of unpaid people [20:59] especially if it comes to laptops [20:59] 1) Sugar. jani has been working on getting the Sugar interface working on regular machines. Is that something we'd be interested in? [20:59] fwiw, i can help testing on the EEE pc [21:00] ogra: as per *that* mail thread ... is just filing a bug visible and helpful enough ? would it be good to have a "user added release notes" wiki page ? [21:00] * ogra isnt a bit fan of sugars usability but for the sake of having it in the distro in any case [21:00] *big [21:00] RichEd, for suspend/hibernate on the dell d600 ? [21:01] 2) I also talked to jani about squeak [21:01] riched- i think it would be a big help for edubuntu bugs [21:01] scrapbunny, thats not edubuntu relted at all [21:01] *related [21:01] ogra ... even a one liner for "known issues" is useful ... to read all at a glance ... it just needs to be a topic & link to actual bug report [21:01] he'd like to see squeak and etoys updated an in *buntu [21:01] RichEd, it has nothing to d with edubuntu [21:01] i have a hard time finding the right catagory to put my bug reports in [21:02] RichEd, the CD split will make that clearer though [21:02] ogra: well then we can add a note to say ... ubuntu related ... and deflect bad perceptions ... [21:02] and also, users could add a bug and say "I need help filing this properly" [21:02] RichEd, i dont work on/ change anything of the ubuntu base in edubuntu [21:03] so suspend hibernate bugs surely dont belong in our release notes [21:03] ogra: I don't think people would see that split [21:03] I agree that Release Notes is a bit odd [21:03] but the report comes in from our users and they think it's our issue ... so we can refer to the correct responsible party [21:03] LaserJock, if they have to install ubuntu to get edubuntu ? [21:04] but certainly some sort of Errata would be useful [21:04] they will *feel* that split [21:04] not only see it [21:04] they have to use a second CD [21:04] sorry i think my side question on suspend/hibernate is getting confused with the need for an easy place for all edubuntu related bugs to be found and discussed [21:04] ogra: yes, in that case it's much better [21:05] scrapbunny, well, usually bugs need to get assigned to packages at some point ... but if you dont know what to file a bug against thats no problem [21:05] first of all filing it is important [21:06] we have a team of bug triagers that goes over them and will try to get the right info out of you to assign it to the right package and people [21:06] scrapbunny: i also feel the need for a single reference page ... it will also give people confidence if they can read through to look for known issues against their current hardware or intended hardware purchse [21:07] launchpad will subscribe the edubuntu-bugs team to all bugs that are filed on edubuntu related packages [21:07] (we might to check that the list is up to date here, i think that hasnt happened for a while) [21:08] I check once in a while [21:08] * lns_ agrees with bug/doc/etc consolidation and easier tracking of current issues/information [21:11] so how many supporters for a "known issues" overview wiki page, listing: [21:11] a one liner description for each issue [21:11] a status of whether it has been filed properly in launchpad (with link) [21:11] a status if the reporting person needs help with proper logging/filing [21:12] sounds good [21:12] * lns_ raises hand [21:12] we might have to work a bit on implementation [21:12] RichEd, how would you judge what goes on that page from the X1000 bugs we get every day in ubuntu ? [21:12] basically it should be mapping what we *should* already be doing [21:12] * note that this will need user input ... it will largely be a self filing system ... [21:12] and who would maintain that [21:13] ogra: users add their issue ... we scan it weekly before meetings, and redirect problems that are not our own [21:13] Personally, I really like LP, I just think it could use an overhaul for user-friendliness [21:13] somebody who doesnt have a life :P [21:13] it will be good for communications with our community [21:14] and also it would be nice if we could find someone to monitor the mailing lists for issues ... [21:14] RichEd, i disagree here LP should be the too to handle bugs ... we should see that we get it straight there [21:14] RichEd: I don't think it should be filled by users [21:14] spamming isues [21:15] what we *do* need is a list of high impact bugs that we have workarounds or upcoming fixes [21:15] it's about us giving info to users not users giving us info [21:15]