[02:12] <len-dt> ailo, I think maybe I was dreaming. The rtirq script doesn't care if the IF is plugged in or not, It raises all the usb irq up in priority.
[02:14] <len-dt> It also apears that the new kernel (3.5) is ok too, the only reason it seemed worse is that it was running on an external USB drive.
[02:15] <len-dt> with the external drive plugged in my precise install is not as good either.
[02:58] <ailo> len-dt: The rtirq should not do anything with -generic, unless you provide it with the "threadirqs" boot parameter
[02:58] <ailo> In -lowlatency it is builtint
[02:59] <ailo> builtin*
[03:03] <ailo> len-dt: To see what the prios are do: ps -eo comm,rtprio
[03:04] <ailo> len-dt: To add threadirqs as a boot parameter, make sure this line reads:
[03:04] <ailo> GRUB_CMDLINE_LINUX="threadirqs"
[03:05] <ailo> Ah, sorry..
[03:06] <ailo> In the file /etc/default/grub that is
[03:06] <ailo> len-dt: Normally, the rtirq script has no effect for me at all
[03:07] <ailo> At one time, it was making things worse. I haven't been able to reproduce, but then, I haven't spent any time investigating
[03:07] <ailo> Never has it made things better
[03:07] <ailo> It will only improve things if you are having problems with priorities
[03:46] <len-dt> ailo, unfortunately, it can't tell the difference between a USB audio IF and a USB mass storage device.
[03:47] <len-dt> Even worse, the mass storage device is USB 2.0 and the audio IF is USB 1.1
[03:47] <len-dt> rtirq leaves the USB irqs in the order they are in and normally the USB 2 irq is already higher priority.
[03:48] <len-dt> On my desktop it is for sure.
[03:56] <len-dt> ailo, I wonder if I can order the usb irqs in the rtirq.config filels
[03:56] <len-dt> *file
[04:03] <ailo> len-dt: You can create your own custom setup
[04:03] <len-dt> ailo, right now the rtirq order is "firewire snd usb i8042". In cases where the USB audio IF is being used, maybe USB should be ahead of snd. The way it is now, puts my internal sound IF at a higher priority than my USB IF and yet the external has the good pre.
[04:04] <ailo> len-dt: Not sure how, but I think in /etc/default/rtirq
[04:04] <len-dt> ailo, can I do usb3 usb4 usb1?
[04:04] <ailo> No idea :P
[04:04] <ailo> I've never edited the config myself
[04:04] <len-dt> ailo, I'll try
[04:07] <astraljava> len-dt: The situation is way less than optimal, yes. I'm quite doubtful of our future at the moment, we're having quite large problems that need to be resolved fairly quickly.
[04:09] <len-dt> I had to look for what you were answering astraljava ... ok
[04:09] <len-dt> what do we need?
[04:10] <len-dt> ailo, I was able to put USB3 before the rest.
[04:13] <astraljava> len-dt: We need to evaluate what we want to achieve during this cycle, we need to come up with a working process in which we track our progress, we need to have some vision about where we want to develop as a flavor, and we need more committed people. :)
[04:13] <len-dt> ailo, I just did usb3 usb
[04:14] <len-dt> astraljava, Ya, need but don't really have.
[04:14] <ailo> astraljava: In what way has this changed from before?
[04:15] <astraljava> Good question.
[04:15] <astraljava> One that I can't answer right now.
[04:15] <len-dt> astraljava, ailo in many ways it is not that different, Scott had a computer with IRC running all the time, but had about the same amount of time to input.
[04:16] <len-dt> I think we should fix anything broken, menu, theme, plymouth.
[04:16] <ailo> astraljava: What is your main concern? XFCE?
[04:16] <astraljava> But the fact remains that this is the gravest situation the project has been in since early '06 that I've been watching. We're not going anywhere.
[04:17] <len-dt> I think we should finish the stuff started with the kernel by making it's improvements available to the users apps
[04:17] <astraljava> ailo: My main concern is the lack of vision and guidance.
[04:17] <ailo> I don't fully agree
[04:17] <ailo> I mean, it hasn't been full throttle at any point during the time I've been around
[04:18] <astraljava> Well okay, maybe there is something there in the background, but even if there were, nothing gets implemented.
[04:18] <ailo> I think we have a good chance of getting some really good work done for next release
[04:18] <ailo> Me and len will make sure of a part of that. With testing and documentation
[04:18] <astraljava> Those are really good things.
[04:18] <ailo> As for XFCE, I have no clue
[04:18] <len-dt> ailo, is the web page up yet?
[04:19] <astraljava> Xfce is not a big issue. Our direct upstream (Xubuntu) will handle that.
[04:19] <ailo> astraljava: In that case, I think the situation is pretty mellow
[04:19] <astraljava> Also, the maintenance of kernel will be there, no worries.
[04:19] <ailo> I'm a little concerned with -lowlatency for precise though
[04:20] <ailo> It seems we are stuck maintaining that
[04:20] <ailo> But that shouldn't be too much of a problem, with a little help from someone
[04:21] <astraljava> I will try to move that forward next week, I have a pretty big deadline this weekend I cannot ignore. After that I will have more time for *buntu matters.
[04:21] <ailo> The main concern I've always had was having a functional system for multimedia
[04:21] <ailo> Not until precise do we have a good kernel, since 9.04
[04:21] <ailo> Just that detail makes a huge difference
[04:22] <ailo> I don't think the OS really needs a lot to be good
[04:22] <ailo> And there is vision. Only, is it too ambitious?
[04:23] <ailo> When dealing with user support, I find most people just need help with basics, and also, getting realtime privilege
[04:23] <ailo> It would help a lot if we could give users an easy way to administer some things, like realtime privilege with a tool like -controls
[04:23] <astraljava> ailo: What is the vision in your opinion? How do you see the team committed to it?
[04:24] <ailo> Last year or so, there has been a lot of talk about workflows. 
[04:24] <astraljava> And lastly, what is the team? How many active contributors do we have? Are enough of the fields covered?
[04:25] <len-dt> From the activity here we have three
[04:26] <len-dt> Maybe five
[04:29] <ailo> astraljava: We need to be better at inviting people to join the project
[04:29] <len-dt> ailo, astraljava I think one of the problems may be the SW we don't ship
[04:29] <ailo> That is one thing I felt was a bit lacking in the past
[04:29] <ailo> Also, documentation has been a big problem
[04:30] <ailo> I think those areas should be solveable this year
[04:30] <ailo> len-dt: We can't ship SW that isn't in the repo
[04:31] <len-dt> some of the sw that has non-ubuntuish licencing 
[04:31] <len-dt> Ya, but we can make it easier to install
[04:31] <ailo> len-dt: Point taken
[04:31] <ailo> The website should have info on things like that
[04:31] <len-dt> It would be nice to have an installer like software center but with what people need.
[04:31] <ailo> It should really be a portal to all the best in linux audio
[04:32] <len-dt> Ya. that is what I mena
[04:32] <len-dt> *mean
[04:32] <ailo> We were talking about a PPA
[04:32] <astraljava> ailo: Good points, again. The team needs new contributors, ones with enthusiasm and drive. The whole project lacks drive. Maybe that was the word I should have used at first. :)
[04:33] <ailo> I think both me and len are pretty well equipped with drive, only things do move a bit slowly
[04:33] <len-dt> astraljava, part of the problem is getting a fix in. I can fix the menu... but I can't put it in. Last cycle I had to do it twice in two different packages
[04:34] <len-dt> Because it took weeks to add it.
[04:34] <astraljava> len-dt: That is again why I was asking questions about the team. We're ill-equipped in many fields.
[04:35] <ailo> astraljava: Perhaps len should just be allowed to make changes directly?
[04:35] <len-dt> astraljava, I found it annoying to "save up" fixes to do them all at once. My personal feeling is that the fixes should be put in as they are done.
[04:36] <len-dt> It allows more time for fixing them if they don't work right.
[04:36] <astraljava> len-dt: Are you not in the ubuntustudio-dev team on LP?
[04:36] <ailo> I am not either
[04:36] <astraljava> meh...
[04:36] <len-dt> I don't thnk so.
[04:37] <astraljava> Well, this here now comes to the lack of guidance I referred to.
[04:37] <ailo> I asked to join more than a year ago, but was denied
[04:37] <ailo> So I haven't asked again
[04:37] <astraljava> Ok.
[04:37] <ailo> But, I was recently allowed to edit the stagin site, so..
[04:39] <ailo> I'm an indirect member of the dev team, whatever that means
[04:39] <astraljava> Sadly I need to get to work, soon, so I'll put my thoughts real quick now: We have to put down the things we want to achieve, for this cycle and preferably for the next one (at least). We need to make sure we can commit to getting them done. We need to come up with a working government. And finally we need momentum.
[04:40] <ailo> As long as we don'
[04:40] <ailo> don't take too big bites
[04:40] <astraljava> I'd like to see your thoughts about these in the backlog when I am online again later today. Hopefully we can move things (and the project) forward, starting from this weekend.
[04:40] <astraljava> ailo: That's why I said we need the commitment to those things.
[04:41] <astraljava> Alright, catch up with you guys later.
[04:41] <len-dt> astraljava, later.
[04:41] <ailo> astraljava: Yeah, later
[04:43] <ailo> My main interests, and what I also think are achievable are: 1. documentation 2. New Website published 3. System tuning, testing and docs 4. -controls to administer at least user realtime privilege and a couple of other things
[04:44] <ailo> 1. Documentation is half done on the user side
[04:44] <ailo> We still need to have some dev docs
[04:44] <ailo> Also, the website is mostly publishable as is
[04:44] <len-dt> My opinion is the web site should have gone up two weeks ago.
[04:45] <len-dt> As a user I would expect it to be a work in progress all the time.
[04:46] <ailo> System tuning, testing and docs is a bit time consuming, but if we find important things (like high res timer for midi), we should really think about adding them
[04:46] <ailo> -controls is not that hard to code. But it will take at least a week for me to get a functional package working
[04:46] <ailo> I'm really busy right now, I have to say
[04:47] <ailo> The closer we get to August, the more time I will have
[04:47] <len-dt> ailo, I have found some things that work and some that don't
[04:47] <ailo> During second half of July, I will have a lot of time, probably
[04:48] <len-dt> August will be my free time work wise, but I will have two kids to do stuff with.
[04:48] <ailo> len-dt: And I'm looking forward to going through all of that with you, so we can put up docs, and standardize testing somewhat. To get clear results
[04:49] <len-dt> Some of the guys on LAU seem to have some tests they use.
[04:50] <ailo> All of the need to be gathered in writing, so it can be read and reviewed, along with posted testing results
[04:50] <len-dt> I would love to have a 64 bit machine... not for the new toy, but just so I could test ISOs
[04:52] <len-dt> But we found out a few weeks ago that a loan we thought we had paid off 10 years ago was in two parts and we had only done one part :P
[04:53] <len-dt> So no new toys right now. Still, I have both audio and MIDI USB IFs now.
[04:55] <len-dt> ailo, I think the mode switch is worth while. It is all script and can be added as part of the settings pkg if needed.
[05:00] <ailo> len-dt: I think it's too early to say what should be done or not. We need to put things in writing first. You need to be able to read about it and understand why you would need it
[05:00] <len-dt> ailo, documenting is not my strong side. Like test results or setting up tests. 
[05:00] <len-dt> I am willing though
[05:01] <len-dt> I think the workflow thing is the right direction
[05:01] <len-dt> start there and then go "what is stopping me from working well"
[05:03] <len-dt> I think starting from talent in and going to art out and defining the steps to get there.
[05:05] <len-dt> ailo, I think there are three parts to workflows (I'll change that number as I go)
[05:05] <ailo> workflows are great, but there are only two ways to guide the users on that basis. One is documentation: explaining what you would use to do this or that. The other is applications that abstract some of the work for you
[05:05] <ailo> If no one is doing documentation, or applications to develop the idea of workflows, nothing is happening on that front
[05:05] <len-dt> There has to be documentation. Either text or video
[05:05] <ailo> I like the idea of a panel
[05:06] <ailo> One thing that the user can never hide from, is having to learn how to use tools for specific tasks
[05:06] <ailo> Doesn't matter who you are, or what your workflow is
[05:06] <len-dt> Yup
[05:07] <ailo> So, I think what the user really needs is easy info
[05:07] <ailo> Categorized in a smart way
[05:08] <ailo> A panel contains information, as well as the ability to contorl applications
[05:09] <ailo> I think for that idea to take off, you really need to put a lot of time into it
[05:09] <len-dt> ailo, so this is an advanced panel? something more than a dock?
[05:09] <ailo> That is what I have had in mind all along. But I haven't tried creating one. Don't have the time. Also, it seems like there are more important tasks at hand right now
[05:10] <len-dt> ailo, that is why I tried making one... not so that mine would be the final product but so that we could try different things.
[05:11] <len-dt> The major comment I got was that the theme was wrong :-)   I was just worried about function.
[05:13] <ailo> Well, it's also a big project I think. I like the idea, but there's a lot to consider. Like what to use for it. dbus I suppose
[05:13] <ailo> And maybe ladish and whatnot
[05:13] <ailo> And how to use it
[05:14] <ailo> Maybe as a set of plugins
[05:14] <ailo> I would be happy to start by creating a simple system config program, like -controls, to do some things. and then add to it. Perhaps let the panel be a part of it
[05:15] <ailo> And all lended technology could be implemented in a plugin sort of fashion
[05:15] <len-dt> ailo, I think for this cycle, docs, fixes, and continue the kernel transition with system settings.
[05:15] <ailo> Yeah
[05:16] <ailo> It's more than enough work :P
[05:19] <len-dt> ailo, Ya, think in terms of two or three people for now.
[05:22] <len-dt> ailo, I think even a rough version of a mode switch would be good for testing. -controls would work well too. Is it easy to make changes on?
[05:31] <astraljava> Good conversation.
[05:32] <astraljava> len-dt: I wouldn't be worried about UI right now. We're in the middle of LTS releases right now. This is our playground, now is the time to go wild and experiment.
[05:33] <len-dt> astraljava, Yes, but it needs more than just me to try it.
[05:33] <len-dt> I can put screen shots up, but that doesn't really say anything.
[05:34] <astraljava> ailo: You are spot on; without documents or supporting applications, or development on those, we got nothing. The DE and the kernel are important, but the former comes from elsewhere, and the latter is mostly taken care of elsewhere as well (minus testing and "developing").
[05:35] <astraljava> len-dt: True.
[05:35] <len-dt> We need someone with more experience than me for testing these things.
[05:36] <len-dt> I can test that it does what it is expected to do.
[05:36] <len-dt> But I can't often tell if "what it is expected to do" is worth while.
[05:40] <ailo> As for me and len-dt, I believe we have our work cut out for us for next release. There are blueprints, and clear goals
[05:40] <ailo> So, in that respect, we know where we are headed
[05:41] <ailo> It's just a matter of getting things done
[05:41]  * len-dt has to go to sleep, he works better with 6 hours of sleep.
[05:42] <len-dt> ailo, I think I/we should set up a ppa to put settings packages in to test.
[05:42] <len-dt> So we can "install" a setting test it and document it.
[05:42] <ailo> len-dt: I can do that ardoun next weekend. These coming days will be wild for me
[05:42] <ailo> I'm also putting up kernels
[05:43] <len-dt> If it is an installed test, it is more likely to be consistent.
[05:43] <len-dt> Ok, good night all.
[05:44] <ailo> astraljava: If we were to post on such lists as LAD to try find developers, I do think we need to have a clear statement with what we need and where we are going. Preferably also a clear hierarchy - or responsibility areas
[05:45] <ailo> If I were to critisize Scott for something, then it is to do too much himself, and not gladly give away responsibility
[05:45] <ailo> But for him to feel doing that is successful, people do need to get things done too
[05:46] <ailo> I mean, he tends to put too much on himself
[05:47] <ailo> A member of the team doesn't need to share an equal percentage of the workload. Just be responsible of his/hers responisibility area
[05:48] <astraljava> ailo: Good that it sounds like you see this from the same perspective. :)
[05:48] <astraljava> I'm a little afraid to recruit, when I don't know what I'm marketing, really.
[05:56] <ailo> astraljava: It's also difficult to manage expanding the team if there isn't clear structure and planning in every area. This is hard to achieve though. 
[05:56] <ailo> I am lead of documentation, and prefer to be notified on all concerning docs
[05:57] <ailo> I would think len-dt would like to be in on anything concerning testing
[05:57] <astraljava> It's not, really. It needs the governing virtual team and regular meetings.
[05:59] <ailo> As long as everyone isn't trying to do everything
[05:59] <ailo> Which easily ends up in noone doing nothing
[06:03] <astraljava> Yep.
[06:30] <astraljava> len-dt: ailo: holstein: knome: You guys are mentioned on the https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[06:31] <astraljava> We need to meet, quick. Post times when you're most available. If we cannot agree on a DateTime soon, I'll create a doodle poll or similar.
[06:31] <astraljava> Considering there's not that many of us, I figure we can do it on here.
[06:32] <astraljava> I'll start; any day, best availability from 1500 UTC till 2100 UTC.
[06:39] <ailo> astraljava: I edited that page some time ago. I tried putting up people in positions that seemed logical
[06:39] <ailo> However, knome is probably not a US team member?
[06:40] <ailo> astraljava: Those times work for me as well
[06:42] <ailo> I mean, he can be if he wants to of course. Just that I was asking about it before, and seemed like none of the Xubuntu people were team members. Everyone are of course welcome to participate anyway, AFAIAC
[06:53] <astraljava> ailo: I don't know currently what the team is, or it consists of.
[06:54] <astraljava> It's a good place to start from, that page. If one wishes to get removed from it, he may voice it now. :)
[12:05] <knome> astraljava, ailo; i'm generally interested how US does, since it's beneficial for xubuntu if another derivative uses xfce too, since we can for some part share resources
[12:06] <knome> astraljava, pretty much any day/evening time works for me, though not on this weekend or next thursday. the rest i can just organize to work
[12:21] <astraljava> knome: Thanks, ACK.
[12:21] <knome> :)
[12:57] <ailo> astraljava: I think it would be good if we focused on the blueprint format as the starting point https://blueprints.launchpad.net/ubuntu/+spec/topic-quantal-flavor-ubuntustudio
[12:58] <ailo> I just realized I better update it with relevant info on my own part, which I just did
[13:00] <ailo> You're welcome to chime in and add yourself to work items. I'm doing docs as far as it is relevant to me. But there are other fields which are basically only done by Scott
[13:02] <ailo> astraljava: What workflows are concerned, please have a look at the feature tour in the staging site https://staging.ubuntustudio.org/tour/
[13:02] <ailo> New workflow for this release is publishing
[13:03] <ailo> So, we need to look at seeding and menu categories for that
[13:05] <ailo> astraljava: I think before the meeting, it would be good if you had a look at the blueprints https://staging.ubuntustudio.org/, the staging site https://staging.ubuntustudio.org/, and the current community wiki https://help.ubuntu.com/community/UbuntuStudio. 
[13:06] <ailo> As for https://wiki.ubuntu.com/UbuntuStudio, any ideas are welcome on how to improve development documentation
[13:06] <ailo> I will be doing that next
[13:06] <astraljava> I just did a little. It's horribly, horribly outdated.
[13:08] <ailo> Not only that. It doesn't really help us much with the format it has
[13:11] <ailo> We need to have clear areas of development, and methods for working as well as documenting results
[13:12] <ailo> And docs on what we need to know, or what new devs need to learn
[13:12] <ailo> Actually, docs for new devs might be the best place to start
[13:13] <ailo> And there should be some kind of procedure to be accepted as a dev
[13:13] <astraljava> So why is that website not live?
[13:14] <ailo> scott-work: Hey. What is it that you feel is lacking from the staging website currently, which needs to be taken care of before publishing it?
[13:16] <holstein> support team!
[13:17] <ailo> holstein: Your it!
[13:17] <holstein> :)
[13:18] <knome> if you want progress on the website, i can file an RT ticket to get it out.
[13:18] <holstein> id like to put out what we have
[13:19] <knome> others agree?
[13:19] <scott-work> ailo: i don't think there is anything that is really preventing us from getting it released, you really did an outstanding job adding to it
[13:19] <scott-work> anything else to be added can be done later i believe
[13:19] <scott-work> knome: i agree
[13:20] <knome> ticket created
[13:20] <knome> https://rt.ubuntu.com/Ticket/Display.html?id=20009
[13:20] <ailo> It's almost cheap champagne time :P
[13:20] <knome> it should be live in about a week max, i suppose
[13:21] <ailo> knome: So, how does it work later? Do we always make changes to the staging site, and get it published with a rt ticket?
[13:21] <knome> ailo, no. you'll just login at ubuntustudio.org/wp-admin and the changes are live immediately
[13:22] <ailo> That's wonderful :)
[13:22] <knome> isn't it :)
[13:22]  * knome hopes there isn't any regressions on going live
[13:22] <holstein> yeah... thats the deal!
[13:22] <holstein> we can change what we need as we go
[13:59] <scott-work> i am sorry i have been so removed from ubuntu studio development over the past months
[13:59] <scott-work> i thought things would sort out at work and i would have more time but it hasn't worked that way
[13:59] <scott-work> i expect to remain minimally involved for a few months coming as well
[14:00] <scott-work> i also have a chance to work on some creative projects that i have desired for a few years and i would deeply regret delaying these if they were not available when i was ready for them
[14:00] <len-dt> knome, +1 to publish website a week ago...
[14:00] <knome> len-dt, the ticket is filed already :)
[14:01] <scott-work> so i'll be sending an email to the mailing list about minimizing my involvement for a while and soliciting others to accept some of the daily/weekly responsibilities
[14:01] <scott-work> i still feel very strongly about ubuntu studio development and i still have a plan through the next LTS
[14:02] <scott-work> i will also be posting this weekend about that as well to outline it
[14:02]  * len-dt wishes to thank holstein for all the support he does.
[14:03] <scott-work> i expect the bulk of the creative projects to require the next three or four months and i believe that i'll be holistically involved again with ubuntu studio, which is roughly right before or right after this release
[14:04] <ailo> scott-work: I think we have a good idea of what you want to accomplish in many areas, and I will do my best to keep working within those lines. 
[14:04] <len-dt> scott-work, understood. Some of us need acces so we can at least make fixes.
[14:04] <ailo> scott-work: Not sure if I'm an Ubuntu Studio developer, but it would be nice to be added
[14:04] <ailo> scott-work: Also, len-dt might be useful having that responsibility too
[14:05] <ailo> Given that we use the responsibility with care and caution
[14:05] <ailo> Which I am certain we will
[14:05] <ailo> I started outlining some sort of dev docs https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation
[14:06] <ailo> scott-work: len-dt: astraljava: holstein: Do tell me if that sounds like what we are after
[14:06] <ailo> Or if not..
[14:07] <ailo> I would need help adding to the Ubuntu Studio developer tasks
[14:07] <ailo> I will create pages for each
[14:08] <ailo> hmm, scott-work: you were wanting to create a new way of testing, right?
[14:08] <scott-work> hehe, you guys are awesome!
[14:08] <scott-work> ailo: well, i intended to document some processes just to help others get involved
[14:09] <scott-work> but also brainstorming minimums to check for quality (e.g. does jack start with rt)
[14:09] <scott-work> holstein and astraljava and micahg are awesome too :)
[14:09] <ailo> I was more thinking about that automated testing thing you were talking about
[14:09]  * len-dt is off to work
[14:09] <scott-work> oh, yes!  there is that too
[14:10] <scott-work> i saw some cool things about that at uds
[14:10] <ailo> That would be one of those current goals, to put that into use
[14:10] <scott-work> by len-dt 
[14:10] <scott-work> ailo: absolutely
[14:11] <scott-work> just to note: i have two main goals for my work during the next few months; creative desire and money
[14:11] <scott-work> i want to create a few things but i also want to explore monetizing 
[14:11] <scott-work> which leads me to one of the long range plans for ubuntu studio;  can it be monetized for those who work with it?
[14:12] <scott-work> i think so and towards the next LTS i had wanted to see if a new audience couldn't be schools (all ages) or non-major-label studios?
[14:13] <ailo> I see. Well, that sounds like a plan a bit further ahead. Something that we perhaps aren't in a hurry to decide about. Sounds intriging
[14:13] <scott-work> my thought is that one could get paid to install audio recording systems in schools or studios
[14:13] <scott-work> AND maintenance contracts could exist in the same locations
[14:13] <ailo> Who would do this? Anyone who wanted to?
[14:14] <scott-work> aye
[14:14] <ailo> And US devs provide support?
[14:15] <scott-work> technically, anyone could
[14:15] <scott-work> but it might be hard to get a contract with a school just being a guy off the street with no affiliation
[14:15] <ailo> I can't say I'm really too interested in anything that deals with economy on this project, but I'm sure it could be easier getting experienced devs to help with US, if they had a chance to get paid for it too
[14:16] <ailo> Just that, how big is that market :P
[14:16] <scott-work> there is a fairly good movement in the US to move towards open source software and with an economic recession, things are changing
[14:16] <scott-work> but i don't know specifics about the market
[14:17] <scott-work> it will be difficult, but a well polished presentation and demonstration might help 
[14:17] <scott-work> getting the first one will give the whole thing a sense of legitimacy as well
[14:17] <ailo> I think the main problem is probably installation. The rest is not supposed to be
[14:17] <ailo> Getting the OS to work with specific hardware
[14:18] <ailo> And just the pain of doing it, if you don't know anything about Linux
[14:18] <scott-work> but that's a year in the future or so to really start brainstorming and making sure things are set up properly
[14:18] <ailo> It would be cool if it happened
[14:19] <scott-work> incidentally, as i learn more about films, i think some groups would be willing to spend a decent amount of money to buy a ubuntu studio derivative specific to making films
[14:19] <scott-work> there is a whole movement to using DSLR cameras and doing things on the cheap
[14:19] <scott-work> anyways, got to go back to work
[14:19] <knome> this all sounds great, but you really need to get the basics right first :)
[14:21] <ailo> I don't think there's anything wrong with pursuing that in the greater perspective, but I agree. We have more basic tasks at hand right now
[14:32] <ailo> scott-work: I guess I am a member of the ubuntustudio-dev team, since being in the website team makes me an indirect member. There's no button for joining anyway
[14:33] <ailo> Or do one need to be invited?
[14:33] <ailo> does*
[18:04] <scott-work> knome:  considering other audiences and what needs to be done is easily over a year away, maybe more
[18:05] <scott-work> ailo: i agree about more important concerns at the moment, i was just mentioning some of these ideas
[18:06] <scott-work> partly because i am starting something long term that i hope will help me perhaps transition from the job i currently have into something that centers around artsy-fartsty stuff like music, video, books, and linux
[18:06] <scott-work> ailo: as for access to the code, i need to look into that and see who has what permissions
[18:23] <scott-work> here's an interesting thought....
[18:23] <scott-work> what if a linux system looked like this: https://tails.boum.org/doc/first_steps/startup_options/windows_camouflage/index.en.html
[18:23] <scott-work> but offered all the audio goodness that ubuntu studio (et el) can offer
[18:23] <scott-work> i wonder if this would be more acceptable to a larger audience and more people would be willing to use it
[21:23] <len-dt> ailo, Just so you know, I was able to use rtirq to improve my USB audio performance even with the usb 2.0 mas storage plugged in.
[21:24] <ailo> len-dt: cool
[21:25] <ailo> len-dt: Would you mind writing down what settings and why the performance improved?
[21:25] <len-dt> ailo, I also found it made a difference which USB socket I used.
[21:25] <ailo> Aha
[21:26] <ailo> I mean, what config you used, and how that helped, etc..
[21:26] <len-dt> ailo, IRQ sharing for one
[21:26] <len-dt> ailo, where would you like me to put it?
[21:28] <ailo> len-dt: You could just post it on the dev mail list if you like
[21:28] <len-dt> ailo, great, will do.
[21:29] <ailo> len-dt: I guess we should try to make use of the mail list more often. Easy way to store info and maybe others will read about it and comment as well
[21:32] <ailo> We could even post to the mail list automatically when doing automated test later
[21:33] <ailo> I have an automated mail setup on this computer to send issue reports for some projects. Using msmtp
[21:33] <ailo> It's a commandline tool for sending emails. Pretty handy when wanting to send automated emails
[21:37] <len-dt> could do.
[21:38] <knome> ailo, please rethink flooding the -devel mailing list
[21:38] <knome> ailo, maybe create another one for -bugs or so
[21:38] <len-dt> :)
[21:39] <ailo> knome: Well, how do we do that?
[21:39] <knome> same with launchpad - i'd really love if the ubuntustudio-devel team wasn't subscribed to all bugs, but ubuntustudio-bugs
[21:39] <knome> ailo, i suppose create an rt ticket ;)
[21:39] <knome> ailo, rt.ubuntu.com
[21:42] <ailo> knome: hmm, I don't seem to have permission
[21:43] <knome> ailo, login with ubuntu SSO
[21:43] <knome> ailo, you should.
[21:44] <ailo> knome: I had some weird problem. Had a login screen where to input info. But I do seem to be logged in now
[21:44] <knome> ailo, yes, there's a login screen, but in that, there's a ubuntu sso button too :)
[21:45] <ailo> knome: I did use the sso button, but was still redirected to a page where to fill in details..
[21:45] <knome> ailo, weird. :)
[21:46] <knome> i'll be around a bit if you need help with filing the ticket
[21:46] <ailo> knome: Thanks. I'm looking around a bit first
[21:47] <knome> ailo, mmhm. basically, requestors is a list of email addresses. after that, you only need to add subject and a description.
[21:48] <ailo> knome: Queue? Lists?
[21:48] <ailo> knome: So I add my email adress as requestor? And explain what I need?
[21:48] <knome> yes
[21:48] <knome> and yeah, i suppose queue can be lists
[21:49] <knome> i looked at another ticket for creating a list, you basically need to just name the list and tell why you want it
[21:50] <ailo> ok. I'm requesting to establish a new list called ubuntustudio-testing, then
[21:51] <knome> ailo, thinking about lists technically too, you probably need to mention them who should be the list admin, if not you
[21:52] <knome> ailo, if you want, you can add me to the cc field and i can follow the progress
[21:52] <knome> oh, created :)
[21:52] <knome> i'll star it
[21:54] <ailo> I can be the admin, np
[21:54] <knome> hehe, yeah :)
[21:55] <knome> ok, i'm off
[21:55] <knome> see you later
[21:55] <ailo> knome: later
[21:55] <len-dt> astraljava, meeting times for me are weekdays 2230 UTC till 0600utc or so. On Saturday, 1500utc till 2200utc on and off (I have other things to do during that time too)
[21:56] <len-dt> astraljava, please note these are daylight savings hours when I am -8hrs. In the winter I am -9
[21:57] <len-dt> so those hours are good for this cycle. The sunday time worked good for me in the winter, but is too late for me now.
[22:01] <ailo> len-dt: We are about, I think +2,+3 right now, so when it's evening for you guys, we're sleeping. So, generally, your earliest time, and our latest time make some kind of a boundary
[22:02] <ailo> 2230 on weekdays may be a bit late, but Saturday from 1500-2200 sounds pretty good
[22:04] <len-dt> ailo, Ya, I have noticed :-)  I normally have about 5 minutes in the morning while eating before work. I read the backlog and maybe comment one or two things.
[22:05] <len-dt> after work I sometimes write two or three pages with the hopes someone will see it when they get up...