Firefox OS Guidelines For Partners

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.

Product related topics

• Logo guideline for Firefox OS.

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 bug 881431)
  • To make those crash reports useful, you also need to 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).
  • 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.

How to debug?

• Debugging:
  • Debugging guideline
  • Debugging Open GL
  • 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. Here you will know how to upload symbols to Mozilla symbol server.

How to contribute?

• How to submit a patch

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?

• Tips for Partner 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?

• Testing Firefox OS.

• Tips and Tricks

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.

Certification Process

To avoid any last minute respins of final builds, we request our partners to make sure the following checklists are covered as a part of certification during IOTs so that failed items can be resolved timely.

• Checklist to be verified by Partner during IOT cycles
• Checklist to be verified by Partner & Mozilla during IOT cycles (This checklist may need collaboration with Mozilla on a few items)
  • Above checklist's serve as "Template" only. For certifying, TAM's/Mozilla Release Management/Partners are expected to make a copy of this before starting the verification

• Please submit the completed checklist to a Mozilla TAM you are working with so we can confirm the results or resolve pending issues/concerns
  
• If any of the items on the checklist do not pass, please raise a bug and needsinfo a Team Contact and release-mgmt@mozilla.com on Mozilla side to get immediate attention.