MeeGo wiki - User contributions [en]

Architecture/Meetings/20101124 Weekly

2011-01-27T22:41:39Z

Sunilsaxena: /* Summary */

= MeeGo Architecture Weekly Meeting 20101124 =

This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101124 07:00 PST.

== Attendees ==
* Sunil Saxena, Arjan van de Ven, James Ketrenos, Sakari Poussa, Mikko K Ylinen, Danny Bennett

== Agenda and minutes ==
* MeeGo 1.3 targets for Kernel, X, Qt, etc

== Summary ==
* Targets for various subsystems are provided in the table below:

{| border="2"
! Component
! MeeGo 1.2
! MeeGo 1.3
! Rational
|-
| Reference Kernel
|
|
|
|-
| Gcc
|
|
|}

Architecture/Meetings/2011Jan26 Weekly

2011-01-27T22:05:32Z

Sunilsaxena: Created page with "= MeeGo Architecture Weekly Meeting 2010, Jan 26 = This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on Jan 26th, 2011 07:00 PST == A…"

= MeeGo Architecture Weekly Meeting 2010, Jan 26 =
This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on Jan 26th, 2011 07:00 PST

== Attendees ==
* Mikko Ylinen, Sakari Poussa, Mark Skarpness, Arjan Van De Ven, Sean V Kelley, Mats D Wichmann, Danny Bennett, Janne Sormunen

== Agenda and minutes ==
* MeeGo 1.1 Compliance
* MeeGo API Update

== Summary ==
*

Architecture/Meetings/2011Jan05 Weekly

2011-01-27T22:02:45Z

Sunilsaxena: /* MeeGo Architecture Weekly Meeting 2010, Jan 05 */

= MeeGo Architecture Weekly Meeting 2010, Jan 05 =
This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on Jan 5th, 2011 07:00 PST

== Attendees ==
* Sunil Saxena, Arjan van de Ven, Sakari Poussa, Mikko K Ylinen, Randy Hall, Ryan Ware, Janne Hirvimies, Janne Mantyla, Janne Karhunen, Ilhan Gurel, Casey Schaufler, Juha Tikkanen, Elena Reshetova

== Agenda and minutes ==
* MeeGo Security Update

== Summary ==
* We reviewed status of security patches since they are not integrated into MeeGo so far. Arjan will start integrating the security-next patch end of this week.
* Most of the components are ready to be integrated into MeeGo with one exception. The exception is the use of libcreds3 that needs to be removed from usage completely. Work is ongoing and we expect the results in 1-2 weeks. Worst possible situation is that we need some parts of libcreds library and we would have to take that upstream.
* Overall, we all agreed this is great progress and we should attempt to keep security as part of MeeGo 1.2. We all understand the risks of getting in this close to the freeze. We all understand that regression / integration issues may throw out security from MeeGo 1.2 and it is the risk we are all ready to take.
* We need a gate keeper to help smoothen the process of integration into MeeGo 1.2 for the next 2-3 months. Ryan agreed to take on the role of gate keeper.

Architecture/Meetings/2011Jan05 Weekly

2011-01-27T21:53:45Z

Sunilsaxena: Created page with "= MeeGo Architecture Weekly Meeting 2010, Jan 05 = == Attendees == * Sunil Saxena, Arjan van de Ven, Sakari Poussa, Mikko K Ylinen, Randy Hall, Ryan Ware, Janne Hirvimies, Janne…"

= MeeGo Architecture Weekly Meeting 2010, Jan 05 =

== Attendees ==
* Sunil Saxena, Arjan van de Ven, Sakari Poussa, Mikko K Ylinen, Randy Hall, Ryan Ware, Janne Hirvimies, Janne Mantyla, Janne Karhunen, Ilhan Gurel, Casey Schaufler, Juha Tikkanen, Elena Reshetova

== Agenda and minutes ==
* MeeGo Security Update

