Open tidoust opened 1 month ago
From a Security point of view, the considerations on WebGPU seem to me to be well written.
I was pondering, reading this paper and also considering the structure of browser processes, whether we can add some mitigation in this regard.
no comment or request from i18n
no comment or request from APA.
New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
If applicable:
diff from previous charter
chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
New
Existing
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach
Groups identified in the Coordination section.
Known or potential areas of concern
None. Proposed scope and deliverables are the same. Main proposed change is the switch to perpetual CR mode. That said, note that the GPU for the Web WG is still reviewing the draft and may adjust it. Internal review in the group should conclude at the upcoming group's F2F end of October.
Where would charter proponents like to see issues raised? In the gpuweb/admin repository (or this strategy funnel issue)
Anything else we should think about as we review?
The group should soon request transition of the WebGPU and WGSL specifications to Candidate Recommendation.
Cc: @Kangz @kdashg