Media/WebRTC/2013-01-08

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

1/8/2013, 9am Pacific

Notes:

1) Interop with Chrome

  • FF nightly will interop with extensively-patches chrome
    • Chrome patches in some form should land "soon" - we will coordinate with Justin
  • major issues resolved
  • mreavy working how to make this info public once things work
  • Question of which "app" to use for the demo. Maybe apprtc, perhaps rehosted.

2) gUM blockers for release: where are we?

  • Bug 827156 ([meta] UI punchlist for getUserMedia blockers)
  • Others are largely hard-to-reproduce crashes, which may be fixed (need to ask for qawanted) or hardware/platform specific issues
  • Need to decide if we need to suppress echo on loopback gUM tests (which aren't typical in real world apps)

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

  • What is blocking us from pref'ing these on? (Bug 796463 has dependencies now)
    • Enabling the AEC (Bug 818670, longer term: Bug 694814)
    • Enabling mochitests for PeerConnection (825510)
    • Cleaning up WebRTC constraints implementation (Bug 826807)
      • Not sure it should block
    • Christoph will run mochitests under ASAN

4) Android work/status

  • Signaling tests all passing but one
  • Android to desktop audio call, intercontinental, through firewalls, crystal clear!!!!
  • moving preferred test device to be a Samsung Galaxy S3
  • need to land webrtc.org update (to match Chrome M26)
  • video: no devices found
    • ekr suggested verifying video reception in parallel to gum work

5) SIPit 30 is coming up -- who wants to go? (Feb 18-22, but one day is dedicated to WebRTC implementation testing)

  • Robert Sparks reached out to Mozilla in Atlanta (IETF-85) asking for at least one representative from Mozilla to show up -- we may want to send 2 people and have more people on call remotely
  • options: 19th or 21st (abr discussed with Sparks)
  • in-person - options abr, derf, ekr
  • remote: jesup, ehugg

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

  • None discussed

7) Testing

  • crashtests disabled pending solving the automation-induced (?) leak

_________________

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

Retrieved from "https://wiki.mozilla.org/index.php?title=Media/WebRTC/2013-01-08&oldid=500094"