While we're waiting for more details on exactly how we're going to sunset the FirefoxOS smartphone program, I think it is worth talking about what parts of the codebase can be re-purposed for use in other contexts.
For example: one of the explicit goals of our work to create FirefoxOS web components was that they would be useful on the open web. Would it be valuable to make a last push to convert our interesting bits of UX into web components hosted at https://github.com/fxos-components? That way some of our work could live on. (And even if web components never get adopted natively, they'll still be usable with polymer) As another example, many of our Gaia apps (such as the gallery, music and email apps) require special permissions and can't run on the open web today. But they probably could run as addons using chrome privileges, if we're willing to do the work to convert them. Is this something we should think about? Is there solid user value in creating an addon to scan, organize and play music from the user's ~/Music directory on their laptop? What about for photos? Are there parts of our codebase that are interesting enough to be worth releasing in their own github repos? The keyboard autocorrect engine, for example, or the gesture detector code in shared/js? I don't know enough about our gecko and gonk layers to know what might be valuable there. But I'd guess that things like the wifi management code could be valuable if converted to a node.js library (if something like that does not already exist.) And I wonder whether our RIL reference implementation is something that is valuable enough to package up and release as a standalone thing. Thoughts? David
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
