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

@marcoscaceres commented on this pull request.



> @@ -0,0 +1,89 @@
+name: Browser-driven specification review
+description: >
+  If your browser is considering shipping a feature
+  that hasn't had a Working Group take it through wide review,
+  please use this form.
+title: "Browser review: "
+labels:
+  - "Progress: untriaged"
+  - "Review type: later review"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for sending us your specification review. If a Working Group generally agrees about this feature, we prefer to have them take it through wide review. If they're willing to do that, please [switch to the WG new specification review template](https://github.com/w3ctag/design-reviews/issues/new?template=005-wg-new-spec-review.yaml). Otherwise, if you're planning to ship the feature anyway, please continue to file the review with this form.

This still reads like, "hey TAG, review our proprietary feature". 

I don't think the TAG should spend time reviewing things that haven't initiated a standardization process (even if it's an incubation process). 

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

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