#1196: [wg/webperf] Web Performance Working Group Charter
Discussions
Log in to see TAG-private discussions.
Comment by @marcoscaceres Feb 19, 2026 (See Github)
@caribouW3, any chance you could put the deliverables back to the original order? (and add the new ones at the end of that section)... Otherwise it's hard to review the changes.
See the diff to see what I mean.
Cc @yoavweiss
Comment by @yoavweiss Feb 19, 2026 (See Github)
Please hold off on reviewing this, as the charter draft doesn't yet include any changes we're aiming to make.
Comment by @marcoscaceres Feb 24, 2026 (See Github)
Ok, let us know when you'd like for us to start having a look.
Comment by @caribouW3 Mar 9, 2026 (See Github)
@marcoscaceres I have reordered according to previous list, it's easier to see the changes globally. @yoavweiss it includes the changes discussed during last WG teleconference, let me know if I missed anything (please report in https://github.com/w3c/charter-drafts/issues rather than here)
Discussed
Mar 16, 2026 (See Github)
Marcos: Does anyone want to collaborate on this one? I think it's ready for review.
Jeffrey: If no one else is interested, I can look along with you.
Marcos: I think it's straightforward, but they've changed the text around the CR criteria and I haven't figured out if that has architectural concerns or not.
Jeffrey: Sounds like we need to wait until we've reviewed next week.
OpenedFeb 17, 2026
This issue was created because the 'horizontal review requested' label was added to § https://github.com/w3c/strategy/issues/531
This review is requested prior to the Advisory Committee Review.
New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
Expected end of charter refinement phase: 2026-04-15
If applicable:
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
Known or potential areas of concern
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
issues in 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. @yoavweiss @nicjansma
Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a Charter Facilitator for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly.
Charter facilitator(s)
cc @caribouW3
<!-- Content below this is maintained by @w3c-tag-bot -->Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1196