Thanks Jonas for introducing the Mulet! The meta bug to track Mulet's development is https://bugzilla.mozilla.org/show_bug.cgi?id=961745 I'm trying to post a new comment every time there is a major update in this bug.
I have many patches, most of them are too hacky to be landed as-is, in a personal git branch over here: https://github.com/ochameau/mozilla-central/tree/mulet (For now, you have to build Firefox target with --enable-mulet option in your mozconfig, and you need to pass a gaia profile when running firefox) Our current challenge is to figure out how to build such mixed up species, any build system tip is welcomed on https://bugzilla.mozilla.org/show_bug.cgi?id=961745 Otherwise, I see many over-expectation about the Mulet. The Mulet is only about merging b2g desktop and Firefox. So that it shouldn't introduce anything new from either b2g desktop or Firefox. We won't be running more "device code" (like APZ, widget code,...) than b2g desktop. Actually, ensuring that we run more "device code" doesn't depend of the Mulet. You can already improve that right into b2g desktop and the Mulet should automatically benefit from it. So if anyone is willing to jump on the "improve our desktop environment" train, please feel free to contribute without waiting for the Mulet! Anything that can make our desktop runtime act like our device runtime is a big win for contributors, gaia developers and automatic testing!
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
