WebAPI/2014-06-24

From MozillaWiki
Jump to: navigation, search


« previous week | index | next week »

WebAPI Meeting Details

  • Tuesday 2014-06-24 - 8:00 am Pacific
  • Dial-in: conference# 98413
    • People with Mozilla phones or softphones please dial x92 Conf# 98413
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98413 (max 48 users at any time)
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 98413
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 98413
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 98413
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 98413
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 98413
    • UK/London: +44 (0)207 855 3000, x92 Conf# 98413
    • FR/Paris: +33 1 84 88 37 37, x92 Conf# 98413
    • sip:conf98413@mozilla.com or, for some clients, sip:conf98413@anonsip.scl3.mozilla.com (may not work for all rooms)
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number
  • WebAPI Vidyo Room / London-Allo Allo / Toronto-Spadina
  • Join irc.mozilla.org #webapi for back channel

Notes below archived from etherpad: https://etherpad.mozilla.org/webapi-meetingnotes

Notes

  • Service Workers shindig in SF this week
  • Ehsan's intern Roshan Vid
    • going to work on prerendering in FxOS and desktop \o/
  • Web Activities
    • W3C (DAP) is interested and it's in their charter
    • from what we hear, Google and others are interested
    • annevk is planning on beginning on this in August
  • Special guests today
    • David Bialer (Product Manager for apps, marketplace, etc.)
      • partner API requirements
    • Ian Bicking (Engineering Manager in Cloud Services)
      • services requiring DOM APIs
    • Myk Melez
      • interested in cross-platform APIs, notably a unified menubar API (like OS X or Unity menus, but unlikely to be of interested on desktop)
      • existing proposal to extend <menu> to use OS menu where possible
      • Myk thinks people are most interested in doing this in standalone (own window, own process, notably Android "ActionBar" (see below)) web apps, not in browser UAs
      • Marcos cautions that the trend with web development has been to maintain unique experiences and avoid too much OS tie-in
      • Myk notes (and Marcos agrees) that there are use cases where native affordances would be useful for web apps; only 2 he knows of right now:
        • on desktop: menu bar
        • on android: action bar
  • David B asked on marketplace-dev about having a single link to a web page / a packaged app and re-iterates his question here
  • Ian notes that they've started another iteration on server side push stuff