Get involved in @w3c and give input on all of our specs. See also youtube.com/@W3COfficial and @w3cdevs@w3c.social. By @dontcallmeDOM and @marieforgue

Joined October 2014
Filter
Exclude
Time range
-
Near
#WebRTC is “a great example of the power the Web has to make people’s lives better and of what we can do when we work together to do that”
1
1
5
We are looking for expert contributors to move this work forward by documenting gaps in support and creating tests. For more info about the program: youtube.com/mx2eDHujM4c
1
1
The @webi18n activity explores gaps in language support (Adlam, Hebrew, German, French, N'Ko, Osage) on the #Web and in #ebooks #timetogiveinput #i18n These drafts complement the 21 Gap-analysis docs published last June: w3.org/blog/International/20…
This tweet is unavailable
1
1
1
#webdevs, @w3c needs your input and feedback! Find out why and how to get involved: youtube.com/sw-j75MQtQU
5
8
1
18
To learn more about our overall efforts toward bringing #developers more into @w3c work at large, please watch: youtube.com/sw-j75MQtQU
2
5
One more week to propose a talk at the Wide Color Gamut (WCG) & High Dynamic Range (HDR) workshop w3.org/Graphics/Color/Worksh…
Several potential speakers for the @W3C Workshop on Wide Color Gamut (WCG) & High Dynamic Range (HDR) on the Web have indicated they need more time. Deadline for talks extended to 8 February. Apply here w3.org/2002/09/wbs/1/WCG-HDR…
3
for sure the past can't be changed :)
Find out how much effort went into the making of #WebRTC - impressive figures!
Replying to @w3cdevs
1) The #WebRTC #WorkingGroup has been chartered since 3554 days (9 years 8 months 20 days); 257 people participated in the group at one point or another. The work happened over 57 teleconferences, 16 #f2fmeetings, and 10114 emails! w3.org/groups/wg/webrtc
1
🆕 @dontcallmeDOM gives a #WebRTC "tour" in this 🎬, introducing the spec's current impact on the #Web & the world, and future improvements: youtube.com/PXhU4zvQDdM
2
1
1
1
4) To ensure wide interop, the spec has also received lots of testing attention, with 149 test files covering 1789 test assertions developed by 61 contributors github.com/web-platform-test…
2
3) The spec itself is made of 55897 words, 622 lines of IDL, incl. 20 interfaces, 37 dictionaries, 22 enums with 40 normative references to @ietf RFCs, each of which is a major achievement in terms of protocol standardization
1
2) The #GitHub repo was busy as well: with 44 contributors, there were 1282 merged pull requests, 4658 commits and 1320 resolved issues github.com/w3c/webrtc-pc/ Check the evolution of spec issues for WebRTC 1.0 at w3c.github.io/spec-dashboard…
1
1
1) The #WebRTC #WorkingGroup has been chartered since 3554 days (9 years 8 months 20 days); 257 people participated in the group at one point or another. The work happened over 57 teleconferences, 16 #f2fmeetings, and 10114 emails! w3.org/groups/wg/webrtc
1
1
A lot of efforts went into this major specification. Here are a few figures to help understand the level of membership and community involvement:
1
... with thanks to former editors Adam Bergkvist, @standardsplay, @anantn, Bernard Aboba and Taylor Brandstetter, and the #WebRTC #WorkingGroup chairs: Stefan Håkansson, @alvestrand, Erik Lagerway, Bernard Aboba and @jibrewery
1
1
2
Congrats to editors @cfluffy, Henrik Boström and @jibrewery for the newly published @w3c #WebStandard "#WebRTC 1.0: Real-Time Communication Between Browsers" w3.org/TR/webrtc/ #timetoadopt
This tweet is unavailable
1
2
13
.@dontcallmeDOM will represent us there to contribute to how and where investments on Web Platform documentation is needed w3.org/blog/2021/01/welcome-…
1
2
5