[08:43] <astraljava> Hmm... could be that our video-genre deficiency is possibly removed soon? http://www.lwks.com/
[09:42] <jussi> yeah, i saw that -looks fantastic
[13:50] <len-dt> astraljava, Our list of conflicts has gotten bigger.. just got a bunch of  build fails in email.
[13:51] <astraljava> len-dt: Heh, cool. :) Well, I'm just leaving the office, so I'll dive in in a few minutes.
[13:51] <len-dt> Great, I am on my way to work...
[13:52] <len-dt> The emails are not in order BTW
[13:52] <astraljava> "Have a nice day!"  I was on support duty today, and tomorrow still... :-/
[13:52] <len-dt> Long hours?
[13:53] <astraljava> Not very, but when the customers are like the few today... They sure feel like it.
[13:53] <len-dt> :-)
[14:51] <holstein> ailo: yeah.. how to make it easier to revert to the old way ;)
[14:52] <ailo> Yep
[14:53] <ailo> For a few releases, the qjackctl starter had the pasuspender command in it
[14:53] <ailo> But now, it's not "needed" with the default config
[14:53]  * holstein is a fuddy-duddy ;)
[14:53] <ailo> We should add this to ubuntustudio-controls. Have a toggle for enabling/disabling the PA bridge
[14:54] <holstein> ailo: i like that a lot!
[15:01] <ailo> Actually, pasuspender is still there
[15:01] <ailo> in /usr/bin/qjackctl
[15:02] <ailo> It should kick in if needed, but I don't yet know the logic behind that script
[15:04] <holstein> well... if you dont, i know i wont get it
[15:06] <ailo> I figure there might be a bug involved
[15:06] <ailo> /usr/bin/pasuspender/usr/bin/X11/pasuspender doesn't seem like an executable to me
[15:06] <holstein> we should file that... that sux its like that in the LTS
[15:07] <holstein> is that something we can fix and "update"
[15:07] <holstein> ?
[15:07] <ailo> We will want to backport qjackctl as soon as it appears in debian repos
[15:07] <ailo> The newer one
[15:07] <ailo> Since we already have a bug with that one
[15:08] <holstein> cool
[15:11] <ailo> I'll have a look at the qjackctl starter script now, and discuss it with deb packagers. If it's a but, it would be nice to have it fixed for the next qjackctl package and get two flies in one blow
[15:11] <ailo> if it's a bug*
[16:15] <ailo> I've been a little busy lately. Eager to finish the website, but I won't do anything about that today. I've set it as a goal for myself to do what I can about that this week
[16:16] <ailo> holstein: You have any suggestions for the website right now? (other than obvious edits to the staging site to make it up to date)
[16:37] <ailo> holstein: /usr/bin/qjackctl is not buggy, just enhanced
[16:38] <ailo> It now assumes you always have pulseaudio-module-jack installed, to enable the jack-pulse bridge. But, if you disable d-bus (jackdmp), starting jack from qjackctl will suspend PA
[16:41] <ailo> Er, can't confirm that yet..
[16:54] <ailo> Nope. I can't make sense of it. I posted about it to the debian multimedia team, so hopefully they can tell me how it is supposed to work
[17:39] <knome> hmpf.
[18:17] <scott-work> for those interested:  https://blueprints.launchpad.net/ubuntu/+spec/topic-quantal-flavor-ubuntustudio
[18:17] <scott-work> this is the "header" blueprint for our other blueprints, look at bottom of page and click on a oval to see that blueprint
[18:17] <scott-work> i'll post to the list later
[18:17] <scott-work> also....
[18:17] <scott-work> PLEASE feel free to review them and change things!!!
[18:18] <scott-work> especially replacing [ubuntustudio-dev] with [<yournamehere>] as you feel you want to commit to an item
[18:18] <scott-work> and i'll be reviewing these again later tonight/tomorrow and making tweaks as well
[18:19] <scott-work> i'm hoping len-dt, in particular, will review https://blueprints.launchpad.net/ubuntu/+spec/ubuntustudio-q-performance
[18:19] <scott-work> and i'm hoping ailo will review https://blueprints.launchpad.net/ubuntu/+spec/ubuntustudio-q-documentation
[18:20] <scott-work> ailo: please note the documentation blueprint includes others that you have not committed, don't worry about these as i expect to head these up
[20:30] <ailo> scott-work: I do believe the documentation I have provided covers some of those items, but of course, some could be reviewed
[20:31] <scott-work> ailo: no problems, i just didn't want you to think you were responsible for ALL of it, but please add your launchpad name to the items you have done/plan to do
[20:34] <ailo> scott-work: I wouldn't mind taking the lead on the whole documentation blueprint, and thus being responsible for all of it. It would help making the organization of it in sync with what has been done, and what has been discussed. Also, I would be responsible for keeping track of all of it
[20:35] <ailo> I mean, keeping track of everything that anyone would think is worth documenting
[20:35] <knome> isn't there also the general assignee field for every blueprint?
[20:40] <ailo> scott-work: I'm a bit late to suggest this, but I also did get into it pretty late, so it's only natural
[20:43] <scott-work> ailo: ptttthh, i'm the late one to this party
[20:44] <scott-work> ailo: i think you should be lead for documentation
[20:45]  * knome kicks scott-work in the ankle shouting: yes you are! (:
[20:46] <scott-work> hehe,,,it's funny because it's true!
[20:46] <ailo> scott-work: Good. I'll try to make the most of it this summer!
[20:49] <scott-work> ailo: my plans are to still help with the development and testing documentation. i'm hoping that janne will help with the testing processes, but his involvement isn't absolutely critical 
[20:52] <ailo> scott-work: I think I will be able to cover most things. One I won't be putting too much attention is material for workflows. I won't mind organizing it, but I won't be producing it. Testing I will be producing, as well as user docs
[20:52] <scott-work> ailo: i'll be able to add several HOWTO's as well for various workflows
[20:53] <scott-work> ailo: and i don't mind taking care of the workflow producing and organizing
[20:57] <ailo> As for testing, I will of course do my best to be ancle deep in it, as much as I can, but it will be up to anyone involved to help decide how to go about it. Since I will be doing a lot of the testing (been setting up a minor facility here at home), it makes sense that I document it. 
[21:26] <scott-work> ailo: one thing you should really look into is the vm tools that the security team has been using
[21:26] <scott-work> they do somethings that are completely stupid simple
[21:27] <scott-work> like 'vm new' which will download the current image, copy and edit some xml, fire up a vm, and start a new instance with the downloaded image
[21:27] <scott-work> there are some tweaks needed i'm sure, e.g. like adjusting the image name/location
[21:27] <scott-work> and apparently the iso testing team also has some automation that could be really, really usefull (i can't currently remember what it was but i have it written down in my blog and elsewhere)
[21:31] <ailo> scott-work: I'll have a look
[21:33] <scott-work> here is the blueprint for qa-tools:  https://launchpad.net/ubuntu-qa-tools
[21:33] <scott-work> you will probably have to locate them in the security PPA 
[21:35] <knome> that doesn't look like a blueprint :)
[21:45] <scott-work> sorry, doing too many things and knome is quite correct
[21:45] <scott-work> i had the blueprint but copied the address from the wrong tab
[21:45] <knome> :)=
[21:45] <scott-work> http://summit.ubuntu.com/uds-q/meeting/20523/qa-q-ubuntu-qa-tools/
[21:46] <scott-work> just received an email from the kernel people (well leann and tim and their kernel mail list) about the lowlatency kernel
[21:46] <scott-work> tim had committed to getting the lowlatency into the kernel team if they had collapsed a few other kernels, which had been accomplished
[21:47] <scott-work> leann was wanting reminders for the compelling reasons to do so. i complied.
[21:47] <scott-work> i hope this helps push this through and something doesn't fall out of place
[21:48] <scott-work> okay, going home