MeeGo Announces Handset and Core OS Hierarchies
Who does what at the MeeGo project.
MeeGo, the open source mobile OS jointly backed by Intel and Nokia, has been fleshing out some of the finer points of the project's governance and policy over on MeeGo.com. The people in charge of both the Core OS and the Handset Program were also named and their positions were fleshed out.
From the project's website:
The Core OS Program has the following structure:
Karl Gran manages the MeeGo Core OS Program, responsible for delivering all the platform functionality to meet the needs of the official MeeGo device categories.
Gavin Hindman is the product manager for the MeeGo Core OS, responsible for managing the content of the Core OS releases, in terms of requirements, roadmap and release descriptions, and for negotiating the content with the core program and its various stakeholders, such as other MeeGo programs and all Working Groups.
Sakari Poussa is the lead architect of MeeGo Core OS, responsible for architecture, day-to-day technical decisions, and architecture evolution in that area.
Alexander Kanevskiy is the MeeGo Core OS release manager, responsible of planning and producing the Core OS releases.
Tommi Toropainen is the QA lead for MeeGo Core OS
The handset program has the following structure:
Pierre Blouin manages the MeeGo Handset Program, responsible for delivering the reference UX for the handset category.
Sami Pienimäki is the product manager for the MeeGo Handset UX, responsible for managing the content of the handset releases in terms of requirements and of roadmap and release descriptions, and for negotiating the content with the program and its various stakeholders, steered by the MeeGo Handset Working Group.
Mikko Ylinen is the lead architect for the MeeGo Handset UX, responsible for architecture, day-to-day technical decisions, and architecture evolution in that area.
Petri Koski is the QA lead for the MeeGo Handset UX.
Chris Ferron is the MeeGo Handset UX release manager, responsible for planning and producing handset releases.
Martin Schuele is the lead designer for the MeeGo handset UX and MeeGo Touch Framework, responsible for the design and validation of the MeeGo Handset UX
MeeGo is governed by a Technical Steering Committee, which sets goals for the project and speaks on its behalf. Imad Sousou and Valtteri Halla serve as the project's benevolent dictators. The Technical Steering Group meets biweekly.
In addition to the Technical Steering Committee, hands-on development is divided up into teams that handle distribution development, manage programs, and uphold quality assurance.
There are also four working groups that are headed by delegates of the Technical Steering Committee. These groups are focused on one of four areas of the project and provide suggestions and expert advice regarding policy, requirements, and direction. Currently the working groups are, Netbook, Handheld, In-Vehicle, and Connected TV.
If the hierarchy looks familiar, that's because the MeeGo Project operates under the supervision of the Linux Foundation.
Azure CTO says Redmond has already considered the unthinkable.
Lead developer quells rumors that the Debian version is slated for center stage.
MSBuild is now just another GitHub project as Redmond continues its path to the light.
Malware could pass data and commands between disconnected computers without leaving a trace on the network.
New rules emphasize collegiality in coding.
Upstart lands in the dust bin as a new era begins for Linux.
HP's annual Cyber Risk report offers a bleak look at the state of IT.
But what do the big numbers really mean?
.NET Core execution engine is the basis for cross-platform .NET implementations.
The Xnote trojan hides itself on the target system and will launch a variety of attacks on command.