Media/WebRTC

WebRTC is a free, open project that will bring peer-to-peer real-time audio, video and data to the web without plugins, using open web standards.

Checkout the WebRTC project page set up by Google for more interesting links and details.

Team meetings and member info: here

• We hold a Google Hangout
  • Maire Reavy pastes the hangout URL into #media so that anyone hanging out in #media can join.
• IRC: #media
• Etherpad: WebRTC (copied to wiki after the meeting)

Draft Project Overview: coming soon

This is not a commitment to dates. It's a planning visualization to see how various teams working on the project relate to each other. It helps to see how changes in one area can impact downstream.

Project Documentation

• Overview of Mozilla's WebRTC Architecture
• Overview and status of navigator.getUserMedia()
• WebRTC Testing
• Instructions for enabling logging messages
• Notes on getting WebRTC working on a Peak
• WebRTC Audio Issues
• Updating from upstream webrtc.org

Work Weeks

Past work week Jun 10-14 2013: -- WebRTC work week June 10 2013

Upcoming Standards Meetings

IETF Berlin

Meeting Notes and Progress Reports

• Meeting Notes from Tue, Apr 8, 2014
• Meeting Notes from Tue, Apr 1, 2014
• Meeting Notes from Tue, Mar 25, 2014
• Meeting Notes from Tue, Mar 18, 2014
• Meeting Notes from Tue, Mar 11, 2014
• Meeting Notes from Tue, Mar 4, 2014
• Meeting Notes from Tue, Feb 25, 2014
• Meeting Notes from Tue, Feb 18, 2014
• Meeting Notes from Tue, Feb 4, 2014
• Meeting Notes from Tue, Jan 28, 2014
• Meeting Notes from Tue, Jan 21, 2014
• Meeting Notes from Tue, Jan 14, 2014
• Meeting Notes from Tue, Jan 7, 2014
• Meeting Notes from Tue, Dec 17, 2013
• Meeting Notes from Tue, Dec 10, 2013
• Meeting Notes from Tue, Dec 3, 2013
• Meeting Notes from Tue, Nov 19, 2013
• Meeting Notes from Thu, Nov 14, 2013
• Meeting Notes from Tue, Oct 29, 2013
• Meeting Notes from Tue, Oct 22, 2013
• Meeting Notes from Tue, Oct 15, 2013
• Meeting Notes from Tue, Oct 1, 2013
• Meeting Notes from Tue, Sep 24, 2013
• Meeting Notes from Tue, Sep 17, 2013
• Meeting Notes from Tue, Sep 10, 2013
• Meeting Notes from Tue, Sep 3, 2013
• Meeting Notes from Tue, Aug 27, 2013
• Meeting Notes from Tue, Aug 20, 2013
• Meeting Notes from Tue, Aug 13, 2013
• Meeting Notes from Tue, Aug 6, 2013
• Meeting Notes from Tue, Jul 23, 2013
• Meeting Notes from Tue, Jul 09, 2013
• Meeting Notes from Tue, Jul 02, 2013
• Meeting Notes from Tue, Jun 25, 2013
• Meeting Notes from Tue, Jun 18, 2013
• Meeting Notes from Tue, Jun 4, 2013
• Meeting Notes from Tue, May 21, 2013
• Meeting Notes from Tue, May 14, 2013
• Meeting Notes from Tue, May 7, 2013
• Meeting Notes from Tue, Apr 30, 2013
• Meeting Notes from Tue, Apr 23, 2013
• Meeting Notes from Tue, Apr 16, 2013
• Meeting Notes from Tue, Apr 9, 2013
• Meeting Notes from Tue, Apr 2, 2013
• Meeting Notes from Thu, Mar 26, 2013
• Meeting Notes from Thu, Mar 21, 2013
• Meeting Notes from Tue, Mar 5, 2013
• Meeting Notes from Tue, Feb 26, 2013
• Meeting Notes from Thu, Feb 21 and Fri, Feb 22, 2013
• Meeting Notes from Tue, Feb 12, 2013
• Meeting Notes from Tue, Jan 29, 2013
• Meeting Notes from Tue, Jan 22, 2013
• Meeting Notes from Tue, Jan 15, 2013
• Meeting Notes from Tue, Jan 8, 2013
• Meeting Notes from Thu, Jan 3, 2013
• Meeting Notes from Thu, Dec 27, 2012
• Meeting Notes from Tue, Dec 18, 2012
• Meeting Notes from Tue, Dec 11, 2012
• Meeting Notes from Tue, Dec 4, 2012
• Meeting Notes from Tue, Nov 27, 2012
• Meeting Notes from Tue, Nov 20, 2012
• Meeting Notes from Tue, Nov 13, 2012
• Meeting Notes from Wed, Oct 31, 2012
• Meeting Notes from Tue, Oct 23, 2012
• Meeting Notes from Tue, Oct 16, 2012
• Meeting Notes from Tue, Oct 9, 2012
• Meeting Notes from Tue, Oct 2, 2012
• Meeting Notes from Wed, Sep 26, 2012
• Meeting Notes from Tue, Sep 18, 2012
• Meeting Notes from Tue, Sep 11, 2012
• Meeting Notes from Tue, Sept 4, 2012
• Meeting Notes from Tue, Aug 28, 2012
• Meeting Notes from Tue, Aug 21, 2012
• Meeting Notes from Tue, Aug 14, 2012
• Meeting Notes from Tue, Aug 7, 2012
• Meeting Notes from Tue, July 24, 2012
• Meeting Notes from Tue, July 17, 2012
• Meeting Notes from Tue, July 10, 2012
• Meeting Notes from Tue, July 3, 2012
• Meeting Notes from Tue, June 26, 2012
• Meeting Notes from Tue, June 19, 2012
• Meeting Notes from Tue, June 5, 2012
• Meeting Notes from Thu, May 31, 2012
• Meeting Notes from Tue, May 25, 2012
• Meeting Notes from Tue, May 15, 2012
• Meeting Notes from Tue, May 8, 2012
• Meeting Notes from Tue, May 1, 2012
• Meeting Notes from Thu, Apr 26, 2012
• Meeting Notes from Thu, Apr 19, 2012