== Summary ==
* We reviewed status of security patches since they are not integrated into MeeGo so far. Arjan will start integrating the security-next patch end of this week.
* Most of the components are ready to be integrated into MeeGo with one exception. The exception is the use of libcreds3 that needs to be removed from usage completely. Work is ongoing and we expect the results in 1-2 weeks. Worst possible situation is that we need some parts of libcreds library and we would have to take that upstream.
* Overall, we all agreed this is great progress and we should attempt to keep security as part of MeeGo 1.2. We all understand the risks of getting in this close to the freeze. We all understand that regression / integration issues may throw out security from MeeGo 1.2 and it is the risk we are all ready to take.
* We need a gate keeper to help smoothen the process of integration into MeeGo 1.2 for the next 2-3 months. Ryan agreed to take on the role of gate keeper.

Architecture/Meetings/20101208 Weekly

2011-01-27T18:38:28Z

Sunilsaxena: Created page with "= MeeGo Architecture Weekly Meeting 20101208 = This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101208 07:00 PST. == Attendees…"

= MeeGo Architecture Weekly Meeting 20101208 =

This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101208 07:00 PST.

== Attendees ==
* Sunil Saxena, Arjan van de Ven, Sakari Poussa, Mikko K Ylinen, Danny Bennett, Igor Stoppa, Padmashree Apparao, Semi Malinen, Ryan Ware, Randy Hall, Petri Ahonen;

== Agenda and minutes ==
* MOSLO Discussion

== Summary ==
* We discussed trusted bootloader implications in MeeGo. FW verifies bootloader and bootloader verifies MeeGo kernel. MeeGo does not prescribe a bootloader.
* If the bootloader is not trusted – the device would not boot.
* If the kernel running is not trusted – functionality of the MeeGo kernel may be limited
** Power Management and battery charging functionality will be limited
* The bootloader can provide command line parameters to the MeeGo Kernel – i.e. reason for boot
* The bootloader can provide SW updates, fix the root file system for MeeGo
* Acting dead mode should be implemented in the bootloader – it should be like waiting to kexec the MeeGo kernel in the bootloader itself
** Acting dead mode should not allow any updates or fixing of the software
** Acting dead mode could allow efficient charging of device
** It could support Alarm UI for the device

Architecture/Meetings

2011-01-27T18:08:18Z

Sunilsaxena: /* Weekly Meetings */

= MeeGo Architecture Meetings =

This page lists the MeeGo Architecture Team meetings, agenda and minutes.

== Weekly Meetings ==
MeeGo Architecture team meets weekly every Wednesday 7:00am PST. Duration 1 hour.
* [[Architecture/Meetings/2011Jan26_Weekly]]
* Jan-19-2011 Meeting Cancelled
* Jan-12-2011 Meeting Cancelled
* [[Architecture/Meetings/2011Jan05_Weekly]]

* [[Architecture/Meetings/20101208_Weekly]]
* [[Architecture/Meetings/20101124_Weekly]]
* [[Architecture/Meetings/20101117_Weekly]]
* Nov-17-2010 Meeting Cancelled due to MeeGo Conference
* [[Architecture/Meetings/20101110_Weekly]]
* Nov-03-2010 Meeting Cancelled due to Linux Plumbers Conference
* [[Architecture/Meetings/20101026_Weekly]]
* [[Architecture/Meetings/20101019_Weekly]]

== Agenda Bin List ==
Here is a list of Agenda items:

* Feature / Architecture for MeeGo 1.2 and 1.3 closure
* MeeGo Architecture Forum at MeeGo Conference
* MeeGo Power-management architecture
* MeeGo Security Architecture Update
* Package Management
* Bugzilla structure
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling

Architecture/Meetings/20101124 Weekly

2010-11-29T06:00:27Z

Sunilsaxena: Created page with "= MeeGo Architecture Weekly Meeting 20101124 = This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101124 07:00 PST. == Attendees…"

Architecture/Meetings/20101117 Weekly

2010-11-29T05:48:32Z

