[w3ctag/design-reviews] What is this for and how is this different than a design review? (Discussion #793)

This section is intended for soliciting TAG input on small, quick, self-contained questions, with a more lightweight, casual process than a Design Review. There are no requirements for posting a question here, no need for writing an explainer, or answering any questionnaires, you can just ask. The tradeoff is that these are less "official": TAG members are posting as individuals, not expressing TAG consensus, and these questions are not added to telcon agendas (though they may influence future [design principles](https://w3ctag.github.io/design-principles/)). See [this issue](https://github.com/w3ctag/design-principles/issues/319) for further background on why this section was created.

Good topics for this Q&A section include:

- One-off, quick API design questions that emerge *while you are designing a feature*. These can be either things not covered by the [Design Principles](https://w3ctag.github.io/design-principles/) or things that are a judgement call per the Design Principles. For example:
  - Should we use an accessor or a method for X?
  - Should we name this attribute X or Y?
  - Should this CSS property inherit?
- Getting TAG input on a specific issue in a WG repo, for cases where the design review process would be too heavyweight but there is also no dispute to escalate.

Please note that :
- Discussions in this repo will not be added to call agendas (though they may influence future [design principles](https://w3ctag.github.io/design-principles/) and may be discussed as part of that process).
- Unless otherwise mentioned, TAG members are posting input as individuals, and their opinions do not necessarily express TAG consensus. You could even get conflicting answers between different TAG members, and it's up to you to decide which reasoning makes more sense for your use case.
- Please note that TAG members are under no obligation to answer questions here, but we do try our best to help. The less context your question requires to be understood, the more likely it is you will get a quick answer.

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

Message ID: <w3ctag/design-reviews/repo-discussions/793@github.com>