[01:01] <ailo_> ScottL, ping
[01:07] <ScottL> ailo_, pong
[01:14] <ailo_> Hi ScottL. Did you read the devel list? Seems like there's someone offering help. Got me thinking. Was going through the wiki pages, trying to find pages dedicated to development.
[01:14] <holstein> http://holstein.shacknet.nu:8227/stream.ogg
[01:15] <ailo_> holstein, alrite. Our favorite jazz radio station.
[01:17] <ailo_> ScottL: Some things have been worked on more than others, like discussing the -controls. But there seems to be a central place missing, where you can see what is being done, what needs to be done, and what is not being done. That sort of thing.
[01:18] <ailo_> ScottL: The new guy is asking for directions, and it would be really easy just to point him to some pages and then discuss what exactly he would like to do, and what needs to be done
[01:18] <ScottL> ailo_, sorry, haven't read much mail today, been working heavily on backporting to lucid
[01:19] <ScottL> ailo_, yeah, that's similar to what holstein suggested, just a nice dev page that links to things going on and where help might be needed
[01:19] <ScottL> just so people can see:  https://launchpad.net/~slavender/+archive/backports-testing/+packages
[01:20] <ailo_> ScottL: How does ther backporting work? You can do that anytime? I saw a wiki about that. I could help out.
[01:20] <ScottL> ailo_, wow, that guy's email sig is fookin' wicked cool :)
[01:21] <ScottL> ailo_,  oh yeah, i'll need people to help test these packages
[01:21] <ScottL> i'm hoping you, holstein, and maybe rlameiro can do help test (i'll test it as well)
[01:21] <ScottL> but my thinking is that the three of you should probably divide up the testing to make it go faster
[01:22] <ailo_> ScottL: How many packages do you have left? When you think you'll be done?
[01:22] <ScottL> once we have two people with success tests who comment in the bug report then i'll post a debdiff and it should be pushed pretty quickly
[01:22] <ScottL> i spoke with ScottK about this yesterday and we knocked out the plan in short order
[01:22] <ScottL> ailo_, re: packages and time - hold on, let me find the link
[01:23] <ScottL> by the way, this is an interesting video about hard real-time and soft real-time
[01:23] <ScottL> http://vimeo.com/6081746
[01:23] <ScottL> ailo_, here's the backports wiki: https://wiki.ubuntu.com/UbuntuStudio/Backports
[01:23] <ScottL> i've been updating it as i get something built or report a bug
[01:24] <ScottL> ailo_,  you could start with the backports from natty if you are interested, that would make a nice division of labor
[01:25] <ailo_> ScottL, Alrite. Nice work. I'll have a look.
[01:25] <ScottL> the idea is that i would _like_ to backport from natty if natty offers a later version of a package
[01:25] <ScottL> but sometimes they depend on a later version of some other package :(
[01:26] <ScottL> and ailo_ , i really recommend test building in a pbuilder environment because it will tell you if it can't satisfy a dependecy in lucid without having to wait for a ppa to build or cluttering up a ppa with a bunch of packages that won't build
[01:27] <ailo_> ScottL, So, the list of backports to Maverick is only started?
[01:27] <ScottL> btw, i'll respond to that email tomorrow morning while i do some other emails
[01:28] <ailo_> ScottL. From: Natty, that is
[01:28] <ScottL> ailo_, these are backports to lucid...from either maverick or natty
[01:28] <ScottL> i only tried to backport qtractor for the natty ones
[01:29] <ScottL> it was because i already had qtractor source code on my machine
[01:30] <ScottL> i am hoping to be done with the maverick backports tomorrow morning, then i get back onto the -lowlatency kernel again
[01:30] <ScottL> that's about 17 hours hence
[01:31] <ailo_> ScottL, Ok. I'll have a look at the Natty packages. It'll probably take a little more time for me to start with.
[01:32] <ScottL> ailo_, the top of the page has this link: https://wiki.ubuntu.com/UbuntuStudio/BackportsHowToHelp
[01:33] <ScottL> it's pretty much a step-by-step guide to do this using qjackctl as an example
[01:33] <ScottL> has lots of good packaging basics in it
[01:33] <ailo_> ScottL, Yep. Thanks. I think I've got all the wiki pages in my bookmarks now, though I may miss new ones, if they are made.
[01:34] <ailo_> I mean newly made pages, I might miss
[01:34] <ailo_> holstein is soloing away :P
[01:55] <ailo_> ScottL, Interesting video, about the -rt stuff!
[01:56] <ScottL> i haven't listened to it all yet, been focusing on the backporting
[01:56] <ScottL> ailo_, i think after natty one of the things i would like to focus on is the documentation, but probably primarily from a user perspective
[01:57] <ScottL> meaning getting work flows fleshed out more and documentation that will help users
[01:57] <ScottL> eh, patchage just took a big dump on me
[01:58] <ScottL> i had been avoiding installing every library and dependency under the sun until i got to patchage
[01:58] <ScottL> that's the nice thing about using pbuilder - it creates a chroot environment that has minimal packages and then when you attempt to build something
[01:59] <ScottL> in it then it realizes what is missing and install those in the pbuilder environment
[01:59] <ScottL> and since this is all temporary, when it's done it just drops everything and your basic system is unmolested
[01:59] <ailo_> ScottL: I think both for users and developers would be a good things. User documentation shouldn't be too hard to work out. There are tons of detailed manuals for most programs, so an Ubuntustudio specific documentation doesn't need to be that extensive. The Ubuntustudio doc on work flows should include most things and explain simply, is what I think.
[02:03] <ScottL> ailo_, that's true....and if we managed to simplify and make our developer documentation more effective then we could probably get more dev help
[02:03] <ailo_> ScottL, I will focus on documentation too, once other things are out of the way. Right now, I'm working a lot on my own stuff as well.
[02:04] <ailo_> ScottL, Pehaps while waiting for the release of Natty +1 alpha 1, I'll have time to work on that type of thing.
[02:05] <ailo_> ScottL, Are you getting a sense of what things are best done in what periods before a release? Perhaps a simple schedule could be made, when it makes most sense to focus on different things?
[02:06] <ailo_> +explaining when*
[02:08] <ailo_> It would be easier to ask for help once things like that are already mapped out. I think many people will have periods of time, when they have a lot of time to help.
[02:09]  * ailo_ is getting some coffee..
[02:36] <ScottL> ailo_, actually, i have been thinking about scheduling
[02:36] <ScottL> mainly because we always seem to be behind the curve LOL
[02:37] <ScottL> ailo_, i don't know if you can see this or not:  https://spreadsheets.google.com/ccc?key=0AkE-Lxi30H8wdGNCTF9fODltNjVOT2dPbm44V3ZLZEE&hl=en&pli=1#gid=0
[02:37] <ScottL> i wanted this just as a reminder to think about things before they're actually needed
[02:37] <ScottL> i also had been thinking about a 'ubuntu studio' google calendar that rlameiro had set up...that would be really nifty to set things up with a reminder
[02:37] <ScottL> and those that want can subscribe
[02:41] <ailo_> ScottL, Sounds like all good ideas to me. Maybe a release schedule, paralell to Ubuntu's would be good too. We should have some deadlines, followed by reviewing and testing for some things.
[02:44] <ScottL> ailo_, that was the general idea between the google calendar and my spreadsheet...just a reminder before something is due
[02:46] <ScottL> ailo_, also, i've started trying to build some of the backports from natty in pbuilder as is (right after apt-get source <package>) just to see if they build in lucid
[02:46] <ScottL> i dont' think many will :(
[02:46] <ScottL> BUT i'm recording what packages are missing for each package that fails to build
[02:47] <ScottL> and i might try to get some of the missing packages backported so we can backport more of our audio packages
[03:09] <ailo_> I think the most important thing for next release is to get the -lowlatency in. I just think that's the most fundamental part for the audio part. ScottL How about starting a duc wiki page on that?
[03:09] <ailo_> doc*
[03:11] <ailo_> Since I have been working on the controls, and even though I have limited experience on software development, I still think I could take charge of laying out some sort of a project planning page on that.
[03:33] <ScottL> ailo_,  here's what i've been working on for release planning: https://wiki.ubuntu.com/UbuntuStudio/ReleasePlanning
[03:33] <ScottL> doesn't mean that's the way it should be though
[03:34] <ailo_> ScottL, I already forgot about that page :P. 
[03:35] <ScottL> lol
[03:36] <ScottL> ailo_, i've already gone through the natty backports, this way i can move back into the maverick stuff now that i know the natty package versions won't work
[03:43] <ScottL> hi raony_  :)
[03:46] <raony_> hey scottl :)
[03:46] <raony_> what's up ?
[03:47] <raony_> I'm reading the release plan and the bugs at launchpad ... 
[03:49] <raony_> I'm still a bit lost about how to set up a station to actually be able to help ! 
[03:50] <raony_> it's better if i set up a virtualbox with the natty version of studio ? 
[04:00] <ScottL> doh, he's gone already :(
[04:15] <ailo_> raony_, https://wiki.ubuntu.com/UbuntuStudio/ReleasePlanning
[04:15] <raony_> I'm reading
[04:16] <ailo_> raony_, As for software projects, there's the ubuntustudio-controls, which needs some attention.
[04:17] <ailo_> raony_, I've been working on a new version on the ubuntustudio-controls, but what I have done doesn't need to end up in the next release
[04:17] <raony_> what are your changes at this control ?
[04:19] <ailo_> raony_, I've made a new one almost from scratch, since some features have become outdated. Also, there have been some big plans for improving it, but I only got it to do some basic things. Add user to audio group, adjust memlock value and install restricted extras.
[04:23] <ailo_> raony_, It's not packaged yet. For the next release it would be good be more organized with the development of that app. paultag has been helping me with this project.
[04:25] <ailo_> raony_, You don't happen to know much about kernels, by any chance?
[04:25] <raony_> not really :/ 
[04:26] <raony_> but I'm here to learn :) just need that you guys point me the directions 
[04:26] <raony_> what language you guys mainly use ? for example on the studio-controls ?
[04:27] <ailo_> raony_, It's been a python gtk project, though my version also uses shell scripts :/
[04:28] <raony_> well, I know python and shell script :)
[04:28] <raony_> never worked with gtk, but it's time learn !
[04:32] <ailo_> raony_, Here's the source for my version git clone git://gitorious.org/ubuntustudio-controls/ubuntustudio-controls.git ubuntustudio-controls
[04:33] <ailo_> raony_, You'll need to use it on Natty
[04:33] <raony_> how is the natty version of studio ?
[04:34] <ailo_> raony_, And if you decide to try it out, you'll notice from the source that shell scripts should be in /usr/lib/ubuntustudio-controls/ and the audio.conf file should be in /usr/share/ubuntustudio-controls/
[04:34] <raony_> are you using it inside a virtualbox or really installed in your pc ?
[04:34] <ailo_> raony_, I've installed it. It's pretty ok now. I installed ubuntu vanilla, though and added packages onto that.
[04:35] <ailo_> Installed on my machine, that is
[04:35] <raony_> all right, tomorrow I'm installing here and checking your code
[04:36] <ailo_> raony_, See you in tomorrows meeting?
[04:36] <raony_> for sure !
[14:55] <holstein> ailo__: hello :)
[14:55] <holstein> ScottL: morning
[14:56] <ailo__> Afternoon, holstein
[14:56] <raony__> 12:00 here ... :D
[14:57] <holstein> i see a lot of activity in the scroll from last nite
[14:57] <holstein> i'll have to read that
[14:57] <holstein> raony__: o/
[14:58] <raony__> I got the studio natty alpha-3 and I'm planning to install after this meeting
[14:58] <ScottL> morning holstein 
[14:58] <holstein> i was just checking the mail to see if that was you raony__ 
[14:58] <ScottL> hi raony__ and ailo__ 
[14:58] <holstein> welcom
[14:58] <holstein> e
[14:59] <ScottL> holstein, are you up to finishing the menu update today?
[14:59] <holstein> ScottL: im off this afternoon
[14:59] <holstein> so, i should be able to try
[14:59] <holstein> natty is all updated
[15:00] <holstein> and ready to rock
[15:00] <holstein> ScottL: did you see the mail from erik?
[15:00] <holstein> about the site?
[15:00] <holstein> and not being able to make the meeting?
[15:01] <raony__> I read that, and I believe I can help him since I've been working more with webdevelopment nowadays :)
[15:01] <raony__> what you guys think ?
[15:02] <holstein> raony__: cool, we'll let ScottL know
[15:02] <holstein> and get you guys in touch with each other
[15:02] <Narwhal_Gym_Sock> Hello, all.
[15:02] <holstein> Narwhal_Gym_Sock: hey :)
[15:02] <holstein> paultag: you around?
[15:02] <Narwhal_Gym_Sock> I've been working on the web site as well on the dev list.  My name is Brian.
[15:03] <raony__> Hello Brian!
[15:03] <Narwhal_Gym_Sock> I didn't catch that last conversation, what's been discussed?
[15:03] <holstein> Narwhal_Gym_Sock: nothing yet
[15:03] <holstein> you're just in time :)
[15:03] <holstein> raony__ was offering assistance with the site
[15:03] <Narwhal_Gym_Sock> Excellent!
[15:04] <holstein> Narwhal_Gym_Sock: are you in the position to give a run down?
[15:04] <holstein> on what is going on?
[15:04] <holstein> site-wise
[15:04] <Narwhal_Gym_Sock> Yes, I can do that.
[15:05] <Narwhal_Gym_Sock> I've been working on the Impact theme.  You can see the original discussion for that here:
[15:05] <Narwhal_Gym_Sock> https://wiki.ubuntu.com/UbuntuStudio/TaskWebRevamp
[15:06] <Narwhal_Gym_Sock> The first 'alpha' (so to speak) of the theme is done.  I really just need people to test it.
[15:06] <holstein> COOL
[15:06] <raony__> are you using wordpress for that?
[15:06] <Narwhal_Gym_Sock> It is being done in Drupal. 
[15:07] <Narwhal_Gym_Sock> I believe that is mandated by Canonical, although it's fine by me, as I like Drupla.
[15:07] <holstein> Narwhal_Gym_Sock: feel free to link us up in here for testing
[15:07] <holstein> yeah, drupal is nice
[15:07] <holstein> as long as the folk working on it are cool with it
[15:07] <holstein> Narwhal_Gym_Sock: to test, do you need a host?
[15:07] <raony__> indeed ... I prefer drupal :)
[15:08] <Narwhal_Gym_Sock> I'll need to upload the files to my server, then I'll link.  I'll have that done in a few minutes here.  I don't have a dev site running, I just use a local server on my machine (using XAMPP).
[15:08] <holstein> OK
[15:08] <Narwhal_Gym_Sock> So, those testing will need to be doing that, as well.
[15:08] <holstein> i can do that locally here
[15:09] <holstein> i would probably get one of the drupal turnkey linux appliance iso's
[15:09] <holstein> and run it in virtual box
[15:09] <holstein> something easy :)
[15:10] <Narwhal_Gym_Sock> Okay, so I'll get those files ready. They will include just the theme directories, a database for those who care to see the set-up I've been using, and a readme file with some release notes.
[15:10] <holstein> raboof: hey
[15:10] <holstein> https://wiki.ubuntu.com/UbuntuStudio/TaskWebRevamp
[15:10] <holstein> raboof: we were just looking at the site
[15:11] <raboof> hi ;) just curious ;)
[15:11] <holstein> and talking about testing with Narwhal_Gym_Sock 
[15:11] <holstein> Narwhal_Gym_Sock: who is the web-team?
[15:11] <holstein> is that pretty much just you and erik right now?
[15:11] <Narwhal_Gym_Sock> Right now it is very bare bones, because I still have no idea what the plan is for the back end.  The theme will work out of the box, though.
[15:11] <Narwhal_Gym_Sock> Yeah, me and Eric and Scott.
[15:12] <holstein> cool
[15:12] <holstein> well, make sure you get raony__ 's info
[15:12] <holstein> if you need extra hands in there
[15:12] <Narwhal_Gym_Sock> I will do that.  And, naturally, we'll take as many helping hands as possible.
[15:13] <holstein> Narwhal_Gym_Sock: and like i said in the email
[15:13] <holstein> i think you guys should feel free to have a seperate meeting
[15:13] <holstein> whenever
[15:13] <holstein> IF needed
[15:13] <holstein> its challenging to find a time that works for everyone
[15:13] <raony__> when this website is supposed to be online ?
[15:14] <holstein> but, i think keeping a regular time will help with attendance
[15:14] <holstein> raony__: good question
[15:14] <raboof> i'd definitely go for shiny or comic rather than punk
[15:14] <Narwhal_Gym_Sock> Right now, it's a 'whenever it gets done' type of thing (like a lot of Linux stuff)
[15:14] <holstein> Narwhal_Gym_Sock: loosely for natty though right?
[15:14] <holstein> or shortly there-after
[15:14] <Narwhal_Gym_Sock> holstein: Natty would be the preference.  At least on my part.
[15:15] <holstein> Narwhal_Gym_Sock: is that realistic?
[15:15] <Narwhal_Gym_Sock> raboof: We'll be using the "Impact" theme for the site.  Although I'm going to try to develop some desktop artwork using the comic style.
[15:15] <raboof> i don't know it, but what i se on the wiki looks good
[15:16] <Narwhal_Gym_Sock> holstein: Not sure.  The theme could definitely be done by them.  As for the rest of it, well, I'm not sure.
[15:16] <holstein> well, i agree, its looking slick
[15:16] <holstein> ScottL: when you get a minute, pop over here, and talk about backporting
[15:17] <Narwhal_Gym_Sock> The whole process as to how we want to organize the content of the site, and then how we get it all uploaded to the server and set up, is still a mystery to me.
[15:17] <holstein> maybe we can get a little unofficial backporting team started
[15:17] <ailo__> Narwhal_Gym_Sock, I see there are some additions intended for the site, like a tutorial section, feature overview. How much of that is done?
[15:17]  * ScottL is catching up on backscroll
[15:17] <ScottL> holstein, i just now read eric's email
[15:17] <ailo__> Narwhal_Gym_Sock, Or maybe it's just easier we try it out
[15:18] <ScottL> Narwhal_Gym_Sock, i'm going to update the list of pages needed for the website for the immediate needs via email shortly
[15:18] <raboof> i'd say put as little content on the site as possible, and litter it with links to the wiki(s)
[15:19] <holstein> ^^ i like that too
[15:19] <raboof> (but don't take me too seriously, i don't even use ubuntu atm :) )
[15:19] <holstein> link to the buntu stuff thats already in place
[15:19] <holstein> ailo__: you want to tell us about the controls thingy?
[15:19] <holstein> that you and paultag are working on?
[15:20] <ailo__> I think we need to organize the wiki, work on documentation for both users and developers. But, I wouldn't mind a feature overview on the main site, with pictures.
[15:20] <holstein> most teams have a wiki team
[15:20] <holstein> maybe we should entertain that for the future
[15:21] <holstein> some folks that keep the studio wiki's clean and up to date
[15:24] <raony__> holstein: I will also try to help ailo with the studio-controls 
[15:24] <raony__> he already sent me his code
[15:24] <ailo__> Well, to answer holstein, I've been working on a new version of the ubuntustudio-controls with some help from paultag. It's very simple. Makes it easier for new users to make sure they have realtime privilege. Here's a picture of it http://imagebin.org/141459
[15:25] <holstein> raony__: cool, i just read a little of the exchange you guys had :)
[15:25] <holstein> ailo__: do you need testers yet?
[15:26] <ScottL> so, i'm working on the backports for lucid:  https://wiki.ubuntu.com/UbuntuStudio/Backports
[15:26] <ScottL> there's a list of what i considered and how that played out with trying to backportr
[15:26] <ScottL> sometimes new versions use updated version of other packages that aren't in luid
[15:26] <ailo__> I'm not suggesting we use the code for future releases, though. paultag had an idea of making it pluginable. Also, I guess accessing realtime will change sooner or later too. There have been a lot of ideas on what to add to the controls, so it could be reallly be expanded.
[15:27] <holstein> https://wiki.ubuntu.com/UbuntuStudio/BackportsHowToHelp
[15:27] <ScottL> so say ardour from either maverick or lucid can't be backported to lucid because it requires a later version of a build package than is in lucid
[15:27] <ScottL> but there are still quite a few packages to backport
[15:27] <ScottL> i've build pretty much all of them and will need people to start testing them
[15:27] <holstein> ScottL: and that would be https://launchpad.net/~slavender/+archive/backports-testing/+packages
[15:27] <ScottL> the general plan is that i committed to building them and providing a test as well
[15:27] <ScottL> aye holstein 
[15:28] <holstein> cool
[15:28] <holstein> ScottL: so, in lucid, add that PPA
[15:28] <ScottL> then we just need one additional tester to test the package and report on the associated bug report
[15:28] <holstein> and upgrade/test
[15:28] <ailo__> I can help with testing those
[15:28] <ScottL> once we have two testers on record in the bug report the backports team should move pretty quickly to push it into the official backports release
[15:29] <ScottL> i also hope to work on the -lowlatency kernel from instructions that abogani has given me
[15:29] <ScottL> i feel pretty confident that i should get them built today (time permitting of course)
[15:30] <holstein> ScottL: and the plan is to have that in natty?
[15:30] <holstein> as an option?
[15:30] <ScottL> holstein, good question :/
[15:30] <ScottL> persia had wanted to push it into the repos about a month ago (i guess) but it may be too late in the cycle, i'll have to see what his intentions are now
[15:31] <holstein> yeah, we need that kernel 
[15:31] <ailo__> Considering how similar the -lowlatency is to the generic kernel, it would make sense to let it in even after feature freeze.
[15:31] <Narwhal_Gym_Sock> Sorry, everyone, my Internet just crapped out.
[15:31] <ScottL> i need to get off my arse about establishing an official Ubuntu Studio PPA so we can dump the -lowlatency kernel (if not in repo) and also an -rt kernel
[15:32] <holstein> ScottL: that would be a PPA we could add 'out of the box' ?
[15:32] <ScottL> ailo__, i got the impression that persia was just going to do it...sounded almost cavalier :P
[15:32] <holstein> ship with?
[15:32] <ailo__> ScottL, It would be great if he did :P
[15:32] <ScottL> holstein, if we updated a package to add the source line to sources.list, then yes
[15:32] <holstein> thats totally fine
[15:32] <holstein> either way then
[15:34] <ailo__> So, Narwhal_Gym_Sock, about the site. How can we test it? We download some files from you and try the site out locally?
[15:34] <ScottL> by the way, if people want to start testing the backports they can
[15:34] <ScottL> https://launchpad.net/~slavender/+archive/backports-testing/+packages
[15:35] <holstein> ScottL: these get backported to lucid or maverick?
[15:35] <holstein> or whatever?
[15:35] <holstein> do they need to be tested in both?
[15:35] <Narwhal_Gym_Sock> ailo: That is correct.  I'm getting those files ready to upload to my website as we speak, and then I'll send a link to everyone.
[15:36] <Narwhal_Gym_Sock> Anyone wanting to test will need to use XAMPP (or something similar).
[15:36] <raony__> why ?
[15:37] <ailo__> Narwhal_Gym_Sock, php and mysql?
[15:38] <Narwhal_Gym_Sock> ailo: Yes.  You will basically need to do a Drupal install yourself on your own local server, and then drop in my theme files and, optionally, upload the database I've been using.
[15:38] <ScottL> holstein, they get backported to lucid...most are coming from maverick and one from natty
[15:39] <ScottL> so just test in lucid
[15:39] <holstein> ScottL: i see
[15:39] <Narwhal_Gym_Sock> ail0: That last part is only necessary if you want to see the basic set-up I've been using.  Otherwise, the theme will work out of the box and you can set up your test site as you'd like.
[15:43] <ailo__> I have a local server running Apache and postgres. Drupal is new to me, so I'll have to see if I can get it all to work.
[15:45] <raony__> I want to ask something, I downloaded studio alpha-3 here to install here, but I tough about trying to upgrade from maverick first, how is that working right now ? I believe is better if I install from zero, am I right ?
[15:46] <holstein> also, http://www.turnkeylinux.org/drupal6
[15:46] <holstein> thats how i probably will do it
[15:46] <Narwhal_Gym_Sock> ailo: I'm not sure, but I believe Drupal needs to use MySQL.  Otherwise, it's really easy to install.
[15:46] <holstein> raony__: fresh install is usually faster
[15:46] <holstein> and preffered
[15:46] <Narwhal_Gym_Sock> Yes, I fresh install will save you many problems.
[15:47] <holstein> IF i were upgrading to natty, i would want to wait til at least beta too
[15:47] <raony__> ok, and what kernel it comes with ? -lowlatency or -rt ?
[15:47] <holstein> just incase
[15:47] <holstein> raony__: -generic
[15:47] <holstein> try it though
[15:47] <raony__> thanks
[15:47] <holstein> i have found that the -lowlatency is working quite well in natty
[15:47] <holstein> with my firewire device
[15:48] <ailo__> The -lowlatency kicks ass.
[15:48] <holstein> yeah ^^
[15:48] <holstein> most folk dont need either though
[15:48] <holstein> but, we need to have -lowlatency i think
[16:04] <holstein> well, i think we all kinda faded out 
[16:04] <holstein> but, we got some things done
[16:04] <holstein> discussion mostly, and thats good
[16:05] <holstein> i'll try and paste our meeting in an email here in a bit
[16:05] <holstein> thanks all, ScottL raony__ Narwhal_Gym_Sock raboof ailo__ :)
[16:05] <ailo__> On making things easier for new user: I started working on a script a couple of months ago, that runs at startup to see if the system is tuned or not. Also, I would want to put the -controls in the notification area, where the user can easily find it. Have a button for help there. Let it be pluginable as paultag suggested.
[16:05] <holstein> and any idlers i missed
[16:06] <raboof> ;)
[16:06] <raony__> that's a good idea holstein.
[16:06] <raony__> the natty studio will be release together with the other releases April 28th ?
[16:06] <Narwhal_Gym_Sock> Thanks, everyone, I'll send a link to the site testing files to the list in a few minutes.
[16:07] <ailo__> Next meeting, a month from now?
[16:07] <holstein> ailo__: yup
[16:07] <holstein> first sunday of the month :)
[16:08] <raony__> all right!
[16:08] <ailo__> Sounds almost holy :)
[16:08] <raony__> I'm moving to natty, see you guys !
[16:21] <ScottL> i've done all the building for backporting i'm going to do at the moment, although there are a few notable exceptions in the wiki:
[16:22] <ScottL> alsa-tools: i'd like to research it more to see if this will affect other packages possibly and cause breakage
[16:22] <ScottL> gcdmaster: there already was a backports bug report for this, although i don't know if it will move without us doing something
[16:22] <ScottL> patchage: i need to research this also, nedko kinda makes things build weird and i think i may need to install a lot of packages
[16:23] <ScottL> rakarrack: saving this for holstein to build :)
[16:29] <Narwhal_Gym_Sock> Hey, everyone, here is a link to the website files for those who would like to do testing:
[16:29] <Narwhal_Gym_Sock> http://www.sunmachine.coop/ubuntu/impact_2011-02-26.tar.gz
[16:29] <Narwhal_Gym_Sock> I will send this to the list as well.
[17:32] <ScottL> holstein, do you need any further help with the menu update?
[17:33] <holstein> ScottL: yeah :)
[17:33] <ScottL> which point are you at currently?
[17:35] <ScottL> holstein,  where are you at now?
[17:35] <holstein> same as before
[17:36] <holstein> let me get some things sorted
[17:36] <holstein> and i'll PM you
[17:38] <ScottL> righty-o
[18:44] <ailo__> ScottL, I'll help testing the backports tomorrow. What's the deal then? What kind of comments? If the package is working, we just say it's working?
[18:44] <ailo__> on the bug reports
[18:53] <ScottL> ailo__,  aaaahhhh, i'm not sure exactly on the wording but I think just a note saying that you tested it and it worked
[18:54] <ailo__> ScottL, And then once three of us have confirmed, the packages are fit for baclporting?
[18:55] <ailo__> Was just installing drupal. If I get it going I'll try and share it with you guys. Don't have a lot of bandwidth, though...
[18:56] <ScottL> ailo__, only two confirmed are necessary (actually ScottK said only one was really necessary but normally it's two)
[18:56] <ScottL> and i'm going to test each as well
[18:56] <ScottL> i think if you follow some of the links on this page you will find examples of what worked to get previous backport bugs closed: https://bugs.launchpad.net/lucid-backports/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&fie
[18:56] <ScottL> ld.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
[18:57] <ScottL> ew
[18:58] <ailo__> ScottL, but the links to the bugs are all in https://wiki.ubuntu.com/UbuntuStudio/Backports, right?
[18:58] <ScottL> try this page instead:  https://bugs.launchpad.net/lucid-backports/+bugs?advanced=1
[18:58] <ScottL> under status make sure only "fixed released" is checked
[18:58] <ScottL> ailo__, yes, all links are on that page
[19:30] <ScottL> ailo__, i don't know if you had seen this already:  https://wiki.ubuntu.com/ScottLavender/scratchpad
[19:30] <ScottL> those are my notes from aboganni to build the -lowlatency kernel from his git tree
[19:30] <ScottL> i just ran through it really quick like and without any apparent problems and uploaded my changes to my ppa
[19:31] <ScottL> after it builds (hopefully correctly) i'll feel  100% good about it then
[19:33] <ailo__> ScottL, Nice, How about creating the source tree from scratch (using the Ubuntu kernel source)?
[19:36] <ailo__> The way it seems to be set up is using a sort of -lowlatency patch on top of the -generic, thought the patch is really only changing a few configs from what I can tell. I guess that belongs to what is still a mystical area, namely debian packaging
[19:37] <ailo__> Mystical to me* :)
[19:39] <ailo__> For a short term I think it will be enough just to hang on to those configs, but in the long term, someone will have to follow up on kernel feature updates.
[19:48] <ScottL> ailo__, lol, it tired to build the kernel before it had built the meta so i was missing the source
[19:49] <ScottL> i'll try to force the kernel to build again
[20:50] <holstein> ScottL: did you see my cop-out-ish PM?
[20:50] <holstein> im heading out the door
[20:50] <holstein> i
[20:50] <holstein> 'll
[20:50] <holstein> try and catch up with you later
[20:50] <holstein> and see if i can carve out some time
[20:50] <holstein> good meeting though i thought
[20:51] <ScottL> holstein, oh, lol, actually i didn't till now
[20:51] <ScottL> i can take of it all
[23:32] <ScottL> doh!  my kernel build needs linux-source-2.6.38-5.32 and can't find it :(
[23:38] <ailo__> ScottL, Don't you have the entire source from aboganis git repo?
[23:46] <ScottL> ailo__, i don't know
[23:46] <ScottL> ailo_, ^
[23:46] <ScottL> i thought it would have come with the -meta
[23:46] <ScottL> but i'm pretty ignorant about a lot of these things
[23:47] <ailo_> The -meta should not hold the actual kernel source, right? Only the -lowlatency itself.
[23:47] <ailo_> And the -lowlatency seemed to be identical to a -ceneric source tree, except for some additions. That is the way it seemed to me
[23:47] <ScottL> but then there was a -lowlatency package as well
[23:47] <ScottL> but i looked at all the packages the -meta built and the source is not in there
[23:48] <ScottL> i'll email abogani later tonight about it and he'll probably answer by the time i wake up
[23:49] <ailo_> ScottL, Probably better. :P