Meego Wiki
Views

SDK/Team Proposal

From MeeGo wiki
< SDK(Difference between revisions)
Jump to: navigation, search
(Added notes from Kerry's mail)
m (→SDK Team Proposal)
 
(3 intermediate revisions not shown)
Line 1: Line 1:
= SDK Team Proposal =
= SDK Team Proposal =
-
* PM - Veli Kaksonen (official), Bob Spencer (Backup)
+
* Program Manager - Veli Kaksonen (official), Bob Spencer (Backup)
* Architect - Bob Spencer (official), Veli Kaksonen (Backup)
* Architect - Bob Spencer (official), Veli Kaksonen (Backup)
* Product Manager - Ville Lavonius  
* Product Manager - Ville Lavonius  
-
* Release Manager - Fathi Boudra (official), Kevin Wang (Backup)
+
* Release Manager - Fathi Boudra (official), Jackie Wu (Backup)
-
* QA Lead - Jaya Uppalapati (official), Cathy Shen (backup)
+
* QA Lead - Jaya Uppalapati (official), Ionut Gavaz (backup)
* Documentation Lead - Bob, Elliot, Ronan, Titta... ??
* Documentation Lead - Bob, Elliot, Ronan, Titta... ??
* Toolchain Lead - Jarmo Kant
* Toolchain Lead - Jarmo Kant
Line 17: Line 17:
* Chroot & Xephyr - Haitao Feng
* Chroot & Xephyr - Haitao Feng
* Toolchains ARM - Al Nikolov
* Toolchains ARM - Al Nikolov
-
* Toolchains IA - Kevin Wang
+
* Toolchains IA32 - Jackie Wu
== Subsystem Maintainers (official, backup) ==
== Subsystem Maintainers (official, backup) ==
Line 40: Line 40:
* Few more comments on task breakdown, to see if there is something important/big item missing here:
* Few more comments on task breakdown, to see if there is something important/big item missing here:
-
** What about integration of tools like PowerTOP, Oprofile,
+
** What about integration of tools like PowerTOP, Oprofile, Valgrind?  including integration into OBS as RPMs and with Qt Creator as plugins
-
Valgrind?  including integration into OBS as RPMs and with Qt Creator as plugins
+
** What about integration with Qt WRT SDK? Qt WRT not in the scope of 1.1?
-
** What about integration with WRT SDK? WRT not in the scope of 1.1?
+
*** Fathi: Qt WRT is available for MeeGo 1.1. It's a bit late for integration into 1.1. I'm in favor of postponing to 1.2.
-
** Is the UI/QT Designer considered by Qt Creator efforts, AFAIK, it is also standalone tool and important to developers? Is it good enough to support all Toolkits/APIs?
+
** Is the UI/Qt Designer considered by Qt Creator efforts, AFAIK, it is also standalone tool and important to developers? Is it good enough to support all Toolkits/APIs?
 +
*** Fathi: definitely, yes. Qt Creator team planned to improve this area. What do you mean by "all" Toolkits/APIs?
** Device simulation (skin, platform specific devices) already covered by QEMU? Should we separate the efforts on QEMU to bootup and run MeeGo images with good performance from the efforts on simulating devices specific to platforms for multiple OSs(Win,Linux, Mac). Both are big task task items.
** Device simulation (skin, platform specific devices) already covered by QEMU? Should we separate the efforts on QEMU to bootup and run MeeGo images with good performance from the efforts on simulating devices specific to platforms for multiple OSs(Win,Linux, Mac). Both are big task task items.
 +
*** Fathi: true. actually, the same team is handling QEMU related tasks.

Latest revision as of 11:33, 8 April 2011

Contents

SDK Team Proposal

  • Program Manager - Veli Kaksonen (official), Bob Spencer (Backup)
  • Architect - Bob Spencer (official), Veli Kaksonen (Backup)
  • Product Manager - Ville Lavonius
  • Release Manager - Fathi Boudra (official), Jackie Wu (Backup)
  • QA Lead - Jaya Uppalapati (official), Ionut Gavaz (backup)
  • Documentation Lead - Bob, Elliot, Ronan, Titta... ??
  • Toolchain Lead - Jarmo Kant

Package Maintainers

  • MADDE - Fathi Boudra
  • Qt Creator + plugins - Fathi Boudra
  • QEMU - Fathi Boudra
  • Virtual Box - Haitao Feng
  • Chroot & Xephyr - Haitao Feng
  • Toolchains ARM - Al Nikolov
  • Toolchains IA32 - Jackie Wu

Subsystem Maintainers (official, backup)

[development. These guys know the components inside out]:

  • Installer - (we need to first figure out what installer we use)
  • Qt Creator - Maurice Kalinowski, John Chen
  • Qt Creator plugin for MADDE - Nishant Tandon
  • Qt Creator plugin for OBS - Max Yu
  • Qt Creator plugins ... - ...
  • MADDE -
  • OBS - (is this ours or not?)
  • QEMU - Riku Voipio, Zhiyan Lv
  • Virtual Box run environment - Haitao Feng
  • Chroot & Xephyr run environment - Haitao Feng
  • Toolchains (this needs to be opened to gcc, glibc...)- (Risto Lankinen)

Notes / discussion

From Kerry:

  • Few more comments on task breakdown, to see if there is something important/big item missing here:
    • What about integration of tools like PowerTOP, Oprofile, Valgrind? including integration into OBS as RPMs and with Qt Creator as plugins
    • What about integration with Qt WRT SDK? Qt WRT not in the scope of 1.1?
      • Fathi: Qt WRT is available for MeeGo 1.1. It's a bit late for integration into 1.1. I'm in favor of postponing to 1.2.
    • Is the UI/Qt Designer considered by Qt Creator efforts, AFAIK, it is also standalone tool and important to developers? Is it good enough to support all Toolkits/APIs?
      • Fathi: definitely, yes. Qt Creator team planned to improve this area. What do you mean by "all" Toolkits/APIs?
    • Device simulation (skin, platform specific devices) already covered by QEMU? Should we separate the efforts on QEMU to bootup and run MeeGo images with good performance from the efforts on simulating devices specific to platforms for multiple OSs(Win,Linux, Mac). Both are big task task items.
      • Fathi: true. actually, the same team is handling QEMU related tasks.
Retrieved from "http://wiki.meego.com/SDK/Team_Proposal"
Personal tools