Details

• Time: Tuesday, 2012 May 15, 9:00 - 9:45am PT (16:00 - 16:45 UTC)
• Backchannel:
  • irc.mozilla.org #openwebapps
• Virtual Location:
  • "Mozilla Apps" Vidyo room
• Physical Locations:
  • Mountain View: 4K - Kung Fu
  • San Francisco: 7N - Noise Pop
• Audio-only Access:
  • +1-650-903-0800 or +1-650-215-1282, x92, conf#: 98652 (US/INTL)
  • +1-800-707-2533, pin: 369, conf#: 98652 (US toll free)

Agenda

• significant changes/updates
  • Desktop WebRT Status - See Bug Metrics section below
  • jsmith: Mobile web compatibility - Going after Google Apps
    • Heavy evidence of UA sniffing & webkit prefixes
• questions and concerns
  • myk: what is the "same origin policy" in the latest version of the Apps Security model?
    • anant: related to the above, what was the consensus in Jonas' thread on "One app per origin"? How can we go about allowing more than one app per origin?
  • jsmith: What are we doing with plugins for the desktop runtime in our first release? What are we doing in the future?
  • jsmith: What is priority for supporting OS X 10.5 with the desktop runtime?
  • jsmith: How does persona.org relate to k9o?
  • jsmith: When are firefox new tab & awesome bar integration features getting worked on for web apps?
  • jsmith: Activity on mozapps API bugs have been quiet - Should we get traction on them?
  • ianbicking: support library for app developers? What should it include, how should we get app developers to use it?
• roundtable
  • jsmith: Tackling the off-origin resources problem in desktop, android, and b2g web runtime in bug 752666
  • jsmith: Mobile web compatibility testing - Help us out!
    • See here for how to get started
  • jsmith: Linux community involvement for desktop web apps
  • jsmith: Localization review of the desktop web runtime - Worth looking into?
  • jsmith: Reminder - nominate bugs for k9o

Minutes

significant changes/updates

• desktop runtime metrics available
• a set of blockers on which we need to get traction
• there are more p1s (serious bugs) on the desktop runtime shell
  • geolocation
  • plugins
• install/uninstall seems to be doing pretty well

• Mobile web compatibility - Going after Google Apps
• a core pain point for Gecko
• using -webkit prefixed properties
• kev needham commented in a bug that google has a list of concerns
• jason is waiting on that list of concerns
• -> jsmith to ping kev needham and lawrence

• anant: submitted manifest and api propsal to webapps w3c working group
• repurcussion is that changes that result as part of standards process need to be converted into actionable items spanning multiple teams (runtime, mozApps DOM API, AITC)
• working group hasn't made any changes yet
• first of those changes might be relaxing one app per origin restriction
• myk: how about changes going in reverse?
• anant: bring them up in this meeting or send email to anant/sicking
• anant/sicking will take them to the working group
• anant/sicking are both in the working group and can raise issues there
• rags: timeline? anant: no timeline at the moment, no one is waiting on a candidate recommendation from the w3c; this is to describe the api we're using; might evolve over time

• rags: basecamp has a june 1 deadline, we need to make sure to take changes they need into account
• relationship between OWA manifest and appcache manifest;
• -> anant to add appcache manifest reference to the OWA manifest
• rags: allowing third-party authentication needs to happen by june 1 too, whether or not that needs a modification to the manifest

• sicking: one app per origin restriction, original reason was security
• don't need it from a security point of view
• don't necessarily need to implement it right now
• but we should be prepared to do so in the future
• would be a very nice capability change
• we should keep in mind that it might happen or likely will happen in the future
• we might need one or two small tweaks to the API
• hopefully very small changes

questions and concerns

myk: what is the "same origin policy" in the latest version of the Apps Security model?

• it's the standard same-origin policy

anant: related to the above, what was the consensus in Jonas' thread on "One app per origin"? How can we go about allowing more than one app per origin?

• was hoping to do this soon
• first of many changes that may happen as a result of the standards process
• should we do it? if so, when?
• myk: mhanson should answer the first question
• if we do it, sooner rather than later
• rags: don't think it's going to happen sooner; use workarounds (subdomains, kev needham's workarounds)
• rags: as it stands right now, not going to happen for basecamp

• anant: there's a dependency from the b2g side
• certified apps are served off same domain with different launch paths
• ianbicking: b2g says it's fine the way it is
• folks meeting later today about this
• jst: issues in appcache implementation on one app per origin
• myk: sounds like we shouldn't do it yet
• sicking: we can make some minor api changes to accommodate
• -> sicking to email dev-webapps with changes that are required

What are we doing with plugins for the desktop runtime in our first release? What are we doing in the future?

• rags: for k9o, flash must work on platforms where we support flash
• what about click to play?
• let's talk about it separately
• jst: i don't think we have a way to whitelist flash support
• what about netflix, which uses silverlight?

What is priority for supporting OS X 10.5 with the desktop runtime?

• it's whatever we do for desktop Firefox

How does persona.org relate to k9o?

• https://wiki.mozilla.org/Kilimanjaro/ProductDraft
• Related Bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=748962
• https://bugzilla.mozilla.org/show_bug.cgi?id=748977
• discovery in firefox will be via the new tab page
• the implementation of the new tab page might be a persona.org page
• persona.org will have a standalone dashboard
• jennifer: persona.org will have list of apps to uninstall/access
• also it will have contacts list
• a bunch of other things will be added, not sure what
• idea is that it'll be where everything will be
• and you can manage things like perhaps browserid email addresses
• advertising? no just existing apps

Activity on mozapps API bugs have been quiet - Should we get traction on them?

• supporting relative URLs in install path of mozapps api
• ones that are flagged with k9o ?
• that's the right thing to do
• https://bugzilla.mozilla.org/buglist.cgi?list_id=3087768;field0-0-0=cf_blocking_kilimanjaro;resolution=---;query_format=advanced;type0-0-0=equals;value0-0-0=%3F;component=DOM%3A%20Mozilla%20Extensions;product=Core

support library for app developers? What should it include, how should we get app developers to use it?

• we've talked about it before, but how should we get it started?
• f.e. none of the paid apps make you pay
• there are probably other things to do to make basic apps work better
• this is part of the developer experience
• should talk to kevin dangoor and kev needham
• startup library on MDN in draft form: https://developer.mozilla.org/en/Apps/App_start-up_library

• Tracking Mozillian performance against KPIs
  • Mac v. Windows platform performance
  • Any areas where Marketing can push
• getting feedback; two UX issues that we already knew about
• there were a couple crashes
• linux was an issue
• -> myk to send email to Dan and/or schedule call to go over quantifiable KPIs for Mozillians release

Actions

• -> jsmith to ping kev needham and lawrence about google's list of concerns wrt. Google Apps
• -> anant to add appcache manifest reference to the OWA manifest
• -> sicking to email dev-webapps with minor api changes he has identified
• -> myk to send email to Dan and/or schedule call to go over quantifiable KPIs for Mozillians release