Closed AlexDawsonUK closed 11 months ago
it seems like you can divide W3C specs into several categories, each have their own sustainability challenges.
You can have problematic resource consumption at each of these layers, but the most critical and the native APIs, since they tend to be close to the hardware (consider webgpu crypto currency miners, or advanced video processing capabilities).
I've marked this on the agenda for one of our meetings this month (October 23). This issue can be re-opened at a later date if our scope needs to be altered or if our groups status requires the issue being re-examined.
Discuss the future reach of the guidelines:
How will the specification grow to account for this (future notes, further specifications, horizontal review, etc). Collaboration (WAI / Equity CG / Sustainability CG / W3C PING / Privacy CG / WebPerf WG / etc)
Note: To be discussed at a later CG meeting, comments welcome below with future ideas. Credit: npd, @jenstrickland, @npdoty, @notmariazoe