View source for Firefox OS Guidelines For Partners

=How to get started?=
* It depends on what you would like to involve: 
** to discuss or [https://wiki.mozilla.org/B2G/Hacking#Communication have more communication] with Firefox OS team. We suggest you to talk with us: 
*** to talk with us via [https://wiki.mozilla.org/B2G/Hacking#IRC IRC]. 
*** to [https://wiki.mozilla.org/B2G/Hacking#Mailinglist subscribe mailing lists].
*** to join Firefox OS [https://wiki.mozilla.org/B2G#Meetings meetings.]
** to [https://wiki.mozilla.org/B2G/Hacking contribute to Firefox OS.]
=Engineering topics=
==Overview==
* [https://wiki.mozilla.org/B2G/Architecture Overview of architecture.]
* [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Platform All information about Firefox OS platform.]
* [https://wiki.mozilla.org/B2G/MarketCustomizations Customization guidelines.]
** Here you will see what can be customized and how to do it.
* 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 [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].
** 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].

==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?==
* Debugging: 
** [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Debugging Debugging guideline]
** [https://wiki.mozilla.org/B2G/Debugging_OpenGL Debugging Open GL]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=847268 What information needs to be collected when devices are freeze]
* Debug symbols
** As a third-party releasing your own builds of Firefox or Firefox OS, you should consider uploading debug symbols from the builds to Mozilla's symbol server. [https://developer.mozilla.org/en-US/docs/Uploading_symbols_to_Mozillas_symbol_server Here you will know how to upload symbols to Mozilla symbol server].

==How to contribute?==
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch How to submit a patch]

==How to write an app?==
* [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Apps/Writing_a_web_app_for_Firefox_OS Writing a web app for Firefox OS]
* [https://marketplace.firefox.com/developers/ The guideline to develop HTML 5 Web Apps for an open marketplace]
** [https://marketplace.firefox.com/developers/docs/quick_start A quick start] to write a hosted app.
** [https://marketplace.firefox.com/developers/docs/firefox_os_simulator Here you will know how to run the Firefox OS simulator].
** [https://marketplace.firefox.com/developers/validator Here you can validate your app] either in hosted app or package app.
* [https://developer.mozilla.org/en-US/docs/Web/Apps/Updating_apps Updating apps] including hosted apps and package apps.
* [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.
* [http://buildingfirefoxos.com/ Building Firefox OS app]: Start creating your own apps.

==How to bug 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=
==How to test Firefox OS?==
* [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Platform/Testing Testing Firefox OS.]

* [https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks Tips and Tricks]

==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].
=Firefox OS 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)].