Sunilsaxena: Created page with "= MeeGo Architecture Weekly Meeting 20101117 = Although the weekly conference call was cancelled, the core team decided to meet at the conference to tackle systemd/upstart f2f. …"

= MeeGo Architecture Weekly Meeting 20101117 =

Although the weekly conference call was cancelled, the core team decided to meet at the conference to tackle systemd/upstart f2f.

== Attendees ==
* Sunil Saxena, Arjan van de Ven, Sakari Poussa, Mikko K Ylinen, Auke-jan Kok, Janne Karhunen

== Agenda and minutes ==
* Upstart / Systemd closure

== Summary ==
* We all agreed that systemd is the way to go for long term. We must have systemd for MeeGo 1.3.
* We may have to live with upstart for MeeGo 1.2 as systemd would not mature in time and would require lots of resources to make it real.
* We agreed to a hand-on workshop on making systemd a reality right after Thanksgiving.

Architecture/Meetings

2010-11-29T05:42:55Z

Sunilsaxena: /* Weekly Meetings */

= MeeGo Architecture Meetings =

This page lists the MeeGo Architecture Team meetings, agenda and minutes.

== Weekly Meetings ==
MeeGo Architecture team meets weekly every Wednesday 7:00am PST. Duration 1 hour.
* [[Architecture/Meetings/20101124_Weekly]]
* [[Architecture/Meetings/20101117_Weekly]]
* Nov-17-2011 Meeting Cancelled due to MeeGo Conference
* [[Architecture/Meetings/20101110_Weekly]]
* Nov-03-2011 Meeting Cancelled due to Linux Plumbers Conference
* [[Architecture/Meetings/20101026_Weekly]]
* [[Architecture/Meetings/20101019_Weekly]]

== Agenda Bin List ==
Here is a list of Agenda items:

* Feature / Architecture for MeeGo 1.2 and 1.3 closure
* MeeGo Architecture Forum at MeeGo Conference
* MeeGo Power-management architecture
* MeeGo Security Architecture Update
* Package Management
* Bugzilla structure
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling

Architecture/Meetings/20101110 Weekly

2010-11-11T16:04:18Z

Sunilsaxena: Created page with "= MeeGo Architecture Weekly Meeting 20101110 = This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101110 07:00 PST. == Attendees…"

= MeeGo Architecture Weekly Meeting 20101110 =

This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101110 07:00 PST.

== Attendees ==
* Sunil Saxena, Arjan van de Ven, Sean V Kelley, Sakari Poussa, Mikko K Ylinen, Danny Bennett

== Agenda and minutes ==
* Review the material for the conference
* Bootloader requirement – Arjan – delayed.

== Summary ==
* We reviewed architecture presentation for the MeeGo conference next week and will continue to work over email.
* We agreed that MCE, Sharing Framework, Non-Graphics-Feedback (NGF), Qt style APIs and Profiles identified on the MeeGo wiki Architecture page should be integrated as new technologies into MeeGo so that we can all review documentation and code and ensure appropriate resources are assigned to fix issues appropriately.

Architecture/Meetings

2010-11-11T15:55:21Z

Sunilsaxena: /* Weekly Meetings */

= MeeGo Architecture Meetings =

This page lists the MeeGo Architecture Team meetings, agenda and minutes.

== Weekly Meetings ==
MeeGo Architecture team meets weekly every Wednesday 7:00am PST. Duration 1 hour.
* Nov-17-2011 Meeting Cancelled due to MeeGo Conference
* [[Architecture/Meetings/20101110_Weekly]]
* Nov-03-2011 Meeting Cancelled due to Linux Plumbers Conference
* [[Architecture/Meetings/20101026_Weekly]]
* [[Architecture/Meetings/20101019_Weekly]]

== Agenda Bin List ==
Here is a list of Agenda items:

* Feature / Architecture for MeeGo 1.2 and 1.3 closure
* MeeGo Architecture Forum at MeeGo Conference
* MeeGo Power-management architecture
* MeeGo Security Architecture Update
* Package Management
* Bugzilla structure
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling

Architecture/Meetings

