Difference between revisions of "Loop"
(→Documentation) |
(→Documentation) |
||
Line 57: | Line 57: | ||
* [[Loop/Architecture]] - Technical documentation of overall system | * [[Loop/Architecture]] - Technical documentation of overall system | ||
* [[Loop/Architecture/MVP]] | * [[Loop/Architecture/MVP]] | ||
+ | * [[Loop/Desktop & Standalon/Code Style & Structure]] | ||
* [[Loop/Data Collection]] - Information to collect about the functioning of the system | * [[Loop/Data Collection]] - Information to collect about the functioning of the system | ||
* [[Loop/UX]] - Documentation of targeted User Experience | * [[Loop/UX]] - Documentation of targeted User Experience |
Revision as of 17:12, 3 November 2014
Contents
Overview
At a high-level, the Loop project aims to create a user-visible real-time communications service for existing Mozilla products. This initially includes two major user-facing components: a Desktop portion, integrated with Firefox Desktop; and a Firefox OS Application intended to be used with Firefox OS 2.0 and later.
A good starting point for roughly understanding the user-facing behavior of these components is that the Desktop behavior will be roughly like "Skype, but integrated into the browser;", while the Mobile behavior will be roughly like "Facetime for Firefox OS Devices."
On Desktop, users will have an address book that can be used to initiate calls to other Firefox users, as well as to receive calls based on email identifiers. Video windows can be docked in front of the current tab, or "popped out" into their own window. In both cases, the call can continue while users change tabs and navigate around the web.
On Firefox OS, the client will use the built-in address book for contact information, and will allow initiating calls to other users as well as to receive calls based on mobile phone numbers.
In terms of project deliveries, the Loop project is using an incremental approach of delivering a minimal initial product consisting of simple voice and video communications. Additional features will be prioritized and added after the initial version is headed towards release, and as we gain more experience with what is most likely to provide the greatest value to our users.
A more complete list of the features planned for the "Minimum Viable Product" (MVP) release can be found in the MVP feature list / User Stories document.
Try Loop
Bug List
- Bugs are filed in the "Loop" product in Bugzilla.
- Bug list and burndown chart for FF 33
- MVP ("Minimum Viable Product")
57 Total; 1 Open (1.75%); 0 Resolved (0%); 56 Verified (98.25%);
Core Team
- Maire Reavy - Engineering Manager
- Romain Testard - Product Manager
- Jorge Munuera - FxOS Product Manager
- Rafael Rebolleda - FxOS UX Lead
- Adam Roach - Technical Architecture Lead
- Shell Escalante - Engineering Program Manager
- Mark Banner - Engineering / Implementation
- Dan Mosedale - Engineering / Implementation
- Nicolas Perriault - Engineering / Implementation
- Alexis Metaireau - Engineering / Implementation
- Romain Gauthier - Engineering / Implementation
- Remy Hubscher - Engineering / Implementation
- Darrin Henein - UX Lead
- María Ángeles Oteo - FxOS Engineering Manager
- Fernando Jiménez - FxOS Engineering
- Borja Salguero - FxOS Engineering
- Jose A. Olivera - FxOS Engineering
- Anthony Hughes - QA Lead
Documentation
- Loop/Architecture - Technical documentation of overall system
- Loop/Architecture/MVP
- Loop/Desktop & Standalon/Code Style & Structure
- Loop/Data Collection - Information to collect about the functioning of the system
- Loop/UX - Documentation of targeted User Experience
- Loop/QA - Documentation of the testing strategy
- Loop/Logging - What we need to know in case of failure to make calls.
- Loop/Load Handling - Our plan for managing initial server load
- Loop server API - Documentation of the REST API used by the Loop server
- Loop/OAuth Setup - Information about adding OAuth client credentials to Firefox
[tbd -- other artifacts as they become available]
Standing Meetings
- Watch dev-media for information.
Project Checklist
Communication Channels
- IRC: #loop on irc.mozilla.org (Use #media on irc.mozilla.org for WebRTC discussion)
- dev-media Discussion List