[10/26/16] webperf group call @ 10AM PST

Last call's experiment with Hangout was a success, so we'll continue. Join
via:
https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg

We'll also be on IRC and keep our existing webex line [1] for backup. If
you're having trouble joining, hop on IRC and let us know.

--- Agenda

   - Review spec status / roadmap: bitly.com/w3c-webperf-status
   - Resolutions to publish new drafts for:
   - HR-Time L3 [2]
      - Performance Timeline L3 [3]
      - Resource Timing L3 [4]
      - Navigation Timing L3 [5]
      - User Timing L3 [6]


   - Resolutions for CR transitions for:
      - HR-Time L2 approved on last call, review next steps.
      - Publish User Timing L2 CR?
         - https://github.com/w3c/user-timing/issues/19
         - Publish Page Visibility L2 CR?
         - https://github.com/w3c/page-visibility/issues/25

         - *Note: Perf Timeline L2, RT L2, NT L2 still need some editorial
      work, I'm hoping to have these ready for next call.*


   - Other
      - HR-Time unload test case: https://github.com/w3c/hr-time/issues/32
      - Beacon tests and interop:
      https://github.com/w3c/beacon/issues/29#issuecomment-255882261
      - Long tasks + long input: same event?
         - https://github.com/w3c/charter-webperf/issues/31
         - https://github.com/spanicker/longtasks
      - Input Latency API: use cases, what we can/should provide, etc.

---

[1] https://www.w3.org/wiki/Web_Performance/Call_Information#VoIP
[2]
https://github.com/w3c/hr-time/issues?utf8=%E2%9C%93&q=milestone%3A%22Level%203%22%20
[3]
https://github.com/w3c/performance-timeline/issues?utf8=%E2%9C%93&q=milestone%3A%22Level%203%22%20
[4]
https://github.com/w3c/resource-timing/issues?utf8=%E2%9C%93&q=milestone%3A%22Level%203%22%20
[5]
https://github.com/w3c/resource-timing/issues?utf8=%E2%9C%93&q=milestone%3A%22Level%203%22%20
[6]
https://github.com/w3c/resource-timing/issues?utf8=%E2%9C%93&q=milestone%3A%22Level%203%22%20

Received on Tuesday, 25 October 2016 22:09:14 UTC