WebAPI/2013-11-26
From MozillaWiki
< WebAPI
« previous week | index | next week »
WebAPI Meeting Details
- Tuesday 2013-11-26 - 8:00 am Pacific
- Dial-in: Audio-only conference# 98413
- People with Mozilla phones or softphones please dial x4000 Conf# 98413
- US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 98413
- US/California/Mountain View: +1 650 903 0800, x4000 Conf# 98413
- US/California/San Francisco: +1 415 762 5700, x4000 Conf# 98413
- US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 98413
- CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 98413
- CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 98413
- UK/London: +44 (0)207 855 3000, x4000 Conf# 98413
- FR/Paris: +33 1 84 88 37 37, x4000 Conf# 98413
- 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
- https://github.com/slightlyoff/ServiceWorker/ if you haven't seen it
- nsm working on it, bent reviewing some patches
- annevk notes that Apple & MS are potentially interested but want to see performance numbers
- currently there is no formal spec and some things still seem open to discussion
- limit scope for a Service Worker to a single origin as a starting point?
- TPAC recap
- annevk has nothing worthing mentioning here but ask him if you have questions
- http://www.w3.org/2013/11/TPAC/
- https://wiki.mozilla.org/WebAPI/XHRBatch
- feedback needed
- Can we add sychronization functions into the Messaging APIs or we have to insist on our proposed DataStore API?
- https://etherpad.mozilla.org/9MiQ4VWKSO
- feedback needed
- New meeting time?
- Andrew going to propose alternating times ... watch for email
- http://www.timeanddate.com/worldclock/meetingtime.html?iso=20131126&p1=241&p2=224&p3=250
- annevk brings up the somewhat meta question about standardization of in-flux FxOS-"specific" ("first" may be a better word choice here) APIs
- no good answers here
- have an in-person conversation at next work week
- get "higher ups" involved in conversation
