- From: Btaxxpress <notifications@github.com>
- Date: Tue, 02 Jul 2024 10:25:20 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/972@github.com>
こんにちは TAG-さん! I'm requesting a TAG review of [feature name]. [One paragraph summary of idea, ideally copy-pasted from Explainer introduction] - Explainer¹ (minimally containing user needs and example code): [url] - User research: [url to public summary/results of research] - Security and Privacy self-review²: [url] - GitHub repo: [url] - Primary contacts (and their relationship to the specification): - [name] ([github username]), [organization/s] (repeat as necessary, we recommend including group chairs and editors in this list) - Organization/project driving the design: [organization and/or project name] - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): Further details: - [ ] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/) - The group where the incubation/design work on this is being done (or is intended to be done in the future): - The group where standardization of this work is intended to be done ("unknown" if not known): - Existing major pieces of multi-implementer review or discussion of this design: - Major unresolved issues with or opposition to this design: - This work is being funded by: You should also know that... [please tell us anything you think is relevant to this review] ------------------------------------------------------------------------------------ CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING Please preview the issue and check that the links work before submitting. In particular: * if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. We would prefer public documents though, since we work in the open. ¹ For background, see our [explanation of how to write a good explainer](https://tag.w3.org/explainers/). We recommend the explainer to be in [Markdown](https://github.github.com/gfm/). ² Even for early-stage ideas, a Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/972 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/972@github.com>
Received on Tuesday, 2 July 2024 17:25:24 UTC