=== JanC_ is now known as JanC [09:25] alan_g: I think we want people to run miral-shell [09:25] when they try clients.. [09:25] or unity8 directly [09:25] so in some way mir demo servers give the wrong impression right now.. [09:25] agreed [09:26] which does not make the documentation wrong.. [09:26] just thinking that we should have a disclaimer there .. [09:27] I was planning to blog about it [09:27] Which documentation? [09:29] the intro documentation.. http://unity.ubuntu.com/mir-docs/0.25/using_mir_on_pc.html .. and http://unity.ubuntu.com/mir-docs/0.25/building_source_for_pc.html [09:32] Sure, that could do with a refresh. Like you say the docs reflect what's in the lp:mir project, not what we've done that is useful [09:32] yes [09:33] So there are two cases: [09:34] 1. testing client toolkits etc. against Mir servers - "just install miral-examples and use miral-shell" [09:34] 2. writing servers - "use libmiral-dev" [09:34] yes [09:38] We should add a couple of paragraphs to those docs, check where the 0.25 release is at, and (maybe) "cherrypick". [09:39] You want to write them? Or should I add to my list? [09:45] alan_g: I can do that.. do we generate miral docs somewhere? [09:47] not currently - it hasn't felt worth the effort of setting up automation for miral as we plan to roll it into lp:mir at some point. [09:49] Once the Unity8 integration has settled down we won't need to release it so often and can progress that. [09:52] Meantime, I guess http://voices.canonical.com/alan.griffiths/category/miral/ is the least bad option. === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === dandrader is now known as dandrader|afk [17:09] anpok_: the blog post I mentioned: http://voices.canonical.com/alan.griffiths/2016/11/25/testing-for-mir/ === dandrader|afk is now known as dandrader