Firefox OS Partner Certification Process: Difference between revisions
Jump to navigation
Jump to search
Karen ward (talk | contribs) (Created page with "=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 ...") |
Karen ward (talk | contribs) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= | == Overview- Co-Branded Branding Level == | ||
The purpose of the Partner Certification Process is to ensure quality and consistency across Firefox Inside Branded Devices. We do this by: | |||
* | * Ensuring that Mozilla Brand assets are being used by partners in an appropriate and consistent way for the branding level | ||
* | * Ensuring that the elements of the end user experience that define our brand are represented in the final product | ||
** | * Ensuring that the technical elements of the OS are not corrupted in the final product | ||
* To the degree possible, ensure that ancillary services that may be out of Mozilla's direct control but that reflect on the end user's experience and our brand are properly implemented (for example AGPS, OEM support services etc.) | |||
* Ensure working infrastructure for passive metric collections and the ability to provide timely support | |||
* | The specifics needed to meet these objectives are called out in the Mozilla Firefox OS Distribution Agreement. These specific elements and policies cannot be changed to produce Firefox Inside Branded devicea. | ||
* If any of the items on the | To assist with validating these key points and avoid any last minute rework, Mozilla has developed a 2 step process: | ||
* Short checklist items for OEM to complete prior to IOT #1 -[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AqkijnluCiEsdFNhc0YtVXo3X0d0a1RTVHJfV3g0alE#gid=0 IOT#1 PCP Submission Early Preview] | |||
** The info in this spreadsheet is provided as a self-check for the OEM. | |||
* More extensive spreadsheet with items for OEM to complete in parallel to final IOT. - [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AqkijnluCiEsdElKSno3RUhKY3RiV1U1djRVOTNHQ0E#gid=0 PCP Final Submission] | |||
** The info in this spreadsheet must be approved by Mozilla prior to the OEM manufacturing Firefox Inside branded devices. | |||
*** If any of the items on the submissions do not pass, please raise a bug and needsinfo a Mozilla Team Contact and release-mgmt@mozilla.com to get immediate attention. | |||
* The final pass/fail decision will be made by Mozilla adhering to tight deadlines supporting the OEMs timeline. In order to be in compliance with the Firefox OS Distribution Agreement Mozilla's approval is required prior to device manufacturing. | |||
* Please submit the completed checklist to the Mozilla Technical Account Manager (TAM) you are working with so we can confirm the results or resolve pending issues/concerns<br> | |||
=== API Reference Section === | |||
=== Security & Privacy Section === | |||
<i><b> Note: Although we are working to keep this a simple process, Mozilla reserves the right to update the requirements of the Partner Certification Process as new features are implemented. | |||
Latest revision as of 05:28, 12 June 2014
Overview- Co-Branded Branding Level
The purpose of the Partner Certification Process is to ensure quality and consistency across Firefox Inside Branded Devices. We do this by:
- Ensuring that Mozilla Brand assets are being used by partners in an appropriate and consistent way for the branding level
- Ensuring that the elements of the end user experience that define our brand are represented in the final product
- Ensuring that the technical elements of the OS are not corrupted in the final product
- To the degree possible, ensure that ancillary services that may be out of Mozilla's direct control but that reflect on the end user's experience and our brand are properly implemented (for example AGPS, OEM support services etc.)
- Ensure working infrastructure for passive metric collections and the ability to provide timely support
The specifics needed to meet these objectives are called out in the Mozilla Firefox OS Distribution Agreement. These specific elements and policies cannot be changed to produce Firefox Inside Branded devicea. To assist with validating these key points and avoid any last minute rework, Mozilla has developed a 2 step process:
- Short checklist items for OEM to complete prior to IOT #1 -IOT#1 PCP Submission Early Preview
- The info in this spreadsheet is provided as a self-check for the OEM.
- More extensive spreadsheet with items for OEM to complete in parallel to final IOT. - PCP Final Submission
- The info in this spreadsheet must be approved by Mozilla prior to the OEM manufacturing Firefox Inside branded devices.
- If any of the items on the submissions do not pass, please raise a bug and needsinfo a Mozilla Team Contact and release-mgmt@mozilla.com to get immediate attention.
- The info in this spreadsheet must be approved by Mozilla prior to the OEM manufacturing Firefox Inside branded devices.
- The final pass/fail decision will be made by Mozilla adhering to tight deadlines supporting the OEMs timeline. In order to be in compliance with the Firefox OS Distribution Agreement Mozilla's approval is required prior to device manufacturing.
- Please submit the completed checklist to the Mozilla Technical Account Manager (TAM) you are working with so we can confirm the results or resolve pending issues/concerns
API Reference Section
Security & Privacy Section
Note: Although we are working to keep this a simple process, Mozilla reserves the right to update the requirements of the Partner Certification Process as new features are implemented.