Bugzilla Flags (in review)

By using the following whiteboard text and Bugzilla flags for tracking User Stories, Estimates, Target Milestones, and Blocked; we'll produce reports on how much work we have per sprint, how likely we'll land that work, and determine risks early.

Task Bugs: Estimates

• Estimates go on the dependent bugs, not [meta] bugs
• Except: new meta bugs that don't have any dependent bugs yet
• Grammar: [p={estimate}]
• The entire block is contained within square brackets, along with other tags
• Case-insensitive. p and P are both valid.
• Key and value are separated by a equal sign (no spaces).
• Key/value pairs are separated by a space and comma.
• Example: [p=5, ft:systems-fe]
• Initial may be filled in after a bug scrub with Engineering Leads
• On-going maintenance by developers, who know when information changes

Task Bugs: Target Milestones

• Target milestone set for [meta] and dependent bugs landing milestone
• [meta] bugs are set for milestone when last dependent bug is fixed
• On-going maintenance by developers, discussion with team on impact when milestone changes

Task Bugs: Blocking

• Blocking Bugs will set Project Flag to: {release}+
• Blocking Bug Nominations will set Project Flag to: {release}?

User Story Data

• ONE bug per user story, starting with the word [meta]
• Implementation tasks and bugs should be marked as blocking the user story bug.
• The user story id, as found in the Product backlog spreadsheet, is written in the bug whiteboard as "ucid:{id}", eg: "ucid:Browser326".
• The user story priority for a release is either P1 (committed) or P2 (targeted). This is written in the bug whiteboard as "{release}:{priority}", eg: "1.3:P1".
• The functional team that is responsible for the implementation of the user story is written as "ft:{teamname}", eg: "ft:media".

User Story Format

• Grammar: [ucid:{id}, {release}:p{1,2}, ft:{team-id}]
• The entire block is contained within square brackets
• Case-insensitive. UCID and ucid are both valid.
• Key and value are separated by a colon (no spaces).
• Key/value pairs are separated by a space and comma.
• Example: [ucid:System26, 1.3:P2, ft:systems-fe]