(Added times) |
|||
| (One intermediate revision not shown) | |||
| Line 9: | Line 9: | ||
== Where == | == Where == | ||
| - | + | Room 440. Go up the stairs from the main Atrium. | |
== Who == | == Who == | ||
| Line 27: | Line 27: | ||
* Lessons learned | * Lessons learned | ||
| + | '''Expected outcome''': Lessons learned wiki page | ||
| - | === 9:30 - 11:00 ::: 1.2 planning | + | |
| + | === 9:30 - 11:00 ::: 1.2 planning === | ||
* Content / architecture proposal | * Content / architecture proposal | ||
| Line 36: | Line 38: | ||
** New SDK engine (MADDE evolution plans) | ** New SDK engine (MADDE evolution plans) | ||
** Builds for multiple targets | ** Builds for multiple targets | ||
| + | |||
* Specific topics | * Specific topics | ||
** Hard-fp support for ARM | ** Hard-fp support for ARM | ||
| Line 41: | Line 44: | ||
** How does a device vendor get to be part of the SDK? | ** How does a device vendor get to be part of the SDK? | ||
** QEMU Skin support | ** QEMU Skin support | ||
| - | ** Device Control Framework | + | ** Device Control Framework |
*** GPS, accelerometer, camera, phone SIM | *** GPS, accelerometer, camera, phone SIM | ||
*** GUI for controlling. (e.g. What do we provide for setting the GPS location etc?) | *** GUI for controlling. (e.g. What do we provide for setting the GPS location etc?) | ||
| + | |||
* Next steps for 1.2 | * Next steps for 1.2 | ||
| + | |||
| + | '''Expected outcome''': Agree on vision for 1.2, Wiki page about the release vision | ||
| Line 52: | Line 58: | ||
* How to handle new potential verticals in 2011 (Tablet, TV, IVI, etc.) | * How to handle new potential verticals in 2011 (Tablet, TV, IVI, etc.) | ||
* QEMU image. Building with each vertical build | * QEMU image. Building with each vertical build | ||
| + | |||
| + | '''Expected outcome''': Collaboration with Release Management Team initiated | ||
| Line 61: | Line 69: | ||
** Team lead prospects | ** Team lead prospects | ||
* Other responsibilities | * Other responsibilities | ||
| + | |||
| + | '''Expected outcome''': Agree on sub-teams and leading roles, team structure wiki page updated | ||
| Line 66: | Line 76: | ||
* Some eating! | * Some eating! | ||
| + | |||
| + | '''Expected outcome''': Culinary satisfaction | ||
| - | === 13:30 - 14:30 ::: GTM activities | + | === 13:30 - 14:30 ::: GTM activities === |
* Release checklist with owner, approver(s) and schedules for each deliverable | * Release checklist with owner, approver(s) and schedules for each deliverable | ||
| Line 74: | Line 86: | ||
* Plan for 1.2 | * Plan for 1.2 | ||
| + | '''Expected outcome''': Release checklist wiki page | ||
| - | === 14:30 - 15:00 ::: Strategic directions | + | |
| + | === 14:30 - 15:00 ::: Strategic directions === | ||
* Requirements beyond 1.2 | * Requirements beyond 1.2 | ||
| Line 82: | Line 96: | ||
* Channel plans (OVI, AppUp, ...) | * Channel plans (OVI, AppUp, ...) | ||
| + | '''Expected outcome''': Ideas collected | ||
| - | === 15:00 - 15:30 ::: RPM support | + | |
| + | === 15:00 - 15:30 ::: RPM support === | ||
* rrpmbuild features (generate rpm package) | * rrpmbuild features (generate rpm package) | ||
* missing features (missing provides/requires) | * missing features (missing provides/requires) | ||
* app store expectations | * app store expectations | ||
| + | |||
| + | '''Expected outcome''': | ||
| Line 95: | Line 113: | ||
* Somewhere accessible by a single flight for all participants | * Somewhere accessible by a single flight for all participants | ||
** Paris? | ** Paris? | ||
| + | |||
| + | '''Expected outcome''': Agreement on next F2F | ||
Wednesday 17.11.2010, the whole day. From 9:00 to 16:00.
Start early, finish by 1600 (vacate the stadium for the game and for the 1845 flight out).
Room 440. Go up the stairs from the main Atrium.
Name in parenthesis is just the person who proposes an item, not an act of volunteering to run that show.
Expected outcome: Lessons learned wiki page
Expected outcome: Agree on vision for 1.2, Wiki page about the release vision
Expected outcome: Collaboration with Release Management Team initiated
Expected outcome: Agree on sub-teams and leading roles, team structure wiki page updated
Expected outcome: Culinary satisfaction
Expected outcome: Release checklist wiki page
Expected outcome: Ideas collected
Expected outcome:
Expected outcome: Agreement on next F2F