Gaia/SMS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Updated etherpad links)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Development Team ==
== Development Team ==
You'll be able to find the current team [[Modules/FirefoxOS#Message|on the Firefox OS modules page]].
You'll be able to find the current team [[Modules/FirefoxOS#Messages|on the Firefox OS modules page]].


The SMS team is part of the larger [[FirefoxOS/Comms|Comms team]].
The SMS team is part of the larger [[FirefoxOS/Comms|Comms team]].


== Design Specs ==
== Design Specs ==
=== Panels-specific spec ===
==== Conversation View ====
* https://bug1087933.bmoattachments.org/attachment.cgi?id=8533556
==== Report Panel ====
* top part: https://bug1202061.bmoattachments.org/attachment.cgi?id=8661096
=== Versions specific specs ===
For 2.1, 2.2 and 3.0 we had no visual refresh so we have no visual design specifications. The specifications for the Right To Left work are common to all apps and [https://mozilla.app.box.com/s/bcm3s5i2v6js5uk0ws3tsywse8bgncgo can be found on box.com] ([https://bug906270.bugzilla.mozilla.org/attachment.cgi?id=8629248 mirror on bugzilla]).
For 2.0, the Visual Refresh specifications are on [http://bugzil.la/950175 bug 950175].
For 2.0, the Visual Refresh specifications are on [http://bugzil.la/950175 bug 950175].


Line 16: Line 25:
The following link contains the specifications for versions 1.0, 1.1 and 1.2:
The following link contains the specifications for versions 1.0, 1.1 and 1.2:
https://mozilla.box.com/applications/1/864518430.
https://mozilla.box.com/applications/1/864518430.
Mirror for the UX spec for version 1.3: [[File:FFOS_MessageApp_V1.3_20131125_V8.0.pdf]].<br>
Mirror for the UX spec for versions 1.1 and 1.2: [[File:HTML5_SMS-MMSUserStorySpecifications_20130503_V8.0.pdf]]. This spec is still the authoritative one for anything that has not been redesigned.<br>
Mirror for the UX spec for version 1.0: [[File:HTML5 SMS 20121212 R2S1 V8.0.pdf]]


== Source Code ==
== Source Code ==
Line 21: Line 34:


== IRC ==
== IRC ==
You can find us on the IRC server irc.mozilla.org, channel #gaia-messaging.
You can find us on the IRC server irc.mozilla.org, channels #gaia and #gaia-messaging.


== Code Style Guidelines ==
== Code Style Guidelines ==
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style Mozilla's Code Style Guidelines]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style Mozilla's Code Style Guidelines]


* [https://etherpad.mozilla.org/sms-code-style-guidelines Ongoing SMS Team specifc Code Style Guidelines]
* [https://public.etherpad-mozilla.org/p/sms-code-style-guidelines Ongoing SMS Team specifc Code Style Guidelines]


== Filing bugs ==
== Filing bugs ==
You can file bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20OS&component=Gaia%3A%3ASMS on Bugzilla]. Please include the Firefox OS version you use, and possibly a screenshot or a video.
You can file bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20OS&component=Gaia%3A%3ASMS on Bugzilla]. Please include the Firefox OS version you use, and possibly a screenshot or a video. Any console from logcat is welcome as well, or you could provide your message sqlite from your device by retrieving the following file & directory(if you don't mind the content):
* /data/local/storage/permanent/chrome/idb/226660312ssm.sqlite
* /data/local/storage/permanent/chrome/idb/226660312ssm.files


== Handling bugs ==
== Handling bugs ==
[[Image:Sms-bug-handling-flow.svg|center|thumb|200px|Sms Bug Handling Flow]]
<imagemap>
[[File:Sms-bug-handling-flow-source.odg|Source]]
Image:Gaia_SMS_Handling_Bugs_digraph_handling_bugs_dot.svg|right|thumb|200px|[[Gaia/SMS/Handling_Bugs|Sms Bug Handling Flow]]
default [[Gaia/SMS/Handling_Bugs]]
</imagemap>
 
See [[Gaia/SMS/Handling_Bugs]].
 
There are 2 goals:
* making the bug move forward thanks to other people until it's actionable.
* not forgetting an important bug
 
With this flow, we still need to be careful to:
* assigned bugs without activity
* needinfo that are not answered
 
Indeed these bugs could still be forgotten if they don't move.


== Project Management ==
== Project Management ==
Line 40: Line 69:
== Some future development ==
== Some future development ==
=== Using datastores for SMS ===
=== Using datastores for SMS ===
* [https://etherpad.mozilla.org/messages-datastore Etherpad]
* [https://public.etherpad-mozilla.org/p/messages-datastore Etherpad]


=== Haida and Sheets ===
=== Haida and Sheets ===
* [https://etherpad.mozilla.org/sms-haida Etherpad]
* [https://public.etherpad-mozilla.org/p/sms-haida Etherpad]


=== Feature backlog ===
=== Feature backlog ===
* [https://etherpad.mozilla.org/sms-feature-backlog Etherpad]
* [https://public.etherpad-mozilla.org/p/sms-feature-backlog Etherpad]
 
=== New Gaia architecture ===
* [https://wiki.mozilla.org/Gaia/Architecture_Proposal New Gaia Architecture Proposal]
* [https://github.com/gaia-components/threads Bridge library repo]


== The Gecko API for Mobile Messaging ==
== The Gecko API for Mobile Messaging ==

Latest revision as of 08:16, 8 October 2015

Development Team

You'll be able to find the current team on the Firefox OS modules page.

The SMS team is part of the larger Comms team.

Design Specs

Panels-specific spec

Conversation View

Report Panel

Versions specific specs

For 2.1, 2.2 and 3.0 we had no visual refresh so we have no visual design specifications. The specifications for the Right To Left work are common to all apps and can be found on box.com (mirror on bugzilla).

For 2.0, the Visual Refresh specifications are on bug 950175.

For 1.4, please visit :

For 1.3, please visit https://mozilla.app.box.com/shared/0u4jt353ei9ov2c150ip/1/1170795225 (for the generic specs) and https://mozilla.app.box.com/shared/0u4jt353ei9ov2c150ip/1/1206603879 (for DSDS)

The following link contains the specifications for versions 1.0, 1.1 and 1.2: https://mozilla.box.com/applications/1/864518430.

Mirror for the UX spec for version 1.3: File:FFOS MessageApp V1.3 20131125 V8.0.pdf.
Mirror for the UX spec for versions 1.1 and 1.2: File:HTML5 SMS-MMSUserStorySpecifications 20130503 V8.0.pdf. This spec is still the authoritative one for anything that has not been redesigned.
Mirror for the UX spec for version 1.0: File:HTML5 SMS 20121212 R2S1 V8.0.pdf

Source Code

The source code can be found in the gaia repository in github.

IRC

You can find us on the IRC server irc.mozilla.org, channels #gaia and #gaia-messaging.

Code Style Guidelines

Filing bugs

You can file bug on Bugzilla. Please include the Firefox OS version you use, and possibly a screenshot or a video. Any console from logcat is welcome as well, or you could provide your message sqlite from your device by retrieving the following file & directory(if you don't mind the content):

  • /data/local/storage/permanent/chrome/idb/226660312ssm.sqlite
  • /data/local/storage/permanent/chrome/idb/226660312ssm.files

Handling bugs

See Gaia/SMS/Handling_Bugs.

There are 2 goals:

  • making the bug move forward thanks to other people until it's actionable.
  • not forgetting an important bug

With this flow, we still need to be careful to:

  • assigned bugs without activity
  • needinfo that are not answered

Indeed these bugs could still be forgotten if they don't move.

Project Management

We try to follow the Scrum methodology. Please have a look to the SMS Scrum Page for more information.

Some future development

Using datastores for SMS

Haida and Sheets

Feature backlog

New Gaia architecture

The Gecko API for Mobile Messaging

The SMS application uses several API from Gecko. Especially it uses the API for Mobile Messaging, which allows to send and receive SMS and MMS.

On this wiki, several pages show the design behind the API: WebAPI/WebSMS and WebAPI/WebMMS. They're probably somewhat obsolete noawadays but they will provide useful information about some design.

MDN has also a good documentation about this API. It's also lagging a bit but is more uptodate.

Finally, the most current information is given by the IDL files in the gecko tree (and some part is in a separate place).

Security Review

The security review for this app can be found here.