Firefox OS Guidelines For Partners: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(16 intermediate revisions by 4 users not shown)
Line 6: Line 6:
*** to join Firefox OS [https://wiki.mozilla.org/B2G#Meetings meetings.]
*** to join Firefox OS [https://wiki.mozilla.org/B2G#Meetings meetings.]
** to [https://wiki.mozilla.org/B2G/Hacking contribute to Firefox OS.]
** to [https://wiki.mozilla.org/B2G/Hacking contribute to Firefox OS.]
=Product related topics=
* [http://www.mozilla.org/en-US/styleguide/identity/firefoxos/branding/ Logo guideline for Firefox OS.]
=Engineering topics=
=Engineering topics=
==Overview==
==Overview==
Line 15: Line 13:
** Here you will see what can be customized and how to do it.
** Here you will see what can be customized and how to do it.
* Build Configuration/Settings :
* Build Configuration/Settings :
**  If you are generating your own builds,you must have MOZILLA_OFFICIAL=1 set in the environment while building to get the crash reporter enabled at run time. Having crash reporter enabled will us fix any instability issues and is an absolute blocker bug if not enabled for final production partner build. (see {{bug|881431}})
**  If you are generating your own builds,you must have MOZILLA_OFFICIAL=1 set in the environment while building to get the crash reporter enabled at run time. Having crash reporter enabled will us fix any instability issues and is an absolute blocker bug if not enabled for final production partner build. (see [https://developer.mozilla.org/en-US/docs/Crash_Reporting_Guide_for_Firefox_OS_Partners#Enable_Firefox_OS_Crash_Reporting Crash Reporting Guide for Firefox OS Partners])
** To make those crash reports useful, you also need to [https://developer.mozilla.org/en-US/docs/Uploading_symbols_to_Mozillas_symbol_server upload build symbols to our servers].
** To make those crash reports useful, you also need to [https://developer.mozilla.org/en-US/docs/Uploading_symbols_to_Mozillas_symbol_server upload build symbols to our servers].
** For release builds, the release channel should be set to release-<vendor>, e.g. release-zte, depending on the vendor that generates builds. Note that this is the same as update channel. If different (gecko) binaries are created for different regions, the region should be appended as well, e.g. release-zte-spain (or similar, the important point is release-<something> for release builds and different channel names for individual builds that could be on the same device).
** In addition, to make crash statistics work correctly, you need to set a useful release channel, see [https://developer.mozilla.org/en-US/docs/Crash_Reporting_Guide_for_Firefox_OS_Partners#Release_Channels Crash Reporting Guide for Firefox OS Partners].
** For preview/pre-release/pre-certification builds, set the release channel to "nightly" on unstable of "beta" on stable branches, and in case there's changes to binary code outside kernel/driver space, also add the vendor suffix, i.e. nightly-<vendor> or beta-<vendor>, following the release build model, in this case.
 
==Crash Reporting Guide for Firefox OS Partners==
* [https://developer.mozilla.org/en-US/docs/Crash_Reporting_Guide_for_Firefox_OS_Partners Crash Reporting Guidelines]


==How to debug?==
==How to debug?==
Line 40: Line 40:
* [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Media_queries?redirectlocale=en-US&redirectslug=CSS%2FMedia_queries Media query] consists of a media type and at least one expression that limits the style sheets' scope by using media features, such as width, height, and color. Media queries, added in CSS3, let the presentation of content be tailored to a specific range of output devices without having to change the content itself.
* [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Media_queries?redirectlocale=en-US&redirectslug=CSS%2FMedia_queries Media query] consists of a media type and at least one expression that limits the style sheets' scope by using media features, such as width, height, and color. Media queries, added in CSS3, let the presentation of content be tailored to a specific range of output devices without having to change the content itself.
* [https://wiki.mozilla.org/WebAPI/WebPayment Moz-Pay API]: The goal of this API is to enable web content to collect payment (or issue a refund) for a virtual good via the navigator.mozPay() function.
* [https://wiki.mozilla.org/WebAPI/WebPayment Moz-Pay API]: The goal of this API is to enable web content to collect payment (or issue a refund) for a virtual good via the navigator.mozPay() function.
* [http://buildingfirefoxos.com/ Building Firefox OS app]: Start creating your own apps.


==How to bug triage?==
==How to bug triage?==
* [[B2G/PartnerTriage | Tips for Partner Triage]]
* [[B2G/PartnerTriage | Tips for Partner Triage]]
==User Agent==
* [https://wiki.mozilla.org/B2G/User_Agent/Partner_Changes_Policy Partner Changes Policy page] contains detailed information about the policies for user agent. Mozilla partner organizations that make use of Mozilla branding must not modify the Mozilla-specified Firefox OS User-Agent string ("UA") or add/modify headers that have a similar effect (e.g. Device-Stock-UA, UAProf, X-Original-User-Agent, X-Device-User-Agent or X-OperaMini-Phone-UA).


=QA testing=
=QA testing=
Line 52: Line 56:
==How to submit bugs to us?==
==How to submit bugs to us?==
* [https://wiki.mozilla.org/B2G/QA/Bugzilla#Template Here is the template] to submit a bug to Bugzilla. Please follow this template and submit bugs on [https://bugzilla.mozilla.org/ Mozilla's Bugzilla system]. Or partners can also submit bugs in [https://bugzilla.mozilla.org/form.b2g.partner this page].
* [https://wiki.mozilla.org/B2G/QA/Bugzilla#Template Here is the template] to submit a bug to Bugzilla. Please follow this template and submit bugs on [https://bugzilla.mozilla.org/ Mozilla's Bugzilla system]. Or partners can also submit bugs in [https://bugzilla.mozilla.org/form.b2g.partner this page].
=Certification Process=
=Firefox OS Certification Process=
To avoid any last minute respins of final builds that are TA accepted, we request our partners to make sure the following checklist are covered as a part of certification process.
To avoid any last minute rework, Mozilla has developed the Firefox OS Partner Certification Process [https://wiki.mozilla.org/Firefox_OS_Partner_Certification_Process#Overview-_Firefox_Inside_Branding_Level (PCP)].
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AqkijnluCiEsdFNhc0YtVXo3X0d0a1RTVHJfV3g0alE#gid=0 Checklist to be verified by Partner during IOT cycles]
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AqkijnluCiEsdElKSno3RUhKY3RiV1U1djRVOTNHQ0E#gid=0 Checklist to be verified by Mozilla during IOT cycles]  
** Please note,as of now both these checklist require you to have logged in with your @mozilla.com to be able to view/edit. You are free to share the document link to partners for them to start editing.

Latest revision as of 05:12, 7 February 2014

How to get started?

Engineering topics

Overview

Crash Reporting Guide for Firefox OS Partners

How to debug?

How to contribute?

How to write an app?

How to bug triage?

User Agent

  • Partner Changes Policy page contains detailed information about the policies for user agent. Mozilla partner organizations that make use of Mozilla branding must not modify the Mozilla-specified Firefox OS User-Agent string ("UA") or add/modify headers that have a similar effect (e.g. Device-Stock-UA, UAProf, X-Original-User-Agent, X-Device-User-Agent or X-OperaMini-Phone-UA).

QA testing

How to test Firefox OS?

How to submit bugs to us?

Firefox OS Certification Process

To avoid any last minute rework, Mozilla has developed the Firefox OS Partner Certification Process (PCP).

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox_OS_Guidelines_For_Partners&oldid=919472"