[02:02] bregma: Are we skipping the hangout? [02:02] camako, bschaefer ^ [02:02] umm i think so [02:02] duflu, i think its just me and you around [02:03] And then more === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === JanC_ is now known as JanC [16:48] alan_g: ping [16:48] mariogrip: ? [16:55] alan_g: I saw your post "a-new-hope", and about canonical maybe continuing mir, and at the same time i'm trying to create a wayland platfrom in mir. but i'm then wondering if I should stop that and keep using mir instead of having mir on top of wayland, since what we dont want is to maintain a display server on our own. And do you know if the android [16:55] platform would also be maintained? [16:59] mariogrip: at the moment I don't know. [17:00] Canonical hasn't had practice at redundancies and information isn't flowing well. [17:01] In particular I don't know if any of the proposed IOT projects would use the android stack. [17:02] unlikely (but still possible) [17:02] right, i'm also a bit worried that android would not prioritized [17:03] not only that ... i doubt anyone at canonical will look at hybris in the future [17:03] so even if the Mir bits keep working, hybris integration will be in possible limbo [17:04] mariogrip: sorry, I gotta go just now. === alan_g is now known as alan_g|EOD [17:04] alan_g: no problem [17:04] ogra_: well, libhybris we can manage since we are not alone on that, but maintaining our own display server is a bit too much [17:05] well, the thing is that you need to maintain the hybris integration of Mir ... neither mir alone or hybris alone [17:05] mir itself ... at least in form of the mir-kiosk snap will surely persist ... but i dont know if there will even be any development [17:06] or if it will just go into "maintenance mode" directly [17:06] right, that's what im worried about that libhybris will change and mir breaks [17:06] it does what it is supposed to do ... (display a single standalone kiosk app) ... so not sure there will be any additional investment [17:07] that's why i'm trying to create this wayland platfrom in mir, that way we dont have to maintain the part that talks with libhybris === chihchun is now known as chihchun_afk [20:10] mariogrip: libhybris is surprisingly stable. I think you are creating more work for yourself by using wayland as an abstraction layer here [20:10] mariogrip: because ultimately, you would have to maintain hybris anyway [20:41] tvoss, well, if the hal stack changes and hybris gets adjustments for that you usually need to adjust Mir as well ... [20:42] ogra_: sure, but you would need to patch thewayland adaptation layer, too [20:42] given the amount of maintainers that care for Mir on hybris ... [20:42] tvoss, upstream will fix all wayland issues [20:42] since they use wayland [20:43] ogra_: upstream of what? [20:43] but nobody will fix the Mir side [20:43] of hybris [20:43] ogra_: sure, but the assumption is that the wayland bits would stay untouched and that the abstraction layer in Mir would need changes either [20:44] ogra_: just saying that introducing an abstraction layer at that level will likely just move the problem [20:44] indeed [20:44] but you add another abstraction that probably makes it easier [20:45] i.e. if the upper side of wayland doesnt change you dont need to adjust Mir ... and the lower side of wayland will be managed by upstream anyway [20:46] sure, that's a risky bet, though [20:46] (i'd actually be more concerned about the performance impact ... maintenance wise it could be less work after all ) [20:48] ...but yeah, based on assumptions :)