Add-ons/InternalSigning: Difference between revisions

(Created page with "The document on Add-ons in Firefox 57 outlines a series of extensions called "Signed by Mozilla internally". These are add-ons that are signed using a i...")
 
Line 20: Line 20:
* Conform to Mozilla security, privacy and data collection policies.
* Conform to Mozilla security, privacy and data collection policies.
* If the add-on is not a WebExtension, or has non-WebExtension parts it must:
* If the add-on is not a WebExtension, or has non-WebExtension parts it must:
** Use APIs that '''will not''' be implemented in WebExtensions or
** Use APIs that '''will not''' be implemented in WebExtensions or have a roadmap to implementing the WebExtensions APIs.
** Have a roadmap to implementing the WebExtensions APIs and
** And understanding that regressions, bugs and issues will occur regularly. These are outside of WebExtensions are not the add-ons team responsibility.
** And understanding that regressions, bugs and issues will occur regularly. These are outside of WebExtensions are not the add-ons team responsibility.


If any of those conditions change (for example the project is disbanded) then signing access will be withdrawn.
If any of those conditions change (for example the project is disbanded) then signing access will be withdrawn.


If you'd like to request this for your add-on, then please contact [[/Add-ons#Who|Andy McKay or Kev Needham]].
If you'd like to request this for your add-on, then please contact [[Add-ons#Who|Andy McKay or Kev Needham]].
Confirmed users
1,158

edits