- From: François Daoust via GitHub <noreply@w3.org>
- Date: Wed, 06 May 2026 12:12:01 +0000
- To: public-privacy@w3.org
tidoust has just labeled an issue for https://github.com/w3c/strategy as "Horizontal review requested": == [wg/webtransport] [WebTransport] Group Charter == New charter proposal, reviewers please take note. # Charter Review [Draft Charter](https://w3c.github.io/charter-drafts/2026/webtransport-wg-charter.html) Note that is it still using an old version of the template, changes were made from the last charter, update to the new template is in progress. [diff from charter template](https://services.w3.org/htmldiff?doc1=https://w3c.github.io/charter-drafts/charter-template.html&doc2=https://w3c.github.io/charter-drafts/2026/webtransport-wg-charter.html) Expected end of charter refinement phase: unknown [diff from previous charter](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2024%2F09%2Fwebtransport-wg-charter.html&doc2=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2F2026%2Fwebtransport-wg-charter.html) [chair dashboard](https://www.w3.org/PM/Groups/chairboard.html?gid=wg/webtransport) What kind of charter is this? Check the relevant box / remove irrelevant branches. * New - [ ] New WG - [ ] New IG * Existing - [X] Existing WG recharter - [ ] Existing IG 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](https://github.com/orgs/w3c/projects/97/views/2).** ## Communities suggested for outreach * HTML ## Known or potential areas of concern Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...) [Use "webtransport" label](https://github.com/w3c/charter-drafts/issues) ## Anything else we should think about as we review? Note: proposed chairs should be copied @... on this issue. @wilaw @jan-ivar Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a [Charter Facilitator](https://www.w3.org/guide/process/charter.html#cr-acceptance) for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly. See https://github.com/w3c/strategy/issues/537 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 May 2026 12:12:05 UTC