I think we should remove the "full getUserMedia backend working on Android" goal for Q3. (I've quoted the current goal list below for reference.)

Reasoning:
Even if we remove the UI piece of this goal, there's the potential for a fair bit of work to get the Android backend working. We would need to either get the core code from webrtc.org working on Android or write an equivalent backend using the NDK, which would likely go away after we landed WebRTC for Android. Landing part of WebRTC for Android is not a Q3 goal, and nothing should depend on that happening. Anant is going to explore implementing getUserMedia using the NDK; if that turns out to be fairly straightforward and not too time consuming, we may do that for Q3. But if it's not, we don't want to do that work for Q3. Getting WebRTC for desktop landed on mozilla-central is a top priority, and since full getUserMedia for Android and WebRTC for desktop would share some developers, I and several other WebRTC team members think it makes sense to just remove the Q3 Android getUserMedia goal.

Thanks!
-Maire


On 7/2/2012 6:19 PM, Maire Reavy wrote:
Q3 Media Goals:
* WebRTC (tracking the W3C and IETF webrtc/rtcweb specs) landed for desktop in mozilla-central (This includes both PeerConnection and full getUserMedia, but not UI -- UI will be a goal for the Firefox team) * Platform decoders running on the Otoro device will playback videos at a similar performance metric to the equivalent android player * For a specific list of Android phones (the list will be the "first phase" of Android phones), platform decoders running in Firefox will playback videos at a similar performance metric to the videos playing back in the default browser on the same phone * Get the full getUserMedia backend working on Android (we need at least one Android dev to work with us on this -- I will make sure the Android team can support this in Q3, else we should/will drop this for Q3) * Publish (to one or more of our newsgroups) a plan for supporting the Web Audio API (or at least the pieces of the API we want to support in the near term)

Mission Note: The media team will support B2G's efforts to ship B2G version 1 above any goals for this quarter.

--
Maire Reavy <[email protected]>
Mozilla



_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media

Reply via email to