Media/WebRTC: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
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]].
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 [http://www.webrtc.org/ WebRTC project page] set up by Google for more interesting links and details.
Checkout the [http://www.webrtc.org/ WebRTC project page] set up by Google for interesting links and details.


==[https://wiki.mozilla.org/FirefoxOS/functionalteams#WebRTC WebRTC Team Info] & [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlKBl68pRmhsdENBZDRKclBSZlhiRC1tb1BGQS1JU2c&usp=drive_web#gid=0 Extended Team Members List]==
==[https://wiki.mozilla.org/FirefoxOS/functionalteams#WebRTC WebRTC Team Info] & [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlKBl68pRmhsdENBZDRKclBSZlhiRC1tb1BGQS1JU2c&usp=drive_web#gid=0 Extended Team Members List]==


=='''Draft''' Project Planning [http://people.mozilla.org/~sescalante/webRTC-allup/webRTC-allupGantt.html View]==
==='''Draft''' Project Planning [http://people.mozilla.org/~sescalante/webRTC-allup/webRTC-allupGantt.html View]===
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.  This will be continually updated as teams come back with more solid estimates for when portions can be completed.
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.  This will be continually updated as teams come back with more solid estimates for when portions can be completed.
=== Meetings ===
* [[Media/WebRTC/WebRTC_workweek_20130610| WebRTC work week June 10 2013]]
* [http://ietf.org/ IETF Berlin Upcoming Standards Meetings]
* Cross Team sync: Tuesday's 11:30 PST (owner shell@mozilla.com)


== Project Documentation ==
== Project Documentation ==
Line 20: Line 25:
*[https://people.mozilla.org/~dhenein/labs/loop-docs/ In Progress- Loop Design Document]
*[https://people.mozilla.org/~dhenein/labs/loop-docs/ In Progress- Loop Design Document]


== Work Weeks ==
==Bugzilla Flags (under final review)==
Past work week Jun 10-14 2013: --  [[Media/WebRTC/WebRTC_workweek_20130610| WebRTC work week June 10 2013]]


== [http://ietf.org/ IETF Berlin Upcoming Standards Meetings] ==
The goal is for the burden of marking bugs to be far less than randomizing folks with the frequent status requests required to coordinate a project.  
 
==webRTC Platform Gantt: [http://people.mozilla.org/~sescalante/webRTC-mini/webRTC-miniGantt.html here] (updated Tuesday's before stand-up)==
 
==Bugzilla Flags (under final review)==
The goal is for the burden of marking bugs to be far less than randomizing folks with frequent status requests required to coordinate a project.  


Using the following Bugzilla whiteboard text & flags for tracking - we'll produce reports on how much work we have per sprint, how likely we'll land that work, and see risks early.
Using the following Bugzilla whiteboard text & flags for tracking - we'll produce reports on how much work we have per sprint, how likely we'll land that work, and see risks early.
Line 47: Line 46:
* Target milestone are set for [meta] and dependent bugs  
* Target milestone are set for [meta] and dependent bugs  
* [meta] bugs are set for milestone when last dependent bug is fixed
* [meta] bugs are set for milestone when last dependent bug is fixed
* FxOS teams are using mobile targets
* webRTC is using Fx targets (ex: "mozilla32") for when a fix is targeted to land- because the work spans FxOS and Fx


'''Task Bugs: Blocking'''
'''Task Bugs: Blocking'''
Line 80: Line 81:
* Summary: This tracks the media quality and connectivity work for MLP.   
* Summary: This tracks the media quality and connectivity work for MLP.   
* Metabug: ([https://bugzilla.mozilla.org/show_bug.cgi?id=970426 bug-970426])
* Metabug: ([https://bugzilla.mozilla.org/show_bug.cgi?id=970426 bug-970426])
* webRTC Platform view: [http://people.mozilla.org/~sescalante/webRTC-mini/webRTC-miniGantt.html here] (updated Tuesday's before stand-up)


<bugzilla>
<bugzilla>
Line 192: Line 194:
*[[Media/WebRTC/2012-04-19| Meeting Notes from Thu, Apr 19,  2012]]
*[[Media/WebRTC/2012-04-19| Meeting Notes from Thu, Apr 19,  2012]]


==Fixed MLP Blockers==
==Fixed MLP Blockers (in progress)==
Working on figuring how to say resolution = "--" in JSON, for demo purposes pulled "fixed"
Working on figuring how to say resolution = "--" in JSON (to show the interesting Open blockers), for demo purposes pulled "fixed"


<bugzilla>
<bugzilla>
Line 204: Line 206:
</bugzilla>
</bugzilla>


==Priority Bugs==
==Priority Bugs (in progress)==
Option to pull query based on whiteboard tag.  Could seperate by group (Core:webrtc, Core:signalling, Loop:server, etc.)
Option to pull query based on whiteboard tag.  Could seperate by group (Core:webrtc, Core:signalling, Loop:server, etc.)


----
----
Confirmed users
1,094

edits