[w3ctag/spec-reviews] Question: Should spec-review discussions live inside respective spec's repository? (#112)

### Problem:
A developer who actively follows specifications issues was not aware of a potential issue with a specification.

### Description:
I actively follow the repositories of specifications that I'm interested in such as [Fetch](https://github.com/whatwg/fetch), [webRTC](https://github.com/w3c/webrtc-pc), and [ServiceWorker](https://github.com/slightlyoff/ServiceWorker) as to read issues with the specifications and any new proposals.

I only found out today about this repositories existence due to a colleague who is in the TAG and asked for opinions on the [Fetch API "WithCredentials" flag issue](https://github.com/w3ctag/spec-reviews/issues/76).

### Proposed Solution:
If a specification already has it's own repository (on Github or similar) which can have issues created, create an issue in it's repository about the potential issues found during a spec-review. I imagine it would get more community involvement as developers who are interested in the spec may be watching the repositories issues.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/112