2010-11-11T15:54:12Z

Sunilsaxena: /* Weekly Meetings */

= MeeGo Architecture Meetings =

This page lists the MeeGo Architecture Team meetings, agenda and minutes.

== Weekly Meetings ==
MeeGo Architecture team meets weekly every Wednesday 7:00am PST. Duration 1 hour.
* [[Architecture/Meetings/20101110_Weekly]]
* Nov-03-2011 Meeting Cancelled due to Linux Plumbers Conference
* [[Architecture/Meetings/20101026_Weekly]]
* [[Architecture/Meetings/20101019_Weekly]]

== Agenda Bin List ==
Here is a list of Agenda items:

* Feature / Architecture for MeeGo 1.2 and 1.3 closure
* MeeGo Architecture Forum at MeeGo Conference
* MeeGo Power-management architecture
* MeeGo Security Architecture Update
* Package Management
* Bugzilla structure
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling

Architecture/Meetings/20101026 Weekly

2010-10-29T17:00:26Z

Sunilsaxena: /* Attendees */

= MeeGo Architecture Weekly Meeting 20101026 =

This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101026 07:00 PST.

== Attendees ==
* Sunil Saxena, Arjan ven de Van, Sean V Kelley, Randy E Hall, Ryan R Ware, Sakari Poussa, Mikko K Ylinen, Danny Bennett, Janne Karhunen

== Agenda and minutes ==
* Init vs Upstart
* Review updated architecture pages on meego.com and wiki.meego.com

=== Init vs Upstart ===
* We discussed upstart vs Init one more time.
* Agreed to consolidate the requirements into one document so that we can decide what can be accomplished in the next 4 weeks of development.
* Agreed to do as little as possible so that we have a solution for MeeGo 1.2 that can be deployed.
* The requirement document will complete this week and we will define next steps next week.

=== Updated Architecture pages on meego.com and wiki.meego.com ===
* Approved the pages to go live 10-27-2009.

Architecture/Meetings

2010-10-29T12:44:19Z

Sunilsaxena: /* Weekly Meetings */

Architecture/Meetings/20101026 Weekly

2010-10-29T12:43:47Z

Sunilsaxena: /* Meetings-2010-10-26 */

= MeeGo Architecture Weekly Meeting 20101026 =

This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101026 07:00 PST.

== Attendees ==
* Sunil Saxena, Arjan ven de Van, Sean V Kelley, Randy E Hall, Ryan R Ware
* Sakari Poussa, Mikko K Ylinen, Danny Bennett, Janne Karhunen

== Agenda and minutes ==
* Init vs Upstart
* Review updated architecture pages on meego.com and wiki.meego.com

=== Init vs Upstart ===
* We discussed upstart vs Init one more time.
* Agreed to consolidate the requirements into one document so that we can decide what can be accomplished in the next 4 weeks of development.
* Agreed to do as little as possible so that we have a solution for MeeGo 1.2 that can be deployed.
* The requirement document will complete this week and we will define next steps next week.

=== Updated Architecture pages on meego.com and wiki.meego.com ===
* Approved the pages to go live 10-27-2009.

Architecture/Meetings

2010-10-29T12:42:38Z

Sunilsaxena: /* Weekly Meetings */

Architecture/Meetings/20101027 Weekly

2010-10-29T12:41:24Z

Sunilsaxena: /* Meetings-2010-10-26 */

= MeeGo Architecture Weekly Meeting 20101026 =

This document contains agenda and minutes of MeeGo Architecture weekly teleconference meeting on 20101026 07:00 PST.

== Attendees ==
* Sunil Saxena, Arjan ven de Van, Sean V Kelley, Randy E Hall, Ryan R Ware
* Sakari Poussa, Mikko K Ylinen, Danny Bennett, Janne Karhunen

== Agenda and minutes ==
* Init vs Upstart
* Review updated architecture pages on meego.com and wiki.meego.com

