[00:50] <zequence> I'm going to start a Ubuntu Studio ppa where we have fixed packages that yet haven't been SRUd
[01:48] <micahg> zequence: can I ask what you're trying to accomplish with the PPA?
[01:53] <zequence> micahg: Give users the possibility to use packages that have been fixed but yet not been SRUd
[01:53] <micahg> zequence: yes, but why are they not being SRUd (I'm wondering if there's some breakdown somewhere we can fix)
[01:54] <zequence> micahg: The SRU process takes a bit of time
[01:54] <zequence> months as it seems
[01:56] <micahg> zequence: should take about 2 weeks if everything is ready from upload to get to -updates, 8-10 days if the SRU queue isn't backed up
[01:56] <zequence> bug #956438
[01:57] <micahg> if you'd like people to test the fixes without -proposed, that's fine, but I'd like to see more stuff pushed through SRU if it's needed (I was thinking of joining the -sru team at some point, but stopped having time)
[01:57] <zequence> I haven't prepared packages for 12.10 and 12.04 though
[01:57] <micahg> there's nothing there indicating it's ready for SRU aside from the bug tasks
[01:57] <micahg> right :)
[01:58] <micahg> something like that can go into the sponsorship queue and you can ping a patch pilot in -devel if it
[01:58] <zequence> But no one has informed me of anything not being right
[01:58] <micahg> s not addressed in a timely fashion
[01:59] <micahg> bug tasks means someone that wants to fix it, can, and they then submit it through the sponsorship process
[01:59] <micahg> so, nothing wrong per se, just that you shouldn't be shocked that nothing has been done with it
[02:00] <zequence> I pinged someone in -bugs
[02:00] <zequence> That got the process started
[02:00] <micahg> well, that'll get you bug tasks, not much more
[02:01] <zequence> I was following the instructions written on the wiki page
[02:01] <micahg> the SRU pagE?
[02:01] <zequence> https://wiki.ubuntu.com/StableReleaseUpdates
[02:02] <micahg> you're at step 5.2 :)
[02:05] <zequence> Well, I wasn't clear on the the details of the process
[02:05] <zequence> I'll have a go tomorrow
[02:07] <micahg> ok, I'm here to help if I can
[02:09] <zequence> micahg: thanks
[02:54] <holstein> Len-nb: i use jamin on the way out of ardour.. as an insert
[02:54] <holstein> Len-nb: sometimes, i use it sandalone on the way out of other things
[03:23] <Len-nb> holstein, where would it make the most sense to have it in the menu?
[03:24] <Len-nb> Would it be hard to find in an effects sub menu?
[03:24] <holstein> Len-nb: i think that would be fine
[03:24] <holstein> i always add a flag anyways. so it doesnt auto connect to outputs
[03:25] <Len-nb> Should we do that to more of the standalone stuff?
[03:25] <Len-nb> We can request changes to the desktop files upstream holstein 
[03:26] <Len-nb> I would thnk it doesn't make sense for JAMin to auto connect anyway.
[03:27] <holstein> depends
[03:28] <Len-nb> It doesn't make sense to auto connect for one use out of four
[15:39] <zequence> Len-nb: I think applications should all have a setting for disabling auto connect. For one thing, not everyone wants apps to connect to 1-2
[15:40] <zequence> and there are ways to make custom auto connects
[15:40] <zequence> Probably people want auto connect by default, but have the ability to disable it
[15:40] <zequence> ..for a lot of apps, not all
[15:45] <Len-nb> I agree
[15:46] <Len-nb> I use inputs 9-10 ... auto connecting to 1-2 is not very useful
[15:47] <Len-nb> zequence, from what I have heard from jack devs, auto connect is considered "rude" (not their words, but my paraphrase)
[15:50] <Len-nb> zequence, is there any way of renaming jack ports? not just in qjackctl, but so that all apps see the new names.
[15:55] <Len-nb> zequence, re backdrops: While we have asked for backdrop submissions, we have not given any guidance.
[15:56] <Len-nb> I would suggest a paragraph or two that gives the backdrop artist an idea of what we are looking for.
[15:56] <zequence> Len-nb: This time around, I don't think we can get much further on the artwork. And I will make a point about this tomorrow
[15:56] <Len-nb> The idea of getting out of the way and not distracting while looking good.
[15:57] <Len-nb> I would suggest just including anything properly licensed to look
[15:58] <zequence> For the next release, we need to have rules for this. Because of the shot time period, I felt putting up a unorganized wallpaper submission thing would be a bad idea on anything else than our -devel mail lsit
[15:59] <zequence> short*
[15:59] <Len-nb> Ya.
[15:59] <Len-nb> I have started working on a list for 13.04+1
[16:00] <Len-nb> I will post it later today... or should I wait?
[16:00] <zequence> Let's wait until this release is out
[16:00] <Len-nb> I think our stuff for 13.04 is done though
[16:00] <Len-nb> Soome of it is just defining work flows.
[16:01] <Len-nb> Some is ongoing.
[16:01] <zequence> I would still rather wait at least for a while, and then start a periof of organized planning, which we also announce
[16:01] <Len-nb> good. I will work on it in private then.
[16:02] <Len-nb> The binary I was referring to yesterday was an image.
[16:02] <Len-nb> the diff seems to have subtracted one image line by line and then added the other the same way.
[16:03] <Len-nb> Maybe that is how it works.
[16:03] <zequence> The diff is only text, AFAIK, so probably not helpful when binaries are involved
[16:03] <zequence> Better to create a bzr branch
[16:04] <Len-nb> Do they use those in debian?
[16:04] <zequence> No, probably mostly git
[16:04] <zequence> In which case, you could create a tar ball, but better ask the Debian guys
[16:04] <Len-nb> Neither the debian or the ubuntu package have a bzr branch
[16:05] <Len-nb> This is for hexter, it looks like they have just taken the original src and added a debian directory
[16:06] <zequence> That's usually how it works
[16:06] <zequence> debian/rules has instructions for some things, including how to build it
[16:07] <zequence> the debian dir really has all of the package info in it
[16:07] <Len-nb> How do I know who to talk to? There is a list , does Alessio Treglia sound right? 
[16:07] <zequence> pkg-multimedia is a good list
[16:07] <zequence> There's also a irc channel, but it's not on freenode
[16:08] <zequence> OFTC
[16:08] <Len-nb> I made a patch but don't know how to submit.
[16:08] <zequence> channel #debian-multimedia
[16:08] <Len-nb> I try those things
[16:13] <zequence> Len-nb: usually when you get the source to a package, using "apt-get source", you can see where the git tree for the package is
[16:13] <zequence> In the case of hexter git://anonscm.debian.org/pkg-multimedia/hexter.git
[16:14] <zequence> Becoming a debian multimedia member gives you upload rights
[16:14] <zequence> Not the same as getting Debian upload rights
[16:14] <zequence> Or, I should say, you get the right to push code
[16:16] <zequence> I think the one most important thing to learn, in order to be really helpful, is probably learning about Debian packagin, the policy and the tools
[16:18] <zequence> Len-nb: Another source for info is http://packages.debian.org/source/sid/hexter
[16:19] <zequence> You can find the adress to the git tree at the bottom
[16:26] <zequence> Well, learning git might be a good idea too :)
[16:26] <Len-nb> Ya it would.. there are some apps that use it for backup and versioning.
[16:27] <Len-nb> NAMA, some people use it for ardour too
[16:28] <Len-nb> I did already DL the debian hexter src packages.
[16:28] <Len-nb> That is what i was using to diff against
[16:30] <zequence> git is very useful to make diffs too
[16:30] <zequence> But, not sure if you can make a usable binary diff. Should be possible. I just don't know how
[16:35] <zequence> anyways, better ask the MM team