Re: [w3ctag/design-reviews] [wg/webperf] Web Performance Working Group Charter (Issue #1196)

marcoscaceres left a comment (w3ctag/design-reviews#1196)

Thanks for sending us this charter to review. The TAG is satisfied with the following concerns:

**Deliverables section structure:** The "Deliverables" section is split into "Normative Specifications", "Past Specifications", "Standards", and "Other Deliverables". We'd appreciate if the charter explained the purpose of the "Past Specifications" and "Standards" sections, or — preferably — dropped the distinction entirely: specifications are generally maintained for as long as the working group is chartered and issues continue to be filed, making the distinction immaterial in practice.

**Moving specs to incubation:** We appreciate the group's willingness to move specifications back to incubation when they lack a path to interoperable implementation. Are the criteria for making this decision stable enough to encode in the charter? If so, please do.

**Single engine vs. single browser:** The charter describes the Long Tasks API as "implemented in a single browser", but [caniuse](https://caniuse.com/mdn-api_performancelongtasktiming) indicates 7 browsers implement it. If you mean "single browser engine", please use that terminology consistently throughout.

**Features with fewer than 2 implementers:** Some TAG members are concerned about allowing features to be added to specifications before they have support from at least 2 implementers. This effectively introduces an incubation mechanism into the specification itself, which risks confusing developers about the level of implementer support even when features are marked "experimental". This is a working-mode issue: implementer consensus should be sought through the working group's normal process — for example, during working group calls — rather than by deferring it into the spec.


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

Message ID: <w3ctag/design-reviews/issues/1196/4351217509@github.com>