Media/WebRTC/2014-03-11
Tues, March 11 at 10am Pacific.
Agenda/Notes:
1) Stand-ups:
- Active developers will give a 3 minute (or less) stand up focusing on -
- what are you currently working on that the team is following/tracking (please give the bug number) and when do you think you'll be done?
- what are you moving onto next?
- have you hit any problems (especially unexpected problems)?
- jesup -
- A/V sync regression found and fixed. Imported with 3.41 (Chrome broke in 31 & 32)
- Should land A/V sync monitoring via logs and about:webrtc in the next day or so
- also we got NetEq jitter buffer depth monitoring
- we'll want to feed a/V sync and jitter depth into telemetry histograms
- We should leverage this into talos tests!
- AEC delay patch seems to work well, though some failures in long calls have been seen (apparently due to output delay in MSG or cubeb, perhaps clock drift).
- Padenot has patches close to ready for the mixing-in-msg/etc which I can connect to the existing patches for AEC-in-gum
- It's highly unlikely that the fixes for AEC platform delay (prefs change only) or the A/V sync bug (minimal patch) will be approved for Beta, which means 28 will regress on both. :-(
- padenot - In Taipei (Working on MSG refactor)
- ekr - Attending late (has a conflict until 30 mins past the hour)
- abr - On PTO
- mt -
- making headway on 907770 which is blocking progress elsewhere
- on half- work week with necko team in Paris
- IETF & HTTP/2 editorial work mostly
- ehugg -
- OpenH264 new landings:
- New targets for Android and iOS
- ARM Assembly code for chips that support Neon.
- Crash bugs found by Mozilla fixed.
- Codenomicon fuzz test run and problems fixed.
- Test suite expanded.
- OpenH264 new landings:
- jib -
- Landed rtcp stats test (bug 970686)
- Almost ready with patch addressing rtcp receiver reports timestamps and packets/bytes received being all wrong. Will need uplift (bug 980497)
- added a/v sync stat to about:webrtc (bug 964127). And then working width height constraints still (bug 907352)
- bwc -
- Have small patches up for 980609 and 980270 awaiting review
- telemetry stuff on 970690 awaiting feedback (mostly of a "Are these useful measurements?" nature), and some other assorted small stuff.
- The bundle filtering ticket (786234) finally landed last week, and stayed landed, so that's good.
- gcp -
- Load Adaption review comments addressed, fixed some try fallout
- Made everything configurable via prefs
- Tracking a crash bug (in logging, meh)
- Expect landing Real Soon Now
- drno (Nils) -
- Helping QA group to get an overview of WebRTC to help deciding where to invest man power
- dmose - On PTO
- standard8 -
- Focussed on client side Loop
- Updated the user stories on the bugs with latest info, added rough estimates
- Progressed first patch for social api to use chrome uris - bug 976614
- Awaiting review
- Second patch will add Loop by default, may need some extra work
- Next client side work will be looking to hook up push notifications in some form (bug 971990)
- Focussed on client side Loop
- tOkeshu - Worked on the following bugs:
- https://bugzilla.mozilla.org/show_bug.cgi?id=971999
- https://bugzilla.mozilla.org/show_bug.cgi?id=971995
- https://bugzilla.mozilla.org/show_bug.cgi?id=981672
- So mostly server side stuff and crypto. Will address soon the retrieving of provider tokens to foward to user agents.
- I am also in contact with multiple person to participate to a WebRTC meetup (Munich and Berlin). I will probably be on PTO as soon as we landed MLP (~2 weeks).
- niko -
- Mostly worked on these bugs related to the Loop client UI:
- Got a basic set of web UI components, initial workflow for getting a call url from the loop server, still strugling a little with l10n but in the process of sorting it out (thx Standard8).
- alexis -
- https://bugzilla.mozilla.org/show_bug.cgi?id=972866
- https://bugzilla.mozilla.org/show_bug.cgi?id=977507
- https://bugzilla.mozilla.org/show_bug.cgi?id=976979
- https://bugzilla.mozilla.org/show_bug.cgi?id=976979
- https://bugzilla.mozilla.org/show_bug.cgi?id=971993
- https://bugzilla.mozilla.org/show_bug.cgi?id=971991
- Crypto and server side stuff;
- started discussions about infra / design decisions with services.
- Integration with tokbox
- onboarding remy from services which will work on scalability mainly
- Are we tracking FxA removal / ping FxA people?
- pkerr -
- Posted patch set to bug 768968. Clears all but one warning from the /media branch. (The one not cleared has to do with a comparision in a template of two different types.) I will begin testing on the try servers.
- https://bugzilla.mozilla.org/show_bug.cgi?id=768968
- crypt - On PTO till 28th March
2) Discussion
a) Loop MLP/MVP scope and scheduling (Bug 972866 , Bug 971986)
b) Platform quality focus (Bug 970426)
- leaks - please investigate if pinged
c) FxOS v1.5 (Gecko 32) - WebRTC using H.264 h/w codecs () and if possible OpenH264 (Bug 948160)
<Read only section>
Notices:
- Reminder to dogfood whenever possible: Use WebRTC for chats within the team whenever possible (prefer to IRC, etc if possible)
- Reviews:
- Reminder to handle review requests in a timely manner (previously discussed), and to raise any design issues early if possible, preferably outside of the the review process (in the bug, email, IRC, calls, whatever makes sense)
- Next meeting with tokbox will be March 4 at 2pm, Pacific.
References:
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
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