[13:16] <OvenWerks> zequence: I don't know if you saw any of it or not. Xubuntu had a meeting yesterday and the the logs would be interesting if you haven't already.
[13:18] <OvenWerks> zequence: much talk about MIR, mostly about how it works (or doesn't) and how ready it is likely to be for 13.10.
[13:19] <OvenWerks> zequence: Xubuntu will be deciding on XMIR/xorg mid August.
[13:21] <OvenWerks> zequence: going into the future, Ubuntu has said MIR will be _the_ X that is supported.
[13:23] <OvenWerks> After 13.10, Canonical intends not to support xorg. I do not know that is a problem. We use a lot of SW now that is in the Ubuntu repos, but not supported.
[13:26] <OvenWerks> zequence: XFCE has no plan to ever support or write a MIR back end. There are very few devs (two?) and there is not enough time etc.
[13:29] <OvenWerks> What this means is that come 14.04, when XMIR is to be replaced with MIR, Xfce's experience with MIR's X compatability will be a good indication for Studio if our SW will work with MIR or not.
[13:31] <OvenWerks> It will also be a good indication if there will be performance issues of the translation layer in MIR that takes X commands and tells MIR how to render them.
[13:33] <OvenWerks> I would suggest that going forward, Audio will become less of a testing priority and video/graphics/GUI will require more of our attention.
[13:38] <OvenWerks> That is, we will need to spend more time testing video applications, particularely KDE based apps. (which should still work with MIR)
[13:40] <OvenWerks> One question I have not even seen asked, is if there is any thought given in The MIR group to supporting/translating wayland interfaces... where the rest of the Linux community and SW are going.
[13:47] <zequence> OvenWerks: My understanding is that xorg will be community supported from there on. How good/bad that is, I have no clue - and what that will do to the other flavors in the long run, but since we always have the choice to use something else, or whatever works, we won't of course be technically affected, like some of the other flavors
[13:48] <zequence> We could engage in the problem, to give opinions and support to the others. We could play a role in the community.
[13:50] <zequence> Me, personally, won't have the resources to add much to it. And my goal is really to understand the maintenance infrastructure better, packaging, ISO building, seeds, etc
[13:50] <zequence> and how to adapt Ubuntu Studio to other flavors
[13:51] <zequence> I've been thinking about the possibility to add us to other flavor installers, at least the audio workflow
[13:52] <zequence> already my goal is to change from audio group to something else, and make it default on all flavors, so jack always works in realtime when installed
[13:53] <zequence> some of these things just need to be organized, and the technical aspects solved, and then try push for the change
[13:54] <zequence> was disconnected from the internet for about 24h, so again, not able to get much done :P
[13:55] <zequence> by adding us to other flavors, I don't mean the audio applications, just the core components to make any flavor audio friendly - kernel, settings and maybe jack
[19:56] <Mish> zequence: I've made some icons with colours. They are in here  ---   https://www.wuala.com/Mishrito/Icons/?key=CRBaTkk2DEln
[19:56] <Mish> They are for Audio and Graphics and I took the colours from the slideshow of the UBS homepage you showed me
[19:57] <Mish> There are two versions of each, one with the object and one with the corresponding letter
[19:58] <Mish> But that probably wouldn't work out since I'd be stuck at photography and publishing since both start with P
[19:58] <Mish> but I put it there anyways so you can see what it looks like
[19:59] <Mish> Is it similar to what you had in mind?
[20:05] <zequence> Mish: I thought your original icons looked quite nice, so I was just imagining those with colored backgrounds. As for the content of the image, the headphones, brush, etc, I suppose I imagined those white, just as they are originally. If you'd like suggestions for colors, I could have a moment to think about that, but otherwise, just choose which ever ones you feel is right yourself.
[20:05] <zequence> That's just how I pictured it. Doesn't matter what it ends up being, as long as it works :)
[20:12] <Mish> So just the old icons with coloured background?  Ok I'll do that. And I'll just take the colours from that slideshow for consistency
[20:12] <zequence> Mish: Don't worry about the slideshow. Those are really random
[20:13] <Mish> So can they be changed easily?
[20:13] <zequence> I'd rather create a more sensible set of colors, and later adapt the slideshow to those
[20:13] <zequence> We just create new artwork for that later, and also, we could use the colors for our workflows in other situations too
[20:13] <zequence> like in documentation, or the feature tour
[20:14] <zequence> the choice of colors might be a really interesting one, especially as it seems some colors have very different meaning in different cultures
[20:15] <zequence> maybe they don't need to make sense, just look pretty, I don't know
[20:16] <zequence> photo could be red, or black (like film), audio could be blue or red (like the rec button). publishing could be white as paper (but then the content would need to be black), or yellow, etc
[20:17] <zequence> the classic blue is a nice blue, I think. I would start with that, and make the other colors have similar strength in color
[20:17] <zequence> Mish: I used three colors for our wiki https://wiki.ubuntu.com/UbuntuStudio
[20:17] <Mish> with colours the main thing would be to make them look good in both light and dark environments. I've been pained by so many apps, mostly java apps using SWT that don't respect GTK+ apps properly and end up forcing white backgrounds despite me having a dark GTK theme, making text sometimes unreadable and graphics look ugly
[20:18] <zequence> not sure if that blue is the classic one, actually, but probably close
[20:19] <Mish> for that reason I tend to avoid java apps
[20:20] <Mish> ok cool got it