=== Init vs Upstart ===
* We discussed upstart vs Init one more time.
* Agreed to consolidate the requirements into one document so that we can decide what can be accomplished in the next 4 weeks of development.
* Agreed to do as little as possible so that we have a solution for MeeGo 1.2 that can be deployed.
* The requirement document will complete this week and we will define next steps next week.

=== Updated Architecture pages on meego.com and wiki.meego.com ===
* Approved the pages to go live 10-27-2009.

Architecture/Meetings

2010-10-29T11:35:46Z

Sunilsaxena: /* Weekly Meetings */

Architecture

2010-10-28T14:08:51Z

Sunilsaxena: /* Documentation */

== 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 ==

* '''[http://meego.com/users/arjan Arjan van de Ven]''', Chief Architect, responsible for MeeGo architecture
* '''[http://meego.com/users/poussa Sakari Poussa]''', Core OS Architect, responsible for Core OS architecture
* '''[http://meego.com/users/mythi Mikko Ylinen]''', Handset UX Architect, responsible for Handset UX architecture
* '''[http://meego.com/users/sunilsaxena Sunil Saxena]''', Core OS Architect, responsible for Core OS architecture

== Communication ==

* MeeGo architecture mailing list ([http://lists.meego.com/listinfo/meego-architecture link])

== 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 ([[http://developer.meego.com]]), to be published soon
* Architecture Documentation: High level architecture pictures and description ([[http://meego.com/developers/meego-architecture]]), to be updated soon
* Developer and Subsystem Documentation: Detailed technical description of each MeeGo subsystem. Guidelines for developers working on MeeGo. ([[http://wiki.meego.com/Architecture/Documentation]])

== Meetings ==

* [[Architecture/Meetings]] - Meetings - agenda, minutes

== Upcoming Features ==
MeeGo can benefit with contribution of technologies and features that are needed for MeeGo devices. Some of the technologies and features under consideration are:

* New APIs in QtMobility 1.2 – Camera, Document Gallery, Feedback, Organizer, Maps and Navigation, Service FW, Bluetooth, NFC.
* MCE - MCE provides activity monitoring and notifications via D-Bus, controls display and backlight, ALS reading and display tuning, airplane mode. Need to ensure we have APIs to handle screen backlight/ALS and how it can be done as the property of the window (per application) with accounting of application is in foreground and background.
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling using MCE.
* Sharing Framework – Architecture team is interested in seeing unified APIs for sharing files via BT, email, web services.

== Tools ==

Architecture tools

* Architecture navigation tool - able to browse meego packages and visually see the dependencies (coming in Nov)

Architecture

2010-10-28T09:35:32Z

Sunilsaxena:

== 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 ==

* '''[http://meego.com/users/arjan Arjan van de Ven]''', Chief Architect, responsible for MeeGo architecture
* '''[http://meego.com/users/poussa Sakari Poussa]''', Core OS Architect, responsible for Core OS architecture
* '''[http://meego.com/users/mythi Mikko Ylinen]''', Handset UX Architect, responsible for Handset UX architecture
* '''[http://meego.com/users/sunilsaxena Sunil Saxena]''', Core OS Architect, responsible for Core OS architecture

== Communication ==

* MeeGo architecture mailing list ([http://lists.meego.com/listinfo/meego-architecture link])

== 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 ([[http://developer.meego.com]]), to be published soon
* Architecture Documentation: High level architecture pictures and description ([[http://meego.com/architecture]]), to be updated 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

== Upcoming Features ==
MeeGo can benefit with contribution of technologies and features that are needed for MeeGo devices. Some of the technologies and features under consideration are:

* New APIs in QtMobility 1.2 – Camera, Document Gallery, Feedback, Organizer, Maps and Navigation, Service FW, Bluetooth, NFC.
* MCE - MCE provides activity monitoring and notifications via D-Bus, controls display and backlight, ALS reading and display tuning, airplane mode. Need to ensure we have APIs to handle screen backlight/ALS and how it can be done as the property of the window (per application) with accounting of application is in foreground and background.
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling using MCE.
* Sharing Framework – Architecture team is interested in seeing unified APIs for sharing files via BT, email, web services.

== Tools ==

Architecture tools

* Architecture navigation tool - able to browse meego packages and visually see the dependencies (coming in Nov)

Architecture

2010-10-27T15:25:57Z

Sunilsaxena:

== 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 ==

* '''[http://meego.com/users/arjan Arjan van de Ven]''', Chief Architect, responsible for MeeGo architecture
* '''[http://meego.com/users/poussa Sakari Poussa]''', Core OS Architect, responsible for Core OS architecture
* '''[http://meego.com/users/mythi Mikko Ylinen]''', Handset UX Architect, responsible for Handset UX architecture
* '''[http://meego.com/users/sunilsaxena Sunil Saxena]''', Core OS Architect, responsible for Core OS architecture

== Communication ==

* MeeGo architecture mailing list ([http://lists.meego.com/listinfo/meego-architecture link])

== 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 ([[http://developer.meego.com]]), to be published soon
* Architecture Documentation: High level architecture pictures and description ([[http://meego.com/architecture]]), to be updated 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

== Upcoming Features ==
MeeGo can benefit with contribution of technologies and features that are needed for MeeGo devices. Some of the technologies and features under consideration are:

* New APIs in QtMobility 1.2 – Camera, Document Gallery, Feedback, Organizer, Maps and Navigation, Service FW, Bluetooth, NFC.
* MCE - MCE provides activity monitoring and notifications via D-Bus, controls display and backlight, ALS reading and display tuning, airplane mode. Need to ensure we have APIs to handle screen backlight/ALS and how it can be done as the property of the window (per application) with accounting of application is in foreground and background.
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling using MCE.
* Sharing Framework – Architecture team is interested in seeing unified APIs for sharing files via BT, email, web services.

Architecture

2010-10-27T12:18:56Z

Sunilsaxena: /* Upcoming Features */

== 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 ==

* '''[http://meego.com/users/arjan Arjan van de Ven]''', Chief Architect, responsible for MeeGo architecture
* '''[http://meego.com/users/poussa Sakari Poussa]''', Core OS Architect, responsible for Core OS architecture
* '''[http://meego.com/users/mythi Mikko Ylinen]''', Handset UX Architect, responsible for Handset UX architecture
* '''[http://meego.com/users/sunilsaxena Sunil Saxena]''', Core OS Architect, responsible for Core OS architecture

== Communication ==

* MeeGo architecture mailing list ([http://lists.meego.com/listinfo/meego-architecture link])

== Process ==

== Documentation ==

* Developer Documentation: APIs, tutorials, videos, examples ([[http://developer.meego.com]]), to be published soon
* Architecture Documentation: High level architecture pictures and description ([[http://meego.com/architecture]]), to be updated 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

== Upcoming Features ==
MeeGo can benefit with contribution of technologies and features that are needed for MeeGo devices. Some of the technologies and features under consideration are:

* New APIs in QtMobility 1.2 – Camera, Document Gallery, Feedback, Organizer, Maps and Navigation, Service FW, BlueTooth, NFC.
* MCE - MCE provides activity monitoring and notifications via D-Bus, controls display and backlight, ALS reading and display tuning, airplane mode. Need to ensure we have APIs to handle screen backlight/ALS and how it can be done as the property of the window (per application) with accounting of application is in foreground and background.
* System APIs – we have gaps for time settings and alarms using timed, profiles using profiled, screen/backlight handling using MCE.
* Sharing Framework – Architecture team is interested in seeing unified APIs for sharing files via BT, email, web services.

== Tools ==

Architecture

2010-10-27T11:56:42Z

Sunilsaxena: /* Team */

Architecture/Meetings

2010-10-27T10:50:23Z

Sunilsaxena: /* Meetings */

Architecture

2010-10-27T10:38:07Z

Sunilsaxena: /* Meetings */

Architecture

2010-10-27T10:36:28Z

Sunilsaxena: /* Status */