=== nixternal [n=nixterna@ubuntu/member/nixternal] has joined #kubuntu-devel === NeoChaosX [n=nael@ppp-71-139-163-10.dsl.snfc21.pacbell.net] has joined #kubuntu-devel === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #kubuntu-devel [01:35] morning all [01:36] morning [01:37] hey everyone, we are getting ready to start editing this weeks UWN, for Kubuntu stuff you would like added, let me know please! [01:37] thanks everyone! [01:38] i am going to do some screenies of some new stuff as well to show off for us [01:40] nixternal: the start of the g-p-m stuff (kde-guidance) [01:40] Hobbsee: link me to further info if possible...that would be awesome [01:41] nixternal: er, that might be the spec? also, Riddell made a blog post about it [01:41] it's on plant [01:41] *planet [01:41] good deal [01:41] just keep plopping ideas, i will transfer em up ;) [01:42] it's a bit early to announce amarok stuff [01:42] seeing as it hasnt been released yet [01:43] true [01:43] Hobbsee: stuff from last saturday until today would be best [01:44] nixternal: we had a meeting, and discussed the alioth stuff. [01:44] we can leave teasers to make them read the next UWN though with pre-release tricks [01:46] true [01:51] nixternal: maybe as a tip of the week a listing of the best lines for sources.list [01:51] to get all the up-to-date goodies for dapper [01:51] no problem [01:51] main, universe, multiverse, security..and what not [01:51] good idea tomoa [01:51] arg [01:51] toma too ;) [01:52] ;-) [01:52] nixternal: were you doing the meeting minutes? [01:52] ow yes, i wanted to ask that too [01:53] if i was, i wasn't asked...but, i have been super busy as well...i can probably get to them in the next couple of days if that is ok [01:53] anyhow..food time..bbiaf ;) [01:53] right === neoncode [n=neoncode@unaffiliated/neoncode] has joined #kubuntu-devel [01:53] nixternal: i regulary reed them back, so i appreciate your work [01:54] thanks toma, glad i can help! plus it saves me from pointy stick attacks [01:54] haha [01:55] nixternal: yes, you have to be carefull with The Manager around [01:55] me too. particularly for last meeting [01:55] haha === Hobbsee suspects that one of the first thing's she'll start changing is to organise the meetings a bit better, so they dont take so long. [01:55] haha [01:56] i have a vague idea your points take the longest ;-) [01:56] curious how you are going to organize them [01:56] toma: hehe, true. actually, i've been cutting them off a bit so that once iv'e got the answer, it goes ot the next point [01:57] toma: yeah, me too, really :P [01:57] yeah, last meeting was an exception [01:57] toma: certainly sending out notification emails a bit quicker, getting the stuff on the wiki to quote the particular bits of the articles, etc, so people have had the time to have a look and a think about things [01:57] although i've a new point for the agenda already [01:57] i frequently find i'm reading whatever they're talking about during the meeting already, cos i havent seen it [01:57] toma: add it :) === Hobbsee may take over the chairing, i'm not sure. [01:58] it's easier to poke people into moving on if i'm chairing [01:58] i just find that i zone out during longer points, thta seem to just go around in circles. [01:58] yeah, the wiki page should have thje 'intro', so we can skip straight to the thing [01:59] toma: exactly. we wouldnt run it like the distro meetings, but something close to that might work [01:59] i havent spoken to Riddell over all of this though, which i'd need to do at some point [01:59] riddell usally does a good job in keeping it short, comparing to what i see in live companies [01:59] oh definetly [02:00] Riddell: does a *great* job. i just want to make it better again :) [02:00] the point i want to discuss is likeback http://basket.kde.org/likeback.php === Hobbsee is better at organising stuff rather than coding stuff. although i like both. [02:01] Hobbsee: you are pretty confident of yourself, non? [02:01] toma: um, is that a problem? === huahua [n=hua@123.49.236.6] has joined #kubuntu-devel [02:01] likeback or your confidence? [02:01] my confidence [02:02] no it is not. [02:03] toma: right. i've done similar stuff before, but not exactly this. not worked in such a big team before, for one thing. [02:03] toma: so when i'm in a mood where i'm coping at all, i can take over the world and be confident, no problem :P [02:03] good ;-) confident and a planning, awesome [02:03] at other times...well...i'm not going into them :P [02:04] ah, pleasssseee... [02:04] hmm? [02:04] toma: read partway thru that likeback stuff - that looks really cool! [02:05] yes, maybe we should add it to a knot thingie to get some feedback [02:05] if we need any, i dont know [02:06] Hobbsee: ow, and i talked to the amarok people [02:06] does it apply just to basket, or to all of them? [02:07] ah yeah. they didnt like me :( [02:07] what'd they say? [02:07] the release could be delayed a bit due to some bugs [02:07] he did not know for sure [02:07] yeah, i was there to hear that [02:07] and he told me that for major release they do give time to packagers [02:07] but not for point releases [02:08] i asked them to consider that [02:08] oh yeah, that's right, i was going to subscribe to that mailing list [02:08] yeah, okay [02:08] and they received similar request from gentoo [02:08] there is a packagers mailinglist for amarok [02:08] there you can receive the tarball in advance [02:08] havent seen where it is yet [02:09] let me check my irc logs, one sec [02:09] Amarok Amarok Mailing List [02:09] Amarok-bugs-dist [no description available] [02:09] Amarok-promo [no description available] [02:09] could be any of them === Hobbsee goes afk === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #kubuntu-devel [02:09] any interesting news this week that UWN should report? [02:10] not that i'm aware of, you would be good to poke Riddell when he is srround tomarrow and check the meeting minutes [02:10] s/tomarrow/monday [02:10] right, it is going out tonight, in less than 4 hours [02:11] guess not then ;) === toma [n=toma@toma.kovoks.nl] has left #kubuntu-devel ["Ooh,] === imbrandon_ pokes nixternal [02:32] Riddell: can we kill off kwifimanager once and for all, now that we have knm/wlassistant? [02:32] and when do we install and run knm by default? [02:32] Hobbsee: knm is knetwork-manager? [02:32] Burgundavia: yep :) [02:32] yea [02:33] Burgundavia: it's just far too long to type. like l-k-h, etc [02:33] the problem is that nm/knm conflicts with ifupdown [02:33] k-d-s and tons of others ;P [02:33] that too [02:34] Burgundavia: true, you have to do it one way or the other. hopefully you get to avoid ifupdown though [02:34] although it's bad if you've got a console only login though. [02:34] Hobbsee: yea but what about server ;) [02:34] heh [02:34] yep [02:34] imbrandon: then you dotn have it installed anyway, so you just use dhclient and all that by default [02:34] plus knm does not deal with static addreesses very well [02:35] s/very well/at all [02:35] in fact, you have to remove nm just to get a static address to take [02:35] true that. i think that's a networkmanager problem? [02:35] absolutely [02:35] but its great for lappys , one more reason for k-{desktop,laptop} hehehe === Hobbsee thought she saw that they were fixing such things. [02:36] Burgundavia: question was more "is it nm's problem, as opposed to knm's?" [02:36] afaik, there are no plans for supporting static ips [02:36] they both use the same backend [02:36] ah ok [02:36] nm=network manager != network-manager-gnome [02:36] oops, missed an = in there. [02:36] lol === Hobbsee should really go and do her comp assignment. === rob [i=Robert@freenode/staff/ubuntu.member.rob] has joined #kubuntu-devel [02:44] wb rob [02:44] Burgundavia: what are you doing in my playground? [02:44] ;) [02:45] nixternal: dappling in the dark side [02:46] Hobbsee: fyi: http://en.opensuse.org/Projects/KNetworkManager [02:46] Burgundavia: ooh, yay. another kubuntu developer then [02:46] that is #ubuntu-devel, you are in geek heaver, #kubuntu-devel ;) [02:46] Hobbsee: I didn't say I had ever installed kubuntu [02:46] my lord [02:46] heaver? [02:46] heaven [02:46] Burgundavia: oh dear... [02:47] Burgundavia: dont make me or Hobbsee /op ;) [02:47] hehe [02:47] hehe [02:47] I pull rank [02:47] oooh [02:47] Burgundavia: what about it in particular? [02:47] I have been around Ubuntu for longer than either of you [02:47] Hobbsee: that is your information on what knm is [02:47] hehe and ? [02:47] lol [02:47] Burgundavia: true. i knew that :P === Hobbsee uses knm all the time === imbrandon_ was just teasin anyhow , i'll get you to the k* side one day [02:48] Hobbsee: right [02:48] imbrandon: i have been working on it, he does some jedi mind trick stuff and gets you to install ubuntu [02:48] don't mess with him [02:48] since you seemed confused about the relationshipo between nm and knm [02:48] although i do enjoy ubuntu on my lappy ( just get rid of the damn orange ) [02:48] luckily he wasn't online today, so i got ubuntu uninstalled and kubuntu edgy back on ;) [02:49] imbrandon i like the orange [02:49] Burgundavia: right.. [02:49] i don't know why === Hobbsee wasnt. seh likely just said it wrong :P [02:49] and the glx compiz stuff is cool as wel [02:49] Hobbsee: there we go [02:49] whats wrong with compiz xgl on kde nixternal ? runs fine here [02:50] funny. I have been involved with Ubuntu since october 2004 and yet I have never even tried Edubuntu, Kubuntu or Xubuntu, even in the live cd versions [02:50] hahah Burgundavia grab a live 6.06.1 kubuntu dapper [02:50] you'll never go back ;) [02:50] funny, I really don't feel the need [02:50] i followed the forums and didn't have fun, put it that way [02:51] Burgundavia: most windows users say the same thing ;) [02:51] nixternal: the forums dont do it the easy "edgy" way ;) [02:55] arg Hobbsee your not building on voyager atm are you ? [02:55] imbrandon: nope === Hobbsee isnt doing any building/packaging at the moment [02:56] kk dont for the next ~1 hour or so please [02:56] cool === Hobbsee wont be doing anything on it for at least 4. === Hobbsee wonders what imbrandon is up to [03:01] i *cough* deleted the base.tgz === imbrandon_ looks at the ceiling [03:01] imbrandon: was this on purpose, or by accident? [03:01] accident [03:01] lol [03:01] its rebuilding now [03:01] heh [03:01] is it rebuilding with the right distro? [03:01] yes [03:01] cool === Hobbsee has had trouble with that before :( === imbrandon_ isnt a /total/ dodo hehehe [03:02] silly imbrandon :P [03:02] nah thats easy , i got pbuilders down pat now [03:02] imbrandon: that's still smarter than deleting .gnupg/ .irssi/ and ./thunderbird [03:02] i spent 2 days learing all the quarks about them [03:02] ouch [03:02] heh [03:02] s#./thunderbird#.thunderbird/# [03:03] keep a nightly backup ;) rsync is your friend [03:03] yeah, or be a little more careful with rm -rf [03:03] and s#./th#.th#g would work ;) heheheh /me is just being an arse now [03:04] good point. === Hobbsee isnt great with all that [03:04] or s/.\/th/.th/g === imbrandon_ actualy hates reg expression, they are great but 99% of the mistakes i make coding are becouse of a reg expression === zakame_ [n=zakame@69.60.114.100] has joined #kubuntu-devel === yuriy [n=yuriy@207-172-219-193.c3-0.frm-ubr3.sbo-frm.ma.cable.rcn.com] has joined #kubuntu-devel === LeeJunFan [n=junfan@166.166.4.210] has joined #kubuntu-devel === lnxkde [n=lnxkde@206.248.109.24] has joined #kubuntu-devel === Burgundavia [n=corey@ubuntu/member/burgundavia] has left #kubuntu-devel ["Ex-Chat"] === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #kubuntu-devel === neoncode [n=neoncode@unaffiliated/neoncode] has joined #kubuntu-devel === lnxkde [n=lnxkde@206.248.109.24] has joined #kubuntu-devel === imbrando1 [n=brandon@CPE-72-135-8-5.kc.res.rr.com] has joined #kubuntu-devel === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #kubuntu-devel === abattoir_ [n=abattoir@59.92.57.49] has joined #kubuntu-devel === pounk [n=pounkf@142-217-81-164.telebecinternet.net] has joined #kubuntu-devel === imbrandon [n=brandon@ubuntu/member/pdpc.active.imbrandon] has joined #kubuntu-devel [09:00] *pokes* [09:00] anyone around here who's used gstreamer engine a bit? [09:01] !edgy [09:01] edgy is the current development version of Ubuntu. Version 6.10, codename "Edgy Eft". For support head to #ubuntu+1. For its release schedule, see !schedule [09:02] !schedule [09:02] Ubuntu uses a strict timetable for releases, which means that sometimes newly released programs miss the timetable. See https://wiki.ubuntu.com/TimeBasedReleases for more. Edgy schedule: https://wiki.ubuntu.com/EdgyReleaseSchedule === mornfall_ is now known as mornfall [09:02] gstreamer is teh sucks , thats why 90% of things have it removed hehe [09:02] moins mornfall [09:02] err afternoon for ya ;) === crimsun beats imbrandon with a GSt pipeline. [09:03] Hobbsee: what's the issue? [09:03] hehe [09:03] crimsun: we may get some gstreamer deps in a package related to amarok [09:04] as in reinstating the former amarok-gstreamer package or some ilk? [09:04] ummm Hobbsee wont that tick the amarok devs off a bit as they droped support for it ( thats why they are all pissy at fedora atm ) [09:04] crimsun: that too. [09:04] imbrandon: they're the ones who are asking my opinion on it in the first place [09:05] if they can make it actualy work cool , heh , /me shudders at the last incarnation [09:05] please tell me amarok-xine wont be droped though [09:06] it wont [09:06] also i would look at the common customizations spec too and talk with those guys as that was one of the things that the 3rd party apps installed ( amarok-xine ) when amarok-gstreamer was in uses [09:07] http://shadowfax.homelinux.net/~guru/moodbar/ [09:07] imbrandon: it's w.r.t that ^ [09:07] which requires a lot of gstreamer deps for the second package [09:07] ye the moodbar was droped becouse of it afaik [09:07] last i talked to them atleaste [09:07] ( arround 1.4.1beta1 ) [09:08] it got rewritten [09:08] stupid firewall/gateway [09:08] (rev 572258) puts the moodbar support into amarok. It it adds absolutely no new dependencies, but will not be very functional without the above package installed. [09:08] I hope that Web site is links-friendly! [09:08] crimsun: it is [09:08] all text [09:08] hey, if we have a package in main, can we have a recommends in universe? [09:09] or do all the recommends need to be in main too then? [09:09] Hobbsee: recommends should always be satisfiable [09:09] well if we move to recomends like riddell said i doubt it [09:09] it should be a Suggests otherwise [09:09] oh hi mdz, didtn know you were watching [09:09] right, yeah [09:10] Hobbsee: the lower patch adds the same functionality with no gstreamer deps [09:10] I wasn't, but I've stopped by to check in [09:10] ah, fair enough === Hobbsee hides from the big and scary mdz [09:10] :P [09:10] hehe [09:10] I am neither big nor scary and I will soundly refute any arguments to the contrary [09:14] mdz: right... === Hobbsee hasnt forgotten that bug report. [09:14] bug report? [09:15] mdz: one that i confirmed, as i'd gotten other people to confirm it on irc, and you full on yelled at me over confirming my own bugs. [09:15] Hobbsee: bug#? [09:15] i dont have it now, it was a while ago :P [09:16] I'm not in the habit of yelling at anyone, though I could very well have asked you not to do that [09:16] it helps to accompany changes with an explanatory comment in those situations [09:16] true. i think i forgot that === Hobbsee is getting lazy with bugs. i see too many of them === Hobbsee shrugs [09:33] crimsun: possible amarok-gstreamer would be a long way off, if it happened at all. and gstreamer would have to be way more stable. === huahua_ [n=hua@123.49.238.100] has joined #kubuntu-devel === zakame_ is now known as zakame === huahua_ is now known as huahua [10:53] Hobbsee: could you look at Bug #56168 and Bug #23326 are wishlist [10:53] Malone bug 56168 in k3b "k3b should *not* calculate md5 sum of images by default" [Untriaged,Confirmed] http://launchpad.net/bugs/56168 [10:53] Malone bug 23326 in k3b "k3b should unmount a CD before burning" [Medium,Unconfirmed] http://launchpad.net/bugs/23326 [10:53] s/are/i think are/ [10:53] 56168 is a valid wishlist imo [10:54] as is 23326 [10:55] they are certainly not things we can do anything about [10:56] and both are filed upstream too iirc [10:56] yeah. i'd mark them as upstream [10:57] ah is there an importance of "upstream"? [11:00] well, you add the upstream bugtracker === Hobbsee is known to mark it as rejected here, as it's not our bug, but i've been told that's a bad thing (tm) [11:01] wishlist it and find the bug upstream and link it with the +upstream [11:01] Hobbsee: if you could wishlist them i'll sort the upstream [11:01] seaLne: for both? sure [11:01] imbrandon: can do that too. [11:03] are you supposed to just create products so that you can do upstream? [11:04] dosent kde have a product already ? [11:04] is it kde rather than k3b? [11:05] i have no idea what products are supposed to be [11:05] if it doesnt have k3b, pick the closest [11:05] well if it uses the kde bug tracker i would use the kde product [11:05] that's what i've been using [11:05] and say it's the kde bug tracker, of course. just file it under the closest package name [11:05] kdemultimedia? [11:06] wha ? [11:06] Hobbsee: s/package/product [11:07] seaLne: use the kde product and file it against the kde bugtracker for the bug number you find [11:07] yeah, that. [11:07] there isn't a kde product [11:07] seaLne: that'll do :P [11:07] seaLne: i've yet to see the product actually do much - as long as you get the right number for the kde bugtracker, it seems to all work fine [11:08] it means tho that the bug is now listed under kdemultimedia rather than k3b [11:08] seaLne: the upstream bug bit is, iirc [11:09] just the upstream bit [11:09] hmm ah its confusing [11:10] true [11:10] seaLne: welcome to LP :P [11:10] https://launchpad.net/distros/ubuntu/+source/k3b/+bug/56168 and https://launchpad.net/products/kdemultimedia/+bug/56168 [11:10] Malone bug 56168 in kdemultimedia "k3b should *not* calculate md5 sum of images by default" [Unknown,Unknown] [11:12] seaLne: looks good. === huahua [n=hua@123.49.238.100] has joined #kubuntu-devel [11:21] and i thought ubuntu bugs were badly written, half of k3b bugs have a subject of k3b can't burn or similar === toma [n=toma@toma.kovoks.nl] has joined #kubuntu-devel [11:32] moguh [11:48] seaLne: heh. yep === insanekane [n=kane@202.83.32.168] has joined #kubuntu-devel === danimo [n=danimo@kde/danimo] has joined #kubuntu-devel === Lure [n=lure@ubuntu/member/lure] has joined #kubuntu-devel === el [n=konversa@p54BD0E6A.dip0.t-ipconnect.de] has joined #kubuntu-devel === Lure [n=lure@ubuntu/member/lure] has joined #kubuntu-devel [12:44] Hobbsee: crimsun did upload powersave, can you look at kpowersave: http://revu.tauware.de/details.py?upid=2874 [12:45] Lure: sure. does it work? [12:45] Hobbsee: of course, otherwise I would not upload it to revu... ;-) [12:45] Hobbsee: works for me (disclaimer) [12:45] ;-) [12:46] hehe [01:40] !ssh [01:40] ssh is the Secure SHell protocol (see https://wiki.ubuntu.com/SSHHowto). Putty is a nice SSH client for Windows, which can be found at http://www.chiark.greenend.org.uk/~sgtatham/putty/ [01:50] Lure: thanks for adding that bug comment i'd forgotten it wasn't in the bug report oops :) [01:50] seaLne: no pp [01:51] s/pp/pb/ === el [n=konversa@p54BD0E6A.dip0.t-ipconnect.de] has joined #kubuntu-devel === freeflying [n=freeflyi@221.221.160.148] has joined #kubuntu-devel === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel === freeflying [n=freeflyi@221.221.160.148] has joined #kubuntu-devel === freeflying [n=freeflyi@221.221.160.148] has joined #kubuntu-devel === goldenear [n=goldenea@vol75-4-82-225-33-186.fbx.proxad.net] has joined #kubuntu-devel [02:21] imbrandon: ping === pounk [n=pounkf@142-217-81-161.telebecinternet.net] has joined #kubuntu-devel === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel [02:28] http://basket.kde.org/likeback.php is pretty cool if people haven't seen it === chavo [n=chavo@67-22-110-236.atlsfl.adelphia.net] has joined #kubuntu-devel [02:29] seaLne: yeah. did that get added to the meeting agenda? and does upstream have to include that, or do we? [02:29] presumably that's more of an upstream thing. [02:30] yeah but not nessesarily [02:30] Hobbsee: probably pretty easy to patch kdelibs to show up in all apps [02:30] seeing as i'm suspecting that people will mostly report upstream bugs with it. [02:30] toma: indeed. but hwat do we do with the bug reports? [02:31] we can disable the bug thingie [02:31] what were you meaning about the agenda? [02:31] seaLne: add it to the meeting agenda, so everyone sees/discusses it? [02:31] we only want the 'i like' button, dont we? [02:31] hehe [02:33] how do we encrypted the passwd of user in livecd? DSA? SHA? thanks [02:33] I'd be careful about likeback [02:33] upstream is working on a way to make the feedback maintainable [02:33] "you clicked don't like, we presume this was a mistake and have changed your vote to like" :) [02:34] toma: hehe! [02:34] danimo: any more details? [02:35] seaLne: no, only that there is a debate going on at kde-core-devel [02:35] seaLne: read it via gmaine.org nntp if you care [02:36] danimo: the idea is good I think, the feedback can be enormous indeed [02:38] toma: yes, we need some sort of rubbish filter [02:38] toma: and means to translate good ideas into implementable strategies === fritsch [i=O8Mcujbd@nat-wh-1.rz.uni-karlsruhe.de] has joined #kubuntu-devel [02:38] would you just enable it before release? [02:38] seaLne: one suggestion was to always enable it on betas and optionally enable it on final releases [02:39] yeah it could look bad for releases [02:39] i'm not so sure to enable it on final releases, but we'll learn about that soon enough [02:39] toma: I agree with ellen there [02:40] toma: only enabling it on beta's empowers the geek-type of testers to push their ideas [02:40] danimo: i'm a bit behind on k-c-d, have not read everything [02:40] but ellen is usually right ;-) [02:40] toma: and those already know how to use bugs.k.o anyway [02:40] toma: yes, she still is in touch with reality :) [02:41] o, that is true, but prepare for a lot of feedback if you enalbe it in final releases === Hobbsee wonders if el in here is ellen. [02:41] Hobbsee: she is [02:41] hi el :) [02:41] ahh :) [02:41] ah ;-) [02:41] hi Hobbsee, hi danimo :) === Hobbsee waves to el, now that she has a clue of who she actually *is* === el waves to Hobbsee [02:42] may I introduce: Hobbsee: ellen of openusability fame: Ellen: Sarah, the kubuntu Community Goddess [02:42] hah [02:42] i think it is a bit too easy maybe for people to report nonsense with likeback === Hobbsee certainly isnt a goddess.... [02:42] Hobbsee: I think they call Goddesses Community Managers nowadays [02:42] el: you'd be http://people.kde.nl/ellen.html <-- that ellen, then. [02:42] Hobbsee: I'm old school :) [02:43] hehe [02:43] yes Hobbsee [02:43] good to see another woman here :) [02:43] gotcha [02:43] yes [02:43] el: take over the world together? [02:43] ytou are talking about likeback? [02:43] el: yes [02:43] Hobbsee: you need a picture to show to el now [02:43] haha, definetly :) [02:43] el: we still need a sensible way to filter feedback [02:43] el: actually, we do have the same problem today already [02:44] http://img357.imageshack.us/img357/9838/hobbseecar10ii.jpg [02:44] http://img357.imageshack.us/img357/3909/hobbseecar22fk.jpg [02:44] there you go [02:44] el: ^ [02:44] el: bugs.k.o contains a lot of crap [02:45] Hobbsee, you live in australia, no? [02:45] k-d-c discussion: http://lists.kde.org/?t=115532209400011&r=1&w=2 [02:45] danimo, yes, that's a real problem [02:45] el: yeah, sydney === el waves again - to the other end of the world ;-) [02:45] hehe [02:45] s/other// [02:45] :) [02:46] /~ It's the end of the world as we know it ~/ === danimo sings [02:46] rem [02:46] danimo, do you thnk of introducing likeback for everybody, or just for beta testers? [02:46] el: I agree with your point [02:46] el: we are biased by our tech-focused beta-testers way too much [02:47] el: otoh, they can provide good bug reports [02:47] :) [02:47] yes, it is a good qay to find typo's, dialog trouble and that stuff [02:47] yeah, but i had to think about my talk with mpt (hobbsee knows him, i guess) who said that making bug reports too easy will overload every bug system [02:47] el: i dont know mpt === chavo [n=chavo@67-22-110-236.atlsfl.adelphia.net] has joined #kubuntu-devel [02:47] i dont know most people [02:47] el: so if we decide "against" those lowhanging fruits in favour of a less biased feedback we definately need an instance between reporters and developers [02:47] el: i've only ever met stevenk and ajmitch in person. [02:47] Hobbsee, he is user interface designer for launchpad [02:47] el: ahh... [02:48] danimo, yes, i think so too [02:48] el: but who would do that? [02:48] el: and why? [02:48] not having to report back to each and every report saves a lot of time [02:48] el: we need to know that so we can actually attract people for those positions [02:48] toma: right [02:49] e.g. opensuse.org has a great bug squad, but those are all paid [02:49] danimo, hmm... i mean the input is really very fruitful for usability people. but we are too few.... [02:49] el: no, you are the wrong group [02:49] el: I imagine people that are not too much into technology, but know about about kde to judge [02:49] for the bugs we are the wrong group, but not for feature requests, likes and dislikes [02:49] el: and people that are open to new technologies and ideas [02:49] el: well, those have to be forwarded appropriately [02:50] el: maybe, each group (hci, dev, docs) could send one representative to be member of the like-back squad [02:50] el: you're german. i'm very jealous. [02:50] Hobbsee: yeah, being in germany helps a lot for all purposes of KDE development [02:50] why are you jealous to being german? it's pretty cold and rainy here, Hobbsee ;-) [02:50] hah [02:50] Hobbsee: even better, she's in berlin [02:51] yeah, okay, i dont like cold and rainy [02:51] ;-) [02:51] Hobbsee: so she's got all cool folks around === Hobbsee studied german for a while. sounds like a nice place. [02:51] more an more kde people move to berlin now, that's cool === danimo gets there twice a year and usually checks into hotel ellen :) [02:51] so if i ever got to germany, i could gatecrash at one of your places. right. [02:51] hehe [02:51] we met matthias a few days ago, that was fun [02:52] el: ettrich? cool [02:52] danimo: do you have any idea what kind of filter would be needed? [02:52] Hobbsee, haha, my guest room is yours :) [02:52] danimo, yes, we got pretty drunk ;-) wodka.... [02:52] liek, what do we dont want to know [02:52] el: nice. i'll hold you to that, you know :P [02:52] el: hehe, yeah, matthias is a cool guys to drink with, if he actually decides to get drunk [02:52] el: although i think you're safe. i doubt i'll get to germany. and my german would be extremely rusty. [02:52] Hobbsee, sure! :) [02:52] Hobbsee: we could change that, no worries :) [02:53] hah [02:53] Hobbsee, no need to know German ;-) [02:53] ok, back to likeback.... [02:53] Hobbsee: you have no ideas how many americans run aroun in berlin without knowing one single word of german :) [02:53] el: yeah, you all seem to speak pretty good englihs [02:53] danimo: point. [02:53] el: yeah, bring us back to topic [02:53] :) [02:54] i think there should also be an easy tag system for users - so that the first classification is done on user level [02:54] danimo: we have a topic? [02:54] Hobbsee: likeback [02:54] oh dear, this feels like some of our kubuntu meetings again [02:54] haha [02:54] Hobbsee: nah === Hobbsee is still trying to figure out where el fits, w.r.t. kubuntu [02:54] Hobbsee: usability [02:54] Hobbsee: yesterday you wanted to take over those meetings, so you can practise now. [02:55] well, obviously. i was looking for more detail than that. === Hobbsee knew that ellen and usability went together before she realised that el = ellen = was at UDS. [02:55] ok, so we have a problem: too much input, very little gold nuggest inbetween common whining and actual bug reports [02:55] el: what kind of tags? [02:55] toma: true. [02:55] Hobbsee, i was at the last ubuntu sprint in paris and helped a bit out with the ui of several applications [02:56] ppl, does anybody know whazzup with the memory usage of etch? [02:56] a clean login (yes, with a lot of apps in the session) uses twice the ram from the previous release, dapper (i upgraded yesterday). for example, klipper ATM uses 9.5 % of my 1 gig ram!!! KLIPPER!!! wtf??? [02:56] superstoned: etch? this is kubuntu, mate [02:56] efty [02:56] i mix up the names :D [02:56] edgy? [02:56] yeah [02:56] el: gotcha. which apps? [02:56] superstoned: want to pastebin ps aux? [02:57] toma, that's something we have to find out. possibly parts of the applicatications in questions [02:57] ok [02:57] Hobbsee, system settings, power management, file transfer dialog... several specs that were discussed there [02:57] el: bugzilla has a karma system for users already [02:57] el: that info is already provided, the objects name gets returned, so we exactly know which dialog the user is talking about [02:57] el: nice :) [02:58] el: i didnt follow UDS that closely - i was in the middle of uni exams, etc. [02:58] el: my idea would be the following: [02:58] toma, for the bugs, yes. but not for like/dislike [02:58] hence i dont know [02:58] hOBBSEE: http://paste.uni.cc/9289 [02:58] el: how about a ticket system for likeback? [02:58] el: for ilike/dislike as well [02:58] el: let me show you the admin interface, one sec [02:58] toma, ok [02:59] el: nah, scrap that [02:59] danimo, ticket system? [02:59] el: scap that [02:59] el: lets see... [02:59] el: we currently have bugzilla for reporting all kind of issues [02:59] superstoned: doenst look too unreasonable. konsole looks a bit high, maybe [03:00] el: so the question is: do we want to use bugzilla for all kind of likeback feedback? [03:00] el: I think it doesn't make sense [03:00] http://toma.kovoks.nl/admin/view.php [03:00] el: since not all likeback issues will be actually bugs or suggestions [03:00] well, hobbsee, point is, yesterday, before i shut down, it was 50% of this... only diff is i did a upgrade to edgy. so i wonder if anybody has seen this too? [03:00] el: so my idea was to have a ticketing system [03:01] danimo, it might overfloat bugzilla. i think only approved issues should go into bugzilla [03:01] el: that allows to handle like likeback reports [03:01] superstoned: which kde were you using before and after upgrade? [03:01] 3.5.4 [03:01] with a way to migrate bugs to lp/bugs.k.o? [03:01] el: like a small small frontend that generates feedback [03:02] el: err, tickets from feedback [03:02] current bugzilla has more problems. As soon as there is a new release, old bugreports should be closed and people should be asked to reopen if needed. that would keep the trash level way lower [03:02] el: it would then take a small group of people to review the feedback and turn those tickets that actually contain issues to the bug tracker [03:02] superstoned: would you happen to be running X from a chroot or something? [03:02] toma: hmmm...i wonder if we could do that with LP.... [03:02] danimo, different from the one that toma just posted? [03:02] el: that's about the same what trolltech does if you send reports to qt-bugs [03:03] nope, tough i started it from the commandline by hand cuz when i use KDM i can't see fonts on the screen, it's all white... [03:03] Hobbsee: it is a small thing to ask from a user imho [03:03] with X [03:03] toma: that looks good [03:03] that's why i use XGL now [03:03] toma: true. i wonder if/how that would work with LP. [03:03] danimo, yes, sounds reasonable. but if toma's admin interface would allow to transfer issues to bugzilla it would be ok, no? [03:03] el: absolutely [03:03] el: I hadn't have a look at toma's interface yet [03:03] toma, hobbsee: i agree old bugs should be closed after a new release, yes. keeps things clean. [03:03] danimo, http://toma.kovoks.nl/admin/view.php [03:04] el: I just saw it [03:04] superstoned: unfortunately, dapper and edgy bugs are filed at the same time, so i'm not sure how you'd figure that out. [03:04] el: all it would take is a "create bug report from feedback" [03:04] danimo, jupp [03:04] indeed [03:04] still, who should go through all the reports and why? [03:04] developers won't have the time, usability neither... [03:04] el: that's the point [03:05] el: if we want to do this, we need to attract a new type of contributors [03:05] yes [03:05] i'm happy to keep an eye on them as author of the app [03:05] el: sorta like those who always wanted to spend time on the project, but couldn't [03:05] Hobbsee, community goddess - how do we get new contributors??? [03:05] just because there are also positive feedback [03:05] el: the amount of positive likes should keep the motivated we home :) [03:05] anyway, nobody noticed big mem usage compared to dapper, i guess, so it's likely an anomaly here. anyone noticed the text doesn't show? [03:05] something missing in bugzilla [03:06] el: good question. do tell when you find the answer. [03:06] :) === danimo would suggest a call on the dot, published through many online garzettes [03:06] danimo, jupp. [03:07] el: we need to get our current devs active in the most useful ways possible, before bothering to get mroe new people [03:07] this way we can turn the tech-savvy people into "community translators" [03:07] fortunately, that's already starting to happen [03:07] if the upstream author only sees a new flow of bugreports, then that would not work. [03:07] el: unfortunately, you cant say "go attack the buglist" because they dont really have the expertise to fix the bugs. [03:07] toma: well, if those bugreports are good, he will [03:07] so a filter, which removes all 'i like' items and makes new reports from the i dont like. would not work for me [03:07] toma: like it would also be their job to find duplicates, etc [03:08] toma: no, this won't work purely automatically [03:08] although I think we could automate a lot [03:08] like the feedback === rraphink [n=raphink@ubuntu/member/raphink] has joined #kubuntu-devel [03:09] i just see it as a database with reaction i would walk through when i'm entering hacking mode [03:09] Hobbsee, yeah, that's true. but right now, we were referring to contributors who go through the LikeBack feedback reports to order them, not fix the bugs. [03:09] "Dear User, I have read your LikeBack entry and forwarded it to the developer of . If you want to follow the activity on this report, visist . Thanks for your contribution. XY [03:10] el: true. [03:10] currently i'm not even being able to comprehend a solution to that === insanekane [n=kane@202.83.32.168] has joined #kubuntu-devel [03:10] we need to find a pitch for the dot story [03:10] like a motivation [03:10] danimo: i could axe murder you? [03:11] Hobbsee: sure, come over and try :) [03:11] danimo: hehe. it could be a talking point, you know. [03:11] Hobbsee: hmm? [03:11] "hey, i was axe murdered last week" [03:12] isn't axe a bit old fashioned? chainsaw would be less work [03:12] haha [03:13] lol [03:13] there is a difference for small apps and bug apps [03:13] kmail has enough feed back, although the quality is not that high. [03:14] yes [03:14] we face that problem a lot [03:14] heh. bug apps [03:14] smaller apps hardly have feedback [03:14] toma: yes, but they surely shouldnt need it, as they're non-bug apps, by definition :P === bddebian [n=bdefrees@71.224.172.103] has joined #kubuntu-devel [03:14] hi bddebian [03:14] toma: well, for instance with kmail, we only occasionally get feedback from people who found their mails trashed [03:14] bddebian: can go thru all the bugs. [03:15] toma: but the more people we get to report the incident, the better the chance to reproduce the underlying problem [03:15] toma: so "bug apps" have a chance there, too [03:15] danimo: exactly, but i dont think likeback is suitable for it [03:15] that [03:15] one of the problems is that there isn't an easy way to automatically find dups [03:15] Heya folks [03:15] Hi Hobbsee [03:16] buzilla isnt either btw [03:16] Hobbsee: I can? :-) [03:16] bddebian: yep [03:16] bddebian: unfortunatly you won't have time to sleep for the rest of your life [03:16] seaLne: but, how difficult would it be to write that? [03:16] hm, toma, but if imagine to be a non-technical user: wouldn't you be frustrated if you're able to give LikeBack feedback to a bug-free app, but not to a bug app? [03:16] toma: maybe that's wanting too much [03:17] seaLne: Well I'm used to that lately :-) [03:17] el: yes. I dont have all the answers here [03:17] toma: to me it seems difficult i imagine its a IR problem [03:18] toma, i think if we decide to offer LikeBack in final releases, then it should be available for the majority of apps, and especially for the core apps === abattoir [n=abattoir@59.92.57.49] has joined #kubuntu-devel [03:18] el: true [03:20] danimo: why? if you would make a system where a user can report bugs which are reproducable.. let them enter each step. the second user can choose from the pulldown of previous users or enter a new step. we could catch dup. reproducable bugs [03:20] el: ok, but then a filter would only be needed for the large (&buggy) apps [03:20] yes, probably, toma [03:20] assuming you could detect dups, a possibility could be to set a threshhold of X people must have reported this before it gets escalated? [03:20] kjots author can probably deal with the feedback [03:20] toma, yes [03:30] seaLne: for bugs which are reproducable it is usually easy to fix them [03:31] so even a single report would be enough for me [03:31] hey cool. kwifimanager isnt on the menus in edgy. [03:32] Hobbsee: very good === Hobbsee installs a package that she fixed a while ago [03:33] at least i know it works now :_ [03:33] yay. it has another bug though :P [03:33] i was thinking as a way to make it easier to go through them if you saw that 5 people had reported the same thing you might look at it more closely than the thousand other reports [03:34] seaLne: yes, you are right [03:34] seaLne, yes, it helps to set priorities for fixing bugs [03:35] but what we miss is an organised system to report reproducable bugs [03:36] and a system to cleanup the current bug system [03:40] toma, well, bug trackers have a two-fold functionality: on the one hand, they report bugs to developers. on the other hadn, they help users to calm down when they were frustrated by the system. === Hobbsee has just discovered amarok's bug reporting system, it seems. [03:41] toma, for frustrated users, it reporting a bug must be really easy. writing down reproductions steps is alreaday too much in many cases [03:41] on the other hand, reports that cannot be reproduced won't help the developers... [03:41] indeed, just about o say that ;-) [03:41] neat that they get you to email with a backtrace === Hobbsee wonders why she hadnt noticed that before [03:42] you have never had amarok crash?! [03:42] wow [03:42] nope [03:42] is the information in the backtrace usually sufficient to identify the source of the problem? [03:42] i dont think so [03:42] el: unlikely [03:42] valid backtraces should be reported with one click (report yes/no) [03:42] el: dunno. i'm not good with backtraces. it had a lot of info though. [03:42] toma, yes [03:43] el: valid backtraces are perfect [03:43] and possibly a free text field to write some angry lines ;-) [03:43] yes ;-) [03:43] Hobbsee: i rarely have amarok not hang/crash on me [03:43] (which is then removed before sent to the developer, haha) [03:43] hehe [03:43] haha [03:43] seaLne: wow [03:43] http://rafb.net/paste/results/5hjbSv91.html [03:44] the problem is mostly that distributions dont ship the symbols needed for a valig backtrace [03:44] by default [03:44] toma: which ones are they? gdb, or osmething else? [03:45] Hobbsee: do you listen to streams much? [03:45] seaLne: no [03:45] bandwidht limit, remember? [03:45] Hobbsee: that are the -dbg packages [03:45] ah, well streams seem to be the main problem with amarok [03:45] toma: true that. that's one heck of a lot of packages === chavo [n=chavo@67-22-110-236.atlsfl.adelphia.net] has joined #kubuntu-devel [03:47] is listening to a 128k stream for an hour really ~0.5Gb or is my maths as bad as that seems? [03:47] Hobbsee: well, there should be a separate repository with the same packages, build with debug enables or something... [03:47] enabled [03:47] toma: true [03:48] if an app crashes without valid debug, it could offer to install that version of the app. [03:48] toma: that sounds good [04:28] hey nasty. 2 amarok crashes in one day. === Hobbsee goes to find 1.4.2beta1 === yuriy [n=yuriy@207-172-219-193.c3-0.frm-ubr3.sbo-frm.ma.cable.rcn.com] has joined #kubuntu-devel === abattoir [n=abattoir@59.92.57.49] has joined #kubuntu-devel === hunger [n=tobias@p54A6143B.dip0.t-ipconnect.de] has joined #kubuntu-devel === toma is now known as toma_ [05:18] its "good" to see the cd burning problem is affecting gnome stuff aswell === yuriy [n=yuriy@207-172-219-193.c3-0.frm-ubr3.sbo-frm.ma.cable.rcn.com] has joined #kubuntu-devel [06:03] Hi there. [06:03] Is there a way to stop that guidance power manager thing from offering to hibernate? [06:05] Anyone working on better icons for it? The current set looks like the battery is half full when it really is at 100%... [06:12] BenC: Pretty sure... I need to enter a passphrase to get to the filesystem that fsck complains about. [06:12] BenC: And I only get asked for the passphrase after waiting. [06:13] BenC: That dmesg log is not really helpful I am afraid:-( [06:15] BenC: Which script outputs this driver loading message? [06:16] BenC: Ah, S10udev... [06:17] BenC: assuming that went OK the delay could be caused in S11mountdevsubfs.sh, S13pcmciautils, S15module-init-tools, S17procps.sh, S20checkroot.sh, S22mtab.sh, S26lvm and S27evms. [06:20] mountdevsubfs.sh seems unlikely... as does S22mtab.sh and S20checkroot.sh (which might actually be the fsck right after the trackpad thinking about it:-) [06:54] hunger: no BenC here... [06:58] Lure: Oh, sorry. Wrong channel once again:-( [06:59] hunger: no problem for us, just that you get your message trough... ;-) [06:59] Lure: It is a dup bug anyway:-) [07:00] I just hope it will get fixed anyway... === hunger has high hopes for edgy... so far it actually does seam to work on my box. [07:00] hunger: regarding guidance power manager - it is first alpha release and you should report feedback to https://wiki.kubuntu.org/KubuntuPowerManagementFeedback [07:01] Lure, Thanks, I will! === Lure goes to grab some food === abattoir [n=abattoir@59.92.39.135] has joined #kubuntu-devel [07:14] Lure: Which package contains the guidance power manager? === toma_ is now known as toma === superstoned [n=supersto@168-234.surfsnel.dsl.internl.net] has joined #kubuntu-devel === yuriy [n=yuriy@207-172-219-193.c3-0.frm-ubr3.sbo-frm.ma.cable.rcn.com] has joined #kubuntu-devel [07:46] hunger: kde-guidance [08:14] now I remember where I have seen purple color windows: http://r-101.blogspot.com/ (see Aug 1992) ;-) [08:19] where do the tar-balls merge-o-matic mentions go? === abattoir_ [n=abattoir@59.92.41.208] has joined #kubuntu-devel === apachelogger [n=me@amarok/rokymotion/apachelogger] has joined #kubuntu-devel === abattoir__ [n=abattoir@59.92.40.200] has joined #kubuntu-devel === apachelogger is now known as fdlogger === fdlogger is now known as apachelogger === ZuZuu [n=ZuZubunt@AVelizy-154-1-84-192.w86-217.abo.wanadoo.fr] has joined #kubuntu-devel [09:13] what was that url for the patched kdelibs + kdebase? === neoncode [n=neoncode@unaffiliated/neoncode] has joined #kubuntu-devel === apachelogger [n=me@amarok/rokymotion/apachelogger] has joined #kubuntu-devel [09:45] Sime: deb http://www.buntudot.org/people/~imbrandon/packages/simes-patches/debs/ ./ [09:49] thx [09:50] toma: is there a wiki page about these patches already? [09:50] Sime: no idea === Seveas [n=seveas@ubuntu/member/seveas] has joined #kubuntu-devel [10:41] https://wiki.ubuntu.com/KubuntuKDEMedia [10:41] does now === omeow [n=omega@co63471-a.olden1.ov.home.nl] has joined #kubuntu-devel