Meego Wiki
Views

SDK/Meetings/1st SDK Team F2F Workshop

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Added times)
Line 27: Line 27:
* Lessons learned
* Lessons learned
 +
'''Expected outcome''': Lessons learned wiki page
-
=== 9:30 - 11:00 ::: 1.2 planning (Ville/Veli)
+
 
 +
=== 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 (Veli)
+
** 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 (Ville) ===
+
=== 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 (Ville) ===
+
 
 +
=== 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 (Fathi) ===
+
 
 +
=== 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

Revision as of 13:46, 16 November 2010

Contents

1st MeeGo SDK Team Face-to-Face Workshop

When

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).

Where

Bob has a room for us!

Who

  • Nokia: Veli Kaksonen, Ville Lavonius, Fathi Boudra, Maurice Kalinowski, Jaya Uppalapati, Titta Väyrynen, Kamal Bhatt, Ronan MacLaverty (?), Janne Sormunen (if needed).
  • Intel: Bob Spencer, Kerry Jiang, Haitao Feng, Zhiyuan Lv, Jackie Wu (phone), Cathy Shen (phone), Elliot Smith (?), Dawn Foster (?),

Agenda

Name in parenthesis is just the person who proposes an item, not an act of volunteering to run that show.


9:00 - 9:30 ::: 1.1 post-mortem (Ville)

  • What went well
  • What didn't go well
  • Lessons learned

Expected outcome: Lessons learned wiki page


9:30 - 11:00 ::: 1.2 planning

  • Content / architecture proposal
    • High-level vision
    • Key use cases
      • Let's NOT go through the actual requirements-set in this meeting
    • New SDK engine (MADDE evolution plans)
    • Builds for multiple targets
  • Specific topics
    • Hard-fp support for ARM
    • Installing & Updating the SDK
    • How does a device vendor get to be part of the SDK?
    • QEMU Skin support
    • Device Control Framework
      • GPS, accelerometer, camera, phone SIM
      • GUI for controlling. (e.g. What do we provide for setting the GPS location etc?)
  • Next steps for 1.2

Expected outcome: Agree on vision for 1.2, Wiki page about the release vision


11:00 - 12:00 ::: Release Management with Distro Team F2F

  • Any open issues with the SDK and distro release process
  • How to handle new potential verticals in 2011 (Tablet, TV, IVI, etc.)
  • QEMU image. Building with each vertical build

Expected outcome: Collaboration with Release Management Team initiated


12:00 - 12:45 ::: SDK program setup

  • Subteams
    • Current
    • Needed
    • Team lead prospects
  • Other responsibilities

Expected outcome: Agree on sub-teams and leading roles, team structure wiki page updated


12:45 - 13:30 ::: Luch

  • Some eating!

Expected outcome: Culinary satisfaction


13:30 - 14:30 ::: GTM activities

  • Release checklist with owner, approver(s) and schedules for each deliverable
  • Creating a release check list (Titta)
  • Plan for 1.2

Expected outcome: Release checklist wiki page


14:30 - 15:00 ::: Strategic directions

  • Requirements beyond 1.2
  • Eclipse-support
  • Commercial tools (VTune, ...)
  • Channel plans (OVI, AppUp, ...)

Expected outcome: Ideas collected


15:00 - 15:30 ::: RPM support

  • rrpmbuild features (generate rpm package)
  • missing features (missing provides/requires)
  • app store expectations

Expected outcome:


15:30 - 16:00 ::: Next face-to-face meeting logistics

  • January 2011?
  • Somewhere accessible by a single flight for all participants
    • Paris?

Expected outcome: Agreement on next F2F

Personal tools