Add-ons/InternalSigning: Difference between revisions

No edit summary
(→‎Can I get access to this?: updated contacts)
 
(3 intermediate revisions by 3 users not shown)
Line 13: Line 13:


This is also used for Firefox features or experiments that want to distinguish themselves from other add-ons in some way. It's planning on being used by the following programs within Mozilla: Test Pilot, Dev Tools, Release Engineering and Shield Studies.
This is also used for Firefox features or experiments that want to distinguish themselves from other add-ons in some way. It's planning on being used by the following programs within Mozilla: Test Pilot, Dev Tools, Release Engineering and Shield Studies.
This can also be used to grant a WebExtension access to APIs that we can't (or just aren't yet ready to) expose to all WebExtensions.  To use this capability, a WebExtension API is placed behind the "mozillaAddons" permission.  A WebExtension that declares this permission in its manifest will only be granted that permission if it is signed using the process outlined in this document.


== Can I get access to this? ==
== Can I get access to this? ==
Line 31: Line 33:
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|Amy Tsay, Andreas Bovens, Philipp Kewisch, and Jim Mathies]].
1,698

edits