New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebRTC 2020 charter #207
Comments
I believe that it is important to have a timeline for WebRTC 1.0 in the charter. At the minimum, it will highlight as part of the AC review and we need the WG to concur with the proposed timeline. |
No i18n-related comments from me. |
@plehegar there was no timeline for webrtc 1.0 and media capture and streams under the assumption they would be done by the time of the rechartering. If that assumption doesn't hold true, I absolutely agree their timeline needs to be in the charter. |
APA WG would like a liaison statement, as we are actively engaged in coordination and expect that to continue. |
@michael-n-cooper could you suggest some text that you would like to see added to the charter to that effect? Thanks! |
Maybe: "The Accessible Platform Architectures identifies use cases for users with disabilities and reviews technologies to avoid unintentional introduction of barriers." That might be enough for a liaison statement, but you could add if you want "Its Media Accessibility User Requirements and Real-Time Communication Accessibility User Requirements provide important input to this." The latter document is under development now in APA and expected to be published as a Note-track first draft in about a month. |
I notice a bunch of specs (including Audio Output Devices API ) in a "until another group take them over:" bucket. What is the story on those? |
Ideally, the group would like a more focused group to take them over; but there isn't a good candidate at the moment (in particular, the Media WG has a different focus since it has less to do with media capture and transport), so for now, the safer approach seems to keep them in the group until such a group emerges. |
OK, thanks. I wondered about possible overlap with the Audio WG, which also wants access to audio outputs (but with very different requirements than the "speakers or headphones" focus from Web RTC. However the current "further collaboration on the management of audio output device is expected." under coordination with Audio WG seems to cover that. |
APA review complete. Over to @brewerj to complete accessibility horizontal review. |
Goal is to start W3M review no later than July 15, and send the charter, with updated timeline and PP2020, around Aug 1. |
NOTE: take w3c/charter-drafts#273 into account. |
Hi Dom, here are the links for the MAUR https://www.w3.org/TR/media-accessibility-reqs/ and the RAUR https://www.w3.org/TR/media-accessibility-reqs/ to please link to from section 3.1 of the draft charter https://w3c.github.io/webrtc-charter/webrtc-charter.html Thanks, Judy |
As suggested in w3c/strategy#207 (comment)
Charter to AC for review: https://lists.w3.org/Archives/Public/public-new-work/2020Aug/0005.html |
New charter proposal, reviewers please take note.
Charter Review
Charter: Web Real-Time Communications Working Group Charter
What kind of charter is this? Check the relevant box / remove irrelevant branches.
diff to previous 2018 charer
discussion on changes
Horizontal Reviews (intended to be checked only by horizontal reviewers when they are satisfied with the charter)
Communities suggested for outreach:
IETF?
Known or potential areas of concern?:
The group will likely delay its rechartering to be able to benefit from process 2020.
Where would charter proponents like to see issues raised? (github preferred, email, ...)
github
Anything else we should think about as we review?
The text was updated successfully, but these errors were encountered: