Firefox OS Guidelines For Partners: Difference between revisions
Jump to navigation
Jump to search
Karen ward (talk | contribs) |
Karen ward (talk | contribs) |
||
| (5 intermediate revisions by 3 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.] | ||
=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 | ** 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]. | ||
** | ** 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?== | ==How to debug?== | ||
| Line 56: | 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 | 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)]. | ||
Latest revision as of 05:12, 7 February 2014
How to get started?
- It depends on what you would like to involve:
- to discuss or have more communication with Firefox OS team. We suggest you to talk with us:
- to talk with us via IRC.
- to subscribe mailing lists.
- to join Firefox OS meetings.
- to contribute to Firefox OS.
- to discuss or have more communication with Firefox OS team. We suggest you to talk with us:
Engineering topics
Overview
- Overview of architecture.
- All information about Firefox OS platform.
- 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 Crash Reporting Guide for Firefox OS Partners)
- To make those crash reports useful, you also need to upload build symbols to our servers.
- In addition, to make crash statistics work correctly, you need to set a useful release channel, see Crash Reporting Guide for Firefox OS Partners.
Crash Reporting Guide for Firefox OS Partners
How to debug?
- Debugging:
- 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. Here you will know how to upload symbols to Mozilla symbol server.
How to contribute?
How to write an app?
- Writing a web app for Firefox OS
- The guideline to develop HTML 5 Web Apps for an open marketplace
- A quick start to write a hosted app.
- Here you will know how to run the Firefox OS simulator.
- Here you can validate your app either in hosted app or package app.
- Updating apps including hosted apps and package apps.
- 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.
- 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.
- Building Firefox OS app: Start creating your own apps.
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?
- Here is the template to submit a bug to Bugzilla. Please follow this template and submit bugs on Mozilla's Bugzilla system. Or partners can also submit bugs in this page.
Firefox OS Certification Process
To avoid any last minute rework, Mozilla has developed the Firefox OS Partner Certification Process (PCP).