.@slightlylate offers his and @ChromiumDev views on how to use the standardization and (specifically) the pre-standardization process to successfully bring new features to the Web
"Effective Standards Work, Part 2: Threading the Needle": infrequently.org/2018/06/eff…
And ICYMI, yesterday's Part 1: infrequently.org/2018/06/eff…
1
1
2
This includes ensuring lots of input and feedback from #developers along the way, and letting innovation bloom in the early design cycles of a technology with less politics, IPR commitments and formalisms.
1
A lot of these ideas have been behind @w3c's #CommunityGroup offer w3.org/community/ in general (started back in 2011), and the start of the @wicg in particular (in 2015).
1
More recently, the @w3CAB has been promoting that approach by documenting best practices on identifying standardization-ready specifications w3.org/Guide/standards-track…
Jun 14, 2018 · 1:12 PM UTC
1
We don't have it all figured out, and we still have a lot to learn.
Some formal standardization Working Groups have been very successful at incubating ideas and bringing developers input to their regular workflows (e.g. @csswg)
1
1
In other cases, #CommunityGroups have sometimes created confusion.
But there are already quite a few amazing examples of new features or technologies landing in standardization that way (#ResponsiveImages, #WebAssembly, hopefully soon #WebXR to name a few).
1
.@w3cdevs is here to help understand, document and promote effective ways for #developers to get involved in this next generation of Web technologies.
What has been *your* experience with @w3c? what are the main obstacles you've hit on the way?
1
If you feel strongly about bringing more exposure of @w3c standards to #developers, infrequently.org/2018/06/eff… is mandatory reading in any case
3