-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 We had an extensive conversation last April on fixing updates and a lot of bugs were filed and work was done. In light of v3, I'd like to re-open the discussion on this and see where we are.
Last year the conversation seemed to be centered around: * Making it easier to change the update channels (Developer menu now has this). * How to deal with vendor incentives while still providing options for users wishing to continue to use their devices. * Moving certified apps to privileged status by reworking the Settings API (which was completed AFAICT) so that we could update more of the default apps. I re-read the old thread and bugs and had a few questions/thoughts. Has anybody reached out to our partners and taken a survey of the ways they modify our code for their devices? If there are patterns (e.g. they all disable feature X) then maybe we should consider abstracting away that part and make it super easy for them to provide their own implementations. An abstraction opens the possibility of swapping their implementation with another implementation at a later date--like after the vendor has dropped support. What I'm getting at, is maybe there is a third option with vendors where we negotiate a "sunset clause" situation. The partners provide us with a signed app that "unlocks" their phones before they ship. They lock their phone down and ship. Then when the partner officially drops support (or otherwise authorizes us), we'll release the unlock app via FOTA update or through the marketplace. It would replace the swappable piece with the stock one and allow the user to change their update channel to whatever they want. This attempts to balance the partner's financial interests with the long-term interests of users. Plus it makes FxOS easier to customize by the vendors. - --dave -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJVEbQsAAoJEJ7v31qiCP4ggv8P/0H2JW7UNVb3VJv0R1Mgg1sn tkgsagAnY+Kw5U0KSgekW5+s6nyRqVDK3S5hsi8U0NOyWNKbbqqbQOB6/WbjB/KC uTSMfIGr8WkUqVJPG/NuQv8QykUdoEJ584MWNLlefZ8gI5/o3Jb2sAyInwG2blGa oCV9DUO5YrIYFZ2qfFpc5N0I6J/1jzRoTtiEj/cb6YnNbx2c36FGSuaEQgjAMLkT 6ZK9lpYCXuU5VVg0FK/G256bX+5YNbyx6CyuJJtlIqqVHiFTzlluTG8sTeufHZwC LUuG5G7xxf7AIf2uwjXG0uvRilgnI5R/zhY3gtukuPZZeYsCY0h+OAIMcMHevI7i xxFajNE3tfkgtsCukU0nCeH2p7NUL9hV0QOjvmiA8hZNweMrtBNihbjJvUqJDZQW Aqs7vsKDsAtKIv7MxbgWFM424eq3gzv+/PW5LbJ/NhlQbY11l2BSyoyUPqbt/0Vx LdByt3mGgj3ALGHJkSLMrQfxuwpjhdm3r6WsosfcR2lNofpU/lKgc0cHrcX7+nzd rl1ZemcT5TyWJzwGlS+WvHh2pfUlVFm4XIEje2gMevVkSIOGtQY/rTos+WskN77w oAuhBcwqtDp91EMo1S0yFvX2C/+pE1m8vZ1Skfv2/fYGJW0VUJedO2l3JKWG905n gdQtmfI7eBXX9CW3+jHC =uocG -----END PGP SIGNATURE----- _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
