At last #FronteersConf, @rachelandrew explains why and how you should engage with @w3c as a #Web #developer
The video of my talk at @FronteersConf is already out, you can find it, my slides and resources on @benotist noti.st/rachelandrew/uC7Ljv/…
1
3
1
Based on her participation as a #developer in @csswg and more recently as a #w3c representative for @fronteers, Rachel shares her experience and reminds that everyone is allowed/encouraged to create #WebPlatform features - you don't need permission!
1
1
As a long-time participant in @csswg, she knows that @w3c #WorkingGroups are very happy when #developers and #designers offer feedback on specifications. It could be any spec.!
1
1
2
So, don't think twice and get started: 1) read and comment on specification issues 2) show use cases 3) contribute examples and diagrams 4) raise browser bugs 5) test and offer feedback on features behind flags ...
1
2
2
and 6) write Web platform tests!
All the features that are defined in @w3c specifications to be shipped in browsers are accompanied by a test suite, to help assess how well and how broadly they are implemented by actual browsers.

Oct 16, 2019 · 2:25 PM UTC

1
2
After raising an issue, remember that patience is required for #WebPlatform contributions. As Rachel puts it: "It's not that people don't care, it's because they are few people editing specs, with priorities and because we are working on stuff that is very much in the future."
1
3
4
.@rachelandrew is also sharing some of these advices in @smashingmag, along with a call for actions and contributions!
This tweet is unavailable
1