MeeGo Architecture
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.
Team
- Arjan van de Ven, Chief Architect, responsible for MeeGo architecture
- Sakari Poussa, Core OS Architect, responsible for Core OS architecture
- Mikko Ylinen, Handset UX Architect, responsible for Handset UX architecture
- Sunil Saxena, Core OS Architect, responsible for Core OS architecture
Communication
Process
- Architecture team meets once a week. Currently the meetings are not public.
- Agenda and minutes of the meetings will be posted to the meego-architecture mailing list
- Anyone can propose topics to the architecture team agenda
- Architecture topics can and should be discussed on meego-architecture mailing list
- Architecture team is responsible of making the decision in case consensus is not reached
Process Improvement Topics
- How to make the architecture meetings open. Not all the topics can be open but most can be. Examples of non-open parts includes topics which involves IPR, legal, patent, business, product or schedule sensitive material.
Documentation
- Developer Documentation: APIs, tutorials, videos, examples ([1]), to be published soon
- Architecture Documentation: High level architecture pictures and description ([2])
- Developer and Subsystem Documentation: Detailed technical description of each MeeGo subsystem. Guidelines for developers working on MeeGo. (Architecture/Documentation)
Meetings
Upcoming Features
- PIM Storage in Evolution Data Server (EDS) and email via Camel, SyncEvolution as sync engine
Tools
Architecture tools
write my essay