Media/WebRTC/2013-04-16
Tuesday, April 16, 2013, 9am Pacific:
Notes:
0) Work week for WebRTC:
- Will include the devs from Taiwan
- Link to the poll: http://doodle.com/9a2vka3qzrmske3k
- Definitely not in July. Frontrunner is the week of June 3. Maire will work to get this approved this week and start locking in plans.
1) PeerConnection, DataChannels blocking-webrtc+ bugs:
- Placeholder for the next few weeks to keep these on on radar
2) Other development work for Fx 23/24
Proposal to target:
- Clean up of higher priority non-blockers bugs
- TURN support (ekr)
- State Machine Cleanup (abr)
- Better error reporting (abr)
- BUNDLE/RTP mux (ehugg)
- Conversion to WebIDL (jib)
- Better AEC (jesup)
- Persona integration (EKR)
- Improved latency (padenot with mreavy, jesup)
- Get C++ unit tests running on Windows (ehugg/ted)
3) Android development
- Android WebRTC on inbound
- Resolution patch missing
- Known bugs in permissions UI
- Needs testing on Android 2.2
- Blog post forthcoming
- Will need bandwidth-resolution adaptation to pref on (jesup), in addition to UI/privacy approval
4) B2G development
- Working happening on Bugs 825110, 825112
- Perforance issues which we are starting to dig into
- Need B2G phones
5) Testing & Mochitests
- Note - Not in attendance, at B2G Work Week in Madrid (bad connection). I'm typing the update right now.
- More complete set of TURN tests
- - minimally make signaling unit tests run TURN
- Barriers:
- [whimboo] Blocked on memory leak for createDataChannel before createOffer bug for landing data channel tests
- Next Week:
- [whimboo] Continuing work on data channel automation
- [jsmith] Focused purely on B2G this week, but will be back on this next week
- Last Week:
- [jsmith] Lots of discussions about the WebRTC automation story on B2G last week
- Starting point - typical mochitests we've already got running on emulators with fake streams. Easy to pull off from what we already have.
- Advancement #1 - v412 loopback driver integration into emulators to run mochitests with fake devices, rather than fake streams. Needs feasibility analysis fOrom Ted, who's actively looking into this.
- Advancement #2 - Run mochitests with real camera hardware on device. The general case for getting mochitests running on device in CI is still being looked into on B2G, although the possibility for running them manually could be possible right now.
- Advancement #3 - Run gaia ui test automation with real camera hardware on device. These tests would be more focused on permission testing with the permission prompt for gUM request grant or deny, rather than focusing on analyzing the DOM-specific use cases (which is covered by mochitests). Relatively straightforward to pull off to get this into CI.
- [jsmith] Had some one-off discussions with Ted about whether the v412 loopback driver work can apply to FxAndroid. Ted is conducting a feasibility assessment here.
- [whimboo] Continued work on data channel automation
- [jsmith] Misc exploratory testing for bug verifications
- [jsmith] Lots of discussions about the WebRTC automation story on B2G last week
6) Discuss any current problems for people or issues that haven't been discussed -- or Any heads up for the group
- Reminders:
- Talkilla is having a work week starting April 22
- Doing a brown bag on WebRTC on Thurs, April 25.
- Documentation for developers
- higher level list of what have and don't have (important differences from the spec) -- perhaps link to bugs
- compiling this over the next few weeks at https://developer.mozilla.org/en-US/docs/WebRTC
- Talkilla is having a work week starting April 22
_________________
References
Blocker List for releasing PeerConnection and DataChannels (the rest of WebRTC): 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
Blockers in Question for PeerConnection and DataChannels: https://bugzilla.mozilla.org/buglist.cgi?list_id=6168658&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=blocking-webrtc%3F
WebRTC Uplift Bugs: https://bugzilla.mozilla.org/buglist.cgi?list_id=6242297&resolution=FIXED&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=webrtc-uplift
Android gUM Blockers: https://bugzilla.mozilla.org/buglist.cgi?list_id=6371418&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=android-gum%2B
Android PeerConnection and DataChannels Blockers: https://bugzilla.mozilla.org/buglist.cgi?list_id=6371420&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=android-webrtc%2B
Intermittent failures in WebRTC Automation: https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6167884&resolution=---&query_format=advanced&component=WebRTC&component=WebRTC%3A%20Audio%2FVideo&component=WebRTC%3A%20Networking&component=WebRTC%3A%20Signaling&product=Core
Android User Stories/Progress: https://webrtc-apps.etherpad.mozilla.org/4
