(→MeeGo Architecture) |
Sunilsaxena (Talk | contribs) m (→Status) |
||
| Line 22: | Line 22: | ||
* Subsystem Documentation: Detailed technical description of each MeeGo subsystem ([[http://wiki.meego.com/Architecture/Documentation]]), to be created soon | * Subsystem Documentation: Detailed technical description of each MeeGo subsystem ([[http://wiki.meego.com/Architecture/Documentation]]), to be created soon | ||
| - | == | + | === Meetings === |
| + | |||
| + | * [[Architecture/Meetings]] - Meetings - agenda, minutes | ||
== Plans == | == Plans == | ||
== Tools == | == Tools == | ||
Contents |
MeeGo architecture team is responsible for defining and managing the MeeGo architecture. MeeGo architecture consists of Core OS layer and number of UX verticals on top the Core OS layer. The architecture team decides which component to use for the functionality needed in MeeGo with the objective of consistency inside the Core OS and to the applications that run above it.