You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Existing
Existing WG recharter
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
Browser vendors, AI systems developers, ML processing units vendors, ML framework developers
Known or potential areas of concern
N/A
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
diff from previous charter
chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
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
Browser vendors, AI systems developers, ML processing units vendors, ML framework developers
Known or potential areas of concern
N/A
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
https://github.com/w3c/machine-learning-charter/issues
Anything else we should think about as we review?
The sister Web Machine Learning Community Group recently adopted a set of LLM-based browser APIs for incubation - the Working Group is not ready to adopt them as tentative deliverables yet, but is signalling its future interest in doing so to call for the attention of the community on this space.
Note: proposed chairs should be copied @... on this issue.
cc @anssiko
The text was updated successfully, but these errors were encountered: