Gaia/New-Architecture-Program: Difference between revisions
mNo edit summary |
(→Status) |
||
| (12 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
= Program Overview = | = Program Overview = | ||
The new Gaia architecture (or | The new Gaia architecture (or, the next generation Gaia architecture) proposes a new Firefox OS application framework that aims to create a more webby Firefox OS application platform. | ||
The proposal is documented in https://wiki.mozilla.org/Gaia/Architecture_Proposal | The proposal is documented in https://wiki.mozilla.org/Gaia/Architecture_Proposal | ||
Each components of the architecture will be validated by applications | Each components of the architecture will be validated by converting applications to use these components. For example Music will be converted to have its front-end separated from its back-end with the app bridge being the protocol machine for the front- and back-ends. | ||
Initially two apps are chosen to be converted to evaluate the new architecture's APIs as well as to evaluate the "new" apps' performance and memory profiles. In the process of conversion we will also focus on the useability of the APIs for apps developers and | Initially two apps (Music and SMS) are chosen to be converted to the new architecture to evaluate the new architecture's APIs as well as to evaluate the "new" apps' performance and memory profiles. In the process of conversion we will also focus on the useability of the APIs for apps developers and Firefox OS apps development best practices based on the new architecture. | ||
More details on the the validation plan is here: https://wiki.mozilla.org/Gaia/Architecture_Transition_Validation | More details on the the validation plan is here: https://wiki.mozilla.org/Gaia/Architecture_Transition_Validation | ||
| Line 13: | Line 13: | ||
= Status = | = Status = | ||
Weekly program meeting notes: https://docs.google.com/a/mozilla.com/document/d/1Y6HJ0TEtr1KocNXiYhuO8u7KJQQzGGg20H-Ug9SELJY/edit?usp=sharing | |||
= Team Wiki's and detailed Team Status = | = Team Wiki's and detailed Team Status = | ||
* [[Gaia/SMS/Scrum/Milestone_Planning/1|SMS]] | |||
* [https://wiki.mozilla.org/FirefoxOS/media/music Music] | |||
* [https://wiki.mozilla.org/Gaia/New-Architecture-Program/Contacts Contacts] | |||
* [https://github.com/gaia-components/threads Web app bridge] | |||
* [https://wiki.mozilla.org/Gaia/Toolkit/Service_Worker Service worker] | |||
* [https://wiki.mozilla.org/Gaia/Metrics Telemetry] | |||
* [[Gaia/New-Architecture-Program/NavigationTransitions|Navigation]] | |||
* [[Firefox_OS_Data_Sync|Data sync]] | |||
= Contacts = | = Contacts = | ||
* EM: Francisco Jordano | * EM: Francisco Jordano | ||
* EPM: | * EPM: Maria Oteo | ||
Latest revision as of 19:17, 4 December 2015
Program Overview
The new Gaia architecture (or, the next generation Gaia architecture) proposes a new Firefox OS application framework that aims to create a more webby Firefox OS application platform.
The proposal is documented in https://wiki.mozilla.org/Gaia/Architecture_Proposal
Each components of the architecture will be validated by converting applications to use these components. For example Music will be converted to have its front-end separated from its back-end with the app bridge being the protocol machine for the front- and back-ends.
Initially two apps (Music and SMS) are chosen to be converted to the new architecture to evaluate the new architecture's APIs as well as to evaluate the "new" apps' performance and memory profiles. In the process of conversion we will also focus on the useability of the APIs for apps developers and Firefox OS apps development best practices based on the new architecture.
More details on the the validation plan is here: https://wiki.mozilla.org/Gaia/Architecture_Transition_Validation
Status
Weekly program meeting notes: https://docs.google.com/a/mozilla.com/document/d/1Y6HJ0TEtr1KocNXiYhuO8u7KJQQzGGg20H-Ug9SELJY/edit?usp=sharing
Team Wiki's and detailed Team Status
Contacts
- EM: Francisco Jordano
- EPM: Maria Oteo