Media/WebRTC/2013-01-15

From MozillaWiki
< Media‎ | WebRTC
Jump to: navigation, search

1/15/2013, 9am Pacific

Agenda:

1) Interop with Chrome

  • Chrome is committing its patches in the next day or so.
  • We agreed to make some changes to our code after talking with Justin
  • All the patches should be in by the end of this week and then we need to talk about uplift,etc and planning a demo call. We will be coordinating with Chrome later this week (Thurs probably).

2) gUM blockers for release: where are we?

  • Bug 827156 ([meta] UI punchlist for getUserMedia blockers)
  • Not much else. A few tough to hit crashes and a small number of new reports that jesup needs to investigate

3) Blockers to pref on PeerConnection, DataChannels: where are we?

  • What is blocking us from pref'ing these on? (Bug 796463 has dependencies now)
    • Updating webrtc.org code (this is causing problems for the Android WebRTC folks, so we don't want to land until they are ok)
    • Did Christoph run mochitests under ASAN last week? (Enable mochitests for PeerConnection -- Bug 825510)
      • Yes, he saw no problems
    • Enabling the AEC (Bug 818670, longer term: Bug 694814)
      • We will enable it, but likely allow the developer/user to turn it off in about:config
    • Cleaning up WebRTC constraints implementation (Bug 826807)
    • Do we need to find someone to adopt Bug 799142?
      • mreavy will find someone, but this doesn't need to block pref'ing
    • We want to fix to fix Bug 822197 as well before we pref on.
    • Want to verifty if bug 827798 still occurs. (Blocks original mwc page)

4) Android work/status

  • Do dmose and gcp have Samsung Galaxy S3 phones now? (gcp: no, I suppose it's on the way - ServiceNow seems to imply it's been ordered)
  • UI metabug: bug 830829, temporary/POC is bug 828963
  • Will land audio: bug 812650
  • Looking at trying to get the new webrtc.org code to work with Android but there are major problems with audio

5) Upcoming meetings:

6) Discuss any current problems for people or issues that haven't been discussed -- or Any Heads up for the group

  • Nothing mentioned

7) Testing

    • [jsmith] Double-booked with Partner Triage for b2g - will be here next week
    • [jsmith] Nothing new to update on - but will have time to focus on this more as some of the b2g stuff calms down
    • [jsmith] Next steps is to burn through a lot of qawanted, bug verifications, get caught up on PC testing

_________________

For Reference:

Interop (Firefox-Chrome) blockers: https://bugzilla.mozilla.org/buglist.cgi?list_id=5124656;resolution=---;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc-interop

Blocker list for gUM: https://bugzilla.mozilla.org/buglist.cgi?query_based_on=gum%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-gum%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=gum%20blocking

Blocker List for preffing PeerConnection and DataChannels (the rest of WebRTC) on: https://bugzilla.mozilla.org/buglist.cgi?query_based_on=WebRTC%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=WebRTC%20blocking

Combined Blocker List for all of WebRTC (gUM, PeerConnection, DataChannels):https://bugzilla.mozilla.org/buglist.cgi?list_id=5234368;query_based_on=WebRTC%2Fgum%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc%2B%20blocking-gum%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=WebRTC%2Fgum%20blocking