Confirmed users
587
edits
No edit summary |
No edit summary |
||
Line 97: | Line 97: | ||
** Jetpack is a good code name, but maybe not a feature name | ** Jetpack is a good code name, but maybe not a feature name | ||
** At least, may make sense to rename "jetpack" object to "env" or similar | ** At least, may make sense to rename "jetpack" object to "env" or similar | ||
* Jetpack has been producing a set of APIs for feature developers to use. How stable are these right now? Does it make any sense to include some of them in Firefox itself for Jetpack to use so we can handle changes as Firefox is upgraded rather than Jetpack having to cope? | |||
* Is Jetpack having to use any ugly or private means to get at the functionality it requires in the platform that it might make sense for us to expose in some stable API? | |||
* Is there any part of the security model that it would be helpful to uplift into Firefox and perhaps make available for add-on developers using the full XPI route to use if they want to keep things safer? | |||
* Have the Jetpack team thought much about uplifting into Firefox and how you envisaged that progressing in the future? |