=== LoganG is now known as LoganG|off [13:27] zequence, hello:) [13:28] smartboyhw: hi [13:30] OvenWerk1: I'd rather work on replacing qjackctl with a new tool [13:30] i.e. -controls [13:30] zequence: what would you use to make jack conections? [13:31] zequence, OK, I'm starting to feel dizzy as to what we are planning for 14.04 LTS now-.- [13:31] smartboyhw: new artwork. [13:32] OvenWerk1: patchage, or a modded version of it, as falktx uses [13:32] OvenWerk1, well, that's not just it, right?! [13:32] smartboyhw: no [13:32] I have had patchage crash on me too many times. [13:33] smartboyhw: sorry, I was joking, art is the one thing we have talked about.. [13:34] OvenWerk1, lol. I do think we need to start planning for 14.04 now (don't know if you guys like it), but we seem to have quite a lot of things planned and I can't remember all of them-.- [13:34] ardour3. Sync the CAPs plugins would be nice. [13:34] We do planning when this cycle is done [13:35] though, 14.04 has already been mapped out quite well in planning already [13:35] one just needs to read through it [13:36] FF is past, we could look more at 14.04. Only artwork left for this cycle. [13:36] Yeah, and it's madeinkobaia's job:P [13:37] in time [13:37] * OvenWerk1 has done the stuff he wanted for this cycle [13:37] yes, and that was very good of you [13:37] OvenWerk1, congratulations [13:37] * smartboyhw didn't do anything this cycle basically;P [13:37] Fortunately, I got goals for 14.04 [13:38] If not I will be a noob here;P [13:38] We need to have a meeting at some point [13:38] at least one meeting before we start working on the next cycle [13:38] * smartboyhw agrees [13:38] It looks like some of the broken things for xfce will get fixed. [13:39] arandr can go, I think. [13:40] If someone wants, they could put some time on thinking about how we do beta testing [13:41] we should make sure no application is suffering from bad packaging, etc [13:41] * smartboyhw should (by his role) [13:41] and just generally try to catch bugs [13:41] kdenlive seems to work. [13:41] jack works, ardour does. [13:42] Did you check full functionality, or just make sure the applications start? [13:42] the audio applet doesn't [13:42] well, there's one problem then - but I suppose Xubuntu is on it? [13:42] as it's shared by both.. [13:42] kdenlive I made/edited a video. [13:42] OvenWerk1, we have quality control in KDE here;P [13:42] I don't think it's helpful citing which apps works on this channel [13:42] xubuntu has a fix... if they can get it out [13:42] there's bugs for testing applications. and we need to write test cases [13:43] ok, so then it's not a problem [13:45] I don't know where to go with blender though. How to test functionality. [13:45] OvenWerk1, well, it's just a matter of how a normal user uses it [13:45] As long as we know how they use it, we test it by doing the exact same [13:45] * OvenWerk1 is trying to say there are a number of apps thet require some knowlage of the craft. [13:46] The one who writes the test case needs to know the application [13:46] and the idea is we involve our users in this [13:46] zequence, yes we are supposed to [13:46] good [13:47] The one thing I did notice with kdenlive is the docs don't work. [13:48] It seems the required kde infrastructure is not installed/running [13:49] Also, there are now 4 BG processes running for KDE that are no longer in use. [13:49] sounds like a packaging problem [13:49] OvenWerk1, huh? [13:49] OvenWerk1, how? [13:51] kdeinit4 klauncher kded4 /usr/bin/knotify4 were started by kdenlive, but of course kdenlive expects them to remain running so it doesn't kill them. [13:52] This is part of the problem with any kde app. [13:55] * OvenWerk1 kills these things and starts krita [14:09] krita starts more kde BG stuff... and it is not the same ones, so after running both krita and kdenlive we would have 6 spare things running around. However the doc book in krita is a web page. [14:11] What did I miss?! [14:12] 06:50 < OvenWerk1> kdeinit4 klauncher kded4 /usr/bin/knotify4 were started by kdenlive, but of course kdenlive expects them to remain running so it doesn't kill them. [14:12] 06:50 < OvenWerk1> This is part of the problem with any kde app. [14:12] 06:54 * OvenWerk1 kills these things and starts krita [14:12] krita starts more kde BG stuff... and it is not the same ones, so after running both krita and kdenlive we would have 6 spare things running around. However the doc book in krita is a web page. [14:13] * smartboyhw recommends OvenWerk1 to use the IRC logs syntax selection of paste.ubuntu.com next time:) [14:15] They don't seem to be actively using cpu, but they are using 115M of RAM [14:25] khelpcenter is quite small, we could include it.... but then I got a not found page... [14:26] OvenWerk1, :O [14:31] There is not a kdenlive doc package, but there are online docs. [14:36] The kdenlive-data package (which we ship) does seem to have the offline docs there. The help center just doesn't seem to know about it. [15:17] Hmm, the extra installer for each workflow should include the ubuntustudio meta for that workflow. [15:18] That would be less confusing for someone who added the menu to another DE [15:31] GA! found the problem with the kdenlive docbook... which doesn't work in a kubuntu session either.