Media/WebRTC/2012-08-21

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

8/21/2012, 9:00am Pacific:

1)Review/Discuss remaining "Priority 0" items from https://wiki.mozilla.org/Media/WebRTC/Status_Post_IETF-84

  • Moving "Allow some minimal variation in the SDP." to the Priority 1 list.
  • Randell to coordinate with Ted on build issues

2) Status on "Priority 1" (Spec compliance) list in https://wiki.mozilla.org/Media/WebRTC/Status_Post_IETF-84 by category:

  • JSEP [emannion, ehugg]
    • RTP/SAVPF SDP is complete
    • DTLS SDP is complete
    • OPUS SDP is in progress
    • Enda will be on PTO 28, 29, 30, 31 Aug
    • EHugg on PTO 27, 28, 29 Aug
    • Crypt back on track tomorrow 8/22
  • Media Transport [ekr, anant]
    • EKR will focus on getting receive trickle ICE working
    • The other items are secondary at this point (needed for spec compliance, not interop)
  • Media [derf, jesup]
    • Target getting Opus support done by next week
  • DOM [jesup, anant]
    • DOM code and JS not fully supported yet
    • None of this work is needed for interop
  • Identity [ekr, anant]
    • Definitely something we want to get in, but less critical than receive trickle ICE

NOTE: Please help get all the items from the "Priority 1" list into bugzilla ASAP. I'm asking the primary owners of each task to make sure this happens.

3) Discuss what system we should adopt for making sure at least the compile piece of tinderbox stays green.

  • No system really put in place. No sheriff or anything like this. We comitted to keeping it green, being extra careful about keeping it green, and bugging the person who broke it as soon as we discover it's broken. We'll see how this goes. If this policy isn't sufficient, we'll revisit

4) Data channels will be ready to check into mozilla-central before PeerConnection. How should we hook data channels up so people can plan with them in mozilla-central before PC is ready?

  • Will hook up data channels to a temporary way to create channels while we wait for PeerConnection to be ready

5) Plan for trying interop with Chrome & when

  • EKR is ready today
  • Chrome will be ready next wekk and they'll reach out
  • Randell and Tim will try to get data channels and Opus ready ASAP

6) Organizing Peer reviews and Security reviews

  • Randell and Maire are reaching out to peer reviewers and talking with security
  • Will be publishing an updated landing plan and new peer review plan within the next week or possibly two

7) What spec issues (with the working groups) are holding us up or will soon be holding us up? How soon do we need them resolved? The current list is here: https://docs.google.com/spreadsheet/ccc?key=0AuAFj6druDCtdHhjZ1J2dHVPQjdCX1NsVjhWWUc0U1E#gid=0 This lists gets discussed during the Google Office Hours. If you need an item added or prioritized, please let Maire know.

  • Nothing new mentioned

8) Testing issues/questions (whatever didn't get resolved in the 8:30am meeting this week)

  • (jsmith) The Android bug for gUM is still busted -> [Maire: blassey is looking at it. I hope to have a fix this week, but I'm waiting for his assessment.]
  • (jsmith) Action item: Morph the gUM triage to be a general

9) Discuss any current blockers for people or new items that haven't been discussed

  • None mentioned
Retrieved from "https://wiki.mozilla.org/index.php?title=Media/WebRTC/2012-08-21&oldid=464708"