Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/server-timing (+1/-0/💬2)
  1 issues created:
  - PerformanceServerTiming entry always has a duration field even when the original header did not (by andydavies)
    https://github.com/w3c/server-timing/issues/95 

  1 issues received 2 new comments:
  - #95 PerformanceServerTiming entry always has a duration field even when the original header did not (2 by andydavies, clelland)
    https://github.com/w3c/server-timing/issues/95 




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/hr-time
* https://github.com/w3c/performance-timeline
* https://github.com/w3c/resource-timing
* https://github.com/w3c/navigation-timing
* https://github.com/w3c/user-timing
* https://github.com/w3c/beacon
* https://github.com/w3c/page-visibility
* https://github.com/w3c/preload
* https://github.com/w3c/resource-hints
* https://github.com/w3c/requestidlecallback
* https://github.com/w3c/device-memory
* https://github.com/w3c/paint-timing
* https://github.com/w3c/longtasks
* https://github.com/w3c/server-timing


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config