On 17 August 2016 at 05:05, Kyle Huey <m...@kylehuey.com> wrote: > s/moved out/deleted/ > > This is a complicated subject caught in a variety of internal > politics. I suggest you raise it with your management chain ;)
It's really not that complicated and there's no need to be so Machiavellian about it :) As discussed in the public B2G Weekly <https://wiki.mozilla.org/B2G/Meeting> meetings, the B2G community want to remove ~30 APIs (~10 of which they have already removed) from Gecko, but keep ~3 chrome-only APIs and the Gonk widget layer which are still in use by the B2G open source project. Some module owners from platform want to go further by removing all B2G-related code from mozilla-central, requiring the B2G community to fork Gecko if they want to continue. They feel the B2G code is getting in the way of other important platform work. The issue has been escalated up the module ownership chain as per Mozilla's governance system and a decision will be made and communicated in due course. I think Marcos' suggestion is a good one. It seems like a good idea to clearly separate standard web APIs from chrome-only APIs which are not on a standards track (e.g. the Browser API which Firefox is using). Ben _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
