Re: [w3ctag/design-reviews] Update issue templates (#447)

dbaron commented on this pull request.



> @@ -0,0 +1,53 @@
+---

So while github's wizard doesn't let you control it... the filenames here control the order [the options](https://github.com/w3ctag/design-reviews/issues/new/choose) are given in.

I think this should probably be before the specification review one, though I don't feel strongly.  If you agree, it should probably be prefixed with `005-`, if not, with `015-`, so that it sorts appropriately.

>  
 You should also know that...
 
 [please tell us anything you think is relevant to this review]
 
-We'd prefer the TAG provide feedback as (please select one):
+We'd prefer the TAG provide feedback as (please delete all but the desired option):
+
+  🐛open issues in our GitHub repo for **each point of feedback**
+  🦋open a single issue in our GitHub repo **for the entire review**
+  💬leave review feedback as a **comment in this issue** and @-notify [github usernames]
+
+------------------------------------------------------------------------------------
+CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Good idea!

>    - Tests: [wpt folder(s), if available]
-  - Primary contacts (and their relationship to the specification): [github usernames and affiliation]
-  - Organization/project driving the specification: [organization or project name] 
+  - Security and Privacy self-review²: [url]
+  - GitHub repo (if you prefer feedback filed there): [url]
+  - Primary contacts (and their relationship to the specification): 
+      - [name] ([github username]), [organization/s] (repeat as necessary)
+  - Organization(s)/project(s) driving the specification: [organization and/or project name] 
+  - Existing major pieces of multi-stakeholder review or discussion of this specification: 

Maybe replace "major" with "main" or "primary"?  I think the idea is that we want to see how much review there was, so we want to see the largest pieces, however large or small they are.

-- 
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/design-reviews/pull/447#pullrequestreview-327963039