[03:54] <navsen> hello?
[04:14] <stochastic> hi
[04:14] <stochastic> how are you navsen 
[04:47] <navsen> good
[04:47] <navsen> I was just wondering how the project was going and if there are any plans to participate in google summer of code?
[04:57] <navsen> ok, well I gotta go.
[10:04] <stochastic> ScottL, ^^  You'd be the one to organize this if it's something we can tap into.
[10:27] <astraljava> We're doing very little ground-breaking stuff, I think vanilla would be a better place for that, or some of the upstream projects.
[10:28] <knome> thinking pretty much the same for xubuntu
[10:29] <knome> i'm not sure who would have all the time for mentoring
[10:29] <astraljava> I mean, what is there to code, when you're practically doing integration?
[10:29] <knome> and if somebody did, that probably took all of his work hours away
[10:32] <knome> well, there is bits here and there ;)
[10:32] <astraljava> That is not to say, if someone found something really cool and interesting, and wanted to work on it, that I would oppose of it. Not at all, I could even find time to mentor, but I have no idea what that would be.
[10:32] <astraljava> Of course, but anything that lasted throughout the summer?
[10:33] <knome> mind you, we're implementing a menu editor completely from scratch this cycle ;]
[10:33] <astraljava> Well, that could be something worth pondering about.
[10:33] <knome> yeah, too bad one of my friends already wrote it :)
[10:33] <astraljava> But we'd be stealing that from you guys anyway. ;)
[10:34] <knome> hehe
[10:34] <astraljava> Ahh...
[10:34] <knome> no, feel free to use that
[10:34] <knome> well, it's not a full-fledged menu editor
[10:34] <knome> so i lied a bit
[10:34] <knome> but you can (un)hide items and add "bookmarks" to the menu
[10:34] <astraljava> Ok.
[10:37] <astraljava> Well, of course we'd feel free to use it. It _is_ free software, right? :D
[10:42] <knome> let me think
[10:42] <knome> ;)
[10:42] <astraljava> *frown*
[10:42] <knome> i suppose
[10:42] <knome> :P
[13:56] <scott-work> astraljava: can i put you down as the responsible person for some livedvd work items in the blueprint?
[13:56] <astraljava> scott-work: Yes, all, if you want.
[13:56] <scott-work> astraljava: just the first two are what i'm thinking:  https://blueprints.launchpad.net/ubuntu/+spec/other-p-ubuntustudio-livedvd
[13:57] <scott-work> astraljava: well, there are others for ubiquity and others as well, i was hoping to distribute the load
[13:57] <astraljava> scott-work: Of course, and since I now have the time, I will try to unload you (as dirty as it sounds) as much as possible.
[13:58] <scott-work> lols
[13:59] <scott-work> astraljava: would you edit the work items as see fit to assign yourself and also make the ones you are currently working on as 'INPROGRESS"?
[14:00] <scott-work> my main concern right now is to update the work items so that the number of TODO items decreases
[14:00] <scott-work> i don't want to lie, of course, just accurately reflect reality, at least as reasonably close as possible
[14:01] <scott-work> astraljava: i had already suggested to falktx that he try his hand at the ubiquity patch portion
[14:01] <scott-work> but that requires us to make some decisions very soon about work flows
[14:01] <scott-work> astraljava: BUT, i don't think we _need_ to reconcile the ubiquity issue right now
[14:02] <scott-work> i would mainly like to focus on getting the live-dvd task resolved first, and i think working through ubiquity might retard that progress
[14:02] <astraljava> scott-work: Yes of course, I'm sorry I've been a tad lousy with the stuff from the project management point of view.
[14:02] <scott-work> and since cjwatson is going to be unavailable soon i think live-dvd is the priority
[14:02] <astraljava> Yep, that's my reasoning too.
[14:03] <scott-work> astraljava: oh no, no.  not you, but me?  aye, i have been lax lately :/
[14:03] <scott-work> but i'm getting back into the routine again :)
[14:03] <astraljava> I think we all need to participate, and you just can't handle it all.
[14:04] <scott-work> now, if i can just get an answer about REVU and when it might be up, then we can start the lowlatency kernel push in earnest :-D
[14:04] <falktx> revu is being deprecated afaik
[14:04] <falktx> it never really worked
[14:04] <falktx> and now ubuntu has the software-center app-portal thing
[14:05] <astraljava> falktx: True, but it is still _supposed_ to be there, until the two projects agree on using mentors.d.o, for instance.
[14:05] <falktx> yeah
[14:05] <falktx> just that I gave up on that a long time ago
[14:07] <scott-work> astraljava: when you talked with cjwatson the other day about live-dvd, which channel did you do it in?  i hope to learn some more about it by reading the logs
[14:07] <astraljava> scott-work: On #ubuntu-devel.
[14:07] <scott-work> thank you
[14:07] <astraljava> scott-work: And you mentioned REVU again on #xubuntu-devel, which I'm not sure was the correct channel.
[14:08] <astraljava> scott-work: I notified of this, and the fact that I already asked about REVU on #-motu a while ago. You need to pay attention, sir! :D
[14:08] <scott-work> astraljava: heheh, thanks :P
[14:08] <scott-work> it looks like REVU is still down :(   i want to get the -lowlatency kernel into it :|
[14:09] <astraljava> scott-work: I guess you could look into utilizing mentors.debian.org for that.
[14:09] <astraljava> scott-work: Or upload to some other public place, and notify necessary people of its whereabouts. Luke springs to mind.
[14:10] <scott-work> astraljava: the later is what i was thinking as well, abogani already has it in his ppa
[14:11] <astraljava> scott-work: Yeah, but they will want to see the other bits and pieces, on top of the binary package.
[14:11] <astraljava> scott-work: That bzr branch Laney suggested isn't a bad idea, either.
[14:11] <scott-work> astraljava: but the source is there, right?
[14:12] <scott-work> in ppa i meant
[14:12] <scott-work> astraljava: so maybe we create a bzr branch under the -dev team?
[14:15] <astraljava> scott-work: If you dget the *.dsc from a PPA, it doesn't give you the debian/, does it?
[14:15] <astraljava> scott-work: Yes, that would be my suggestion.
[14:20] <scott-work> astraljava: not sure about the *.dsc/PPA/debian/ bit... i have always grabbed the source, removed '~ppa*', and then ran debuild 
[14:21] <scott-work> astraljava: i have final changes to seeds for theme-ui update and then i'll move onto the lowlatency kernel then
[14:21] <astraljava> scott-work: Yep. That's why the bzr branch would be best.
[14:22] <scott-work> TheMuso: do you have any input on the fact that REVU doesn't seem to be available, placing the lowlatency kernel into one of our BZR branches for review by you and another MOTU?
[14:22] <astraljava> Giving upload rights to the kernel team would guarantee the best possible cooperation.
[14:33] <scott-work> astraljava: good point!  do we have a kernel team?  :grin
[14:33]  * scott-work thinks that he's suppossed to create one per the blueprint and hasn't done it yet
[14:34] <astraljava> scott-work: We don't, but the Ubuntu project does, and they will want to work with you (okay, us|US).
[14:47] <scott-work> astraljava: i'm not sure the kernel team does want to work with us|US
[14:47] <scott-work> that wasn't meant to be deragatory or mean
[14:48] <scott-work> but i think the kernel team has been very clear that the lowlatency kernel will be a community maintained kernel and they will not support it
[14:49] <scott-work> and they (apw, leann, steve c.) seemed quite okay with us making it as long as we base off of the ubuntu kernel and maintain security updates
[14:50] <astraljava> scott-work: Fine, I don't really mind. But still, having it publicly shared would make it easier to maintain, community or not.
[14:53] <scott-work> astraljava: oh, i should have pointed out as well that abogani already has a git repo set up for it as well
[14:54] <astraljava> scott-work: That's good, too. But having it under the studio-dev, for instance, would make it much more efficient, privilege-management-wise, for instance. But yeah, we probably have to think about it more.
[14:55] <scott-work> good point
[14:57] <scott-work> i like the idea of putting it under a -dev bzr branch myself, not sure i can justify that desire though
[14:58] <astraljava> I do understand that it's Alessio who's going to work with it the most, so we will have to respect his opinions about it the most.
[14:59] <astraljava> But, if it is, by definition, community-maintained, others would have to have access to it as well. But there should be certain limitations to 'others', it's a kernel after all, FCOL! :D
[15:00] <scott-work> hehe, good points, again
[15:02] <scott-work> my understanding (limited and inferred) from the uds session was that if alessio maintains the code in git, it can be rebased on new/updated kernel fairly easily due to some automation
[15:02] <scott-work> this apparently applies to security updates as well
[15:04] <astraljava> Yeah. And I do understand that kernel is exclusively developed and maintained in git, and that is in strong favor of keeping it in git in the future. git is fairly easily managed, privileges-wise, though, so we shouldn't have problems there.
[18:09] <scott-work> progress looks much better after updating the blueprint work items :)   http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-ubuntu-studio.html
[18:09] <scott-work> thank you for helping with that astraljava 
[18:12] <ailo> scott-work, Read that each distro must decide for themselves if they will be LTS or not. Xubuntu is named as being one. Does UbuntuStudio need to sign up for that as well?
[18:17] <scott-work> ailo: yes we do, i had forgotten about that
[18:17] <scott-work> ailo: is this something you would like to head up?
[18:17] <scott-work> i would really appreciate it
[18:18] <scott-work> although i think astraljava and i talked about this we considered discussing it at this week's meeting (yes, we REALLY will have one)
[18:19] <scott-work> so maybe a first step is to send an email to the -dev list noting that we need to apply, asking for opinions on what time durations (old LTS is 3 years, new LTS is five years - although we can choose what we want), and then mention discussion will occur in the meeting
[18:20] <astraljava> ...which reminds me to check up on the agenda.
[18:21] <scott-work> this is the email about the LTS approval for other derivatives:  https://lists.ubuntu.com/archives/ubuntu-devel-announce/2012-January/000922.html
[18:21] <scott-work> astraljava: i'm not too worried about populating the agenda with unnecessary items if you are not as well
[18:21] <scott-work> i wouldn't mind keeping it short and sweet...maybe the LTS items and then an update on where we stand for 12.04
[18:22] <scott-work> unless you think we need to have more and i'm agreeable to that as well, of course ;)
[18:23] <astraljava> scott-work: Define unnecessary. :)
[18:25] <scott-work> uhhhh, anything we don't need?  :P
[18:25] <scott-work> hmmmmm, good question, actually
[18:25] <scott-work> i would rather have a nice short, but effective meeting, rather that address a bunch of topics, for which we aren't prepared, because we are trying to emulate another team's meeting agenda or style
[18:26] <scott-work> i suppose that is really what i meant
[18:26] <scott-work> although i am not intending to be deragatory about any other teams or their agendas
[18:29] <astraljava> Satisfactory? https://wiki.ubuntu.com/UbuntuStudio/Meetings/2012January22
[18:32] <scott-work> hehe, yeah, that's pretty lean
[18:32] <scott-work> thanks for updating that, to be honest i had completely forgotten about some of the items under "old business"
[18:32] <scott-work> astraljava: are you making any progress so far on the live-dvd?
[18:34] <scott-work> i hadn't actually had a chance to read or digest what cjwatson told you in the irc logs
[18:37] <scott-work> astraljava: hmmm, i was hoping cjwatson would have given more explanation
[18:39] <scott-work> i'm confused actually
[18:40] <scott-work> other than not including that installer, what would we not want available on the live dvd?  maybe i need to reread the irc log
[18:42] <scott-work> s/that installer/the installer
[18:42] <scott-work> i also realize that we probably will need a new pacakge:   'ubiquity-slideshow-ubuntustudio'
[18:42] <astraljava> I don't know, really. I haven't had much time today, in fact, to spend on that.
[18:42] <astraljava> Uhh... yeah. :-/
[18:42] <astraljava> Who's got artistic skills in here?
[18:43]  * astraljava sent a meeting reminder on u-s-devel@
[18:44] <scott-work> astraljava: you rock!
[18:45]  * astraljava bows
[19:02] <scott-work> interesting, a "professional DAW for linxu"  http://www.ubuntuvibes.com/2012/01/bitwig-professional-music-creation.html
[19:10] <falktx> lol, "professional"
[20:59] <TheMuso> scott-work: I know nothing about revu not being available, and a kernel tree in a bzr branch is only going to cause much pain.
[22:03] <len> Just wondering. Is there any web page that has the work flows we want and the applications and usage that goes with them?
[22:39] <astraljava> len: You're probably looking for this: https://wiki.ubuntu.com/UbuntuStudio/Workflows
[22:40] <astraljava> len: Also of considerable source of information, this is a good point to start from: https://blueprints.launchpad.net/ubuntu/+spec/topic-precise-flavor-ubuntu-studio
[22:40] <ScottL> TheMuso, we weren't going to host the code necessarily in the bzr branch, it was just to get the code reviewed