[00:58] knome, do you know which email address was used to email distrowatch? [00:59] i seem to recall theone i used before (and used today) might not have worked [00:59] no idea [00:59] * knome has had "too many" [01:01] hehe, i haven't drank any alcohol for over five years [01:01] seems kinda strange considering how much i used to drink [01:01] mmh [01:02] * knome is more drunk than ever [01:02] at least, as far i can remember [01:02] i've definitely been "more drunk" [01:03] scott-upstairs, so did the release-day go well for ubuntu studio ? [01:07] knome, i guess so, i'm still tidying up some stuff and also trying to change the current website to mention the release and new website coming soon [01:07] hehe :) [01:07] that's going to be a battle... [01:08] knome, which part will be a battle, adjusting the current site to mention release and new website? or the new website? [01:08] brb, fixing kids dinner [01:08] adjusting the curent site to mention release ;) [01:13] knome, i'm hoping i can create a new page and then set it to the "home" page [01:14] scott-upstairs, i'm too drunk to handle *drupal*, sorry... :D [01:15] scott-upstairs, wordpress would *barely* go.. [01:16] knome, hehehe, it's okay [01:16] i am getting much better at wordpress though [01:16] i have set up my own server and have begun exploring fairly pervasively [01:16] eyah [01:16] *yeah [01:16] it's much easier on the admin side too, than drupal [01:17] ochosi just praised it :) [01:18] just praised drupal? [01:20] no, wordpress :D [01:20] and its admin interface [01:20] (for xubuntu.org) [01:24] knome, i freely admit that xubuntu is certainly a model of functionality that we wish to emulate :) [01:26] scott-upstairs, well, it's good to hear that - at least we've done something right... [01:33] scott-upstairs, @XubuntuLinux has now 640+ followers, three days ago a bit more than 500 :) [01:33] very cool! [01:33] yeah! [01:34] over 20% increase [01:34] this just reminds me that i need to do a twitter and facebook account for these things [01:34] mmh [01:34] pleia2 registered the twitter account for xubuntu - i'm just tweeting [01:35] pleia2 <3 [01:35] :) [01:46] i wonder how hard it was to register the account on twitter [01:46] this weekend i'm going to register some stuff on facebook and twitter [01:47] i'll probalby have to do soemthing stupid like "TheRealScottLavender" or "ScottLavender2012" [01:55] scott-upstairs, not too much.... :) [01:56] scott-upstairs, rather register UbuntuStudio, that'll (unfortunately) get way more followers [01:56] at least in twitter [01:56] probably true fore fb too [01:56] *for [02:24] okay, i think i'm done for right now on the website [02:24] holstein, http://ubuntustudio.org [02:25] its a step [02:25] scott-upstairs: thanks [02:25] please let me know what people think about this, it's temporary until i get the other website sorted and pushed to rt (which should be before UDS) [02:25] the other is sorted, right? [02:25] i say we push what we got [02:25] holstein or anyone, if you want different wording left me know [02:26] content wise [02:26] just put *somthing* else up [02:26] if i told them "go", it wouldn't happen for a week or so [02:26] so i'm going to use that week to make changes and finish it [02:26] sure.. i guess what im saying is, say go [02:26] hit the button... [02:26] i know [02:27] i also dont think it would be bad to just redirect the URL [02:33] which url? [02:34] ubuntustudio.org [02:34] hop it over to a wiki page or whatever [02:36] i don't even know who has authorization to make the dns redirect it [02:37] ScottL: what you got is good i think [02:37] temporarily [02:37] agreed, it is a temporary step [02:37] im just sad about the timeline [02:37] now that i've cleared most of my tasks (although i still need to do a few things this weekend) i will finish the other website and file the rt ticket before i go to UDS [11:44] yay! ubuntu studio 12.04 LTS release is mentioned on distrowatch :) [11:49] Cool. :) [12:00] i've been documenting things like this (the public relations things) and others, i hope get some things organized in the wiki soon [12:00] kinda like a "playbook" for studio work [12:00] one of my personal goals is to plan for longevity of the project when i am not lead [12:01] and this goes along with that [12:01] i should note that my vision of where ubuntu studio should go will require another 1.59 years, so it is not my intent to leave anytime soon :P [12:08] Ok, expecting to find a new leader a month into the T cycle, then. Got it. [12:11] lol [12:53] scott-work, ever thought of registering a LP group for bugs? [12:54] scott-work, like xubuntu-bugs [12:58] There are no bugs in Ubuntu Studio code. Only well-thought-out features. [13:04] :P [13:04] that's why i'm getting so much mail then, i suppose... [13:04] astraljava, i need to get back to you with an idea later this weekend, remind me if i haven't done that on sunday [13:10] knome: I won't be online much before Tuesday, if then even. And on Wednesday I'm off to Tallinn, where I'm going to be online even less for a little over a week. So consider me gone for two weeks from now on. [13:11] knome: no, i had not considered it, but that sounds like a very good idea, could reduce the email for many, many people [13:12] astraljava, oh well, i can email [13:14] scott-work: Just as long as some people still get them. :) [14:05] astraljava: oh yeah, defintely [14:07] micahg: would it be too presumptuous to start and submit a dev application now? [15:17] scott-work: theres a great example in #ardour right now [15:17] 11:13 < las> pinqvin: it will not be possible to debug this with the Ubuntu-provided version of Ardour [15:17] holstein: example of what? [15:17] 11:14 < las> pinqvin: if you would like help, you should start by getting Ardour 2.8.12 from ardour.org and not from Ubuntu - they have a history of messing up the operation of the program [15:17] scott-work: i had spoken to you about this in the past [15:18] i know las is pretty bitter about our version of ardour, but i don't understand the difference [15:18] the FUD in ardour [15:18] and other places [15:18] i would like to work on that difference [15:18] address it at some point [15:18] if we are breaking it, then id like to stop [15:18] if not, id like for him to stop [15:18] either way, this BS is just that.. BS [15:20] i also wonder if the delta is created in ubuntu....or is it debian? [15:20] scott-work: these are good questions [15:20] im just sick of that [15:20] and quite frankly, i know las is _particular_ and maybe the change greatly upsets him, but in reality is not very critical [15:20] you mention ubuntustudio in that channel and its flames [15:21] and thats one of the best supported apps in FOSS [15:21] to have that negativity in the channel and forums for ardour sux [15:21] i think i'll try to engage him after he helps the guy and talk about what he's saying [15:21] scott-work: ive been planning a PM with him [15:21] i just havent had time.. and im not ready yet :) [15:21] i don't think other applciation authors go into their channels and bash a distro because of the version of libraries used [15:22] but i would like to find a path forward that would work for debian, ubuntu, and las [15:23] totally [15:27] see, las keeps mentioning possibilities [15:28] i might be mainly that he's upset anyone is building it [15:28] i just want him to either help, or STFU [15:28] i have nothing but respect for the guy.. and i think he's awesome, obvioulsy [15:28] but, he leads the buntu flaming in that channel... and im over it [15:29] we need to turn around the thinking [15:29] we are an easy to use, professional OS [15:29] not some repackaged crap that no professional would touch [15:29] and if we are not, i want to move that way [15:31] hehe, i agree [15:33] interesting, las has not responded yet [15:34] yup [15:34] it'll take a while i think [17:58] astraljava: Have you heard anymore about -lowlatency maintenance? [17:58] I was waiting until the release was out before picking it up again [18:06] ailo: there are a few items that are lined out already to be done [18:07] the first would be to figure out where to host the code so that it is accessible to everyone [18:07] i.e. github or similar would probably be good [18:07] but since we need to make lowlatency a "derivative" of the ubuntu kernel i thought getting their input or blessing woudl be helpful as well [18:08] i was hoping to speak to apw or steve conklin or someone with UKT at UDS about this [18:08] sometimes it's easy to get an answer in person ;) [18:10] I think the first thing we should do is to document how TheMuso maintains the source, and start from there [18:10] Hosting the source at github is no problem [18:11] Or, if TheMuso doesn't mind maintaining the source for longer, we need to get ourselves educated on kernel maintenance enough to be able to do everything from scratch ourselves [18:12] My goal would be to make as little changes to the -generic tree as possible [18:12] As simple as possible is the best way to do it [18:14] TheMuso made a short list of commands on how to maintain the source tree, but there was a problem with conflicts last time [18:22] In the long run, we do need to fully document the whole procedure from scratch of course [18:32] scott-work: Why do you think it needs to be in github? Wouldn't LP make more sense? [18:33] +infinity "In the long run, we do need to fully document the whole procedure from scratch of course" [18:34] astraljava: i'm not sure why launchpad isn't used, but i think it might be because the kernel is in git as well [18:34] and i'm sure there are reasons for that [18:34] scott-work: Oh yeah. Well, what about where Luke keeps his tree, then? [18:34] Can it be team-managed? [18:35] astraljava: i don't know where luke keeps his but i've been told only he has access to it [18:35] astraljava: one of the main tenets people keep repeating is that it should be accessible to several people in order to maintain it, so the long answer is yes :) [18:35] scott-work: It's at kernel.ubuntu.com/git [18:36] scott-work: No, I meant can that tree there ^^ be team-managed. Obviously our tree needs to be. [18:37] It seems to host the mainline git trees as well, so I suppose it can. [18:37] astraljava: i haven't a clue about the trees being team-managed [18:38] scott-work: Well basically, every distributed revision control system are, if there are no access control mechanisms in place. The question in this one is, can those be controlled by LP teams? [18:39] astraljava: i don't know, maybe the kernel team might have some insight (since they are on launchpad and using git as well) [18:41] I've been reading about kernel maintenance at https://wiki.ubuntu.com/Kernel/Dev, but most things are pretty scetchy there. I'm going to read this next (particularly about how the source is patched with debian stuff, and the scripts involved) http://kernel-handbook.alioth.debian.org/index.html#contents [18:42] scott-work: Yeah, I was really kinda thinking out loud here. [18:43] scott-work: I'm going to be very scarcely online for the next two weeks. If you have something important, you know my email addresses. Please use them as primary method of getting in touch. [18:43] scott-work: The whole procedure is just a few commands, but knowing which, and why is a different matter [18:46] ailo: i was hoping to get a brain dump from themuso and alessio once we get the git hosting and other things established [18:46] astraljava: ack'd [19:18] scott-work: I've been using gitorious and I also have a github account, so I know how to use those, as well as having about a years experience with git [19:19] So, I could set up the whole thing at github [19:20] scott-work: Do you have a github account? [19:20] ailo: before we go headlong into this can we first ask someone with UKT if we use github would it prove problematic when setting up lowlatency as a derivative (something to do with their processes and automating udpating) of the main ubuntu kernel [19:20] ? [19:20] ailo: no, not yet [19:20] ailo: Please hold off though until we figure out the access control issue. [19:21] Heh, yeah. [19:21] That, too. [19:23] scott-work: I believe the only thing we need to worry about is making sure the source is ok, and that whoever is doing the uploading can pull from our git tree. [19:23] Who was it that suggested github anyway? [19:24] alessio was keeping his source along with all the other ubuntu kernel sources [19:24] As is TheMuso right now [19:29] By uploading I of course meant whoever uploads the source to the Ubuntu repo, which we cannot do [19:29] The package repo, that is [19:36] Well, I'll try to create my own -lowlatency from scratch for educational purposes and see how that compares to the existing one. But now, bedtime.. [19:49] ailo: i don't really remember who suggested github [19:50] good night ai.lo, sorry about pinging you right then :P [19:50] * scott-work didn't read all backscroll before replying [20:53] I hate my nvidia card. 1000s of lines of :Apr 27 08:28:30 music1204 kernel: [226939.249488] [drm] nouveau 0000:01:00.0: validate vram_list [20:53] Apr 27 08:28:30 music1204 kernel: [226939.249495] [drm] nouveau 0000:01:00.0: validate: -12 [20:53] Apr 27 08:28:30 music1204 kernel: [226939.249573] [drm] nouveau 0000:01:00.0: fail ttm_validate [20:54] Over and over. [20:54] I would guess (by the time) one of the kids was playing a web video game. [20:59] Nope, maybe not... [22:07] Screen saver trouble.