Jetpack/Features/2012-02-10

From MozillaWiki
Jump to: navigation, search

Details

  • Time: Friday, 2012 February 10, 9:05 - 9:50am PT (17:05 - 17:50 UTC)
  • Location:
    • Audio/Video: Jetpack Vidyo room
    • Audio Only:
      • US: +1-800-707-2533, password 369, conference number 99449
      • US/Intl: +1-650-903-0800 or +1-650-215-1282, extension 92, conference number 99449

Agenda

  • actions from previous meeting
    • dietrich to get adw and jetpack principals together to discuss SDK APIs in core Firefox
  • pdf.js as default addon
  • jetpack in core
  • apps initiative

Attendees

  • dietrich
  • mixedpuppy
  • myk

Minutes

dietrich gave this [talk at fosdem]

actions from previous meeting

dietrich to get adw and jetpack principals together to discuss SDK APIs in core Firefox

  • didn't happen
  • dietrich will discuss adw's proposal in jetpack discussion forum
  • dietrich will talk to gavin and mossop next week about timeline
  • proposal to allow addons to use modules from other addons
  • that would enable jetpack core to be packaged as default addon

pdf.js as default addon

  • pdf.js team had work week this week
  • produced a patch that integrates pdf.js as default addon
  • addon is not jetpack, but this is still a step forward

jetpack in core

  • timeline for jetpack in core uncertain
  • features that need to ship soon shouldn't hitch train to it
  • jhammel's work on testing firefox with addons installed will help
  • peptest to make it easy to write responsive tests will help

apps initiative

  • apps frontend features are currently in addon
  • descriptions/specifications of firefox feature are all over the place
  • we need to consolidate that information

web activities

  • mixedpuppy and dietrich talked about landing version being used by share addon
  • then benadida proposed rewriting it
  • we're shipping a feature in firefox that depends on it
  • it will be an experimental api that will be prefixed (navigator.mozActivities)
  • similar to intents, but with some differences
  • the registerProtocolHandler (RPH) apis have a whole nother set of issues
  • RPH is programmatic approach to registering protocol handlers for actions
  • a lot of issues with programmatic approach to registration that would be good to avoid
  • asa is fine with prefixed approach, allows api to change or be abandoned in future

Actions

  • dietrich to discuss adw's "jetpack in core" proposal in jetpack discussion forum
  • dietrich to talk to gavin and mossop next week about timeline for "jetpack in core"