[00:30] * ryanakca agrees about the logos [00:42] new kdevplatform fixes things [01:14] jussi01: Trying to make sure Quassel highlights worked OK with plasma-netbook. [01:14] They do. [03:20] I think the kubuntu logo could be the ubuntu logo with different colors [03:20] and no kogs [03:23] * ScottK likes it the way it is. [03:25] * shtylman agrees :) [03:25] * yuriy wonders how long Riddell took coming up with it [03:26] * shtylman likes to think god spoke through riddel to make it [03:26] *Riddell [04:49] lex79: I just uploaded Debian's akonadi-googledata to Karmic. [04:49] \o/ thank you :) [04:52] Thanks for reminding me. === Guest76973 is now known as santiago-ve [10:18] shtylman: the logo was done by the chap who does konqi the dragon [10:44] neversfelde: koffice 2.1 beta is available if you want to take it [11:08] without searching: is it known bug that apport is failing in karmic? [11:11] python2.6 seems crashing during startup that causes apport to fail [11:23] taavikko: yeah python2.6 is on my list of things to look at today [11:24] Riddell: ok, thanks, just got worried :) === xerosis_ is now known as xerosis [13:19] fabo: how does this look to you? http://people.canonical.com/~jriddell/tmp/kubuntu.mk [13:21] _Sime: you just tought me a new ccTLD :) [13:24] <_Sime> hi [13:39] agateau! [13:39] JontheEchidna: amarok uploaded [13:42] damn i had could bet there was TB3 in universe [13:42] :| [13:45] Riddell \o/ [13:46] agateau: ken doesn't seem to have got round to packaging the libindicate update so no kmail patches uploaded yet :( [13:46] Riddell: oh [13:47] Riddell: I just updated it and got r325 [13:47] Riddell: so it should be good [13:49] agateau: still 319 in the archive https://edge.launchpad.net/ubuntu/+source/indicator-applet [13:49] Riddell: mmm maybe this come from a ppa [13:49] * agateau checks [13:51] apt-cache policy libindicate2 will know [13:51] Riddell: comes from dx team ppa :/ === rickspencer3-afk is now known as rickspencer3 [14:32] Riddell: I can have a look at koffice this evening [15:05] hi. [15:06] hi bakkdoor [15:10] i'm working as an intern at intevation gmbh, which is part of the kolab konsortium ( http://www.kolab-konsortium.de/ ) and i'm currently working on a ubuntu package of kontact enterprise 3.5. i was wondering if there is a package like this already out there (I could not find one) and if it would make sense to integrate the package to the official ubuntu repository. [15:12] or in general, i'd like to know how the best way of getting in contact with the ubuntu community would be. [15:13] bakkdoor: here is a pretty good place to get in contact with the Kubuntu contributors [15:13] bakkdoor: kontact enterprise is KDE 3 still? [15:13] that's what I thought ;) [15:13] kontact enterprise 3.5 is [15:14] there is also enterprise 4, which is kde4 [15:14] but for now i'm dealing with e3.5. e4 might follow soon [15:14] bakkdoor: there's no package currently, of course we used to have kdepim from KDE 3 packaged including patches from the enterprise branch [15:16] Riddell: alright. well i have a version working for hardy. we chose hardy as a first system, since it's LTS. but once I have this fully covered, I'll also work on a package for the newer versions [15:17] bakkdoor: groovy, are you planning to put it in a PPA? [15:19] hardy probably had kontact 3.5.10 enterprise, no? [15:19] i have the currently build packages available for installation via apt-get [15:19] the url is: http://files.kolab.org/apt/ubuntu/ [15:19] yuriy: yes, correct [15:20] yuriy: reason for choosing hardy was also, because we have a stable debian etch version and the kdelibs was nearly the same to hardy. [15:21] would be great, if anyone willing to try them out, would do so and give some feedback, as I'm still new to the whole packaging system etc. but i'm willing to learn ;) [15:23] Riddell: by ppa, you mean publishing it at launchpad? [15:24] bakkdoor: yes, publishing it yourself is fine too but a PPA will give you a build daemon for that extra certainty that it builds correctly [15:24] Riddell: ah ok, cool. well if that is the preferred way, I will talk to my boss. we want to make it as easy as possible for ubuntu users to use the enterprise package. [15:29] bakkdoor: packaging looks fine at a glance [15:29] there's no ./configure file, where is the autofoo stuff run? [15:33] bakkdoor: You should know that Hardy is not LTS for Kubuntu. KDE support expires in October of this year. [15:33] ScottK: oh, really? good to know. what is the latest LTS for kubuntu then? [15:33] For Kubuntu it's pretty pointless to deal with anything other than kDE4. [15:34] There isn't one. [15:34] 10.04 will be our next opportunity. [15:34] just the next lts [15:35] bakkdoor: I think our kolab server packages are not in good shape either. If someone were interested in helping out with that, it would be very useful. [15:35] ScottK: alright, thanks for the info. then I guess working on 9.04 would make more sense then? [15:35] ScottK: ok. i'll mention it to my boss. [15:36] bakkdoor: Or depending on your timeline, maybe 9.10. [15:36] Riddell: i don't really know, why ./configure file is missing. it is in my work directory. maybe i missed something? [15:37] ScottK: problem is, that i'm only going to be here up to middle of october. but I'll see what i can do [15:37] bakkdoor: that's why a PPA is nice, to make sure the package builds and it's not just a fluke on your machine :) [15:38] ScottK: our final plan is to set up a automated build and release system so that there are always ubuntu packages of the latest stable version out there [15:38] Riddell: true :) [15:41] Riddell: Do you have an upgrade app you want tested? [15:41] ryanakca: you're doing a jaunty to karmic upgrade? [15:41] Yes [15:42] ryanakca: you can try update-notifier-kde -d [15:42] I don't know if anyone else has tried it this cycle so it may well explide [15:44] Riddell: Well, it fails on "W: Failed to fetch http://mirror.noreply.org/pub/tor/dists/karmic/main/binary-amd64/Packages 404 Not Found [15:45] ryanakca: is that the mirror you're using? [15:45] " ... Maybe have a "Would you like to ignore this line" instead of telling me I have network issues and quitting? [15:46] Riddell: Well, it's one of them, to get the latest tor. We know it's a 404 (so we know it isn't a network issue, we can contact it and get the 404), so maybe say "This repository may not have packages for $RELEASE, would you like to ignore it?" [15:46] * ryanakca realizes he just repeated himself [15:48] it normally disabled all but the main ubuntu repositories [15:49] Riddell: do you have any hint for what i should do to fix the problem of the autoconf files missing? do i need to add these files somewhere so they get into the package as well? [15:49] Riddell: http://pastebin.com/m359754de [15:50] Riddell: Also, is it written for Qt3 or something? It looks... old, compare the look of the two windows on http://ryanak.ca/~ryan/old-look.png [16:00] bakkdoor: you generate them with make -f debian/rules buildprep [16:01] ryanakca: it's using Qt 4's built in theme [16:01] fabo: ooh thanks [16:02] Riddell: isn't that step done automatically when calling debuild ? [16:04] bakkdoor: it can be if you turn on the right variable, I havn't touched KDE 3 packaging in so long I don't remember what that variable is [16:04] DEB_KDE_CVS_MAKE := yes [16:04] that's the one [16:04] bakkdoor: so all is well [16:06] Riddell: ah ok thanks [16:08] hm it seems that i have that within my rules file. [16:08] Riddell: http://ryanak.ca/~ryan/error-update.png is the box with the network issue message and the 404 one. [16:18] Riddell: any idea, what else could cause this problem? [16:18] bakkdoor: well it's not a probklem [16:19] if they get generated during the package build that's fine [16:20] Riddell: so its not a problem that the files are missing? [16:23] bakkdoor: no [16:24] Riddell: ok, good to know. thanks. === |newbie| is now known as dantti_ [16:53] Tonio_: k3b packaging question? toolame and kdebase-kio-plugins are listed in Suggests (but neither exist). [16:53] Tonio_: should toolame be replaced by lame? and not sure what the kio is replaced by (if anything). [16:54] rgreening: hum old stuff that should be removed... I have to upload another fix today, I'll fix this :) [16:54] kk. cool man :) === dantti_ is now known as dantti [17:00] Riddell: I'm just finishing a call [17:03] rgreening: Feel like uploading what you got done in the Dooble package somewheres please? [17:03] agateau, davidbarth: about? [17:03] Riddell: I think davidbarth may have another meeting now :( ? [17:04] he did accept the invite [17:04] ok [17:04] Riddell: I feel like I am missing something [17:04] agateau: meeting to discuss xsplash equivalent in Kubuntu [17:04] Riddell: I'm here and off the phone [17:04] oh [17:05] Riddell: what is the current status? [17:05] rickspencer3: we need to get KDM to start and stop ksplashx at the apprioriate time [17:05] davidbarth mentioned agateau may be able to help with it [17:05] Riddell: hi [17:06] Riddell: yes, sorry unplanned meeting that i have to attend [17:06] Riddell, agateau: on irc, in this channel, right? [17:06] ok [17:07] yes [17:07] Riddell: bratsche is here too [17:07] hi bratsche [17:07] Hi. [17:08] agateau: do you know anything about this, and are you willing/able to work on itso if davidbarth agrees, are you able to look into this? [17:08] hmm, two sentences in one there but you get the idea :) [17:08] Riddell: don't know much, but I count on bratsche can update me [17:09] as for being able to work on this, it depends on the deadline [17:09] Riddell: agateau: does Kubuntu even need xsplash? [17:09] does it solve a problem for Kubuntu, or just create a problem? [17:09] Yeah, that's what I'm wondering. [17:10] bratsche: can you summarize the reason for xsplash? [17:10] s/for/for creating/ [17:10] agateau: I can summarize part of it. The other part I kind of don't really get, it seems pointless to me. [17:11] agateau: The part that makes sense is that we're starting X earlier and not displaying usplash, so we need something to display before the gdm greeter. [17:11] So we show a full-screen window with an Ubuntu logo and a throbber moving back and forth, and not a progress bar since historically system startup progress bars are not very accurate. [17:11] xsplash provides feedback that the computer is booting, and covers for gdm and gnome as they set themselves up [17:11] And once we receive a signal from gdm that it is loaded then we hide xsplash. [17:12] bratsche: what's the part that seems pointless to you? [17:12] bratsche: so without xsplash you get a blank screen until gdm shows up, that's it? [17:12] agateau: Yes, I think so. [17:13] Riddell: After the user logs in then we show xsplash again until the desktop is loaded, and when it receives signals from gnome-panel and nautilus then xsplash hides again. [17:13] bratsche: right, that's to make the experience look better [17:13] Okay. [17:13] we have that part already with ksplashx [17:13] bratsche: it replaces GNOME splash screen then [17:13] instead of watching gnome load the desktop slowly, and not being able to click, xsplash fades into a functional desktop [17:14] Riddell: that was what I was thinking [17:15] Riddell: is it possible to simply deliver Kubuntu with the Jaunty boot experience? [17:15] This part ends up being tricky to get it very smooth, and I'm still trying to fix things up with various XComposite related hacks. [17:15] (we can ask if we *want to * next) [17:15] on whether we want this, it's nice to have a quick bootup so if X/KDM can be made to startup sooner that would be nice [17:16] and in the worst case if we don't have a splash it's only a few seconds until the greeter loads anyway [17:16] Riddell: Well, basically everything that was starting behind usplash is now starting behind X on Karmic. It will supposedly start faster, but there is still some time there. [17:16] So that's kind of the issue for the first half of the splash. [17:17] X will be started as soon as is possible. [17:17] (please correct me if I'm wrong, someone) [17:17] bratsche, Keybuk: will X continute to be started as part of GDM or started separately? [17:18] but xsplash has some weird gnomish dependencies? [17:18] xsplash is written in gtk+. I could have just written it in Xlib directly, but writing it in gtk+ was faster. [17:19] so xsplash is essentially a non-starter for Kubuntu as presently written, correct? [17:19] right [17:19] interestingly, ksplashx does not even depend on Qt :) [17:19] but the hard part is the *DM integration rather than an app which shows a pretty picture [17:19] Yeah, I know. But it would have taken me longer to write xsplash using Xlib. [17:19] if ksplashx does not depend on Qt, then it's not really "k" is it? [17:20] Riddell: X is started by the display manager [17:20] the display manager by Upstart [17:20] rickspencer3: it just happens to be kde splash screen, but it was written to be lean and mean [17:20] (there is even asm in it) [17:20] rickspencer3: right, the KDE and Qt dependencies were all removed because the point is to start immediately not once half the libraries have loaded anyway [17:20] agateau: so could Ubunutu not use it in place of xsplash? [17:20] bratsche: ^ [17:20] ? [17:21] probably but it doesn't matter much which splash is used, as I say the important point is getting it started [17:21] rickspencer3: We would have to hack it up to support the signals we want, and we'd have to do a bunch of testing. If we want to do that, fine. [17:21] and GDM has a nice init system which I think KDM doesn't [17:21] rickspencer3: I've never looked at it. [17:21] probably too late, then [17:21] what happens if the display manager does not start xsplash, just a blank screen until kdm? [17:22] If it's fast enough it doesn't matter. [17:22] ScottK: right [17:22] who is responsible for starting xsplash? [17:22] agateau: GDM does [17:22] gdm init scripts. [17:22] rickspencer3: blank screen until kdm / appearing desktop during auto-login [17:23] it's in /etc/gdm/Init/Default [17:23] /etc/gdm/Init/Default and /etc/gdm/PreSession/Default [17:23] which I guess is the first thing GDM runs before loading itself [17:23] ScottK, Riddell would a blank screen be ok? [17:23] Riddell: gdm/Init is what GDM runs to display the greeter [17:23] gdm/PreSession is what GDM runs for the user's session [17:23] How long are we talking? [17:24] but for Kubuntu, we would need something to run, as well as something to start up that thing [17:24] unless we go with a blank screen [17:24] It seems to me I get to KDM pretty darn fast on my mini 10v. [17:24] scottK: no idea, we'd need to see bootcharts [17:24] OK. I can do some boot charts tonight. [17:24] * ScottK needs to focus on $WORK for the next several hours. [17:25] bye bye ScottK ;) [17:25] so perhaps a feasible fall back is to do nothing [17:25] for comparison, the GNOME session (auto-login) currently takes 13s to start [17:25] Conveniently I have the reference system for boot speed testing. ;-) [17:25] while the GDM Greeter session currently takes around 5s to start [17:26] The times to care about are: start to KDM start and KDM start to desktop? [17:26] no [17:26] OK [17:26] What then? [17:26] X "ready" to KDM Greeter ready [17:26] X "ready" to KDE Desktop ready [17:26] OK. [17:26] the usual way to tell when X is ready is when the first process with $DISPLAY set is run [17:26] kdm has a Xsetup script which is run before showing the greeter [17:26] I'll see what it tells me and report back then. [17:27] does gdm greeter shows as fast as possible or does it wait for some services to be started [17:27] . [17:27] ? [17:29] as fast as possible [17:29] I mean, how does gdm knows it's time to show its greeter? [17:29] kdm usually takes a second or two to load at the most when X is started, is that the time we are talking about? [17:29] agateau: it doesn't need to know [17:30] GDM starts X, once X is started, it either starts the GDM Greeter session or GNOME Desktop session [17:30] Keybuk: I don't see xsplash in this sequence [17:31] agateau: in which? [17:31] Keybuk: in this "GDM starts X, once X is started, it either starts the GDM Greeter session or GNOME Desktop session" [17:31] agateau: as bratsche says above, xsplash is one of the first items in /etc/gdm/Init/Default and /etc/gdm/PreSession/Default [17:32] yuriy: yes although with more things happening at the same time it may be slower [17:32] ie. GDM starts it as one of the first things it does _to_ start the GDM Greeter session or the GNOME Desktop session [17:32] yuriy, Riddell: and don't forget, that at that point the screen has *already* been black for a few seconds [17:32] even if KDM takes only a "couple of seconds" to start, that brings the black time up really quite high [17:32] agateau: Yes, we start xsplash from the gdm init scripts. Once gdm moves into the greeter then the greeter sends a signal to xsplash to go away. Or if we go into a desktop session then Nautilus and gnome-panel send signals to xsplash to go away. [17:32] Riddell: where can I get the koffice 2.1 beta tarball [17:33] bratsche: ok [17:34] bratsche: so it's "only" there to show up while gdm greeter is starting [17:34] Yes. [17:34] so all we need is to start ksplashx in Xsetup then find a suitable place in the KDM code to tell it to phase out (stealing the relevant code from ksmserver) [17:35] Riddell: yes, I think so [17:35] Riddell: and create a throbber ksplashx theme [17:35] agateau: yes, or just keep the current "phasing in disk" which I think would be suitable [17:36] how easy will it be to add the OS Switcher to ksplashx later on? [17:36] Keybuk: since ksplashx does not support text, not very easy [17:39] Keybuk: that's a plan for future releases? [17:39] yes [17:40] it could have pretty pictures of OSs :) [17:40] we can always do prerendering though [17:40] that's probably something to worry about at the time [17:40] * agateau agrees [17:41] bratsche: I guess the throbber is expected to "not jump" between xsplash before gdm and xsplash after gdm [17:41] bratsche: I mean: the throbber position should be the same [17:42] or more precisely, the throbber current image in the throbber animation [17:42] agateau: No, we don't try to do anything fancy like this. I'm concerned enough trying to come up with XComposite hacks to keep the entire splash window from disappearing when we start window/composite managers. :) [17:43] bratsche: ok, then we should be able to implement something in a reasonable time frame with ksplashx then [17:43] Yeah.. don't worry about little hiccups like that. It's still a better experience than a black screen. [17:43] is this supposed to land before feature freeze or ui freeze [17:43] ? [17:43] davidbarth or rickspencer3 ^ [17:45] uh [17:45] before feature freeze seems a tad unreasonable [17:45] I presume Kubuntu is booting, right? [17:45] it seems to :) [17:46] I suggest someone needs to create a somewhat detailed plan ... and then we need to get it implemented asap [17:48] I am quite busy until FF, but I can probably put together a plan before UIF [17:48] I just tried adding ksplashx to Xsetup and it works ok [17:48] so it's just a case of getting KDM to send the upAndRunning signal [17:49] Riddell: sounds like you are already on it :) [17:50] and making sure KDM gets the same upstart-ification as GDM is due [17:50] Keybuk: what needs to be done for that? [17:53] rickspencer3: I can turn this into a spec if that's useful, then me and agateau and davidbarth can fight between who gets to implement it [17:53] Riddell: sounds good [17:54] Riddell: probably just remind me ;) [17:54] I assume that KDM doesn't have exotic dependencies compared to GDM? :p [17:55] Keybuk: # Should-Start: console-screen acpid dbus hal [17:55] says the current script [17:55] right [17:55] nothing silly like network-manager :) [17:55] why acpid? [17:56] Keybuk: When does the new init stuff land btw? [17:56] bratsche: between now and beta freeze [17:58] Keybuk: I think that's obsolete, it would have been used to suspend from kdm, but now hal (via solid) will be used [17:58] gdm also has acpid in it's init.d script [17:59] yeah, but I can't find anything that even uses it [17:59] I think we're done, thanks for showing up all [18:00] ok bye [18:03] Thank you. === jjesse_ is now known as jjesse [18:34] Riddell: we have a little issue with libavformat/ffmpeg [18:34] grrr any of you have some notes plasmoid thingy keep adding itself to the panel without you telling it to? [18:34] Riddell: basically kubuntu-restricted depends on the unstripped libavformat [18:34] Tonio_: mm? [18:34] Riddell: k3b depends on the standard one [18:34] Riddell: but libaformat-unstripped doesn't exist anymore [18:35] gettin in the way of my kickoff. wish i had a typewriter :( [18:35] Riddell: although the -dev package still conditionnaly depends on it.... messy :) [18:35] maco: that happened to me once, no idea what caused it [18:35] Tonio_: I don't see k3b depending on it [18:36] Tonio_: so fix kubuntu-restricted-extras? [18:36] Riddell: libk3b6-extracodecs [18:36] Riddell: well I don't know yet if it's normal that the unstripped ain't there [18:37] Riddell: the ffmpeg package has an issue on that point, as the binary package has been removed, but there are still deps on it in the control file... [18:37] Riddell: I have to investigate and will fix k3b or kubuntu-restricted extras according to this... [18:37] Riddell: I just wanted to let you know in case you really want the unstripped version... [18:37] Tonio_: libavformat-unstripped-52 is still there [18:37] sure you have multiverse enabled? [18:38] version 4:0.5+svn20090609-2+unstripped2 [18:38] Riddell: still there but from a previous upload [18:39] Riddell: https://edge.launchpad.net/ubuntu/+source/ffmpeg/4:0.5+svn20090706-1ubuntu1/+build/1171935 [18:39] Riddell: last ffmpeg version doesn't have it, and there is a conditionnal de on it [18:39] Riddell: simply try to "sudo apt-get install libavformat-dev libavformat-unstripped-52" [18:40] Riddell: breaks, and in order to get k3b libs depends on the unstripped version, I need to build-dep on both.... [18:40] Riddell: I told you that was messy ;) [18:41] Tonio_: have you asked siretart why it has gone? [18:42] Riddell: nope I'm going to ping him, especially since it's supposed to be debian merge, but I can't find his version anywhere, only the previous one... [18:42] Riddell: let's ping him [18:44] Riddell: I asked, and will fix accordingly... [19:21] i guys, any chance you are patching help->report bug menu entry to not work? [19:22] If 'work' means report to bugs.kde.org, then yes. [19:22] We patch it to report to Launchpad. [19:22] does nothing here [19:23] click -> nothing [19:23] 4.3.0 packages in 9.04 [19:23] Probably missing some launchpad integration or something. [19:24] want a bug report about that or better i don't waste my time? [19:24] tsdgeos: confirmed - 4.3 on jaunty [19:25] ScottK: and you really have so many people to triage the bugs and send them upstream? i don't think si [19:25] -i+o [19:26] Not really my area. [19:26] ok === rickspencer3 is now known as rickspencer3-afk [19:28] tsdgeos: the patch may need adjustments in the jaunty version which havn't been made [19:29] tsdgeos: we've been using apport for crash handling for the last few release cycles turning it off before release and as far as I can tell bugs have been flowing upstream smoothly enough without annoying upstream with crashes we create [19:29] :-) [19:37] yay, eet finally compiled [19:54] nixternal: Ask NCommander to bump your package build priority. [19:54] is it really a rush for it in the PPA? [19:54] plus if it is, I think you just did that for me :) [19:55] I didn't give him the package name. [19:55] We got ~2days for feature freeze, so yes. [19:55] ScottK: true, I don't think NCommander would have guessed kairmode in the nixternal ppa :p [19:59] tsdgeos: kde4libs kde4libs_4.3.0-0ubuntu1~jaunty1~ppa3 uploaded to backports PPA with Report Bug apport patch removed, it doesn't make much sense for backports [19:59] you rock :-) [19:59] thanks for reporting [20:00] well, irc is easy :D [20:14] Tonio_: kid3 is broken. maybe a problem with the latest changes? [20:14] nixternal, I need to bump what? [20:14] NCommander: nadda, I am going to put it in REVU [20:15] nixternal: Don't you want kairmode bumped so I can test it? [20:16] i will link you to a deb here in a minute [20:16] OK [20:17] python apps == arch: all right? [20:17] no need to build the same thing for all the archs [20:20] nixternal: Depends on if you're using any arch any components. [20:20] if it's pure python yes [20:20] pyqt4, pykde4 [20:21] with some deps on wireless-tools and bluez, just to make sure they are there [20:24] ScottK: http://people.ubuntu.com/~nixternal/kairmode_1.0-0ubuntu1_all.deb [20:24] I haven't tried restarting KDE to see if it starts automatically [20:24] it should, I think :) [20:31] nixternal: there's nothing in /usr/bin [20:34] nixternal: segfaults after turning off wireless [20:35] can't turn wireless back on either it seems [20:41] Riddell: ya, fixing that now [20:41] thought I got it in the package portion but I didn't === EqS is now known as EgS [21:09] Riddell: the reason for the segfault on shutting off wireless might because we don't support your machine (yet?) === kubotu_ is now known as kubotu === nixternal_ is now known as nixternal [21:25] Tonio_: toolame -> twolame ? maybe thats the correct change for k3b suggests [21:33] anyone has a kubuntu-default-settings bzr link? ... LP keeps timing out on me [21:35] rgreening: I don't think so, but I'll check ;) [21:35] rgreening: we also have a problem with ffmpeg I ned informations from sirestart to fix [21:36] Tonio_: yeah, I tried ripping a CD today, and it fails to generate the mp3s... least on my system [21:36] a|wen: https://code.edge.launchpad.net/~kubuntu-members/kubuntu-default-settings/ubuntu === Unksi is now known as unksi_ [21:37] great, thx [21:39] JontheEchidna: What's your plan for kadu? [21:49] building koffice is fun :/ [22:00] neversfelde: it's a beast [22:07] nixternal: Seems to basically work. I say ship it. === spstarr_ is now known as spstarr [22:56] Hello! I'm Olof from Sweden... got a little tempted to start getting involved in the kubuntu community so I thought I'de check this channel out [22:57] hi spacelime! welcome on board [22:57] * a|wen waves from the other side of Øresund [22:58] thank you! =) [22:59] your from Denmark I persume? whereabouts? [22:59] spacelime: indeed i am ... from greater copenhagen [22:59] cool... i'm from Uddevalla, near Gothenburg [23:00] that is not that far away [23:02] it's not.... if you have a boat you can sail here in a day or two =) [23:02] or even swim [23:03] i'd stick to the boat :P [23:05] the choice is yours! =) anyway... this is my first visti here.. actually, i havn't used computers for any creative stuff for about 10 years... i used to do some game programming as a teenager.... was a die hard amiga fan boy... but amiga didn't keep up and i switched to MS and then the spirit slowly faded =) [23:06] linux always felt too treckie for me =) but the last few months I came across some very inspiring articles.. .especially by the *buntu- community [23:06] so i decided to give it a try with ubuntu and liked it big time [23:07] but now I'm switching to Kubuntu because i feel there is more wind in the sails on the kde side somehow [23:08] basically i just like the spirit of creativity, sharing and so on and would like to get a piece of the cake [23:08] but i'm not sure where to start [23:08] packaging seems a little boring to be honest =) but maybe its a good place to begin... [23:09] spacelime: cool, glad you like it! ... and appreciate you stopping by here; there is loads of ways, you can help out in the community: packaging, translations, bug squashing / fixing, PR, artwork ... just name what interests you, and we can find the right person to talk to :) [23:09] cool =) [23:11] what i like the most is to improve innovation.. making things more simple and clever... I also like designing. but as I havn't really done anything along these lines in a long long time it will probably take me a good while before I can to anything usable [23:12] i used to program in C++ [23:14] one thing you can do is to try out the development release, and help us make some great default settings ... if you want an idea about, what happens this cycle also have a look at https://wiki.kubuntu.org/Kubuntu/Todo [23:14] translation is also something I could see myself doing [23:15] ok, I'll check it out! [23:15] KDE is mostly c++, so that is a good thing to know! [23:15] yes that's convenient =) [23:15] :) [23:16] i've never touched qt though... maybe it would be good to start by learning that.. can you recommend a good tutorial? [23:20] i don't know C++, so no good links in that area, sorry :) [23:20]