Skip to content
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

Closed
3 of 6 tasks
dontcallmedom opened this issue Jan 16, 2020 · 14 comments
Closed
3 of 6 tasks

WebRTC 2020 charter #207

dontcallmedom opened this issue Jan 16, 2020 · 14 comments

Comments

@dontcallmedom
Copy link
Member

dontcallmedom commented Jan 16, 2020

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.

  • Existing

Horizontal Reviews (intended to be checked only by horizontal reviewers when they are satisfied with the charter)

  • Accessibility (a11y)
  • Internationalization (i18n)
  • Privacy
  • Security

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?

@plehegar
Copy link
Member

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.

@r12a
Copy link

r12a commented Jan 27, 2020

No i18n-related comments from me.

@dontcallmedom
Copy link
Member Author

@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.

@michael-n-cooper
Copy link
Member

APA WG would like a liaison statement, as we are actively engaged in coordination and expect that to continue.

@dontcallmedom
Copy link
Member Author

@michael-n-cooper could you suggest some text that you would like to see added to the charter to that effect? Thanks!

@michael-n-cooper
Copy link
Member

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.

@svgeesus
Copy link
Contributor

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?

@dontcallmedom
Copy link
Member Author

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.

@svgeesus
Copy link
Contributor

svgeesus commented Mar 31, 2020

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.

@michael-n-cooper
Copy link
Member

APA review complete. Over to @brewerj to complete accessibility horizontal review.

@dontcallmedom dontcallmedom moved this from Evaluation to Chartering in Strategy Team's Incubation Pipeline (Funnel) Jun 29, 2020
@plehegar
Copy link
Member

Goal is to start W3M review no later than July 15, and send the charter, with updated timeline and PP2020, around Aug 1.

@plehegar
Copy link
Member

plehegar commented Jul 2, 2020

NOTE: take w3c/charter-drafts#273 into account.

@brewerj
Copy link

brewerj commented Jul 29, 2020

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

dontcallmedom added a commit to w3c/webrtc-charter that referenced this issue Jul 29, 2020
@samuelweiler
Copy link
Member

@wseltzer wseltzer moved this from Chartering to Strategy Work Concluded in Strategy Team's Incubation Pipeline (Funnel) Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

7 participants