Re: [w3ctag/design-reviews] Rethink the TAG's review intake process. (PR #1102)

@xiaochengh commented on this pull request.



> +      label: Explainer
+      description: |
+        An explainer must describe the problem that your proposed feature aims to solve **from an end-user's perspective**. It must also show example pieces of code that use the proposed solution to solve the user-facing problems. See our [explanation of how to write a good explainer](https://w3ctag.github.io/explainer-explainer/#introduction).
+      placeholder: Enter a URL.
+      value: "https://"
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: The explainer
+      options:
+        - label: Includes the information requested by the [Explainer Explainer](https://w3ctag.github.io/explainer-explainer/#introduction).
+          required: true
+        - label: Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
+        - label: Includes or links to answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

Should we include more here, like accessibility and etc?

It should be better to identify which horizontal reviews are needed as early as possible.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/pull/1102#pullrequestreview-2977833602
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/pull/1102/review/2977833602@github.com>