Jetpack/Features/2011-12-16

Details

• Time: Friday, 2011 December 16, 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
  • myk to talk to joduinn again and get him to designate someone to dedicate time to addressing perf test issues
  • dascher to talk to bwalker about the priority of Jetpack Features to Apps (and, if this initiative is important, who is the point person) --> apps isn't blocking on jetpack as a feature delivery vehicle.
  • myk to invite benadida to next Jetpack Features meeting via Zimbra and email
  • myk to ask jrburke for his insights into issues with HTML page l10n proposal
  • myk to prototype HTML page l10n proposal to further investigate concerns
  • mixedpuppy to send technical overview of WebRT project to myk and gozala
  • mixedpuppy to send proposal for landing content injection code in core SDK
  • dietrich to email/talk to clee about attending these meetings (DONE 12/2)
  • myk to re-raise question of whether or not to continue these meetings at their next occurrence
• status of HTML page l10n prototype
• next steps on getting core Jetpack stuff into Firefox
• whether or not to continue these meetings given low participation to date
• whether or not to have a meeting on Friday, December 30 given impending New Year's holiday weekend

Attendees

• myk
• canuckistani
• dietrich
• mixedpuppy
• benadida
• dascher

Minutes

Actions From Previous Meeting

• myk to talk to joduinn again and get him to designate someone to dedicate time to addressing perf test issues
  • myk talked to joduinn, who didn't designate someone but explained how to get releng to address issues
  • first, talk to the release engineer on duty
  • then file bugs as appropriate

• dascher to talk to bwalker about the priority of Jetpack Features to Apps (and, if this initiative is important, who is the point person)
  • bwalker told dascher that apps isn't blocking on jetpack as a feature delivery vehicle
  • and a bunch of the core functionality has landed in nightlies
  • but apps integration into firefox is p1 for q1, the UI is still an addon, and dietrich would be surprised to see it rewritten in q1
  • -> dietrich to talk to bwalker to clarify plans for Apps UI integration into Firefox

• myk to invite benadida to next Jetpack Features meeting via Zimbra and email
  • myk invited him, and he is attending!

• myk to ask jrburke for his insights into issues with HTML page l10n proposal
  • myk talked to jrburke and others, who said jQuery works fine from resource: URLs but has issues with slashless URLs

• myk to prototype HTML page l10n proposal to further investigate concerns
  • prototyping underway, more details when we talk about "status of HTML page l10n prototype" agenda item

• mixedpuppy to send technical overview of WebRT project to myk and gozala
  • mixedpuppy sent overview to myk and gozala
  • it would be useful to be able to use Jetpack within a non-Firefox environment
  • i.e. the native XUL app bundles that the Apps project is creating
  • this needs some Jetpack platform changes
    • make it possible to specify custom app compatibility in install.rdf
    • make hidden-frame compatible with custom apps
  • it'd be worth having a conversation about this with Mike Hanson, maybe in January
  • -> mixedpuppy to file bug on making hidden-frame compatible with custom apps

• mixedpuppy to send proposal for landing content injection code in core SDK
  • mixedpuppy sent this (although it might have gotten lost in the zimbrapocalypse)

• dietrich to email/talk to clee about attending these meetings (DONE 12/2)
  • dietrich did so

• myk to re-raise question of whether or not to continue these meetings at their next occurrence
  • on the agenda!

status of HTML page l10n prototype

• prototyping is under way, and myk is making progress, but he doesn't have anything to show for it yet
• he initially thought to use a custom protocol handler, but custom protocols can have security boundary issues
• he's now looking into a stream converter, possibly in conjunction with a content sniffer
• it'd be useful for myk to talk to mak about his experiences using similar APIs to do some chromey stuff in contenty about:home

next steps on getting core Jetpack stuff into Firefox

• some folks met a few weeks ago
• meeting minutes: https://etherpad.mozilla.org/jetpack-in-firefox
• it seems like this should be a Q1 goal for Firefox team, Jetpack team, or both (shared goal)
• -> myk to talk to mossop and johnath about making it a Q1 goal to land core Jetpack stuff into Firefox

whether or not to continue these meetings given low participation to date

• concern that no one owns this proposal and is driving it to completion
• until we figure out how to make it an explicit goal, we're just laying the groundwork
• and the meetings aren't attracting a broad enough audience

• the big picture goal is to make firefox feature development more flexible
• development teams want it to make their work easier/faster/funner
• products team wants it to give them ability to ship features to select audiences
• several related outcomes
  • feature teams ship features as default addons
  • feature teams ship features as separate addons that can be updated independently of Firefox schedule
  • Firefox team ships core features developed using Jetpack platform
• if, when, and how to do this needs involvement at higher (director, VP) level

• some folks are unclear on the value proposition
• they see jetpack as the limited api for shallow, isolated integration
• especially since that was the original goal for the Jetpack project
• whereas this effort is about giving core developers a better platform for deep integration

• the short-term goal is to help Apps, Identity, Sharing teams ship features in Q1
• mardak helping benadida with Identity addon
• Identity addon ships first alpha next week, team intends make it really good next quarter
• jetpack api not quite sufficient yet (f.e. panel needs to persist per-tab)
• but once provably good, no reason to rewrite it as core code

• we should write up what we've learned so far and next steps
• we should continue these meetings, which seem useful enough for making progress on both short- and long-term goals
• -> dietrich to blog about what we've learned so far and next steps

whether or not to have a meeting on Friday, December 30 given impending New Year's holiday weekend

• no one wants a meeting; we're not going to have a meeting

Actions

• dietrich to talk to bwalker to clarify plans for Apps UI integration into Firefox
• mixedpuppy to file bug on making hidden-frame compatible with custom apps
• myk to talk to mossop and johnath about making it a Q1 goal to land core Jetpack stuff into Firefox
• dietrich to blog about what we've learned so far and next steps