Re: [w3ctag/design-reviews] WebGPU and WGSL (#626)

It is now the one year birthday of this request for a TAG review, and there is still no official feedback that has been provided.

 - Some TAG members did look at the API and provided feedback out of band, but it doesn't replace the official review.
 - WebGPU is a large and complex API, but the CG/WG members provided detailed explainers and have always been available to write more or answer questions directly.
 - We were told the TAG review queue could be month long and that the group should be patient, but it's been a year, multiple reminders after the 6th month and WebGPU is still getting moved from milestone to milestone.

We're trying to finish the first version of the WebGPU API and go to CR. We're supposed to wait for horizontal reviews but blocking indefinitely on the TAG is not okay. If feedback from the TAG comes before CR then we'll try to address it, but if it doesn't, then we'll have to do without.

My suggestion for handling large APIs like WebGPU in the TAG is to ask the groups which parts of the API are most "at risk" of receiving feedback and do partial reviews for each of these parts. Trying to make one full review for the full API can be too high a commitment for TAG members, and might not be a good use of their time. Especially when some details (in the case of WebGPU) are purely technical and internal, without any interaction with the user or the rest of the Web platform.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/626#issuecomment-1110971517
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/626/1110971517@github.com>