Hello!
I have started collecting the actions from the mini summit into our technical requirement (TR) blueprints in Launchpad. I created 4 already check the links below:
https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multim... https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multim... https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multim... https://blueprints.launchpad.net/linaro-multimedia-wg/+spec/tr-linaro-multim...
To ease any immediate worries - relax folks! These are not yet connected anywhere, so they do not show up in any status reports for the cycle. However they should be used as handles to register any work involved, including postponing or deferrals and track requirements and dependencies. So they are really placeholders for now - whiteboards for the work to come. This means also that the assignees will probably be reconfigured once we plan the work properly.
More will come based on the work to be done still in the mini summit. I will be posting the new blueprints as soon as they are ready.
Kurt one question: the parsers work as indicated in http://pad.ubuntu.com/g40gcIob12 - does that merit a separate blueprint or can the work be tracked in the vendor survey associated with the openmax blueprint?
BR,
************************************* Ilias Biris, Aallonkohina 2D 19, 02320 Espoo, Finland Tel: +358 50 4839608 (mobile) Email: ilias dot biris at linaro dot org Skype: ilias_biris *************************************