[00:12] <TheMuso> /c
[10:24] <smartboyhw> Hello falktx
[10:24] <falktx> hi
[11:36] <smartboyhw> ailo-w: Hi mate. How are you comfortable with 12.10?
[11:45] <ailo-w> smartboyhw: I don't use Ubuntu much these days
[11:46] <ailo-w> smartboyhw: I saw you postponed your work on documentation. Does that mean you are not working on it anymore?
[12:01] <smartboyhw> ailo-w: No, just that I will postpone it a bit, maybe next week
[12:04] <ailo-w> smartboyhw: postpone is only required if you are not to finish before next release
[12:04] <smartboyhw> Oops sorry new to blueprints
[12:04] <smartboyhw> I will change it...
[12:05] <ailo-w> No big deal. But it's good to see where we are at with items.
[12:06] <smartboyhw> OK changing
[12:08] <smartboyhw> ailo-w: Changed:)
[12:17] <ailo-w> len-dt: When you have time, I'd like to talk to you about some developer tasks. I'm working on the developer documentation, and there are some things I have no idea about
[12:19] <ailo-w> len-dt: I'm going to try putting down everything we do, and howtos for them. Saves a lot of time for everyone, if we can just point to the docs when someone has questions
[13:08] <ailo-w> len-dt: On second thought, I'll send you an email with some questions later.
[13:09] <ailo-w> Then you can just respond whenever you have time
[13:09] <smartboyhw> len-dt is not awake today is he?
[13:24] <len-dt> ailo, smartboyhw good morning.
[13:25] <smartboyhw> GM le
[13:25] <smartboyhw> len-dt
[13:25] <len-dt> ailo, found another hint
[13:25] <len-dt> "Another tip, if you have to use a slot that shares IRQs, then you have
[13:25] <len-dt> to raise the priority of all the soft interrupt threads that share
[13:25] <len-dt> the IRQ with the soundcard, otherwise you will get a lot of xruns."
[13:26] <len-dt> It seems on new MB it is getting harder to find slots with their own irq.
[13:26] <len-dt> PCI slots that is.
[13:27] <ailo-w> I guess often shared with usb ports
[13:27] <ailo-w> So many of them these days
[13:27] <ailo-w> And what else
[13:27] <len-dt> USB (which means some of the MB stuff) and PCIe slots too.
[13:28] <len-dt> irq 16 seems to get shared with a lot of stuff on all my machines
[13:28] <len-dt> must be for legacy purposes
[13:29] <ailo-w> I have a bit of a problem with irq 16 on my most recent MB
[13:29] <smartboyhw> ailo-w: I asked a wrong question: (applies to len-dt too) what is your view towards Ubuntu Studio 12.10 Beta 1
[13:29] <len-dt> I mean a lot of these MB have 100 irqs and a lot not being used.
[13:29] <ailo-w> The internal card is on irq 16. The device becomes unavaible after some time. An error message about IRQ, and a beep sound
[13:30] <len-dt> 12.10 has two big holes (three now that ubuntu has split off their settings)
[13:30] <len-dt> we are missing two metas and the systray is not there
[13:30] <smartboyhw> Actually talking about Beta 1 
[13:31] <smartboyhw> I saw some Ubuntu Studio links have Ubuntu Studio icons and some with info icons
[13:31] <ailo-w> len-dt: I haven't at all looked at how to upload changes to seeds, and other things
[13:31] <len-dt> Ok, and? I picked what made sense to me
[13:32] <ailo-w> len-dt: That is something I was meaning to ask of you, to write down some of the things you do
[13:33] <ailo-w> len-dt: The Ubuntu devs are making things easy for us on the settings thing. We just need to add ubuntu-default-settings, and we're fine
[13:33] <len-dt> Changing seeds is easy. they are just text files. Putting in new metas requires more info than Micah has. He asked me to talk to Cjwatson after B1
[13:34] <ailo-w> len-dt: Would you be so kind as to write down the procedure for managing seeds in an email to me? I'll add it to the developer wiki shortly
[13:34] <len-dt> If I can't get it done soon, I will stuff them into the graphic meta (where they were)
[13:35] <len-dt> I will see what I can do. Just address it to the dev list?
[13:35] <ailo-w> len-dt: Or just to me, personally
[13:35] <smartboyhw> I do wonder: Since it is beta should we add it to http://ubuntustudio.org/download/ ?
[13:36] <len-dt> No
[13:36] <smartboyhw> Oh alright:)
[13:36] <len-dt> not ready for the wild.
[13:37] <len-dt> BRB
[13:37] <smartboyhw> BRB
[13:42] <smartboyhw> Yay it's our project leader scott-work!
[13:48] <ailo-w> scott-work: I was fiddling with developer documentation today, and was wondering if you could take a look. To begin with, you could help me see if I got the entire list of Ubuntu Studio Launchpad teams and projects listed at: https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation#UbuntuStudio_at_Launchpad
[13:49] <ailo-w> scott-work: I'd like to sort those out, and see how we can use them to our best benefit, as we try getting more people involved in the future
[13:50] <smartboyhw> OK, so the non-active ones are the open ones, and the active ones are the closed ones LOL
[13:53] <ailo-w> Going home now
[13:54] <smartboyhw> scott-work: I think I can help update the website
[14:09] <smartboyhw> Len-nb: You're on your notebook now
[14:09] <ailo> smartboyhw: There are enough people working on the website already, I think. What is it that you would like to change on it?
[14:10] <smartboyhw> OH yeah alright:
[14:10] <smartboyhw> :(
[14:10] <smartboyhw> I don't actually KNOW we have a Ubuntu Studio testing mail list ailo
[14:10] <smartboyhw> Is there a channel too?:)
[14:11] <Len-nb> ailo,  I have put a generic kernel on my notebook to test battery use differences. I am guessing I will have to do a discharge cycle to reset things.
[14:11] <ailo> Len-nb: There's a phoronix test you could try
[14:11] <Len-nb> I did notice that I get a lot less battery life than I used to
[14:11] <ailo> Or did I spell it wrong, let me check..
[14:12] <smartboyhw> phoenix You mean?
[14:12] <ailo> Len-nb: phoronix-test-suite
[14:12] <Len-nb> I used to get almost 4 hr (3.5 anyway) now is 1.5
[14:12] <smartboyhw> Len-nb: So you mean that generic kernel uses a lot more battery
[14:12] <smartboyhw> Not good
[14:12] <Len-nb> no low latency uses more
[14:12] <Len-nb> I want to see if generic uses less
[14:13] <smartboyhw> OH ok
[14:13] <ailo> Len-nb: The test suite includes a power usage test
[14:13] <smartboyhw> SO you mean lowlatency dropped from 4 to 1.5?
[14:13] <ailo> Len-nb: I'm adding some of it to Ubuntu Studio testing
[14:13] <Len-nb> ok
[14:14] <Len-nb> I had thought it was a cheap battery in my cheap netbook, but there is at least one other user who has complained.
[14:18] <ailo> Len-nb: I was just looking at how to operate the phoronix-test-suite. To list tests, you do: phoronix-test-suit list-tests
[14:18] <ailo> But, I'm not getting a list right now
[14:19] <ailo> I think it's trying to fetch them from some url
[14:19] <ailo> Anyway, I was most interested in the power usage test, as I wasn't able to find any other at the time
[14:21] <ailo> smartboyhw: The ubuntustudio-testing mail list is not active right now, but it is meant that we use it to post testing results, and anything else test related that we would like to document and save
[14:21] <smartboyhw> Oh yeah
[14:22] <ailo> smartboyhw: We are lacking documentation and work tasks for new developers. This, and that many developers have become inactive, or that some tasks were never completed is the reason we have so many inactive teams and other resources
[14:22] <smartboyhw> Oh alright
[14:22] <ailo> I'm going to sort that out during the months to come
[14:23] <smartboyhw> ailo: I support you! :)
[14:23] <ailo> And hopefully it will be easier for new developers to dive into development directly
[14:24] <smartboyhw> ailo: I agree. Not many devs except you and Len-nb huh?
[14:27] <ailo> smartboyhw: I don't think we need that many more core devs all the time, but if we would like to get someone helping us fast on something, even for a short time, it helps having docs ready. Also, I don't think we are making it easy for inexperienced people who want to learn and get into things step by step
[14:27] <smartboyhw> Yes, Ubuntu Studio is NOT for beginners 
[14:33] <ailo> smartboyhw: I think any skill level is fine, but the work you do needs to fit your skill level
[14:33] <ailo> Also, not everyone can just jump in and get dev rights. Even if there are enough skills. 
[14:34] <smartboyhw> Oh alright. I mean using Ubuntu Studio is not mainly for beginners to touch but contributing can be for beginners
[14:34] <smartboyhw> ailo: I have enough skills, I know C++, and I did some coding too LOL but then noone can easily jump in of course:)
[14:34] <ailo> The important thing I believe is that there is an easy way to find out what needs to be done, and how one can help
[14:35] <smartboyhw> Yes!
[14:35] <ailo> smartboyhw: Have you done any graphic programming? GTK?
[14:35] <smartboyhw> Done a bit UI
[14:35] <smartboyhw> But mainly in C++ I do command line ones
[14:36] <smartboyhw> I will show you an example
[14:36] <ailo> smartboyhw: If you like, you could help Len-nb with his workflow panel idea. 
[14:37] <smartboyhw> workflow panel...Too complicated for me:)
[14:37] <smartboyhw> I do UI at https://github.com/thesii/speechcontrol
[14:37] <smartboyhw> It's an Artificial Intelligence software (not an ad)
[14:38] <scott-work> ailo: will you be around for another thirty minutes?  i am busy at work until probably then
[14:39] <smartboyhw> scott-work is very busy today:)
[14:39] <ailo> scott-work: Yeah, I'm around. But, you can always send me an email, if you think of something, anything.
[14:41] <ailo> smartboyhw: Looks fun.
[14:41] <ailo> smartboyhw: And how are your python skills?
[14:41] <smartboyhw> python: 0
[14:41] <smartboyhw> HAHAHA
[14:41] <smartboyhw> I only learnt C++ and Visual Basic
[14:42] <smartboyhw> And that's enough for a 14-year-old. I learn a new language every year
[14:42] <ailo> Should be easy for you to learn python, if you can get by with the C languages
[14:42] <smartboyhw> :)
[14:42] <ailo> smartboyhw: python + GTK is not that difficult. There are some nice tutorials around
[14:43] <smartboyhw> OK I will start reading
[14:43] <ailo> smartboyhw: http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
[14:43] <smartboyhw> Thanks ailo. But then I am still more interested in testing:)
[14:44] <ailo> smartboyhw: Maybe you could help out with organizing testing procedures then. It's a bit specific for Ubuntu Studio. We don't need to test all the same things as other distros do
[14:44] <len-dt> scott-work, I have put the fix in as suggested for bug 1039792, I would like to see a more detailed look at this be done for next cycle if you can add it to your notes for next cycle blue prints
[14:44] <smartboyhw> ailo: Good. Especially I am in the Testcase Admins Team:)
[14:45] <smartboyhw> ailo: I'm thinking when I should apply to be Ubuntu membe
[14:45] <smartboyhw> *member
[14:45] <ailo> Team membership is not the most important. It's more important that we get good work done
[14:46] <ailo> I have not even tried to find out about Ubuntu membership, for instance
[14:46] <smartboyhw> Yeah
[14:46] <smartboyhw> ailo: Oh
[14:46] <ailo> I'm going to try join Debian Multimedia team later on, cause I want to help with some packaging and bug management
[14:46] <ailo> And that is the only reason
[14:46] <smartboyhw> OK
[14:49] <ailo> I see it this way. There are things that could be a lot better on Debian based distros. Some things are best done with software development, some with Debian development, some with Debian derived development(such as Ubuntu Studio). Add to that, documentation that is clear and true on forums that are popular, such as the Ubuntu Studio wiki
[14:49] <ailo> And when you find a problem, you try to find the best place to solve it
[14:49] <ailo> So, whether I'm a team member or not, will not help me solve any problems, if I haven't identified one, and decided where I should solve it
[14:50] <ailo> And that is all we are doing here. Solving problems
[14:50] <smartboyhw> solve quizzes:)
[14:51] <ailo> I think many more would probably want to help, and would be able to, but if there's not clear information for those on how to do that, a lot of energy will just be wasted
[14:51] <ailo> And that's why I'd like to sort out developer documentation 
[14:52] <len-dt> +1
[14:52] <ailo> Enough speech. bbl
[14:52] <smartboyhw> +1
[14:52] <smartboyhw> I think I should save this up and sent it to whose who want to help ubuntu studio
[14:53] <ailo> smartboyhw: That's why I'm focused on the dev docs. The idea is that it will contain all the info people will need
[15:08] <smartboyhw> Oh OK
[15:12] <smartboyhw> ailo: I want to join the debian multimedia team too, but then I got a problem with one of its requirements;(