This is an overview about add-ons. * Have you seen any questions about add-ons lately? * Did the question owner not find a support site listed for an add-on? * Perhaps they just need an add-on to help improve their experience. Nonetheless there are going to be some questions about these. This background information about add-ons can be useful to a new or advanced contributor. __TOC__ = Suggesting an add-on = When suggesting an add-on, pay particular attention to the platform and operating system version you search for at [addons.mozilla.org]. [[Image:"Add on Page of Mozilla Firefox RC 2"]] = How to become an add-on developer = # First create an account on the add-on page [https://addons.mozilla.org/firefox/users/register Register Here] # Upload [https://addons.mozilla.org/firefox/users/login?to=/developers/addon/submit/1] # Then wait for a group of reviewers to test the add-on. The two levels of passing tests for add-ons are as follows: # Preliminary quailification is passing the security stage, but not quality # Full qualification is passing all stages. = Who reviews updates = Updates are reviewed. There are number of volunteers and contractors who test updates. = The review process = In any new versions of Firefox there are a series of checks that happen in each update before they are approved for compatibility in the new version. = What happens when they are all passed = Fully reviewed add-ons are the ones that are featured. Preliminary add-ons are a different color if they have not completed the process. = For support issues with add-ons = *First suggest that they try [[Troubleshoot Firefox issues using Safe Mode|Safe Mode]]. *Please ask the user to contact the developers because they know most of the issues with an add-on. The user will see support links that they can use to contact them. * Or, if there are any preliminary questions, visit the irc channel #amo-editors * Supporting developers: developer.mozilla.com/ add-on section has everything you will need. * Report abuse button if the add-on becomes malicious or causes issues with the performance of Firefox. *To check to see if an add-on has passed or if the development of the add-on has stopped, there will be a greyed-out icon for the add-on or they will no longer be searchable. = Filing bugs for add-ons = If there is an issue and you need to file a bug for blocking Use the component - add-on and refer to these guidelines: block request: [https://wiki.mozilla.org/Blocklisting Blocklisting] and provide as much information as possible. [https://developer.mozilla.org/Add-ons/Add-on_guidelines Please follow these guidelines when filing a bug.] = Advanced contributor challenge questions = *Have you ever had malware in an add-on before, do you know what this looks like? *What troubleshooting information is needed to show unusual behavior? * What would you recommend to an add-on developer having trouble uploading their new add-on? *Who would you contact if the user was having trouble with the approval process? An excellent example of plugin troubleshooting: [/questions/985421 Example Question]

This is an overview about add-ons.

• Have you seen any questions about add-ons lately?
• Did the question owner not find a support site listed for an add-on?
• Perhaps they just need an add-on to help improve their experience.

Nonetheless there are going to be some questions about these. This background information about add-ons can be useful to a new or advanced contributor.

Suggesting an add-on

When suggesting an add-on, pay particular attention to the platform and operating system version you search for at [addons.mozilla.org].

How to become an add-on developer

1. First create an account on the add-on page Register Here
2. Upload https://addons.mozilla.org/firefox/us.../1
3. Then wait for a group of reviewers to test the add-on.

The two levels of passing tests for add-ons are as follows:

1. Preliminary quailification is passing the security stage, but not quality
2. Full qualification is passing all stages.

Who reviews updates

Updates are reviewed. There are number of volunteers and contractors who test updates.

The review process

In any new versions of Firefox there are a series of checks that happen in each update before they are approved for compatibility in the new version.

What happens when they are all passed

Fully reviewed add-ons are the ones that are featured. Preliminary add-ons are a different color if they have not completed the process.

For support issues with add-ons

• First suggest that they try Safe Mode.
• Please ask the user to contact the developers because they know most of the issues with an add-on. The user will see support links that they can use to contact them.
• Or, if there are any preliminary questions, visit the irc channel #amo-editors
• Supporting developers: developer.mozilla.com/ add-on section has everything you will need.
• Report abuse button if the add-on becomes malicious or causes issues with the performance of Firefox.
• To check to see if an add-on has passed or if the development of the add-on has stopped, there will be a greyed-out icon for the add-on or they will no longer be searchable.

Filing bugs for add-ons

If there is an issue and you need to file a bug for blocking Use the component - add-on and refer to these guidelines: block request: Blocklisting and provide as much information as possible.

Please follow these guidelines when filing a bug.

Advanced contributor challenge questions

• Have you ever had malware in an add-on before, do you know what this looks like?
• What troubleshooting information is needed to show unusual behavior?
• What would you recommend to an add-on developer having trouble uploading their new add-on?
• Who would you contact if the user was having trouble with the approval process?

An excellent example of plugin troubleshooting: Example Question