[02:21] <Len-nb> zequence, on a netbook 4 workspaces are not enough.
[02:21] <Len-nb> (not that we should base studio on a netbook)
[03:20] <Len-nb> zequence, we have some double settings dialogs.
[03:22] <Len-nb> There are two keyboard input methods config applets, and there are two online account managers
[03:22] <Len-nb> I will only put the xfce version in our settings manager.
[03:34] <zequence> Been doing some mixing with ardour3, finishing up a project I initially started doing on Ardour2. Not too bad. Calf plugins are pretty nice, plus I have the LinuxDPS plugins as well
[03:35] <zequence> And Ardour3 isn't in the way too much. One crash so far, but the project could be recovered
[03:59] <Len-nb> A2 crashes sometimes too. But normally from a plugin.
[04:35] <len_1304> zequence, qamix sounds  interesting. Not in our repo though. It doesn't come with a configure script though... harder to build.
[04:35] <smartboyhw> Happy Mother's Day len_1304 zequence :P
[04:37] <len_1304> I'll pass that to my Yf   ;)
[04:37] <len_1304> zequence, qamix is by the same author as ams
[04:39] <len_1304> It has persound card profiles and is midi controllable. Once I manage to build it I will be able to tell how it looks ...
[06:07] <Len-nb> micahg, when  you have time, ubuntustudio-default-settings needs to be released.
[06:24] <Len-nb> zequence, ^^ when it gets released, I would like opinions :)
[06:26] <Len-nb> I have moved all the settings into the settings manager and removed the settings menu... similar to xubuntu. 
[06:27] <Len-nb> The settings manager has a new audio section for the LADI bits, but could include other audio config stuff
[06:28] <Len-nb> Unlike xubuntu, things like software installation and gparted are still in system.
[06:29] <Len-nb> I could put a graphics section in as well for colour setup if that makes sense.
[13:16] <smartboyhw> Hello DarkEra 
[13:18] <DarkEra> Hi smartboyhw 
[14:25] <len_1304> smartboyhw_, our page https://launchpad.net/ubuntustudio seems out of date. Do you know how to fix it?
[14:26] <zequence> len_1304: Those are done manually
[14:26] <zequence> There's actually no point in doing that, since we aren't using Ubuntu Studio as the project for our releases anymore
[14:26] <len_1304> Ya, but I don't see an edit button
[14:27] <zequence> That's probably because ubuntustudio-core is the maintainer
[14:27] <len_1304> Ok
[14:27] <zequence> I've moved over ownership to that team for most things recently
[14:28] <zequence> Once can get an overview of things from there too https://launchpad.net/~ubuntustudio-core
[14:28] <len_1304> Not  problem really. I am less sure how to change it anyway.
[14:28] <zequence> There's no real logic behind the teams right now, I think
[14:28] <zequence> The projects, I mean
[14:29] <zequence> I think Ubuntu Studio had its own repos and stuff in the past
[14:29] <zequence> So, it made sense to have a project, and a bug tracker for that
[14:29] <zequence> Since we're all apart of the Ubuntu project these days, we don't really need a Ubuntu project. But, I still use it for some things, like the blueprints that aren't release specific
[14:30] <len_1304> Yup. Well the menu is just about finished
[14:30] <zequence> I mean, we don't really need a Ubuntu Studio project, is what I meant
[14:31] <zequence> len_1304: We should start packaging ourselves, so let's set up a PPA for that
[14:31] <len_1304> Ok.
[14:31] <smartboyhw_> Hello madeinkobaia
[14:31] <zequence> len_1304: That means, we build the package, and then someone can sponsor by just copying it from PPA
[14:31]  * smartboyhw_ just done some merging for Kubuntu, heh;P
[14:32] <len_1304> zequence, that also means other team members can test them sooner.
[14:32] <zequence> len_1304: Yeah
[14:32] <smartboyhw_> A PPA is certainly best
[14:32] <madeinkobaia> Hi smartboyhw :) Hi all, I added a new version for the 13.04 "box banner" : http://bazaar.launchpad.net/~ubuntustudio-art/ubuntustudio-resources/art/view/head:/ON-AIR/ubuntu-studio_box-banner_1304_02_by_madeinkobaia.png
[14:33] <madeinkobaia> zequence ^
[14:35] <len_1304> madeinkobaia, looks good to me.
[14:35] <smartboyhw_> madeinkobaia: Nice job!
[14:36]  * smartboyhw_ rather wants madeinkobaia to focus on making 13.10 wallpapers :P
[14:36] <madeinkobaia> Hi len_1304, thanks : )
[14:39] <zequence> madeinkobaia: I thought it looked just good. Couldn't remember what the changes were, so looking at the older version it seems you have moved the background a bit, and lightened the blue text
[14:39] <zequence> I like it
[14:40] <madeinkobaia> smartboyhw_ : I started working on wallpapers ; )
[14:41] <zequence> micahg: So, I was thinking we should start building our own packages, and put them in a PPA so we can ask to get them copied from there, but would there be any problems with that? I'm thinking of gpg signatures
[14:42] <smartboyhw_> madeinkobaia: \o/ We have so many good wallpapers from the community. 
[14:42] <zequence> smartboyhw_: I'm sure madeinkobaia knows best himself what to focus on, being the art lead and all
[14:42] <madeinkobaia> zequence : You caught the changes perfectly well : )
[14:44] <madeinkobaia> zequence : Let me know when its on line, I am curious to see the result : )
[14:48] <zequence> smartboyhw_: Do you build the packages, and upload to a PPA first? How does it work?
[14:48] <zequence> ..or does someone else build it for you?
[14:49] <smartboyhw_> zequence: PPA or branch review… I always upload to the PPA and see whether that guy wants a bzr m.p. insteas
[14:49] <zequence> I had to personally meet someone to get my gpg signature signed, in order for it to be trusted when doing linux-lowlatency uploads
[14:49] <smartboyhw_> In this merge case, yes
[14:49] <len_1304> and how do you tell the build to be 32bit or 64 bit or both?
[14:50] <zequence> len_1304: One only builds the source package, and that's more about building the diff and changes. When uploaded to PPA, only the diff is uploaded, and the rest is built on the server, both arches
[14:51] <smartboyhw_> I like PPAs:P
[14:52] <zequence> len_1304: It's pretty straight forward. I'll set up a page for that, as soon as I've confirmed that we can proceed this way
[14:52] <len_1304> i'm getting confused already... I'm thinking about -settings and think what I'm working on is already src
[14:52] <len_1304> That should help make things clear.
[14:55] <zequence> len_1304: There are two kinds of packages. The source, and the binaries. When uploading, you only upload source. The binaries are built on the server. The Debian source package build includes some files that you probably recognize, *changes, *dsc, *diff, *orig. What you upload is really just the diff and the changes file, signed with your gpg signature
[14:55] <len_1304> Ya, that is what bzr is doing now.
[14:56] <zequence> The bzr branch is just for keeping track of changes. Also, you make changes to the debian folder
[14:56] <len_1304> I branch a package change it and bzr makes a diff and pushes it
[14:57] <zequence> Well, yes, the changes are documented in debian/changes
[14:58] <zequence> But, it doesn't become a package until you build it. The build instructions are in debian/rules
[14:58] <zequence> It's like a makefile
[14:58] <len_1304> I can build the binary from that branch so it is the source. If the package is built at the server what is a PPA for?
[14:58] <zequence> You can also build the source package from that branch
[14:58] <len_1304> I thought the ppa was for installable packages.
[14:59] <zequence> Both
[14:59] <zequence> Just like the repos
[14:59] <zequence> I mean, main, univers, etc
[14:59] <zequence> You have both binary and source packages tehre
[14:59] <zequence> A source package is what you get when you do: apt-get source <package>
[14:59] <len_1304> So I shold be taking the branch and creating a set of deb src files (3 I think?)
[15:01] <zequence> Yes, you need to build the source package from the bzr branch
[15:01] <zequence> And, then, upload it
[15:01] <len_1304> Seems like a lot of work for some thing like settings where the src is effectively already the binary.
[15:01] <zequence> The gpg signature you use to sign it is like your ID
[15:02] <zequence> So, that is how people can see it was really you who did the package
[15:02] <zequence> You can't install something, unless you make it into a package
[15:03] <len_1304> Yes. That part is obvious.
[15:03] <zequence> You don't upload the entire source each time either
[15:03] <zequence> Just the diff
[15:03] <zequence> ..which is signed
[15:03] <len_1304> same with bzr
[15:03] <zequence> well, sure, but it's not a Debian package. It's a bzr branch with Debian source in it
[15:03] <zequence> You can set up bzr branches to autobuild though
[15:04] <len_1304> To a source package or binary or both?
[15:04] <zequence> both
[15:06] <len_1304> I can learn whatever. First is setting up pgp. I need to do that on my other machine though.
[15:07] <len_1304> This one is a testing drive always changing
[15:09] <zequence> len_1304: I made short howto on that here https://wiki.ubuntu.com/UbuntuStudio/SetupDeveloperEnvironment#Create_a_GPG_Key
[15:09] <zequence> Similar ones exist a little here and there
[15:10] <len_1304> Ya, I have seen them, I will look at yours too. But I need to get ready to go out. I'm playing in a few hours.
[15:10] <zequence> Alright, I need some food
[16:42] <micahg> zequence: I don't see any reason to use PPAs for that
[16:43] <micahg> zequence: what problem are you trying to solve?
[16:43] <micahg> zequence: please don't use the kernel packages as standard fare, they are special
[16:56] <zequence> micahg: So, what you are saying to get packages sponsored, we stick to bzr branches?
[16:57] <zequence> micahg: Doesn't really matter. Even if building them is another step in learning how it all works
[16:58] <zequence> We can still keep our PPA for testing
[16:58] <zequence> or, a PPA
[16:59] <micahg> zequence: bzr branches, debdiffs, syncs from Debian
[17:00] <micahg> zequence: since you're a member of the Debian Multimedia packaging team, you can push stuff through there as well
[17:00] <zequence> micahg: This is just about our own packages
[17:00] <zequence> the ubuntustudio stuff
[17:00] <micahg> yeah, you want to test build locally or in a PPA to make sure things are fine
[17:00] <micahg> zequence: oh, yeah, sponsoring from the branch is best as it has the history
[17:01] <micahg> we should make it so core-devs can commit as well so that you have access to more sponsors
[17:02] <micahg> it requires creating/assigning a mailing list for the ubuntustudio-devel team
[17:02] <zequence> in launchpad?
[17:02] <micahg> yeah
[17:03] <micahg> if there's either an ML or an address associated with the team, it won't send changes to members
[17:03] <zequence> do I invite a team to ubuntustudio-dev?
[17:03] <zequence> ..for them to get access I mean
[17:05] <micahg> so, for https://launchpad.net/~ubuntustudio-dev , you need to set an e-mail address or create a mailing list so that the members aren't mailed directly anymore (so as not to spam core-devs) and then we can add the team
[17:05] <zequence> The team is called core-team?
[17:06] <micahg> it's ubuntu-core-dev or something, but first you need to fix up the studio dev team in LP before adding them
[17:06] <zequence> I'm creating the mail list right now
[17:09] <zequence> micahg: Isn't MOTU able to sponsor as well?
[17:09] <micahg> yeah, was thinking to just add MOTU
[17:10] <micahg> core dev is a member of MOTU
[17:11] <micahg> ok, I'll propose the addition and you can accept
[17:12] <zequence> I already added MOTU as a member
[17:12] <zequence> https://launchpad.net/~ubuntustudio-dev
[17:12] <micahg> oh, that works then, you have 150 available sponsors now :)
[17:15] <zequence> Well, hopefully I can get upload rights not too far into the future, and we'll have that problem solved
[17:29] <micahg> zequence: yes, but the packageset is much more than those few sources
[20:18] <len_1304> zequence, I am not sure what this new mailing list is for.
[20:31] <micahg> len_1304: the new ML is so that the members of the team aren't spammed with bug comments and what not
[20:31] <micahg> otherwise, you can't have MOTU as a member as most people don't care about the day to day stuff
[20:39] <len_1304> Ok thank you micahg Did you get my other note about settings?
[20:39] <micahg> Len-nb: no, sorry
[20:40] <len_1304> Settings needs to be uploaded
[20:40] <len_1304> It may have scrolled off the top of chat by now :)
[20:43] <micahg> len_1304: ACK
[20:43] <len_1304> Thankyou micahg 
[23:44] <zequence> len_1304: I made a more extensive description of the uploading to PPA process, as I'm kind of directing it towards beginners. But, you should find some useful info in there https://wiki.ubuntu.com/UbuntuStudio/UploadingToPPA
[23:47] <len_1304> Ok, I have figured out the pgp thing... Finally. Guess I am someone...
[23:48] <zequence> len_1304: Yeah, it's a little bit tricky at first :P
[23:48] <zequence> Even though, it's also very simple
[23:50] <zequence> I'm deleting the PPA that we had
[23:50] <zequence> The last package was for Karmic, so don't think anyone will miss it
[23:53] <zequence> len_1304: I set up this ppa now https://launchpad.net/~ubuntustudio-dev/+archive/devel
[23:54] <zequence> ppa:ubuntustudio-dev/devel
[23:54] <zequence> For our own packages, that we have in bzr branches, etc
[23:54] <zequence> Whenever we want to try one out, or if we decide to set up daily builds, or whatever
[23:54] <zequence> We could do that for all the bzr branches if we want
[23:55] <zequence> ..or I should check how that works more thoroughly first, probably