Hello media folk,

It's Q3 goals time, and I believe every team needs to have their Q3 goals "published" (i.e. on our wiki) by Thurs, July 12 which is two weeks from today.

For background, B2G is still the top company priority. In fact I believe the top three company priorities in order are
1) Supporting/advancing B2G
2) Helping Firefox desktop to remain competitive
3) Helping Firefox Android establish a market share

Although most of our work for B2G support will be completed shortly after Q3 starts (circa the first month or so), I think it makes sense to include "supporting" B2G in our goals.
____________
So here are the Q3 Media goals that seem to make sense to me and Rob (Roc):

* WebRTC (tracking the W3C and IETF webrtc/rtcweb specs) landed for desktop in mozilla-central
* Getting platform decoders working on the Otoro device
* Platform decoders working on a specific list of Android phones (the list would be the "first phase" of Android phones) * Support getting full getUserMedia working on B2G, as needed (this remaining work will be done by the B2G team itself, so that is why this goal says "support")
* Get the full getUserMedia backend working on desktop
* Get the full getUserMedia backend working on Android (we need at least one Android dev to work with us on this) * 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)
____________

Some clarifying notes:
* I need to verify with the Android devs that they have the bandwidth to help us get full getUserMedia working on Android in Q3. If they don't, then we may need to drop this. Anant will continue to be tech lead on getUserMedia (for all products: desktop, Android, and B2G).

*I'm also hoping we can get the Firefox desktop UI group and Android Native UI group to support the full getUserMedia UI in Q3. Once we have this, we can turn on full getUserMedia and WebRTC by default and not hide behind a config option (modulo bugs, of course).

*Regarding the Web Audio API goal, we may decide to do a "first phase" for Web Audio in Q3, but I think we at least need to communicate what we're planning to do for it (at least over the next few quarters)
____________

Comments and discussion welcome and appreciated!

I think we need to target trying to get consensus by next Thursday (July 5th) because we'll then need to see how our goals align with other team's goals and the Q3 goals of the company before the July 12th deadline.

Thanks!
-Maire

--
Maire Reavy<[email protected]>
Mozilla

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

Reply via email to