[10:19] <cub> basically the US team is 24/7 and cover all the globe?
[10:19] <cub> the US, Canada, Europe, Asia
[10:19] <smartboyhw> cub, yeah sure but I'm 6 hours ahead
[13:15] <OvenWerks> cub: A very loose 24/7... it is good to have a life too ;)
[13:16] <cub> sure, but when you sleep or live life..someone else is awake. :D
[13:16] <OvenWerks> sort of...
[13:17] <OvenWerks> we cover the globe, but are not a large bunch
[13:17] <cub> if not zequence seems to never sleep.
[13:17] <zequence> I like to sleep 8-9h, if I can :)
[13:18] <cub> according to the irc logs you seem to not do that very often. ;)
[13:18] <cub> since I got a baby I'm happy if I get 6 hours sleep.
[13:18] <zequence> my chat client is on 24/7. It's a irssi cle
[13:18] <zequence> ..client on my se3rver
[13:19] <OvenWerks> as is mine
[13:19] <zequence> I'm not using it only for chatting, but also for logging different channels
[13:20] <zequence> I have alerts for certain words, so I'm alerted if someone discusses some topics
[13:20] <cub> your own private PRISM
[13:21] <zequence> also, channels like #ubuntu-bugs-announce is good to monitor. I get alerts when there are linux-lowlatency bugs
[13:21] <OvenWerks> speaking of which, I will probably be doing a merge of the menus in the next few days.
[13:22] <OvenWerks> I think if no one finds any problems with it I will put up versions on my ppa for back to precise
[13:22] <cub> zequence, on another note, you are not leaning towards moving to Stockholm? The company I work for are looking for linux techs
[13:23] <zequence> cub: not really. I'm pretty rooted here, at least for the time being. no chance to do work from home? :)
[13:23] <cub> It should, but management like people on site
[13:25] <zequence> I'm getting some certificates for another 6 months at most, and after that, the plan is I'll try to find a job somewhere
[13:26] <OvenWerks> Managment people are odd ducks anyway...
[13:28] <smartboyhw> Hey zequence OvenWerks 
[13:28]  * smartboyhw is still bundled under KDE SC packaging:P
[13:29] <OvenWerks> Whats SC?
[13:31] <smartboyhw> OvenWerks, Software Collection aka the KDE desktop 
[13:32] <OvenWerks> Ah! You may want to make your own PPA for it. It is a lot easier to test.
[13:32] <smartboyhw> I have worked on 6 packages today:O
[13:32] <smartboyhw> OvenWerks, the Kubuntu team has a secret PPA;P
[13:32] <OvenWerks> That would work.
[13:33] <smartboyhw> Actually, this is the fifth one I'm working on. I do have a sixth.
[13:35]  * OvenWerks does one at a time
[13:35] <zequence> OvenWerks: I've put up a PPA for our development work here, so it would be good if you put the menu there, once you're ready to have people test it https://launchpad.net/~ubuntustudio-dev/+archive/devel
[13:35] <zequence> -default-settings is auto built once a day from source there
[13:35] <zequence> the meta needs to be built manually
[13:35] <smartboyhw> OvenWerks, I do do one at a time. I did 4 already.
[13:36] <smartboyhw> zequence, auto-built. Nice.
[13:36] <OvenWerks> That would be the place to put -menu packages for older studio versions too then
[13:37] <zequence> OvenWerks: backporting is a different issue though
[13:38] <zequence> we should set up a special ppa for backport testing
[13:38] <smartboyhw> +1
[13:38] <OvenWerks> There are not that many people who want it, but I think Luke is doing cinnamon on R
[13:38] <zequence> I assume the menu package doesn't need any changes for older releases
[13:39] <OvenWerks> No, just marked as P, Q and R
[13:39] <OvenWerks> One word difference in the changelog :P
[13:40] <zequence> I still want to separate development release work from SRU and backporting work
[13:40] <OvenWerks> OK
[13:41] <zequence> so, for backports https://launchpad.net/~ubuntustudio-dev/+archive/backport-testing
[13:41] <zequence> OvenWerks: but, if the menu is to be backported, that would mean changing -default-settings as well, right
[13:42] <zequence> so, that makes it a little bit more complicated
[13:42] <OvenWerks> No, I would not worry about that.
[13:42] <OvenWerks> This is more for those installing our metas on top of something else.
[13:43] <zequence> yet, you can install it on top of Ubuntu Studio too
[13:43] <OvenWerks> And it would work.
[13:43] <zequence> we would need to do a SRU on our -default-settings, and make it depend on the menu
[13:43] <OvenWerks> May not need to.
[13:44] <OvenWerks> unless we want to update the menu for P
[13:44] <zequence> Why do you want to test the menu for older releases then?
[13:44] <OvenWerks> I will work on -settings next for -menu integration.
[13:45] <OvenWerks> As I said only for those who want to use it on top of another DE/flavour.
[13:45] <zequence> the problem is if it conflicts with our -default-settings package
[13:46] <OvenWerks> I will test.
[13:46] <zequence> it will of course, if both are installing files with the same names that diff
[13:46] <OvenWerks> The menu itself is a different file
[13:46] <OvenWerks> in a different directory
[13:47] <OvenWerks> It does not replace the system menu
[13:47] <OvenWerks> It merges on top of it
[13:47] <zequence> Ok, well, one thing at the time then. First we make sure the development version is ok, then worry about backporting it
[13:48] <smartboyhw> R shouldn't conflict, nor should Q.
[13:49] <OvenWerks> What I will be doing (If I can) is basically reverting our system menu to stock xfce in settings and using the merge for our menu
[13:49] <smartboyhw> Not sure for R though.
[13:49] <zequence> Yeah, well, let's see when the packages are ready for testing :)
[13:49] <OvenWerks> P is the important one.
[13:50] <zequence> it's just that we are required to backport one release at the time, in sequence
[13:50] <zequence> so, beginning with R, then Q and finally P
[13:50] <OvenWerks> Ok
[13:50]  * OvenWerks has to go eat and get to work
[13:51] <OvenWerks> Bye now
[13:51] <zequence> see you OvenWerks 
[16:42] <madeinkobaia> Hi fellows
[17:57] <madeinkobaia1> I am twice here ? :-/
[17:59] <madeinkobaia1> Strange, I log out/in again...