To understand why, and to understand why formal chartered working groups _tend_ towards ossification, gatekeeping, and stagnation we need to keep in mind how they come to be and what problems they're formed to solve.
-
-
This is why you see Chrome engineers preferring to start new explorations in forums like
@wicg_. It's an open space that's super easy for web developers to participate in, which also preserves the ability to migrate a design/spec to a WG at the next rechartering opportunity.Show this thread -
I don't set many policies for the Standards Team here, but "incubate first" is the most important of the short list; finding the spaces where you can iterate rapidly, not annoy the "right people" while you sort through rough hewn ideas, and get real developer feedback is *key*
Show this thread -
Chartered WGs of course *want* to take web developer feedback into account the way incubations processes can, but they literally don't have the time...and that's by design.
Show this thread -
Anyhow, if you're a web developer and want to have a big impact on the future of the platform, comments you leave in repos and discourse threads in
@wicg_ shape things at a critical moment: https://wicg.ioShow this thread -
BTW, none of this takes away from the great work that WGs do. They're the big leagues and CGs are the farm teams. We need them both! But we also need to expect reasonable things of each, else we'll always be disappointed.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.