Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/navigation-timing (+0/-0/💬2)
  2 issues received 2 new comments:
  - #126 Possibility to get the HTTP status code from the Response Header ? (1 by mmocny)
    https://github.com/w3c/navigation-timing/issues/126 [enhancement] 
  - #124 What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? (1 by wanderview)
    https://github.com/w3c/navigation-timing/issues/124 

* w3c/preload (+1/-0/💬0)
  1 issues created:
  - Link header processing (by annevk)
    https://github.com/w3c/preload/issues/148 

* w3c/server-timing (+0/-1/💬1)
  1 issues received 1 new comments:
  - #65 Using Server-timing to carry TraceID (1 by yoavweiss)
    https://github.com/w3c/server-timing/issues/65 [question] 

  1 issues closed:
  - Using Server-timing to carry TraceID https://github.com/w3c/server-timing/issues/65 [question] 




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