Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/performance-timeline (+0/-0/💬1)
  1 issues received 1 new comments:
  - #85 Would like a precise way to map PerformanceTimings to FetchEvent (1 by clayw)
    https://github.com/w3c/performance-timeline/issues/85 

* w3c/user-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #19 Transition Level 2 to CR (1 by igrigorik)
    https://github.com/w3c/user-timing/issues/19 [w3c] 



Pull requests
-------------
* w3c/user-timing (+1/-1/💬2)
  1 pull requests submitted:
  - editorial tweak (by dret)
    https://github.com/w3c/user-timing/pull/42 

  1 pull requests received 2 new comments:
  - #42 editorial tweak (2 by yoavweiss)
    https://github.com/w3c/user-timing/pull/42 

  1 pull requests merged:
  - editorial tweak
    https://github.com/w3c/user-timing/pull/42 


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