From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

WebAPI Meeting Details

  • Tuesday 2013-09-17 - 10: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 / SF-Golden Gate (3rd floor) / Toronto-Spadina
  • Join irc.mozilla.org #webapi for back channel

Notes will be taken on etherpad: https://etherpad.mozilla.org/webapi-meetingnotes


  • B2G in Oslo recap
    • worker work (async IDB (on shared workers), notifications, XHR, TCP, mozContact, event stuff, plumbing for all this (bholley, bz on this))
    • good discussions around event pages, notifications, data store, IDB in workers
      • outcomes: new method of data syncing for datastore, patches written; datastore should land preffed off in the next 2 weeks; questions around UX prompting
    • notification API: lots of use cases that current API can't address
      • Ehsan to gather issues and work with Anne/wchen on possible spec changes
    • inter-app communication API working for certified apps; will allow for homescreen<->music app working
    • 1.3: multi-SIM
      • agreed within Mozilla but community disagreement ... marcosc suggests not worrying about getting agreement on the API which will be used by such a small # of people
  • responsive images meeting in Paris
    • great outcomes (agreement among browser vendors including MS hopefully for IE12)
    • largescale websites and others provided great discussion topics
    • <img srcset will happen (initially only with dpr selection)
    • marcosc to speak with johns about what we're going to implement
  • Potential Summit open session ideas
    • Web APIs: a conversation between implementers and users -- Starting with the needs of developers, how can we use the fact that Mozilla includes both creators and consumers of APIs to help us build APIs that have empathy for devs, and maximally benefit from the platform capabilities.
    • Evolving Web APIs: Which APIs are at which stage of development, and which ones need what help (from use cases and design reviews to optimization and demos) (demos are good to explain APIs to a broad audience)
    • Fulfilling the promise of Web Apps: Given the need to compete with alternative security models, how should we combine the generative power of remixable client code with a domain-centric security architecture, also known as "how do web apps become maximally open and secure".